Many Bets, Charge Early
Maximize the number of fast bets, then force a verdict by asking the customer to pay a lot — now
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 85%
Qureshi's core operating principle for his new startup: your probability of hitting something is a function of how many bets you make times each bet's odds, so make lots of bets and cycle through them very quickly. To avoid running a dead bet too long, apply the classic YC test — take the thing to a customer, ask them to pay a lot of money, and if they say no, move to a new problem rather than waiting three weeks.
Origin
From Qureshi's own 'principles' essay and his Palantir experience with fast iteration cycles, combined with the classic Y Combinator advice on charging customers early.
Core principles
- 01Probability of success rises with the number of bets made, weighted by each bet's odds.
- 02Making many bets and cycling fast is one of the easiest ways to almost guarantee a hit.
- 03Willingness to pay a lot of money is the sharpest signal a bet is real.
- 04A 'no' should end the bet fast — do not wait three weeks like most founding teams.
- 05The hard judgment call is telling a failing bet from one you are quitting too soon.
How to run it
- 1
Place many bets deliberately
Rather than betting everything on one idea, spin up a portfolio of bets, understanding your hit probability is a function of bet count times individual odds.
- 2
Cycle through them very quickly
Test each bet as early as possible and move fast between them, rather than nurturing any single one for weeks before validation.
Watch out The honest tension is knowing whether a bet is truly failing or you are quitting too soon — do not pretend this away.
- 3
Force a verdict: ask for real money now
Take the thing to a customer and ask them to pay a lot of money. Their willingness (or refusal) is the fastest, truest signal on the bet.
Pro tip Asking for a large amount, not a token amount, is what makes the signal trustworthy.
- 4
On a no, move to a new problem
If they say no, find a new problem immediately. Do not wait three weeks — the default behavior of most founding teams — because you do not have that kind of time.
In the wild
Qureshi cites the classic YC move: when you take something to a customer, ask them to pay you a lot of money, and if they say no, find a new problem. He contrasts this with what every founding team typically does — waiting three weeks before concluding.
→ Faster kill/keep decisions on each bet, preserving scarce founder time for bets that show real willingness to pay.
Common mistakes
Nurturing a single bet for weeks before testing
Founding teams typically wait three weeks before concluding a bet is dead, burning time they do not have. Testing early and asking for real money forces the verdict in days instead.
Asking for a token amount instead of a lot
A small ask produces a weak signal — people will pay a little for many things. Asking them to pay a lot of money is what separates a real problem from a nice-to-have, so under-asking hides the truth about the bet.
Is it for you?
Best for
Early-stage founders searching for product-market fit who need to test many directions under time pressure
Not ideal for
Deep-tech or long-horizon bets where willingness-to-pay cannot be surfaced quickly and premature abandonment is the bigger risk
From the transcript
“your P success is goes up the more bets you make”
“one easy way to almost guarantee that you'll hit something is just to make a lot of bets and then just kind of like cycle…”
“when you take something to a customer ask them to pay you a lot of money and if they say no then find a new…”
“don't don't wait 3 weeks which is what every founding team typically does because you don't have that kind of time”
From the episode
How Palantir built the ultimate founder factory
Nabeel S. Qureshi (founder, writer, ex-Palantir)