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.

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 →

Alchemy Pro CRM

SEP 01 2026

THE RECEIPTAlchemy Pro CRM

BuildAlchemy Pro CRM

Requirements< 24 hours

Crew build~2 days / 748 tasks

Final-mile human hours61.8h

Deterministic estimate11,912h

Use cases covered105 / 105

Specs traced into shipped code125

StatusOpen source at public go-live

“We replaced our CRM in three weeks. Here’s the receipt — and the source code.”

View full receipt →

AUG 15 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 →