How we deliver
Every stage leaves a drawing. Every drawing is signed.
Agents now write much of our code. That moved the real work to deciding what to build and checking what was built. Here’s the set of drawings a project works through, and who signs each one.
How to read a sheet
Agents draw. AI checks. A person approves, and answers for it.
Every sheet carries the same three signatures. The third is the one you’re paying for.
Drawn by
Agent from stories the team walked through
Checked by
AI review on every change
Approved by
A named engineer who answers for what ships
An agent drafts. Screens, code or a plan, written from stories the whole team has walked through first.
AI review checks. Every change gets an AI review. An engineer checks each finding before anyone acts on it.
An engineer approves. A named person decides what’s real and what ships, and answers for that decision.
Sheet 00 · before you sign
A first design for your project, before you pay for anything.
- For build work, after the discovery call, the engineer who’d lead your project builds a first design from what you told us.
- If the work is on screen, it’s clickable screens. If it lives behind the screen, like an API or an integration, it’s an architecture sketch with the real constraints marked.
- They walk you through it live, and you keep the design as screenshots or a PDF.
- In the same meeting, we propose the paid next step. Decisions, estimates and the written plan come with that.
You receive A first design, walked through live, yours to keep as screenshots or a PDF.
- Project
- Yours
- Sheet
- 00 of 06
- Title
- First design
- Drawn by
- Agent, from your call
- Checked by
- AI review
- Approved by
- The engineer who’d lead your project
Sheet 01 · Discover
Show you something real, early.
- We listen first. With your permission we record the conversations, so we work from what you said, not from memory.
- Before anything is priced, you see screens built from those conversations, grounded in your own data where we can get it.
- Anything only illustrative is labeled that way, so a design never promises scope nobody agreed to.
- 1 “We re-key every order from email.” Dispatcher, first call.
- 2 Unassigned orders, from the export you sent.
- 3 Illustrative. We haven’t seen route data yet.
You receive Clickable screens built from what you told us.
- Project
- Dispatch (sample)
- Sheet
- 01 of 06
- Title
- Discover · clickable screens
- Drawn by
- Agent, from transcripts
- Checked by
- AI review
- Approved by
- Lead engineer
Sheet 02 · Plan
Choose the trade-offs before they’re expensive.
- The first design becomes a written scope: the requirements, the assumptions behind them, and an estimate built item by item.
- Every assumption is written down. When one turns out to be wrong, we both see it, and we decide together what to do about it.
You receive A written scope, every assumption on paper.
| Item | Requirement | Assumption | Size |
|---|---|---|---|
| R-01 | Import orders from email attachments | A-03 · One CSV layout per customer | M |
| R-02 | Assign by dragging onto a driver | — | S |
| R-03 | Flag windows a driver can’t make | A-07 · Order data arrives nightly, not live | M |
| R-04 | Print a day sheet for each driver | A-09 · Drivers keep paper day sheets for now | S |
A-07 if wrong: R-03 needs live data, and the size changes. We’d both see it, and decide together.
- Sheet
- 02 of 06
- Drawn by
- Agent, from the discovery sheet
- Checked by
- AI review
- Approved by
- Lead engineer and you
Sheet 03 · Build
Agents do much of the typing. Engineers own the result.
- Before any code is written, the work is broken into stories with acceptance criteria, and the whole team walks through them.
- Agents write much of the code, in small changes that are easy to review.
- An engineer is accountable for every change that ships, and the decisions behind it are recorded where the next person will find them.
You receive A record of every change, and the decisions behind them.
- #409 Parse CSV attachments · small change · drafted by agent · approved
- #410 Map each customer’s layout (A-03) · drafted by agent · approved
- #411 Reject rows with no delivery window · drafted by agent · approved
- #412 Update on re-import, never duplicate · drafted by agent · approved · see DR-06
DR-06 · decision record. A re-sent file updates existing orders by order number. Why: dispatchers re-send corrected files. Decided by the lead engineer.
- Sheet
- 03 of 06
- Drawn by
- Agent, per story
- Checked by
- AI review, per change
- Approved by
- Lead engineer, every change
Sheet 04 · Test
Prove it before we ask you to.
- Every change gets an AI review.
- An engineer checks each finding and decides which ones are real. Nothing is acted on until a person says yes.
- Then we test our own work against the cases that would hurt if they broke, and tell you exactly what we tested.
You receive A review record, and a list of what we tested.
| Finding | What the review said | Checked | Decision |
|---|---|---|---|
| F1 | Re-import creates duplicate orders | Real | Fixed |
| F2 | Window parsed in server time, not depot time | Real | Fixed, test added |
| F3 | No limit on file size | Real | Fixed |
| F4 | Possible injection in the parser | Not reproduced | Dismissed: parameterized |
| F5 | Rename a variable | Style | Dismissed |
Our test pass before yours: daylight-saving change day · empty file · very large file · the same file sent twice · a customer with two depots.
- Sheet
- 04 of 06
- Drawn by
- Agent, tests per story
- Checked by
- AI review
- Approved by
- Lead engineer
Sheet 05 · Deploy
Plan for the morning after.
- We cut over with a plan for the first day of real use, not just the launch.
- You get the documentation to run what we built, and coaching if you want to bring the work in house.
You receive A cutover runbook, and the documents to run the system.
- T – 7 days Rehearse the cutover on a copy of production. Time the rollback.
- T – 1 day Freeze imports. Brief the dispatch leads.
- T 0 Sunday, early. Cut over. Run a dozen real orders end to end.
- T + 1 The morning after: we’re on the dispatch floor for the first shift.
- Rollback One step, rehearsed, with a named owner.
- Sheet
- 05 of 06
- Drawn by
- Agent
- Checked by
- Rehearsal
- Approved by
- Lead engineer and your operations lead
Sheet 06 · Iterate
Keep building on a system you own.
- We keep a backlog groomed ahead of the work and meet with you regularly on scope.
- You decide what comes next, and by default you own the code, the decisions and the documentation.
You receive The code, the decisions and the documents, yours by default.
| Rev | Description | Approved |
|---|---|---|
| A | First release to dispatch | Lead engineer |
| B | Carrier import, from dispatcher feedback | Lead engineer |
| C | Bulk reassign when a driver calls in sick | Lead engineer |
| D | Groomed and ready, ahead of the work | You decide |
- Sheet
- 06 of 06
- Drawn by
- Agent
- Checked by
- AI review
- Approved by
- Lead engineer, with you
Sheet 00 is drawn for your project.
Book a discovery call. For build work, the engineer who’d lead it can come back with a first design, walk you through it, and tell you what the next step would be.