Where every build starts
Change your mind on paper, not in week nine.
The expensive mistakes in a build are all made in the first week, by people in a hurry: the wrong shape for your records, the integration nobody checked, the word 'finished' meaning two different things to two people. We go looking for them while they still cost nothing to fix.
- 5 - 8 working days
- start to written pack
- Your records
- shaped right before anyone builds
- Yours
- to keep, whatever you decide next
What you walk away with
The four things a build goes wrong without
Not a proposal and not a deck. These are the working papers a build actually runs on, written by the people who would do the building - and yours to take to another firm if you would rather.
What is actually being built
The scope written down in plain words - every screen, every role, every report - with the things we agreed to leave out listed just as plainly. The argument about what "finished" means happens here, on paper, not in week nine.
How your records fit together
The data model: what a customer is, what an order is, what happens to an invoice when it is part paid. Getting this wrong is the single most expensive mistake in a build, and it is almost always made in the first week by somebody in a hurry.
What it has to talk to
Your payment providers, your bank, your accounting package, whatever your suppliers send you. Which integrations are documented, which ones are not, and which one is going to be the difficult one. We find that out now rather than in week six.
A price and a date that hold
One number and one date, fixed, with the payment schedule and what happens if you change your mind halfway. Not a range, not an estimate, and not something that moves once we start.
How the week runs
Eight days with the people who would build it
The same senior people who would build the thing. Not a salesperson, and not a junior sent to take notes.
When this is not for you
Three times you should keep your money
If the week shows that you do not need a build - that an off-the-shelf product does it, or that the real problem is a process rather than software - that is what the pack will say, and we will have talked you out of a much larger invoice. That happens, and it is a fair use of the fee.
If you want the week
What it costs, and how it is paid
Half on signing and half when the pack is delivered. We do not ask anyone to pay for a week of work before any of it exists, and the balance falls due against something you can read.
KES 150,000
USD 1,500 billed internationally
half to start, half on delivery
What the fee buys
- Scope, data model, and integration plan, written down
- A fixed price and a fixed date for the build
- Yours to take to another firm and quote against
- Credited in full against a build started inside 60 days
The obvious objection
KES 150,000 and you have not built anything yet
That is a fair reaction, and it is why we do not quote before discovery. For 150,000 you get the scope, the plan, and a fixed price, and if the answer is that this should be a 400,000 job rather than a 1.6 million one, we will tell you that and you will have it in writing. If you build with us inside 60 days, the 150,000 comes off the price.
Not what you needed?
Book the discovery call
Thirty minutes, free, and no obligation to buy the week at the end of it. Tell us what you are trying to build and we will tell you whether discovery is the right next step - or whether something cheaper would fix it.
- Free 30-minute call
- A straight answer on whether you need this
- No obligation either way
Or reach us directly
Weekdays, and we answer the same day.