Which ones apply becomes clear once we've watched the work. Every example below comes from a real engagement.
Time on site with the people doing the work, and the process written down as it really runs. Where the hours actually go, handover by handover.
Following a purchase order end to end — from the moment somebody wants something to the moment it's paid — then a map showing the same information keyed in at four separate points.
The same job drawn as it would run: the same steps, in the same order, with the handovers between them redesigned so information moves instead of being carried by a person.
The same handful of facts keyed in seven times between an enquiry arriving and the invoice going out — and the version where they're entered once.
Connecting the software you already pay for, so information moves between systems instead of through a person. Most of what we build sits between things.
A weekly ordering and delivery report, compiled by hand every Friday out of three separate spreadsheets and emailed round the business.
The repetitive work that shouldn't need a person at all — reports, notifications, data moving from where it's captured to where it's needed, recurring jobs that currently live in somebody's head.
Quotes rebuilt by hand from scratch every time — around two hours of an estimator's day, twenty times a month.
Most businesses already own it and use a fraction of what they pay for. Shared data, sensible permissions, approvals, forms, reporting — built inside the tenant you already have rather than alongside it.
Replacing a shared drive and a spreadsheet with a single structured list that the whole business can see, inside your existing tenant.
Reading documents, pulling figures out of them, drafting text a person then checks. Narrow jobs with a clear right answer and a human at the end — built, where it's worth it, so their corrections feed back in and the checking shrinks.
A valuer's client pack — accounts, asset register, lease schedule — read, analysed and retyped into a report by hand. An hour and a half to three hours, every time.
Built only when nothing you can buy fits the job — and to a written standard covering where your data lives, how it's separated, and how you get it all out again.
QCapture, the product we built and run ourselves — site quality records captured once at the point of work, instead of a photo, a spreadsheet and a report.
That depends on where it lives, and we agree which before anything is built.
If it runs on our systems, there's a fixed monthly cost to use it: hosting, keeping it running, small changes as the business shifts, and somebody who already understands how it all fits together on the day something breaks. It's part of the price of using it, not an optional extra, and you'll know the figure before you agree to the build.
If it's built into your own systems, it's yours outright. We build and test it in ours, move it into yours and hand it over. From then on you run it, and there's nothing further to pay us.
Where software runs on our systems, we keep the source, as most software suppliers do, so you depend on us to change it. Escrow is available if that matters.
Your data is yours either way, and you can take all of it with you. Anything built into your own systems is yours to keep, change or hand to someone else.
We're not tied to any of these, and we'll work inside whatever you already run. This is simply where most of it ends up.
Book a discovery callOr describe one job and we'll draw it back to you →