Answer-first guide
What is a Project Bet?
A Project Bet is a bounded commitment of resources intended to reduce one important project uncertainty. It records the desired outcome, allocation budget, Evidence Threshold, permitted scope, excluded work, first evidence-producing action, and review timing before the result is known.
Method guide · Updated July 30, 2026
Why use a Project Bet?
A Project Bet separates a temporary allocation from an unlimited commitment. It makes the builder state what the next 1–6 weeks are meant to learn before scope expands or the evidence bar moves. It is not a prediction that the project will succeed.
What belongs in a Project Bet?
- Primary Outcome
- The concrete result the allocation is meant to produce.
- Biggest Uncertainty
- The most decision-relevant unknown the work should reduce.
- Allocation Budget
- The maximum hours, optional spending, and review horizon committed to this bet.
- Evidence Threshold
- The observable signal and decision rule that would justify considering another allocation.
- Permitted Scope
- Work allowed because it directly supports the bet.
- Excluded Work
- Tempting work intentionally kept outside the current allocation.
- First Evidence-Producing Action
- The next action most likely to reduce the uncertainty.
- Early Review Trigger
- A condition that makes waiting for the scheduled review unnecessary.
Project Bet example for a solo SaaS builder
Validate paid demand before building integrations
- Biggest uncertainty
- Will qualified solo developers pay $10/month?
- Allocation
- 10 hours across 14 days, maximum $100.
- Evidence Threshold
- At least three qualified written payment commitments or completed checkouts.
- Permitted scope
- Targeted outreach, interviews, manual onboarding, and a payment page.
- Excluded work
- Integrations, analytics dashboard, referral system, and unrelated visual polish.
This example does not claim that the product will succeed. It makes the next allocation test willingness to pay instead of rewarding unrelated implementation progress.
How do you write a useful Evidence Threshold?
A useful threshold names an observable signal, a quantity or decision rule, a source, and an evaluation date. “Finish the landing page” restates a task. “Five qualified visitors start checkout within 14 days” describes reviewable evidence.
Project Bet integrity checklist
- The uncertainty can change the next allocation.
- The threshold is observable and is not merely a completed task.
- The scope fits the hours and spending boundary.
- Excluded Work protects the test from attractive distractions.
- The first action produces evidence rather than only implementation.
- The review date is 3–60 days after activation.
- A continuation becomes a new linked bet, not a silent extension.
Common Project Bet questions
Is a Project Bet the same as a project plan?
No. A project plan organizes work. A Project Bet bounds the resources and evidence used to decide whether more work is justified.
Can the bet change after activation?
Yes, but material changes preserve the original value, proposed value, remaining allocation, and reason.
What happens when the threshold is not reached?
The user reviews the evidence and chooses whether to change direction, pause, stop, complete, or define a new bet with a different condition.