How we work
Software projects rarely
fail on the code.
They fail on vague scope, long silences and a handover that leaves you stuck. Every step below exists to stop one of those.
The five steps
-
1. A conversation
Half an hour. We go through the process, the systems involved and what a good outcome looks like. If custom software is the wrong answer, we will say so on that call.
-
2. Scoping, paid and separate
We map the process with the people who do it, confirm how we will connect to your systems, and write down exactly what is included and what is not.
-
3. Build, in stages
You see working software while it is being built, not a demonstration at the end. Each stage is agreed, and anything new is quoted before it is started.
-
4. Testing and launch
We test as we build. Then your team tests it with real data before anything goes live. It runs in your environment or on hosting we manage.
-
5. Handover and support
Documentation, an administrator guide and training for your team. The code is yours. Fixes for thirty days after launch are included.
You can stop after step two
Scoping produces a written scope and a fixed quote for the build. If you decide not to go ahead, both are yours to keep or take elsewhere. That is the point of charging for it separately.
Pricing
How pricing works
No price list. A number invented before scoping is a number that changes later.
Scoping is charged separately and ends with a fixed quote. After that, anything outside the agreed scope is quoted before it starts — so there are no invoices you did not approve.
In every project
- A fixed quote for the agreed scope.
- Access to the people building it, not an account manager relaying messages.
- Full ownership of the code and the intellectual property.
- Documentation and training at handover.
- Thirty days of fixes after launch.
- Mainstream technology, so another developer could take over if you ever wanted that.
AI
Yes, we use AI.
No, it does not decide.
We use it. It is a large part of why a focused tool is now affordable, and we would rather say so than have you wonder.
What it does not do is decide. A developer designs it, reviews every change and is accountable for it — against the same security standards we apply to the infrastructure we manage.
You get documented software you can hand to anyone. Not a black box.
Where your tool includes AI features, we agree in advance what data they can see, and that is written into the scope.
Why it is built this way
What went wrong last time
And the step that stops it happening again.
- “It ran late, and the scope grew quietly.”
- Scoping is paid, separate, and finished before a quote exists. Changes are quoted before they start.
- “We heard nothing for weeks.”
- You talk to the people writing the code. That is an inclusion, not a courtesy.
- “There was nothing to look at for months.”
- You see it working while it is being built, stage by stage.
- “The work was quietly passed to someone else.”
- The team you meet is the team that builds it, led by the founder, inside a company trading since 2002. Who you deal with.
- “They would not hand over the code.”
- Yours, with the documentation. In the contract, not just on this page.
- “Nobody else could maintain it.”
- Mainstream technology and an administrator guide, so another developer can pick it up.
- “The security problems turned up after launch.”
- Sign-in, access, secrets and hosting are decided during scoping. What that covers.
Tell us about the process that wastes the most time
One call is usually enough to know whether it is worth building, and how we would approach it.
- We read your enquiry and reply within one working day.
- If an off-the-shelf product would do the job better, we will say so.
- No sales sequence and no automated follow-ups.