I sign a receipt when a piece of work is done. Not drafted, not in review, not 80% complete, done. The work is in the client’s hands, the client has tested it, and both of us have agreed that the engagement moves on. The receipt is a single line in a Notion database. It has a date, a name, a category, and a one-line summary. That’s it.
The only metric that matters
In a single-operator studio, the vanity metrics that larger agencies track, headcount, monthly recurring revenue, client logos on a wall, are not useful. They do not predict anything. The metric that actually predicts the health of the studio is receipts per quarter. A quarter with eight receipts is a healthy quarter. A quarter with two is a slow quarter. A quarter with zero is a crisis.
The metric is also the only one the client sees, although they would not call it a receipt. They would call it a delivery. The number of times a client signs off on a deliverable in a quarter is the number of times they renew. The two numbers are correlated almost perfectly. Clients who get deliverables, renew. Clients who wait, churn.
28 days is a forcing function
I picked 28 days for a reason. It is one lunar cycle, four working weeks, and slightly shorter than a calendar month. It is also a number small enough to plan around and large enough to ship something meaningful. Every engagement has a 28-day horizon. Every 28 days, something ships. The cadence is non-negotiable.
The cadence is non-negotiable. If a 28-day cycle cannot ship a meaningful piece of work, the scope of the engagement is wrong.
What breaks the cadence
Three things break the cadence. Scope creep, decision latency, and the urge to over-polish. The first is solved by fixed-scope agreements, every engagement has a written scope, signed before work begins, and any change is a new engagement. The second is solved by hard deadlines on client feedback, three business days, otherwise the work proceeds with documented assumptions. The third is solved by the receipt itself, done is done, the work ships, and the next cycle starts.
A receipt, in this system, is not a deliverable. A deliverable is a file. A receipt is a sign-off. The two are different because a file can be “done” and still be wrong. A sign-off is the client’s confirmation that the file is right. Without the sign-off, the work is in transit. With it, the work is closed.
The Notion database
The Notion database is a single table. Date, client, category (BRAND / PRODUCT / ENGINEERING / STRATEGY), summary, receipt link. Every quarter, I run a report. Eight rows in a healthy quarter. Two in a slow quarter. The report does not lie, and it does not negotiate. It tells me what happened.
“Clients who get deliverables, renew. Clients who wait, churn.
If you run a single-operator studio, I recommend the receipt. Not the invoice, not the project, not the deliverable. The receipt. It is a small discipline with outsized effects on the shape of the year. The receipts add up. The year adds up. The studio survives because the receipts are the spine.
I run delivery on fixed scope and fixed price. See how engagements work or open a channel.
