The process
You will see itbefore we build it.
Software projects fail in the gap between what was specified and what was understood. We close that gap by building the thing you can click, before anyone writes the thing you cannot see.
Start to live
Four stages, and one of them is free.
- Stage 0A conversation
No charge, no deck.
You describe how your network actually runs, including the parts that embarrass you. We tell you honestly which of our fifty-eight modules you need and which you do not, and whether we are the right people at all.
- Stage 1 · DiscoveryOne month
The month that decides the project.
We prototype your system as clickable screens: your terminology, your roles, your pricing model, your royalty plan, your actual workflow. You use it, you tell us what is wrong, we change it that week.
By the end of the month you have approved a working prototype of the system rather than a document describing one. Nothing has been built, so nothing is expensive to change.
- Stage 2 · BuildThree months
Built to the prototype you approved.
You see working increments continuously, not a reveal at the end. Because the design decisions were settled in month one, this stage is engineering rather than negotiation, which is precisely why it fits in three months.
- Stage 3 · MobileTo six months in total
Where the operation needs an app.
Bespoke staff and customer apps are designed and built the same way, prototype first. This is what takes a project to six months.
- Stage 4 · DeployAnd stay
Deployment is the start, not the end.
Live, supported, and continually improved. Your system keeps getting better for as long as we work together.
Why prototype first
Prototypes are cheap. Rebuilds are not.
A specification is a shared guess
Everyone reads the same sentence and pictures a different screen. Nobody finds out until the build is finished and expensive to change.
A prototype is a shared object
You click it. You find the missing step, the field that should have been a dropdown, the approval that has to happen before the other thing. In month one, all of that costs an afternoon.
It de-risks the decision, not just the build
You are committing to a month of prototyping to start with. If we are wrong for each other, you find out inside the first month holding a prototype, rather than a year in holding an invoice.
We work this way on our own products
This website was scoped and prototyped exactly like this before a line of it was built.
Your side
What makes month one work.
Honest process
Including the workarounds. Especially the workarounds.
One decision-maker
Somebody who can say yes without a committee.
Two or three hours a week
For prototype reviews. That is the whole time commitment.
Early access to the systems you are leaving
Migrations are where the surprises live, so we would rather meet them in month one.
That is genuinely it. You do not need to arrive with a specification. Producing one is our job, and by the end of month one it will exist as something you can click.
Not integrated. Whole.
Start with a month.
One month of discovery, and a prototype of your system you can put in front of your franchisees.