Budget Kill Number

A budget kill number is the hard ceiling written into the one page constraints sheet that stops a design project the instant it is crossed. It is not the price the client agrees to pay. It is the number that kills the engagement if exceeded so both sides avoid the slow bleed of unpaid revisions and creeping scope. The kill number forces the conversation about money to happen on day one instead of week nine when everyone is already pissed off. It lives right next to the decider name the done definition and the out of scope list. Cross it and the team invoices for work completed pauses new deliverables and renegotiates the next phase from a position of facts not favors.

It is not a flexible range labeled competitive or investment level. It is not the internal number you keep in the agency spreadsheet while telling the client everything is fine. It is not a padded quote you hope never gets tested. Those versions create exactly the theater the article rails against. A budget kill number is specific signed and visible to the decider from the first meeting. It turns vague promises into mechanical triggers that protect both the studio margin and the client from surprise invoices.

Look at the 2023 identity project for a fintech startup preparing for Series B. The sold number sat at 85000 dollars. The kill number was set at 103000 dollars a clean 21 percent buffer. The constraints sheet listed both figures next to the single decider the VP of marketing. By week six the client had added motion versions for every mark three extra pitch deck templates and localization files for two new markets none of which appeared in the done definition or out of scope list. The team tracked every hour in Toggl. When the internal total hit 102400 dollars they sent the kill notice delivered the original asset folder and stopped. The client did not love the message but respected the document they had signed. A new change order for the extra work was scoped at full rate and signed two days later. The original project shipped on the kill date instead of drifting into a money losing nightmare that would have consumed the entire next quarter.

Contrast that with a 2022 website project for an HR tech company that had no kill number. The proposal said 65000 dollars. The team absorbed rounds of feedback that added micro animations a full illustration library and three additional landing pages. By the time the project limped across the finish line the real cost had reached 112000 dollars. The agency ate the difference wrote it off as a learning experience and never worked with that client again. The absence of a kill number turned a profitable gig into a six month resentment machine. The brief had beautiful adjectives and a perfect mood board but no mechanical off switch.

Stripe runs its internal feature launches with the same posture even though the public never sees the brief. Docs ship the same day as the feature because the budget kill number and the timeline kill date were locked before engineering started. Linear ships every six weeks because the accountable owner knows exactly what budget and scope will kill the cycle. Vercel treats the deploy log as the launch surface because the brief defined done so tightly that extra nice to haves never survived the first review against the kill criteria. These teams do not guess at money. They write the number that ends the work and build everything else around it.

Use the budget kill number on every fixed bid design engagement especially with new clients or founders who have never shipped before. Write it in the brief read it out loud at kickoff and get the decider to initial it. Tie it directly to the out of scope list and the one metric that matters so the entire document becomes one self enforcing contract. Do not use it on pure time and materials retainers where the client pays monthly and controls the priority queue. Those relationships need monthly caps and explicit priority rules instead. Never use it as a surprise weapon midway through a project. Springing a kill number on week eight that was never discussed on week one destroys trust faster than any scope creep.

The kill number also protects clients. When the figure is visible from day one they think harder before requesting the twentieth round of logo explorations. They understand that every addition has a mechanical consequence instead of assuming the studio will absorb it to stay friendly. This clarity alone removes 70 percent of the passive aggressive inbox threads that kill design projects.

Write the two numbers every single time. Sold at this. Kill at that. Fifteen to twenty five percent feels like the right gap in practice. It gives the team room to absorb honest estimation errors without forcing them to hide overruns or lie about progress. Anything tighter creates panic. Anything wider invites sloppy scoping. The exact gap gets negotiated with the decider in the room on the day the constraints sheet is signed.

The budget kill number is the difference between running a design business and running a charity with mood boards.