Writing a Business Case That Survives a Handoff in a Startup Campaign
On startup campaigns, the business case usually loses fidelity at the first handoff. A short retrospective practice for delivery managers — and the three lines that don't get lost.
The handoff that loses the why is the handoff that loses the project
On a startup campaign, the business case is what justifies trade-offs at 11pm on day 18. The handoff has to carry the why or the trade-offs go wrong.
Startup campaign projects almost always involve a handoff — from the founder who briefed it to the marketer who runs it; from the in-house lead to the agency; from the agency to a freelancer; from the freelancer back. At each handoff, fidelity is lost. The handoff pattern is most visible in the business case, because the business case is what people skim, not read, when picking up a project.
The retrospective version of this work — running it after a campaign ships — surfaces a consistent finding: the lines that get lost in handoff are not the ones the original author would predict.
What gets lost in handoff, in order
When you walk through completed startup campaigns and ask each person who held the project, 'what did you understand the business case to be at the moment you took it over,' three things consistently disappear:
1. The unstated outcome. What the founder actually wanted, which was rarely the literal words of the brief. The handoff carries the brief but not the founder's tone. 2. The trade-offs already made. The original PM negotiated cost or scope with leadership before brief; the new owner inherits the brief but not the negotiation. 3. The known risks the team accepted. The original team agreed to ship without a piece of due diligence; the next owner does not know that decision was made.
The written business case typically captures the first set of decisions clearly and the others poorly. Three handoffs later, the project is operating on a fictional version of the original case.
- Day 0Write the business case with the three extra linesStandard format plus the three handoff-survival lines.
- Day 1 of any handoffWalk through the three lines firstBefore discussing tactics, the new owner reads the three lines. Disagreement at this point is cheaper than disagreement at week three.
- End of campaignRetro: did the lines hold?In the retro, ask each person who held the project: 'were the three lines accurate?' The answers update the standard template.
Three-line handoff test
0 / 4- The founder's real desired outcome is captured in their language, not the team's
- Trade-offs already made are written down with the reasoning
- Accepted risks are documented with who accepted them and when
- Each new project owner walks through these three lines before touching tactics
This practice doesn't require a heavier business case format — it requires three more lines. The reason it works specifically in startup campaign settings is that those projects depend on context that is socially obvious to the original team and structurally invisible to the next one. Writing the context down is what makes the handoff survivable. For the more elaborate version of this work in software settings, see the moderate software handoff guide; for the broader set of mistakes around business cases on creative projects, see the twelve mistakes article.