You see the price and the shape before anyone builds anything.
Five steps, in this order, every time. The first one is free and produces something you keep whether or not you hire us. Below is exactly what happens at each step, including how much of your time it costs, because that is the part most agencies leave vague.
Understand
We learn how your business actually runs before proposing anything.
- A conversation about your week, not about software
- We map where work starts, where it waits and where it gets re-entered
- We list the tools you pay for and what each is genuinely doing for you
- We look at the numbers with you, so the priority is evidence rather than opinion
What you hold at the end
A short written summary of what we heard, what we would tackle first and why. Yours to keep whether or not you go further with us.
What it costs you in time
About forty-five minutes, plus a follow-up read. No preparation needed.
Design and quote
You see the shape of the solution and its price before anyone builds anything.
- We agree the scope of a first useful version, deliberately kept small
- We show you the screens and the flow, so you can react to something concrete
- We name what is out of scope as clearly as what is in it
- You get an itemised written quote, module by module
What you hold at the end
An approved scope and a fixed written quote. The price does not move unless you change the scope, and then you get a revised quote first.
What it costs you in time
One review session and a decision. No commitment until you approve the quote.
Build in the open
You watch it happen instead of waiting for a reveal.
- We build the core record and the highest-value screens first
- You get a login to our portal showing live progress
- Short reviews as each piece becomes usable, on your real data
- Your feedback changes the next iteration, not a change-request form
What you hold at the end
Working software you have already used, arriving in pieces rather than as one delivery at the end.
What it costs you in time
A short review whenever something becomes usable. Typically every week or two.
Switch over safely
The cut-over is rehearsed, verified and reversible.
- Data migrated with counts and totals reconciled against the old system
- Your team trained on real data, not a demo
- The old system kept readable in parallel until you are confident
- A named person available through the first live week
What you hold at the end
A reconciliation report you can check yourself, plus a team that has used the system before it went live.
What it costs you in time
A training session per group of users, and a decision on when to switch.
Keep it running
Software that still fits in month twelve, not just week one.
- We monitor what we built and often see problems before you report them
- A person to contact, with a response time agreed in advance
- Adjustments as your process changes, quoted the same transparent way
- You keep your data and your source code throughout
What you hold at the end
An optional support arrangement, priced separately, that you can end without losing anything.
What it costs you in time
None, until you want something changed.
Why we build the core first instead of designing it all up front
A specification written before anyone has used anything is a set of guesses, and the guesses that turn out wrong are always the expensive ones. So we build the smallest genuinely useful version and put it in front of you.
Feedback on a working screen is worth more than feedback on a document, because you can only tell us the form asks the wrong question once you have tried to fill it in.
It also changes the commercial risk. You are never paying for a large build on trust: by the time the bulk of the work happens, you have already used the thing and know it fits. If it does not, we have found out early and cheaply, which is the whole point.
Questions about working with us
Do we have to replace the software we already use?
Usually not, and we push back when a client suggests it. Replacing a tool that works is expensive and disruptive. Far more often the problem is that your tools do not talk to each other, which integration fixes at a fraction of the cost. We only recommend replacing something when it is genuinely holding the business back.
How long does a project take?
It depends on scope, but you should expect to see something real and usable within the first few weeks rather than at the end. We deliberately build the core of a system first and put it in front of you, because feedback on a working screen is worth more than feedback on a document. Larger builds continue in short iterations from there.
Will an AI be talking to our customers without us seeing it?
Not unless you explicitly ask for that, and we would advise against it. Our default is that AI drafts and a person approves before anything reaches a customer. Automation handles the mechanical work; judgement stays with your team. Every automated action is logged so you can see exactly what ran and what it changed.
How much of our time will this take?
Less than you fear, but it is not zero and we would rather be honest about that. Expect a couple of hours in the discovery stage, then short review sessions as pieces become usable. Nobody knows your process like you do, so that input is the part we cannot substitute. Everything else is ours to carry.
Can we see progress without having to ask?
Yes. Clients get a login to our portal showing live project progress, what is in flight, what is done, and every quote and invoice. Transparency is a stated company value and this is how we actually implement it rather than just claiming it.
Step one is a conversation and it is free.
Forty-five minutes on how your business actually runs, then a written summary of what we would fix first. Yours to keep either way.