Software built for a market of one
Your pricing rules, your approval steps, the exceptions off-the-shelf tools politely ignore. We treat them as the spec, not the problem.
What a build actually includes
Not a template with your logo in the corner. A working system, assembled around your operation.
One system, five layers
The screens your team lives in.
Jobs, clients, paperwork and deadlines in one place, laid out the way your week actually runs.
A front door for your clients.
They log in, see where things stand, and send what's needed. Your inbox gets noticeably quieter.
The pipes between your tools.
Invoicing, e-signatures and the rest connected properly, so a number typed once shows up everywhere it should.
Your history, moved in.
The spreadsheet years come with you. Existing records are migrated as part of the build, so day one isn't a blank screen.
A handover your team can hold.
Documentation, training and recorded walkthroughs. The next hire learns the system without booking a call with us.
From first call to first login
Six steps. The expensive surprises get removed at step two.
One conversation about the problem.
What's slow, what's manual, what you keep meaning to fix. If a build makes sense, we'll sketch its shape on the call.
Scope and price, in writing.
What we're building, what it costs, when it lands. Agreed before any code exists, so the number you say yes to is the number you pay.
Working screens inside weeks.
You're clicking through a real, running version early. It's easier to react to a screen than to imagine one.
You steer while it grows.
Short rounds of build, review, adjust. The system your team launches with is one they already had a hand in shaping.
Launch is a switch, not a leap.
Data in, team trained, and the old way kept running alongside until you're confident. Then you turn it off.
The first month is ours to watch.
New systems surface small things early. We expect that, we look for it, and sorting it is part of the build, not a fresh invoice.
Yours. Properly yours
The code lives in a repository you can open. The database is yours. The accounts it runs on are registered in your name, not ours.
There are no per-seat fees from us. Your eleventh employee costs the same as your first: nothing.
It's written on ordinary, widely used technology and documented as we go. Any experienced developer could pick it up and carry on without us.
If you ever want to leave, everything leaves with you. We'd rather keep you by being useful than by holding the keys.
Custom used to mean six figures and a Gantt chart
That was the going rate for years. A discovery phase, a team of eight, an invoice that read like a phone number.
What changed is how code gets written. AI now handles the parts that were only ever typing: the boilerplate, the plumbing, the hundredth near-identical form.
It doesn't design your system and it doesn't understand your business. That's still done by a person, the same one you talk to.
The hours it saves come off your quote. That's the whole trick.
When it breaks at 9am on a Tuesday
You message the person who wrote it. They already know where to look.
We keep an eye on what we ship, so problems tend to introduce themselves to us first.
If you want that in writing, support plans put a guaranteed response behind it. Most clients take one. None of them are forced to.
Asked on almost every first call
If yours isn't here, it'll fit comfortably in the first ten minutes of one.
Honestly, it depends on size. Smaller systems tend to land in weeks, larger ones take a few months. You'll have a date in writing before we start, and if it ever moves, you'll hear it from us the day we know.
You do, from the first invoice onwards. Nothing about it is licensed back to you, and nothing needs renting from us to keep working.
An ordinary, modern web stack: TypeScript, PostgreSQL, infrastructure from Cloudflare. Picked for being dependable and widely known, which means any experienced developer can read it without a decoder ring.
A fair question to ask any small firm. Everything is documented, built on standard technology, and held in accounts you control. Your system runs whether we're in the room or not.
It's the normal starting point. Most builds begin as a feeling that the current setup takes more effort than it should. And if the picture needs proper untangling before anyone builds anything, that's what the systems audit is for. About the systems audit
Usually, yes. Some builds need finishing, some need rewiring, and a few deserve a dignified burial. We'll tell you which one you've got after a look under the hood.
It moves in with you. Migrating existing records, from spreadsheets or whatever you're retiring, is part of the build rather than an optional extra.
In your own database, in accounts registered to you, with access limited to the people you choose. It isn't pooled with other clients' and it's never handed to a third party.
Let’s build yours
Start with a call, not a brief. No salesperson, no discovery deck — you talk to the person who writes the code.
If we’re not the right fit, we’ll say so. That’s cheaper for both of us.