What $150 buys
This is the whole document. Read it before you pay for one.
Every blueprint we write has these nine sections. Below is a complete worked example for an invented company, at the same level of detail you would get for yours — including the parts that say no.
Free 1-minute fit check · no equity · no retainer
About this example
Northgate Logistics does not exist. The document is invented so we can show you one in full — a real blueprint belongs to the client who paid for it, even with the names taken out. The structure, the depth and the tone are exactly what we deliver.
Section 01
What we understood
Northgate runs 18 delivery vans out of two depots. Today the route for each van is printed the night before, and drivers phone the office when something cannot be delivered. The office copies that into a spreadsheet, and customers are told “sometime tomorrow”.
The one thing that has to work: a driver opens the app, sees today's stops in order, and marks each one delivered or failed without phoning anyone.
Everything else in this document exists to support that sentence. Where something does not, we have put it in section 08.
Section 02
Who uses it, and what they can do
| Role | How many | What they can do |
|---|---|---|
| Driver | 18 | See only today's own route. Mark delivered or failed, add a photo and a note. |
| Dispatcher | 3 | Build tomorrow's routes, reassign a stop, see the live board. |
| Depot manager | 2 | Everything a dispatcher can, plus the weekly export. |
| Customer | — | No login. Receives a tracking link by SMS. |
Roles are enforced in the database, not only in the screens. A driver who edits the address bar still cannot read another driver's route. That test is part of the build and it blocks delivery if it fails.
Section 03
Screens, one by one
| Screen | Who | What happens there |
|---|---|---|
| Sign in | All | Email and a six-digit code. No passwords to forget on a van. |
| Today's route | Driver | Ordered list of stops, distance to next, one tap to open maps. |
| Stop detail | Driver | Address, contact, notes. Delivered / Failed, photo, reason. |
| Live board | Dispatcher | All 18 vans, stops done and remaining, anything failed in red. |
| Route builder | Dispatcher | Drag stops between vans for tomorrow. Publish at 18:00. |
| Stop history | Manager | Search by address, date or driver. Photo and timestamp attached. |
| Weekly export | Manager | CSV of every stop, for the invoicing they already do. |
Seven screens. Anything not on this list is not in version one, and the price below assumes exactly these.
Section 04
What it stores
| Thing | Fields that matter | Who can read it |
|---|---|---|
| Driver | name, phone, depot, active | Dispatchers and managers |
| Route | date, van, driver, published at | Its own driver, all dispatchers |
| Stop | address, window, contact, order in route, status | Its own driver, all dispatchers |
| Delivery proof | photo, timestamp, GPS point, note | Dispatchers and managers |
| Failure reason | one of six, free text optional | Dispatchers and managers |
GPS is recorded at the moment a stop is marked, not continuously. Drivers are not tracked between stops — that is a deliberate decision and it is in the document so nobody discovers it later.
Section 05
What it talks to
| Service | What for | Cost and whose account |
|---|---|---|
| Twilio | The tracking SMS to the customer | About $0.008 per message, your account |
| Google Maps | Open navigation to the next stop | Free at this volume, your API key |
| Your accounting tool | Nothing in v1 — the CSV export covers it | — |
Every third-party account is opened in your name, with us added as a collaborator and removed on handover. We are never the account holder for anything you depend on.
Section 06
How we will know it works
These are the acceptance criteria. Each one becomes an automated test that has to pass before you are shown anything:
- ›A driver signs in and sees only their own route for today.
- ›A driver marks a stop delivered with a photo; it appears on the dispatcher board within five seconds.
- ›A driver marks a stop failed with a reason; the customer is not sent a delivery SMS.
- ›A dispatcher moves a stop between two vans and publishes; both drivers see the change.
- ›A driver signed in on one account cannot open another driver's route by changing the URL.
- ›The weekly export opens in Excel with one row per stop.
Section 07
The ten days, day by day
| Days | What happens | What you do |
|---|---|---|
| 1–2 | Data model, roles, sign-in. The isolation test is written first. | Nothing |
| 3–5 | Driver screens end to end. Route, stop, proof, failure. | Nothing |
| 5 | You get a link and use it on your own phone. | Half an hour, tell us what is wrong |
| 6–8 | Dispatcher board and route builder. The SMS. | Answer questions same day |
| 9 | The seven acceptance criteria run green. Load test at 50 drivers. | Nothing |
| 10 | Handover: code, accounts, a written manual. | Decide: keep it or walk |
Section 08
What we are deliberately leaving out
This is the section most studios do not write. It is the one that protects the ten days.
| Not in version one | Why | When it would make sense |
|---|---|---|
| Automatic route optimisation | Your dispatchers already do this well and it is weeks of work to beat them. | Sprint 2, once there is real stop data to optimise against. |
| Native app in the stores | A web app on the phone does everything above. Store review alone can take the ten days. | When you need offline in dead zones. |
| Customer accounts | Customers want a link, not a password. | Only if they start asking for history. |
| Live van tracking on a map | Nice to look at, changes no decision today. | When you have more depots than you can phone. |
| Invoicing | You have a system that works. Two systems is worse than one. | Never, probably. |
Section 09
The price, locked
$2,490 total for everything above. Not an estimate and not a range. If sections 01 to 08 do not change, that number does not change either.
You have already paid $150 for this document. The remaining $2,340 is due on day 10, after you have used the product — and only if you decide to keep it.
If you want something that is in section 08, we price it as a second sprint before starting, so you always know the whole number.
Why we show you this
Nobody should pay $150 for a word.
“Blueprint” means nothing until you have seen one. Now you have. If what you get back for your own product is less useful than what you just read, ask for the $150 back and we will send it the same day.
Next step
Find out if your idea fits in 10 working days.
Tell us what you want to build. We reply the same day with a straight yes, no, or here is what we would cut.