Ideation.

Problems exist on a spectrum defined by two key variables: frequency (how often the user encounters the problem) and pain intensity (how significantly the problem disrupts their life, work, finances, or goals). The most commercially valuable problems sit at the intersection of both high frequency and high pain intensity.

High-frequency, high-pain problems (daily/weekly, severe disruption) carry extremely high commercial opportunity - users will pay a premium. High-frequency, low-pain problems present a moderate volume opportunity but with low willingness to pay. Low-frequency, high-pain problems can support an insurance or one-time premium model. Low-frequency, low-pain problems should generally be avoided entirely.

Investors and experienced founders use a taxonomy to classify problems by urgency:

• Hair-on-Fire: The problem is so urgent the user will try anything immediately. Examples: data breach, medical emergency.

• Painkiller: Causes real, recurring pain. Users compare options, are willing to pay, and seek the best fix. Examples: unreliable logistics, slow invoicing, poor exam scores.

• Vitamin: A "nice to have" - the user sees value but rarely prioritises purchasing. Examples: productivity apps, wellness trackers.

Paul Graham of Y Combinator describes the ideal problem as one where users are already doing something about it: using workarounds, paying for inadequate solutions, or simply tolerating pain. If no one is currently trying to solve it in any way, be suspicious of whether the problem is real.

Developed by Sakichi Toyoda for Toyota's manufacturing process and directly applicable to startup ideation. When you identify a problem, ask "why does this happen?" five times in sequence. Each answer reveals a deeper layer of causation.

Example: Students in India drop out of online courses at very high rates.

Why 1 → They lose motivation after the first few sessions.

Why 2 → The content does not feel relevant to their immediate goals.

Why 3 → Courses are designed for a global audience, not Indian students.

Why 4 → No one has built localised, context-specific learning paths.

Why 5 → Localisation is expensive and platforms optimise for global scale.

Founders who operate at the root-cause level build solutions that competitors cannot easily copy by tweaking a surface-level feature.

1. Urgency - Do people want this solved now, or someday?

2. Pervasiveness - How many people experience this problem?

3. Willingness to pay - Would people pay money to solve it, or expect it free?

4. Underserved - Are existing solutions inadequate, or is the market already well-served?

5. Founder-problem fit - Do you have unique insight, access, or experience that gives you an edge here?

Idea generation and idea evaluation are fundamentally different cognitive modes and must be kept strictly separate. When generating ideas, suspend all judgment entirely. Volume matters far more than quality at this stage. When evaluating, be ruthless. Never mix the two in the same session.

Keep a daily record of every moment of friction you experience: things that annoy you, tasks that take longer than they should, processes that feel broken. Do this for two to four weeks before evaluating any ideas. Most of your best ideas will emerge from this catalogue, because you have first-hand experience with the problem - the most powerful form of validation a founder can have.

Major technological, demographic, or regulatory shifts create temporary windows where new solutions become possible. The smartphone enabled Uber. Cheap cloud computing enabled the SaaS industry. UPI penetration across India enabled an entire generation of fintech startups.

Key trends to monitor: Smartphone adoption (Paytm, Dream11, ShareChat) → UPI infrastructure (Razorpay, PhonePe, CRED) → 4G rollout (Hotstar, YouTube India) → Remote work (Notion, Zoom) → Generative AI (Krutrim, Sarvam AI).

Instead of asking "how do we solve this problem?", ask "how could we make this problem dramatically worse?" This inversion forces your brain to identify the mechanisms that cause the problem. Once you have a list of ways to worsen the problem, reverse each item. The reversal often reveals non-obvious solutions that direct brainstorming would not produce.

Many great businesses exist at the intersection of two domains that had not previously been meaningfully connected. Healthcare + AI, logistics + social commerce, education + gaming. List your areas of knowledge, interest, and experience. Draw explicit connections between them. The intersections form your primary search space for original ideas.

