Skip to main content

Proof of build

The Receipts

Every build we talk about is listed here with its receipt: what it cost in human hours, how long it took, and how you can check.

We budget two hours of human time per use case. No build has spent it. The receipts below are how you check.

AUG 13 2026

THE RECEIPTTenkiller
Scope11 features · 106 use cases · 765 planned tasks
Estimated the traditional way2,892 story points × 4 hours = 11,568 hours ≈ 72 team-weeks
Build one — human hours38, one non-developer directing the crew
Build two — human hours433 logged, across five senior engineers
CalendarBuild one: 21 days · Build two: 11 weeks, part-time
CommitsBuild one: 6,813 · Build two: 162 — separate repos, no shared authors
Scope carriedBuild one: all 106 · Build two: 58, phase one of a deliberate two-phase split
The 2-hour testBuild one: ≈ 21 min per use case against a 120-minute budget
Requirements, both buildsunder 12 hours, once, with no standing meeting after it

“One requirements package. Two teams. Two working applications.”

View full receipt →

Product Campaign Manager

CIRCA 2025

THE RECEIPTProduct Campaign Manager
Requirements & discovery6 hours through Alchemist
Crew build execution9 hours to a functional, cloud-deployed system
Features · use cases10 features · 395 use cases — 100% delivered
Test scripts1,086, tied to acceptance criteria
Delivery4 weeks of calendar against a 50-week plan
Cost$250K actual against a $2.27M plan — roughly $2M unspent
Team3–4 against a planned 9
StatusRetired — the capabilities it orchestrated moved into the platform

“The application we kept rebuilding until rebuilding was the method.”

View full receipt →

AUG 10 2026

THE RECEIPTGlitchDash
Attempts14 — thirteen discarded on purpose; the name of the repo is the count
Scope7 features · 53 use cases · 492 planned tasks
Traditional estimate6,780 hours ≈ 42 weeks (in the repo, written at kickoff)
Crew buildovernight — 474 agent commits, agents named in the log
Away Team2 passes, same day, one engineer — fix list in the commit messages
Human commits, total7, across 3 people
What went wrongprinted, not hidden — the BUILD_ERRORS ledger is in the repo
Cost to throw a build awaylow enough that we did it thirteen times

“A kid designed a video game. We built it fourteen times.”

Play & View Receipt →