The scope sheet that lists what it doesn't know
A nine-person design-only studio with no engineers was asked by its longest-retained client for a trade-show lead capture flow and had no way to estimate it.
Can't scope a technical client request without guessing a price
It reads the owner's hand-drawn sketch and recorded walking memo, then builds a scope sheet of steps, systems and human checkpoints. Hedged phrases become open questions with who must answer, never assumed answers, and sketch-memo mismatches are flagged for the owner. Hour ranges stay wide until questions are answered, and a labeled prototype supports the client conversation.
- 4 open questions listed, 0 answered by assumption (by construction: the run fails if any question carries an answer)
- 3 sketch-memo mismatches flagged, 0 resolved by the build; each held for the principal
- SVG sketch parsing
- Transcript parsing
- Rule-based reconciler
- Static HTML prototype
- Puppeteer
Same problem?Send it over.
Tell me what your version looks like and which tools it runs in. I reply with how I would build it.
-
Media and creative agency
The Monday margin watch that reads jobs, not people
1,124 timesheet rows read, 31 person ids dropped at load, 0 found in any output file
-
Advertising agency
The account defense that starts before the RFP arrives
one approved record, 9 sizes, 1.402 seconds for the still family, an average of 0.156 per size
-
Performance marketing
The retainer, on the record
all 6 approved spend changes carry a named approver, and the gate sent 1 approval back for a missing reason