Go to places where your target customers live their lives and observe them without intervening. Watch how people shop at a kirana store. Notice what is inefficient, what causes visible frustration, and what people work around with improvised solutions. This technique produces insights that no survey can replicate, because you are watching real behaviour rather than reported behaviour.

Look at a business model that has worked in one country or sector and ask whether it can be transferred to a different market. Meesho adapted social commerce from China's Pinduoduo. CRED borrowed the curated credit card rewards concept from US Amex. Zepto borrowed the dark-store model from European quick-commerce players. The key is not blind copying but understanding why the model works and whether the conditions exist in your target market.

TAM (Total Addressable Market) - the entire global demand for what you offer if you had 100% market share. Confirms the category is worth pursuing.

SAM (Serviceable Addressable Market) - the portion of TAM you can realistically reach given your geography and go-to-market model.

SOM (Serviceable Obtainable Market) - the share of SAM you can realistically capture in your first 2-3 years. Investors care most about this.

Worked Example: A tutoring app for Class 10-12 students in Maharashtra. TAM = all EdTech spending in India (~₹40,000 crore). SAM = Maharashtra, Class 10-12 students with smartphones and intent to pay (~₹800 crore). SOM = 2% capture in Year 2 = ₹16 crore.

Can you actually build the product with the skills and resources available to you right now? The key question is not "is this possible in the world?" but "is this buildable by us, now, with what we have?" If the honest answer is no, you have three options: acquire the necessary capability, simplify the product, or find a different problem within reach.

Can the business be run on an ongoing basis? This includes supply chain requirements, customer support capacity, regulatory compliance, and ongoing team requirements. Operational complexity is one of the most common silent killers of startups that have great products - the product works, customers love it, but the business cannot be run reliably at scale.

Can the business model generate revenue in excess of its costs, and on what timeline? Key questions:

• What is the cost to acquire one customer? (Red flag if CAC > lifetime revenue)

• What does it cost to serve one customer monthly? (Red flag if serving costs > 70% of revenue)

• When does the business reach gross profit per unit?

• How much capital is required to reach break-even?

Product Business: A tangible or digital item sold repeatedly without new effort each time. Highly scalable - each additional unit costs almost nothing to produce. Gross margins: 60–90%. Valued at revenue multiples (3–10× ARR for SaaS).

Service Business: A human-delivered output requiring time and effort per client. Limited by human hours - scaling requires proportional hiring. Gross margins: 20–50%. Valued at profit multiples (5–10× EBITDA).

The most valuable businesses in the world are predominantly product businesses, because the marginal cost of serving one additional customer approaches zero. This is why software companies like Zepto or Razorpay attract premium valuations that a service business of the same revenue would never receive.

Modern startups often blend both models. A SaaS company might offer professional services for enterprise implementation. A consulting firm might productise its most common deliverables into templated tools. The key is to be intentional about where you sit on the spectrum and to understand the implications for your cost structure, valuation, and team design.

Developed by Alex Osterwalder, the canvas has two sides that must be aligned for a business to achieve product-market fit:

Customer Profile (right side):

• Jobs - what the customer is trying to accomplish

• Pains - the frustrations and obstacles they experience

• Gains - the outcomes and benefits they hope for

Value Map (left side):

• Products and Services - what you offer

• Pain Relievers - how your offering reduces their pains

• Gain Creators - how your offering produces their desired gains

Fit occurs when your Value Map directly addresses the Customer Profile.

Use this template to force clarity:

For [target customer] who [problem], our [product name] is a [category] that [key benefit]. Unlike [primary alternative], we [primary differentiator].

Worked Example: "For Class 11-12 students in Maharashtra who cannot afford or access quality JEE coaching, our PrepEdge platform is an adaptive learning application that personalises daily practice to each student's weak areas. Unlike physical coaching centres, we deliver at one-tenth the cost with no fixed schedule."

Before designing any MVP, identify your single riskiest assumption - the one belief that, if proven wrong, would immediately kill the idea. For most early-stage startups, this is not a technical question. It is a human behaviour question.

Common riskiest assumptions and the right MVP:

• "People will pay for this solution" → Landing page with a paid pre-order

