Five steps,
no surprises.
Every step ends in something you can hold: a document, a spec, a price, working software. You always know what you have paid for and what comes next.
- 01
Discovery
One conversation, about 90 minutes
We sit down with you and whoever actually does the work. Not the org chart version, the real one. How does a new client reach you? What happens between the first call and the first invoice? Where does someone say “I just handle that manually”?
What you getA written map of how work moves through your business, in plain language, with the manual steps marked.
- 02
Process analysis
About a week
We put hours against the map. Which of those manual steps costs the most time, which ones cause the most errors, and which ones are load-bearing enough that breaking them would hurt. Some of what looks broken is fine. Some of what looks fine is quietly expensive.
What you getA ranked list of what is worth fixing, with hours attached, and an explicit list of what we would leave alone.
- 03
Solution design
About a week
Now we decide what to build. Every integration gets named. Every system that has to talk to another system gets checked against its actual API, not its marketing page. If something cannot be done the way you want it, you hear that here rather than halfway through the build.
What you getA build spec naming every component and integration, and a fixed price against it.
- 04
Implementation
Scoped in step three
We build it, wired into the tools you already pay for. You see progress as it happens rather than at the end. Nothing goes live without you having used it first.
What you getWorking software, deployed, running against your real data.
- 05
Training and optimisation
Handover, then 30 days
Software nobody uses is not a solution. We train the people who will actually touch it, then check back after a month, when the real edge cases have surfaced and the novelty has worn off.
What you getRecorded walkthroughs for your team, written documentation, and a 30-day review.
When we will tell you not to build it.
Turning down work is cheaper for you than a project that never pays for itself, and it is the fastest way to find out whether we are worth listening to.
- The underlying process is broken. Automating it just produces broken output faster, so we fix the process first or we do not proceed.
- The volume does not justify it. If a task takes twenty minutes a month, a custom build will never pay for itself. Sometimes the answer is a checklist.
- The tool you already own does it. We will tell you when the feature exists in software you are already paying for and nobody turned it on.
- It needs judgment you cannot delegate. Some decisions should stay with a person, and we will say so rather than sell you a machine to make them.
It starts with a conversation, and the conversation is free.
Discovery is not a sales call with a different name. You will end it with a clearer picture of your own operation whether or not you hire us.