Every business is built on a stack of assumptions. Some you’re aware of. Most you’re not. And the ones you don’t see coming are the ones that take you down.
The Devil’s Advocate post was about arguing against your idea broadly. This is more surgical — it’s about identifying the **specific assumptions** your business depends on and systematically testing whether they’re true.
—
## Assumption Mapping: What Your Business Believes to Be True
Every element of your Lean Canvas is an assumption until proven otherwise:
– **”Freelancers have this problem”** — assumption. Have you confirmed this with 20+ freelancers?
– **”They’d pay $25/month to solve it”** — assumption. Has anyone actually opened their wallet?
– **”I can reach them through Twitter”** — assumption. Have you gotten a single customer that way?
– **”My churn will be under 5%”** — assumption. Based on what data?
– **”The competitor gap I see is real”** — assumption. Have customers confirmed they feel the gap?
Write down every claim your business model makes. Each one is an assumption that needs testing. The more central the assumption, the more dangerous it is if wrong.
**Critical assumptions** (business dies if wrong):
– The problem exists and is painful enough to pay to solve
– The target audience has money and willingness to spend it
– You can reach the audience cost-effectively
– Your solution actually solves the problem
**Important assumptions** (business struggles if wrong):
– Your pricing is in the right range
– Your churn rate is sustainable
– You can build and maintain the product sustainably as a solo founder
– The market is large enough to support a viable business
Test critical assumptions first. If any turn out to be false, everything downstream is moot.
—
## The Riskiest Assumption Test (RAT)
The Riskiest Assumption Test is simple: identify the single assumption that, if wrong, would most completely invalidate your business. Then design the cheapest, fastest test to validate or kill it.
**Example:**
– Riskiest assumption: “Freelance developers will pay $20/month for automated invoice tracking.”
– Cheapest test: Create a landing page describing the product. Drive 200 targeted visitors to it. Include a “Buy Now” button at $20/month. Measure how many people click it (or better yet, how many enter payment info).
– Result: If 5%+ click “Buy Now,” the assumption has some support. If 0.2% click, it’s likely wrong.
– Timeline: 1 week.
– Cost: Nearly $0 (excluding ad spend to drive traffic).
This isn’t perfect validation. But it’s cheap, fast evidence that’s infinitely better than no evidence.
—
## Killing Assumptions With Conversations
The fastest assumption-killing tool isn’t a landing page test. It’s a conversation.
But it needs to be the right kind of conversation. Most founders have the wrong kind:
**Bad validation conversation:**
“I’m building a tool that auto-tracks freelance invoices. Would you use it?”
“Yeah, sounds useful!”
This tells you nothing. People say “sounds useful” to be polite. It costs them nothing to say yes.
**Good validation conversation:**
“How do you currently handle invoicing? … What’s the most frustrating part? … How much time do you spend on it per week? … Have you tried any tools for this? … Why did you stop using them? … If something solved [specific pain], what would it be worth to you?”
This reveals whether the problem is real, how they currently cope, why existing solutions failed, and what price range is realistic — all without revealing your idea or inviting polite lies.
The best question is often: **”What have you already tried?”** If someone has actively spent time or money trying to solve this problem, it’s a real problem. If they’ve never bothered looking for a solution, it might not be painful enough to motivate action.
—
## Continuous Killing: Not Just an Early-Stage Exercise
Assumption-testing isn’t just for pre-launch. Your business generates new assumptions constantly:
– “Customers love the new feature” — Do they? Check usage data.
– “Our marketing is working because signups are up” — Is it? Or is it a one-time spike from a mention you didn’t track?
– “We should expand into [new market]” — Should you? Have you validated demand there?
– “Churn is fine” — Is it? Have you checked this month’s numbers?
Build an ongoing habit: every month, write down the 3 biggest assumptions your business is currently operating on. For each, write down what evidence supports or undermines it. If evidence is thin, design a test.
—
## 🔨 Your Action Item: The Assumption Stress Test
1. **Write down 10 assumptions** your business model relies on. Be specific. “People will pay” is too vague. “Freelance designers earning $50-100K will pay $20/month to consolidate client feedback” is specific.
2. **Rank them by risk.** Which ones, if wrong, would be most devastating?
3. **Pick the top 3** and design a test for each. The cheapest, fastest test that would give you evidence.
4. **Run the first test this week.** Speed matters more than perfection. A quick-and-messy test this week beats a perfect test next month.
5. **Document the results.** Assumption confirmed, partially confirmed, or killed. Adjust your business model accordingly.
—
**CTA Tip:** Become an expert in spotting what could destroy your business — not to be pessimistic, but to be prepared. Every assumption you test and validate makes your business more resilient. Every assumption you test and kill saves you months of wasted effort. The founders who fail hardest are the ones who assumed everything and tested nothing. Constantly try to kill your own idea — the parts that survive are the ones worth building on.
—
*Next up: What if your idea survives the stress test but the competition is brutal? Let’s talk about oversaturation and replaceability — and whether your idea has staying power.*
—
—