-
1
Discovery
We work out what it actually is.
A short, fixed-price engagement on its own. We sit with the people who do the work, map the process as it really runs, and write it down. You leave with a written scope, wireframes and a fixed quote for the build.
Those documents are yours whether or not you build with us. If the answer turns out to be "buy something off the shelf", we will say so.
-
2
Build
You see it working, not reported on.
We ship to a staging site you can open from the first fortnight, and every fortnight after. Your staff use it long before launch, which is when the awkward truths about a process surface.
The fixed quote from discovery holds. If scope changes, it changes because you asked, and you see the new number before we start.
-
3
Handover
It is yours, including the parts you cannot see.
Source code, database, deployment and documentation, in your accounts and your name. We train your staff on it the same way we do for the register — at your desk, not over a chatbot.
No lock-in clause and no proprietary runtime. You can hire anyone to carry it on, and we would rather you stayed because the work is good.
What it costs depends on the work
We price each build against its own scope rather than a rate card. Discovery is
quoted as a fixed price once we understand roughly what you need, and it ends
with a fixed quote for the build itself — so you approve a number before any of
it starts, and that number does not move unless you change what you asked for.
- What it has to do
- How many workflows the system covers, and how much of the business runs through it.
- What it has to talk to
- Existing systems, payment providers, government or supplier formats — each connection is work, and some are more work than the rest of the build.
- What has to come with you
- Years of records in spreadsheets or an old system have to be cleaned and moved. This is routinely the most underestimated part of a project.
- Who has to use it
- How many people, in how many roles and locations, and how much has to work when the connection does not.
We do not quote a build before discovery. Anyone who gives you a number for an
unscoped project has either padded it heavily or is about to discover why they
should have.