Process
Every phase ends with something in your hands.
One process at a time, usually weeks, not months.
Discover
A written map of the process as it runs, with the bottlenecks ranked by hours lost.
What you receive
- A written map of the process as it runs
- The bottlenecks, ranked by hours lost
- A recommendation on where to start
Process map
Order intake, as it runs today. Hours per week.
| Step | Who | Hours | Rank |
|---|---|---|---|
| Orders arrive by phone, email and chat | Sales | 5 | 2 |
| Each order is retyped into a spreadsheet | Sales | 6 | 1 |
| Stock is checked on the warehouse floor | Warehouse | 4 | 3 |
| A confirmation is written by hand | Sales | 3 | 4 |
Start here: retyping orders. It costs the most hours, and every later step waits on it.
Plan
Requirements in plain language and a phased plan. Nothing starts until you approve it.
What you receive
- A requirements document in plain language
- A phased plan in priority order
- What is out of scope, written down
Requirements
Order intake, phase 1 of 2
- R-01 A buyer sends an order from one form, without an account.
- R-02 Each order reaches one inbox, with its items attached.
- R-03 The sales desk marks an order New, Confirmed or Shipped.
- R-04 Confirming an order updates the stock count.
Out of scope: invoicing and delivery tracking. Phase 2, if approved.
Build and test
Working software at the end of each phase, tested against every requirement.
What you receive
- Working software at the end of each phase
- A link to try it, not a screenshot
- The source code, in your own repository
- A plain-language test list you can run
- A pass or fail against every requirement
Test list
Run it yourself, one line at a time
- T-01 Send an order with three items, without signing in. R-01 Pass
- T-02 Open the inbox. The order is there with all three items. R-02 Pass
- T-03 Mark the order Confirmed. Its status changes. R-03 Pass
- T-04 Check the stock. Each item went down by its quantity. R-04 Pass
Deliver
Documentation for your staff, a walkthrough, and an agreed support period.
What you receive
- System documentation written for your team
- A walkthrough for the people who use it
- Every known issue, listed before handover
- An agreed support period after go-live
Staff guide
Confirming an order
- Open Inbox. New orders are at the top.
- Open the order and check its items.
- Press Confirm. The stock count updates on its own.
- The buyer gets an email saying the order is confirmed.
Two ways to work. One will fit you.
What changes is how the scope is agreed, not what gets built.
Fixed price
Fits when
- The outcome is clear enough to write down
- One process, one build, or a first engagement
Not this one if
The scope is still moving — monthly absorbs that better.
What you commit to
A scope that does not move. Anything new is agreed separately.
Monthly
Fits when
- The operation keeps changing underneath you
- Several processes will be tackled in sequence
Not this one if
You want a bounded piece with a known end — fixed price is cleaner.
What you commit to
A cost that does not move. What it is spent on does.