Sitemate Blog Post – On Sitemate’s Working Arrangements
SITEMATE BLOG POSTS
On Sitemate's Working Arrangements
This blog tells the story of how Sitemate’s current working arrangements came to be - including specific examples from over the years, each of which has influenced the way we now operate.
Our first remote team member
I remember when I was first faced with a decision to consider hiring someone fully remotely; it was very early in 2018, and we were at the end of a long and painful process that involved Sam and I 'breaking up' with an original third co-founder - we were in a very, very bad place as a company.
There was only five or six of us working full-time every day in the Sydney office, and we had an early production version of what is now Dashpivot up and running. However, our mobile app was horrendous; offline mode didn’t work, basic upload functionality didn’t work, and unfortunately we didn’t have the skills on the current team to fix any of it.
This single piece of our product offering was creating a risk of killing the entire company, and due to this happening on top of the ongoing founding team issues, as well as barely generating any revenue, confidence from our early investors was hanging on a knife edge - we were literally on the brink of death as a company.
I was introduced to Nick Lammertyn through a mutual connection - another founder who had been through the same accelerator program as us (Startmate).
Nick ticked all the boxes on paper - experience with backend, frontend and mobile, although, he made it very clear that he didn’t want to touch the front end… But, most importantly; Nick had just worked on another product that had a form/field data collection aspect, and even required seamless offline data capture.
There was just one problem… he was based in Vancouver, Canada!
This might sound ridiculous to you reading this now, given our current team size and structure globally, but at the time, I was immensely skeptical - likely a hangover from my experience working in the industry as an engineer, where ‘on site’ was the only working arrangement available.
Being a 'cool tech founder’ now (sarcasm intended) and no longer a construction engineer, I decided to ignore my concerns and take the meeting - which then happened over Skype (yes this was pre zoom days!), from my Mum’s house, in my bed (it was a ‘video off’ meeting), on a Saturday morning Sydney time, or Friday afternoon Vancouver time.
The meeting went very well, I described the pain points with our current mobile app to Nick, he described the user experience, particularly from an offline perspective, that he’d just developed and built with the other startup, and I was keen to progress to the next step in our robust ‘interview’ process - which involved me asking Nick; “Can I have a log in to the product you just built?”.
Nick spoke to the founder, sent me a set of credentials to login, and after a few hours of testing, I had… found a few ‘HP bug reports’ (Dashpivot eng and QA team can relate here…), but also confirmed that the user experience around offline mode usage was exactly what Sam and I had been dreaming of for the early version of Dashpivot’s mobile app.
As I was the only person occupying the Product Manager role (Sam was working on Product Design and Customer Success at the time), Nick and I paired up 1:1 over the next 12-18 months up to tear apart our old app and piece by piece, deliver the mobile experience that our early user base was asking for, and in turn, with this mobile work - we pulled the company back from the brink of death.
For me personally though, Nick proved that one’s working location didn’t always determine their ability to work hard (very hard in Nick’s case), communicate well, and deliver fantastic results - he opened my eyes to the possibilities, and I’ve never looked back.
Going from one to many
Heading into 2019 with a new perspective on what work and teams can be, as well as increasing demand on the go to market side with Lance now on board, and our mobile app now stable enough to support continuous customer growth, it hit me that we needed to grow the team!
Based on the success of Nick joining, I decided to open up for engineering roles both locally and globally… at which point we were flooded with applications to review from engineers all over the world.
It was this volume, along with having no budget for recruiters and no experience with recruiting, that triggered Khanh and I to decide built the original v1.0 of our heavily engineered recruitment process, albeit no where near as good as it is now, but that didn’t matter - it still worked, and over the next 12 months Ulan, Hudson and Yestay joined Sitemate as remote engineering team members.
As our engineering team was growing, and based on demand from the go to market side, was expected to keep growing, and growing - the board discussions around our need for a CTO bubbled towards top priority.
I first met Tim Bray in 2018, and actually pitched him to join back then, to which he declined as he wanted to start his own company.
Fast forward to late 2019, and unfortunately Tim and his co-founder had decided to shut down their startup due to challenges in the market. But, fortunately for Tim I “was actually going to be in Melbourne next week” (I wasn’t), so suggested that we should catch up for lunch (wink wink).
This time, after experiencing first hand the challenges of the early stage, and seeing how much progress we’d made at Sitemate, whilst also not quite having his itch for the startup journey ‘scratched’, it seemed like Tim was keen to join the team.
At which point, I was faced with another big decision around foundational team build out strategy - ‘ok sure, we can have some of the team remote, but could we really have our CTO and CEO not working in the same office?!’
The board was skeptical, even requesting that we bring Tim up to Sydney for some interviews… Needless to say, I had full conviction, Tim joined the team, and the rest is history!
The impact of Covid
Prior to covid, Sitemate was only around ten people full-time, and when covid hit, we had about five people working in the Sydney office, doing five days a week, every day in the office, and everyone else on the team was fully remote.
Due to having such a large portion of the company working fully remote day to day, albeit with only ten or so people in total, it allowed us to adapt to fully remote operations seamlessly - as the Sydney office (all five of us) just stayed home!
As we all know, covid sent a shock wave around the world, and from a business perspective - it was by far the most uncertain period that I’ve had to navigate.
But, through this challenging period, with nothing but uncertainty ahead of us - I learned what remote teams are truly capable of.
We’d been suffering with a deficient part of Dashpivot as a product since launch - where the Manual Signature field wasn’t getting used for large groups of workers to sign onto forms. Instead, users were signing people onto a piece of paper the old way, taking a photo of the signed piece of paper, and then attaching the photo at the bottom of the digital form on Dashpivot.
Sam and I had done some concept designs on a potential solution, where Dashpivot ‘remembered’ previous signatories, so that you didn’t need to type everyone’s name and company each day before using your finger to squiggle a signature on the screen, but we never had enough conviction to actually start building it.
I remember when covid hit, I sat there and thought - “our roadmap is out the window for now, what can we do to help our customers right now during this period?”
I kept thinking about the issues with passing around a piece of paper, and we thought that it might be worth looking at it again with a fresh set of eyes, and in the context of everything needing to be ‘contactless’ during covid.
I called the entire product and engineering team onto a zoom call - me, Sam, Tim, Nick, Ulan, Hudson and Yestay, and we brainstormed what could be done.
In less than two months, we went from the idea of ‘contactless scan and sign on’, to the new Scan Sitemate ID field, as well as a brand new mobile app, available for users.
Tim worked on the Sitemate Mobile App (built from scratch), Yestay worked on the Dashpivot Mobile App, Nick worked on the Sitemate API, Hudson worked on the Dashpivot API, Ulan worked on the Dashpivot web app, and even Khanh was involved - he load tested the scan and sign process to ensure it wouldn’t break, by mounting a tablet to his bed, and endlessly scanning a Sitemate user’s QR code!
From that point onward, Sitemate’s entire product strategy had shifted towards a focus on connecting both office and field management, as well as the individual workers - and the Sitemate App was often the differentiator that started winning us more and more customers during this period.
Reflecting a few months after this experience, my mindset shifted from having some members of our team as remote being ‘acceptable’, to ‘we need to find the best people globally, wherever they are’.
The second wave of remote success stories
I remember sitting down with Khanh towards the end of 2020 and explaining the vision I had for how we build our hybrid remote culture, and then discussing what we needed to do operationally to make sure this vision came to life.
It went something along the lines of;
“When someone joins Sitemate remotely, I don’t want them to feel like a second class citizen to the Sydney office, they shouldn’t have less access to information, just because they are remote.”
“Yes from a practical perspective they aren’t an Aus based employee, but that’s where I want the differences to end - I want them to get equity, I want them to get leave, and I want them to know everything about what’s going on.”
“If we do this, we’ll be able to widen the pool of possible people who will want to join the Sitemate team, and once they’re here, they will hopefully want to stay and grow with the company - because they will be treated well, listened to, and respected, regardless of where they are.”
What followed in 2021 was the start of the second wave of remote success stories.
I remember Matheus' first day - Alvaro and I nearly had an epileptic fit in his new starter channel on slack, because he was the first one to start using custom emojis, and it was as if he’d found the most colorful, exuberant pack of emojis, and just bulk imported all of them.
Matheus had just kick started our now crazy emoji culture, I remember feeling a little overwhelmed by his emojis, but couldn’t believe how much energy someone who’s remote had brought into the team. I don’t think any of us knew the can of worms he had just opened.