• "Suppliers will participate in this marketplace" → Manual concierge process before building the platform

• "Users will complete the core action" → Wizard of Oz MVP

• "Customers will return without being prompted" → Single-feature product measuring organic return rate

• "The unit economics will work at scale" → Small-batch pilot charging real money

1. Concierge MVP - Manually deliver the service before building technology. Example: Airbnb founders renting air mattresses from their own apartment.

2. Wizard of Oz - The user thinks they interact with automation, but a human fulfils the task behind the scenes. Example: An "AI" recommendation engine that is actually a human analyst.

3. Landing Page - A page describing a product that does not yet exist. Measures intent via sign-ups or pre-orders. Example: Early-access waitlist before any development begins.

4. Prototype - A clickable mockup with no working backend. Tests UX and workflow assumptions. Example: A Figma prototype shared with target users.

5. Single Feature Build - Build only the one feature that is the core value proposition. Example: WhatsApp launched as messaging only. Uber launched as black cars in San Francisco only.

Ask your active users one question: "How would you feel if you could no longer use this product?" Options: Very disappointed / Somewhat disappointed / Not disappointed / Not applicable.

If 40% or more answer "Very disappointed," you likely have product-market fit. Below 40%, continue improving the product before scaling. This benchmark has been validated across hundreds of startups globally.

• Day-30 Retention - Above 20% is notable; above 40% is strong.

• Net Promoter Score (NPS) - Above 50 is considered strong.

• Organic New User Share - More than 30% organic is a positive signal.

• Monthly Churn Rate - Below 5% monthly for consumer; below 2% for B2B SaaS.

• Net Revenue Retention - Above 100% is exceptional.

Early traction from friends, family, early adopters, or paid promotions can masquerade convincingly as product-market fit. Common sources of false PMF:

• Launch-day excitement that does not sustain into week two

• Traction from a niche community that does not generalise to the broader market

• Retention driven by heavy discounting that disappears when pricing normalises

• High acquisition, low retention → Do not scale. Fix the core product experience first.

• Strong retention in a tiny cohort → Expand cohort size gradually. Test whether the pattern holds.

• Users love it but won't pay → Test different pricing models or reconsider whether the market exists.

• Strong at launch, rapid drop-off → Map the user journey carefully. Find where value breaks down.

Developed by Clayton Christensen at Harvard Business School. The theory holds that customers do not buy products; they hire them to get a job done. The classic example: people do not buy a drill - they hire it to make a hole. And they do not want a hole; they want a picture on their wall.

Jobs exist across three categories:

• Functional Job - the core task the user is trying to accomplish.

• Social Job - how the user wants to be perceived by others.

• Emotional Job - how the user wants to feel.

JTBD thinking reveals hidden competitors. Customers hired milkshakes in the morning not because they were hungry, but to make a boring commute more interesting. The milkshake's main competitor was therefore a podcast, not a burger.

Developed by W. Chan Kim and Renée Mauborgne at INSEAD. The best companies do not compete in existing market spaces ("red oceans") but create new market spaces ("blue oceans") where competition is irrelevant.

The Four Actions Framework:

• Eliminate - Which factors the industry takes for granted should be removed entirely?

• Reduce - Which factors should be reduced below the industry standard?

• Raise - Which factors should be raised above the industry standard?

• Create - Which factors should be created that the industry has never offered?

Ash Maurya's adaptation of Osterwalder's Business Model Canvas for early-stage startups. Nine boxes, completed in one sitting (maximum 20 minutes) and treated as a living document:

1. Problem - Top 1-3 problems your customers have.

2. Customer Segments - Who specifically you are building for.

3. Unique Value Proposition - The single, clear reason to buy from you.

4. Solution - How you solve the stated problems.

5. Channels - How you reach and acquire customers.

6. Revenue Streams - How you make money.

7. Cost Structure - Your most significant costs.

8. Key Metrics - The one or two numbers that tell you the business is working.

9. Unfair Advantage - Something that cannot easily be copied or bought.