This is placeholder content shipped with the FoundryLume theme. Replace it with your own writing before launch — the structure is here to show how the blog handles long-form posts, headings, callouts, lists and code.
Most operating plans fail for a boring reason: nobody opens them after the kickoff meeting. They are written in the register of a pitch deck — confident, comprehensive, and completely unfalsifiable.
A plan that survives contact with reality has a different shape. It is shorter, it names people, and every line on it can be proven wrong.
Start with the three bets, not the thirty tasks
If your team cannot name the quarter’s bets from memory, you do not have a plan — you have a backlog with ambition attached.
Three is the number that works. Two feels like you are not trying. Four is where focus starts to leak.
For each bet, write down:
- The claim. One sentence, phrased so it could turn out to be false.
- The owner. One name. Not a team, not two names with a slash.
- The evidence. What you would need to see to believe it.
- The date. When you will look at the evidence and decide.
Score confidence, then argue about the score
The single highest-leverage habit we have seen is attaching a confidence percentage to each bet and updating it weekly.
It sounds like theatre. It is not. The number forces a specific conversation: why did confidence move from 60% to 40% this week? That question has an answer. “How is the project going?” does not.
A worked example
| Bet | Owner | Confidence | Moved because |
|---|---|---|---|
| Design partners will pay at $89 | AR | 82% | 7 of 12 signed a letter of intent |
| Self-serve onboarding lifts activation | JB | 64% | Week-2 cohort flat, needs another test |
| Two enterprise pilots close by Q3 | SO | 41% | Procurement added a security review |
The third row is the useful one. At 41% you are not “on track with risks” — you are probably wrong, and you have six weeks to find out cheaply.
Write the update before you need it
A monthly investor update written the night before is a work of fiction assembled from memory. Written continuously, it becomes a byproduct of the work rather than a task on top of it.
The format we like is deliberately unglamorous:
## Month in one line
[What changed materially. Not "we made great progress".]
## Metrics
MRR · Runway · Activation · Churn — with last month's number beside it.
## Bets
Each bet, its confidence, and what moved it.
## Asks
Two specific things. Names, intros, decisions.
## Lowlights
The thing you would rather not write down. Write it down.The lowlights section is the one that builds trust. Investors have read several hundred updates that contain only good news, and they have learned exactly what that means.
What to cut
If you are trimming a plan down to one page, cut these first:
- Anything describing the market rather than your response to it.
- Adjectives in front of nouns you have not measured.
- Initiatives with no owner. They are wishes.
- The roadmap beyond one quarter. You will rewrite it anyway.
The test
Hand the page to somebody who joined two weeks ago. If they can explain your quarter back to you in ninety seconds, the plan works. If they ask a clarifying question about priority, it does not — and that is a cheap thing to learn on a Tuesday rather than at the end of the quarter.