Emoji reactions to a #general Sitemate post
Matheus then brought into Sitemate (either directly or indirectly) PH, Julia and Gabi.
And in turn, Julia has since brought into Sitemate Renata and Victoria.
The above being said, building our team and culture has not been without challenges - there have been some office based, and remote team members that did not work out, although in most of these cases, it hasn’t been anything to do with whether they were in the office, or remote, but moreso general alignment.
It has been both the many positive and few negative experiences, that have helped shape not only our working arrangements, but our values and where we are today.
Defining our ‘new normal’
The post covid era has, in many cases, seen leaders over-correct and try to force people back into the office full-time, which I suspect is due to a combination of top down pressure due to economic headwind, and not having adequate systems, processes and operating principles in place to enable them (both their teams, and the leaders themselves!) to operate in an effective manner.
- The result in many companies now is that for office based staff you have chaotic and unproductive flexibility running rampant:
- People spend way too long coordinating and voting on which days to go to the office without actually knowing who’s decision it is.
- Some random person wakes up with energy as they haven’t been to the office in a month and shows up proactively to then only find no one else is there that day and that they should have stayed home.
- Introverts happily stay at home all week because there’s no forcing function to do otherwise, but then also start to feel a little lonely.
- Management, who are stuck in a state of terrified indecisiveness, see all of this noise spinning around and around, whilst also spending tens or hundreds of thousands of dollars on office space, get frustrated, and then send out a knee jerk policy change as a reaction - pissing everyone off because it’s out of the blue and not well thought through.
My goal is to avoid all of the above.
The best way I can describe Sitemate’s approach wasn’t actually described by me, it was described by Lara a few months after she joined, as “highly structured flexibility”. This is exactly the intent of our working arrangements.
I believe that a team can comprise of people working in an office, some people hybrid, and some people fully remote, and that the team can be extremely successful in doing so.
That's why we offer three distinct role types: office-based, hybrid, and remote. This diversity allows our roles to align to the work arrangement that suits them best.
We are generally moving towards a pattern where go to market team members have a preference towards office based, with hybrid considered in some special cases, and virtually never remote.
Whereas engineering has to date, been much more aligned around timezone overlap.
It is likely that our offices in Australia; currently in Sydney and Melbourne, but I suspect will expand to Brisbane in future, will need to become ‘sister’ offices, to expand the talent pool for go to market, product, design, engineering and operational team members as we grow from 100 to 500 people.
For our office based roles, I believe that establishment of fixed office days across our global offices is the only solution. This deliberate decision aims to eliminate the endless back-and-forth discussions about which days to come into the office. By having fixed office days, a cohesive and predictable work environment is created, reducing the noise and uncertainty associated with varying schedules.
Our hybrid role type has been a useful mechanism to allow us to bring on great people, who are ‘arms length’ away from a city where we have an office - for example, an hour or two outside of Sydney, or a few hours outside of London.
By creating a role type for this, it allows us to agree on a different set of expectations, due to the greater travel distance involved, whilst not disrupting the day to day of the office based team members.
Of course anyone new, or candidates in the interview process, are always hesitant when Monday and Friday are set as the fixed office days.
However, during initial research, we found that this was due to underlying concern with this was actually due the handful of times each year that you go away for a weekend, or have something on over a weekend - and by making decisions due to this, you risk optimising the entire company’s working schedule and cadence around outlier events.
The solution here has been low battery days and weekender days - a light weight process to have an annual allowance of flexi days around the Monday and Friday schedule, to ensure that individual’s have got some breathing room when they do have something on, whilst also allowing the rest of the team to maintain a strong weekly rhythm by starting the week and ending the week together.
Everything set out in our policies is the default approach, however, I believe that your well-being should always be top priority. That's why we make exceptions for medical conditions when it comes to our work arrangements. We understand that life can throw unexpected challenges our way, whether it's a health issue or a family situation.
In such cases, there are no issues temporarily deviating from the norm, it just needs to be planned and documented with your manager and the Ops team. If a permanent role type change is required, then that it is also an option to discuss - although this is equivalent to a promotion or remuneration change in terms of impact, so does need to be submitted for approval by a manager.
In summary, my belief around, and hence Sitemate’s approach to, work arrangements is rooted in the belief that flexibility, predictability, structure and fairness are the foundation for a thriving work place in this post covid environment.
I believe our working arrangements are enabling us to setup a foundational operating cadence that will support our lofty ambitions as a company, whilst also enhancing your working lives, not complicating them.
Keen to learn more or join the Sitemate team?