The handoff that broke in front of the client
A founder-led customer-experience studio with under 20 people ran delivery on the founder's memory and verbal delegation, so a client found an outdated draft beside internal QA notes in a shared review folder.
Undocumented process let unapproved, outdated work reach the client
A model turns the founder's interview into an SOP file that code validates. A runner executes it one step at a time, sealing a receipt per step and halting on any skipped step. A person approves the exact files at a gate before anything reaches the client folder. A one-sentence change rewrites the SOP and re-plans runs in flight.
- the runner wrote 29 work-in-progress files and 8 reached the client's folder, every one traced by the audit to a sealed approval; the 2 injected failures added 0
- the 1-sentence SOP change was written, validated, and live on both runs in flight in under 8 seconds
- Claude
- SOP file validation
- Step runner with sealed receipts
- Human approval gate
- Automated QA checks
- Audit of client folder
- 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.
-
Marketing agency
The clip desk that reads its own drop-off
the desk pinned 6 of 6 drops to a transcript line and an export row; against the drops we designed into the curves ourselves, it found 6 of 6 and 0 of 1 decoy dips fired
-
Brand agency
The coordinator job we rebuilt before it was posted
7 of the 9 bullets on the drafted coordinator posting now run as fixed workflows; 2 stay with people
-
Marketing agency
The skill that had to earn its schedule
Run 1 checked 20 files and units: 8 real defects caught, 19 false flags, and 1 miss