How we work
Five stages.
The first one is free.
You know the cost before anything is built, and you can stop after any stage. Tap through to see what each one involves.
We talk about how your business runs.
Who does what, where things get stuck, what breaks when someone’s away. Mostly not a technical conversation.
An honest picture of how the work gets done.
My read on what’s worth fixing first — and what isn’t.
Nothing owed. The read is yours to keep.
I study the business and write the plan.
I go deeper than one call allows: your process end to end, where the money and hours leak, what should change before any software exists.
A document: what to build, in what order, what each part costs.
If you don’t continue, take the plan to anyone you like.
Built in front of you, not behind a curtain.
You see a working first version early. Then we correct it together until it fits how you actually work.
You pay per stage and can stop after any of them.
Feedback, and one person who can answer questions.
You own it. Completely.
The code, the accounts, the data. Nothing runs on infrastructure only I can reach, and nothing locks you in.
Handover, documentation, and getting it running.
Staff training, and setting it up across the business.
Or we close the file here.
Some clients take it from here. Others want me on hand as the business changes. Both are fine.
Changes, additions, and someone who knows the system.
Close it out. It’s yours and it keeps working.
The questions people actually ask
How long does it take?
A single automation is usually days. A focused web application is a few weeks. A full internal system covering several parts of a business runs into months — but you see working pieces along the way, not one delivery at the end. You’ll get a real timeline in the written plan at stage two, before you commit to anything.
What does it cost?
It depends on what gets built, which is why there’s no price list here — a published number would be wrong for almost everyone. What I can promise is that you get a costed plan before any work starts, broken into parts, so you can start with one piece rather than committing to everything at once.
Is my business too small for this?
Probably not. The useful test isn’t headcount — it’s whether something repetitive is eating real hours every week, or whether information keeps getting lost between people. If neither is true, you likely don’t need me yet, and I’ll say so.
You’re one person. What happens if you’re unavailable?
A fair question, and the honest answer matters more than a reassuring one. Everything I build is documented and handed over: you own the code, the accounts and the data, and nothing runs on infrastructure only I can reach. If I’m ever not around, another developer can pick it up — and you aren’t locked into a platform you can’t leave.
Do I need technical staff to use it?
No. If your team needs training to do their existing job, the system was designed badly. What I do need is one person on your side who knows how the work really happens and has time to answer questions during the build.
What if I already have software that half works?
That’s common, and replacing it isn’t always the answer. Often the fix is connecting what you have so it stops needing a person in the middle. If your existing tools are worth keeping, I’ll tell you that instead of selling you a rebuild.
Stage one costs nothing.
Tell me how your business runs. I’ll tell you what’s worth fixing first.
No cost, no pitch · I reply personally, within 24 hours