What "Coram Deo" looks like inside a Stripe invoice
The number on the quote is the number on the invoice — even when scope creep would let us bill more invisibly. The mechanism that makes the rule livable, and why it's a conviction rather than a policy.
Coram Deo— "before the face of God" — is an old phrase that points at a specific idea: that what you do when no one is watching is the real measure of what you do. Borrow the framing or leave it; the practical claim is simple. It is a constraint on how we send invoices.
The standard small-shop temptation
Anyone who has run a small studio knows the moment. You quote a project at $X. The work expands by 10% — a couple of extra revisions, a small feature the client asked for in passing, a test environment that turned into a real one. You finish the work. The client is happy. They expect an invoice for $X.
The temptation is to bill $X plus a small "additional scope" line, calling it $1,500 or whatever feels right. The client probably won't flinch — they know they asked for the extras. You'll capture some of the value you actually delivered. Everyone in the agency world considers this normal.
Why we don't do that
We've picked, deliberately, the harder rule: the number on the quote is the number on the invoice. If scope expanded and we didn't write a new mini-quote first, that's our miss, and we eat it. The invoice doesn't move.
The economic logic against this rule is obvious. We're leaving real revenue on the table. The logic for it takes a sentence to explain: the invoice is the same whether the client checks our math or not. If I'm only honest because I might get caught, the honesty is doing nothing — it's just risk management on my reputation. Honesty as a probability calculation isn't honesty.
The mechanism that makes this livable
It's easy to keep this rule when scope holds. The stress test is when scope expands. Our process for that has one mechanic: as soon as a scope addition is requested or discovered, before we do the work, we send a written mini-quote — a one-paragraph email with the new line item, the new number, and a request for a yes / no. If the client says yes, the new amount is added to the invoice. If they say no, the scope returns to original.
This mechanism does almost all the moral work. It prevents the "surprise scope addition on the invoice" problem because there are no surprises — there's just a written record of what was agreed. It also prevents us from quietly absorbing scope expansion at our own loss; the discipline runs in both directions.
What this looks like to clients
The client sees, throughout the project, a small handful of plain-English emails: "You asked for X. That's outside the original scope. We can do it for $Y, included in the final invoice. Reply yes and we'll start."They can say no. They almost always say yes. What they don't see is a final invoice that's 12% larger than the quote with no explanation.
Why this matters past the studio
We don't advertise the phrase on the homepage and we don't expect clients to care about the framing. The practice it produces — strict scope discipline, written mini-quotes, fixed final invoices — is good business on its own terms. The framing is for us; the practice is for the client. We'd rather operate this way universally than figure out which clients to operate this way for.