And it all started with a few spreadsheets, a lot of templates… and one conversation about “there has to be a better way to do this.”

By Rob Hufton

Before Sitesteps was a platform, it was a problem.
A very real, very familiar problem.
James Hockey had been running his business successfully for years. Like many experienced professionals, he’d built his own systems over time — refining them, improving them, and shaping them around how his team actually worked day to day.
On the surface, everything functioned.
But underneath?
It was a web of spreadsheets, Word documents, PDFs, email templates, folders, mail merges, and manual processes all stitched together through experience and memory.
It worked… until it didn’t.
James’ process covered everything the business needed:
The challenge wasn’t that the system was bad.
The challenge was that it was manual, repetitive, and fragile.
Every job required:
It relied heavily on experience and attention to detail. If someone missed a step, used the wrong version, or forgot to update one document, errors crept in.
And as the business grew, so did the admin.
Having worked with James for years on his digital strategy, I already understood how his business operated. My background in UX and product design meant I wasn’t just looking at the documents — I was looking at the journey behind them.
Not:
“How do we digitise these templates?”
But:
“Why does this information move through the business this way in the first place?”
We mapped everything.
Every document.
Every spreadsheet.
Every handoff.
Every repeated step.
What became clear was that James hadn’t built a messy system.
He’d built a clever system using the only tools available to him at the time.
The problem was the tools, not the thinking.
At some point the question shifted from:
“How do we improve these documents?”
to
“What if this wasn’t a collection of documents at all?”
What if:
That was the moment Sitesteps stopped being an idea and started becoming a product.
Sitesteps wasn’t designed in a boardroom.
It was designed around real jobs, real constraints, and real working days.
Every feature came from a genuine need:
Old WaySitesteps WayRe-entering job details in multiple documentsEnter once, used everywhereManually building reportsReports generated instantlyCopying findings into quotesQuotes linked directly to survey dataStoring photos in foldersPhotos tied to the job automaticallyEmailing documents manuallyDocuments sent in a few clicks
Instead of forcing James to change how he worked, we built software that supported his existing workflow — just without the admin burden.
What started as a collaboration to help one business run more efficiently quickly revealed something bigger:
This wasn’t just James’ problem.
Many companies in the industry were doing the same thing:
Sitesteps grew from that realisation — turning a proven, field-tested workflow into a platform other businesses could use too.
Because Sitesteps came from inside the day-to-day reality of the work, it understands:
This isn’t generic software adapted to the industry.
It’s industry experience, turned into software.
Sitesteps wasn’t created to change how professionals work.
It was created to remove the admin, duplication, and friction from the way they already do their best work.
And it all started with a few spreadsheets, a lot of templates… and one conversation about “there has to be a better way to do this.”