12. Market Sizing
Market sizing is not an investor slide exercise. It is a way to understand whether the opportunity can support the company you want to build. A market can be too small for venture capital and still be a wonderful business. A market can look huge in reports and still be impossible for you to enter.
Good market sizing helps you answer: if we win our first wedge, what can this become?
The core sizing question is: how many reachable customers have this problem, what can they realistically pay, and what expansion path makes the first wedge worth pursuing?
For founders, market sizing should create discipline, not decoration. The goal is to understand whether the opportunity fits the company you want to build: venture-scale startup, profitable software business, services-led company, community business, marketplace, or cash-flow business.
What This Chapter Covers
Section titled “What This Chapter Covers”- TAM, SAM, and SOM in plain language.
- Bottom-up versus top-down sizing.
- First market versus future market.
- India-specific sizing traps.
- How to build a useful early market-size estimate.
TAM, SAM, SOM
Section titled “TAM, SAM, SOM”| Term | Meaning | Useful Question |
|---|---|---|
| TAM | Total addressable market. | If everyone who could use this bought, how large is the total opportunity? |
| SAM | Serviceable available market. | Which part can our product and geography realistically serve? |
| SOM | Serviceable obtainable market. | What share can we plausibly win in the next few years? |
The mistake is making TAM the hero. Investors may ask for TAM, but founders should care more about the path from beachhead to expansion. A believable SOM with a strong wedge is often more useful than a giant TAM with no entry plan.
What Market Size Should Prove
Section titled “What Market Size Should Prove”Market sizing should prove different things at different stages.
Idea stage
Section titled “Idea stage”You are checking whether the problem is worth discovery. A rough estimate is enough. The goal is to avoid spending months on a market that obviously cannot support your ambition.
MVP stage
Section titled “MVP stage”You are checking whether the first segment is big enough for meaningful learning and early revenue. The exact TAM is less important than the density of reachable customers.
Fundraising stage
Section titled “Fundraising stage”You need to show a credible path from wedge to large opportunity. Investors do not need every number to be perfect, but they need to trust your logic.
Scaling stage
Section titled “Scaling stage”You need sharper segmentation, pricing, adoption, churn, gross margin, and channel assumptions. At this stage, bad sizing can create hiring and burn mistakes.
Top-Down Sizing
Section titled “Top-Down Sizing”Top-down sizing starts with reports: industry revenue, number of businesses, consumer spend, government data, or analyst estimates. It is useful for orientation, but dangerous when copied blindly.
Example:
“India has X million SMEs. If we charge each Y per month, the market is huge.”
This ignores digital maturity, willingness to pay, buyer access, churn, onboarding cost, support cost, and whether the SME segment is one market at all.
Use top-down sizing only as a rough boundary.
Top-down sizing is most useful when it helps you understand category scale, growth direction, adjacent markets, investor expectations, and whether the opportunity is obviously too small or plausibly large. It is weak for predicting your first customers.
Bottom-Up Sizing
Section titled “Bottom-Up Sizing”Bottom-up sizing starts with real customer segments.
Formula:
Number of target customers x realistic annual revenue per customer = annual market opportunity
Better version:
Reachable customers x adoption rate x annual contract value x gross margin = practical opportunity
Example:
| Input | Estimate |
|---|---|
| Target segment | Indian D2C brands doing 100-1,000 orders/day |
| Number of reachable companies | 5,000 |
| Likely adoption over 5 years | 20% |
| Annual revenue per customer | Rs 1.2 lakh |
| Practical annual revenue opportunity | Rs 120 crore |
This may be less glamorous than a report-based TAM, but it tells you what kind of company you may actually build.
Bottom-Up Sizing Worksheet
Section titled “Bottom-Up Sizing Worksheet”Use a worksheet instead of one heroic TAM number.
| Input | Conservative | Base | Optimistic |
|---|---|---|---|
| Reachable customers in beachhead | |||
| Percentage reachable through chosen channels | |||
| Adoption over 3-5 years | |||
| Annual revenue per customer | |||
| Gross margin | |||
| Sales and onboarding cost | |||
| Churn or replacement rate | |||
| Expansion revenue |
Then calculate:
reachable customers x adoption x annual revenue x gross margin
This is less exciting than a giant market report, but it is much harder to fool yourself. If the business only works in the optimistic case, the founder needs stronger evidence before hiring or raising against the plan.
Sizing From A Prospect List
Section titled “Sizing From A Prospect List”For the first market, build a real list before trusting the model.
Ask:
- Can we name 100 companies or users in this segment?
- Can we find contact paths for at least 50?
- Can we get 20 qualified conversations without paid fantasy channels?
- Do at least 10 show the same pain?
- Do at least 5 show commitment through time, data, payment, or pilot interest?
If you cannot build a prospect list, the market may still be real, but it is not yet reachable by you. Reachability is part of market size. A customer you cannot find is not part of your obtainable market today.
Budget-Based Sizing
Section titled “Budget-Based Sizing”For B2B, market size often comes from existing budgets. Ask:
- What budget line does this replace or create?
- Is the buyer already spending on software, people, agencies, tools, compliance, ads, support, or manual operations?
- What is the cost of the current workaround?
- Who owns that budget?
- Is the spend recurring or one-time?
If the problem has no budget, you may need to sell strategic value, risk reduction, revenue lift, or cost savings. That is possible, but harder than shifting existing spend.
Three Useful Sizing Models
Section titled “Three Useful Sizing Models”Use more than one model so one fantasy assumption does not control the answer.
Customer-count model
Section titled “Customer-count model”Number of target customers x annual revenue per customer
Useful for SaaS, services, and B2B tools.
Transaction model
Section titled “Transaction model”Number of transactions x take rate or fee
Useful for marketplaces, fintech, logistics, commerce, and payment-linked products.
Workload model
Section titled “Workload model”Number of workflows or tasks x value per workflow
Useful for AI, automation, compliance, back-office, support, and operational tools.
If all three models give wildly different answers, that is not a problem. It is a signal to understand the business model more deeply.
Sensitivity Analysis
Section titled “Sensitivity Analysis”Most early sizing models are wrong. The question is which assumption matters most.
Stress-test:
| Assumption | What if it is half as good? |
|---|---|
| Number of reachable customers | Does the beachhead still justify focus? |
| Price | Can the business support sales and support? |
| Adoption | Is the channel or urgency weaker than expected? |
| Gross margin | Is delivery too service-heavy? |
| Churn | Does acquisition need to be much cheaper? |
| Sales cycle | Can runway survive the buying process? |
| Support load | Does price match customer effort? |
Founders often discover that the market is not too small; the model is too fragile. For example, a SaaS plan may look strong at Rs 1 lakh ACV and 20% adoption, but weak at Rs 36,000 ACV, 8% adoption, and high support. That does not mean the startup is bad. It means pricing, segment, onboarding, or GTM must change.
User-Based Sizing
Section titled “User-Based Sizing”For consumer products, user count is not enough. You need monetizable behavior.
Estimate:
- Target users.
- Reachable users.
- Activation rate.
- Retention rate.
- Paying conversion or revenue per active user.
- Acquisition cost.
- Gross margin.
Large user numbers can hide tiny revenue if willingness to pay is weak, ad inventory is low value, or retention is poor.
Revenue Quality in Sizing
Section titled “Revenue Quality in Sizing”A market that supports Rs 100 crore of high-margin recurring software revenue is different from Rs 100 crore of low-margin, service-heavy, support-heavy revenue. Include gross margin and operating burden in your thinking.
Ask:
- Does revenue repeat?
- Does usage expand?
- Does servicing cost rise with revenue?
- Does the customer segment churn?
- Does collection take too long?
- Does the product require heavy customization?
First Market Versus Future Market
Section titled “First Market Versus Future Market”Your first market is not your final market. Strong startups often begin narrow and expand.
Think in layers:
- First customer type.
- First workflow.
- First geography.
- Adjacent customer type.
- Adjacent workflow.
- Larger platform or product line.
Example:
- Start: compliance workflow for funded Indian startups.
- Expand: compliance and finance operations for Indian SMEs.
- Expand further: finance automation for companies selling globally from India.
The first wedge must be specific. The future story must be plausible.
Expansion Logic
Section titled “Expansion Logic”A good expansion story has adjacency, not fantasy.
Strong expansion:
- Same buyer, adjacent workflow.
- Same workflow, adjacent customer segment.
- Same customer, higher-value module.
- Same category, new geography with similar behavior.
- Same data asset, new insight product.
Weak expansion:
- “Then we sell to everyone.”
- “Then we launch in all countries.”
- “Then we add AI.”
- “Then large enterprises will buy.”
- “Then we become a platform.”
Investors and founders should both ask: what proof from the first market gives us the right to enter the second?
India Market Sizing Traps
Section titled “India Market Sizing Traps”Formal vs Informal Markets
Section titled “Formal vs Informal Markets”India has large informal markets. Spend may exist but not appear in clean data. Customers may pay agents, staff, brokers, cash vendors, or family networks instead of software.
Urban vs Non-Urban
Section titled “Urban vs Non-Urban”Tier 1 behavior cannot represent India. Pricing, language, trust, payment behavior, and support expectations can change outside metros.
Digital Maturity
Section titled “Digital Maturity”Some segments are smartphone-heavy but software-light. Others use digital tools but still rely on manual reconciliation, WhatsApp, Excel, or phone calls.
Price Sensitivity
Section titled “Price Sensitivity”A large number of users does not mean a large revenue market. Ask what customers already pay for and what budget line you can replace.
Distribution Cost
Section titled “Distribution Cost”If customers require field sales, implementation, training, or local trust, your obtainable market may be much smaller than your theoretical market.
Data Quality
Section titled “Data Quality”Public data may be outdated, inconsistent, or too broad. Combine reports with primary interviews and observable business lists.
Buyer Concentration
Section titled “Buyer Concentration”Some Indian markets have many users but few real buyers. Students may use a product, but parents, colleges, employers, or coaching institutes may pay. Users can be large while budget is concentrated elsewhere.
Collection Reality
Section titled “Collection Reality”Revenue potential is not the same as cash collected. Long payment cycles, TDS, GST issues, purchase order processes, and informal negotiations can reduce practical market size.
Support Cost
Section titled “Support Cost”High-touch onboarding, WhatsApp support, training, language needs, and field operations can make a large market less attractive if price points are low.
Market Sizing Process
Section titled “Market Sizing Process”- Define the beachhead segment.
- Estimate how many such customers exist.
- Estimate how many are reachable through your channels.
- Estimate realistic annual revenue per customer.
- Estimate adoption over 3-5 years.
- Compare gross margin and sales cost.
- List expansion segments.
- State assumptions clearly.
Sizing Sanity Checks
Section titled “Sizing Sanity Checks”After building the model, stress-test it:
- Can we name 50 real customers in the first segment?
- Can we reach them through a channel we control or can afford?
- Does the assumed price match current spend or visible pain?
- Does gross margin support sales, onboarding, support, and collections?
- Does adoption require behavior change that the model ignores?
- Does the first market produce enough proof for the next market?
- Is the expansion path adjacent or imaginary?
- Are we counting users when the payer is someone else?
- Are we assuming US or global ARPU in an Indian segment without evidence?
Investor Slide Versus Founder Model
Section titled “Investor Slide Versus Founder Model”You may eventually show a clean TAM/SAM/SOM slide. Internally, keep a messier founder model.
| Investor slide | Founder model |
|---|---|
| Shows the large opportunity. | Shows the first reachable market. |
| Uses simple categories. | Uses segment, channel, price, margin, and adoption assumptions. |
| Explains expansion story. | Tests whether expansion is adjacent and earned. |
| Communicates ambition. | Guides hiring, burn, pricing, and GTM. |
Do not let the investor slide become the operating plan. The slide can show the mountain. The founder model must show the first climb.
A smaller, honest model is better than a large model that hides weak assumptions.
Venture-Scale Versus Good Business
Section titled “Venture-Scale Versus Good Business”Not every good market is a venture-scale market. That is fine, but founders must know the difference.
Venture-scale usually needs:
- Large reachable market.
- Fast growth potential.
- High gross margins or strong marketplace economics.
- Repeatable acquisition.
- Retention or network effects.
- Ability to deploy capital efficiently.
- Expansion beyond the first niche.
A good non-venture business may have:
- Smaller market.
- Strong cash flow.
- Services-heavy delivery.
- Slower but profitable growth.
- Founder-led sales.
- High customer trust and low churn.
The danger is raising venture money for a market that wants a slower, profitable company. Market sizing should inform financing strategy.
Assumption Quality
Section titled “Assumption Quality”Label every number:
- Evidence: based on customer list, invoices, usage, interviews, paid pilots, government data, or reliable reports.
- Estimate: based on partial evidence and reasonable extrapolation.
- Guess: plausible but unverified.
Your next discovery work should replace guesses with evidence. A sizing model that admits uncertainty is more useful than a confident spreadsheet built on fiction.
Example Bottom-Up Walkthrough
Section titled “Example Bottom-Up Walkthrough”Suppose you are building software for small diagnostic labs in India.
Start narrow:
- Segment: independent labs in three metro regions.
- Number of likely reachable labs: 2,000.
- Early adoption over five years: 15%.
- Annual revenue per lab: Rs 60,000.
- Revenue opportunity: Rs 1.8 crore annually in the first wedge.
That may be too small for a venture-scale company by itself. Then test expansion: multi-branch labs, clinics with in-house diagnostics, billing and reporting modules, inventory workflows, patient communication, and integrations if relevant.
Now the founder can see whether the first wedge is a learning wedge, a cash-flow business, or the start of a larger platform.
Sizing Assumption Audit
Section titled “Sizing Assumption Audit”The most useful part of market sizing is not the final number. It is seeing which assumptions control the number. A founder should know which assumptions are solid, which are fragile, and which need fieldwork.
Create an assumption table:
| Assumption | Current Number | Evidence Level | Risk If Wrong | Next Validation Action |
|---|---|---|---|---|
| Reachable customers in wedge | Evidence / estimate / guess | Build named prospect list. | ||
| Decision makers who feel urgency | Evidence / estimate / guess | Interview buyers, not only users. | ||
| Annual price customer will accept | Evidence / estimate / guess | Test paid pilot or proposal. | ||
| Sales cycle | Evidence / estimate / guess | Track first 10 real deals. | ||
| Gross margin | Evidence / estimate / guess | Model onboarding, support, infrastructure, and service cost. | ||
| Retention | Evidence / estimate / guess | Track usage after first value. | ||
| Expansion path | Evidence / estimate / guess | Identify adjacent workflows or segments. |
Do not hide weak assumptions in a beautiful spreadsheet. Highlight them. Your next operating plan should attack the weakest high-impact assumptions first.
First Wedge Size Versus Company Size
Section titled “First Wedge Size Versus Company Size”The first market does not need to be the whole company, but it must be honest about its job.
There are four common jobs for the first wedge:
| Wedge Job | What It Means | Financing Implication |
|---|---|---|
| Learning wedge | Small but reachable segment that teaches the product and buyer. | Keep burn low; do not over-hire for scale. |
| Cash-flow wedge | Segment can produce profitable early revenue. | Useful for bootstrapping or extending runway. |
| Reference wedge | Segment creates logos, case studies, or credibility for a bigger adjacent market. | Measure transferability of references. |
| Platform wedge | Segment creates data, supply, demand, integrations, or network density. | Needs proof that the wedge compounds. |
A weak first wedge is one that is small, hard to reach, low-margin, non-referential, and does not lead anywhere. A strong first wedge may be small but gives the company leverage: learning, revenue, trust, data, distribution, or expansion.
Wedge-To-Expansion Sizing
Section titled “Wedge-To-Expansion Sizing”After sizing the first wedge, write the expansion chain:
- First exact segment.
- Adjacent customer with similar workflow.
- Adjacent workflow inside the same customer.
- Adjacent geography or language market.
- Adjacent product line or monetization layer.
For each step, write what must be true before expansion:
| Expansion Step | What Must Be True | Proof Needed |
|---|---|---|
| Segment 1 to segment 2 | Pain and buying process are similar. | References transfer and sales message still works. |
| Workflow 1 to workflow 2 | Customer trusts you inside the operation. | Customers request the adjacent workflow and will pay. |
| City or region expansion | Channel and support can repeat. | Acquisition, onboarding, and retention stay healthy. |
| Product-line expansion | The first product has retention and credibility. | Existing customers adopt the second product. |
This protects you from fake TAM thinking. Expansion is not a slide. Expansion is a sequence of earned permissions.
Sizing Falsification Plan
Section titled “Sizing Falsification Plan”A good market-size model should be easy to attack. If the model only confirms your optimism, it is not yet a founder tool.
List the assumptions that, if wrong, would break the opportunity:
| Assumption | Optimistic Version | Conservative Version | What Would Prove It Wrong? | Test |
|---|---|---|---|---|
| Number of reachable customers | Build actual prospect list. | |||
| Buyer existence | Interview budget owners. | |||
| Price | Ask for paid pilot or invoice-level commitment. | |||
| Adoption rate | Track conversion from qualified conversations. | |||
| Retention | Follow usage after first value. | |||
| Sales cost | Measure founder hours and channel cost per qualified buyer. | |||
| Support load | Track onboarding, training, and exception handling. | |||
| Expansion path | Ask whether adjacent segment accepts current proof. |
Then choose the three assumptions with the highest impact and weakest evidence. Those are not spreadsheet cells. They are next week’s research agenda.
The Founder Sanity Check
Section titled “The Founder Sanity Check”Ask:
- If the market is as large as we claim, why has the problem not already been solved well?
- What changed that makes the opportunity newly accessible?
- Which customers can we actually reach in the next 90 days?
- What price can we defend without fantasy ROI?
- Which segment is big enough for the next funding or bootstrapping milestone?
- What would make this a good business but a poor venture-backed business?
- What hidden service, support, compliance, or distribution cost shrinks the real market?
Investors may ask for TAM. Founders need something more useful: a believable sequence from first wedge to durable company.
Reachable Market Audit
Section titled “Reachable Market Audit”The most practical market-size number in the early days is not TAM. It is the number of customers you can credibly identify, contact, qualify, and serve.
Build a reachable market audit:
| Layer | Count | Evidence Source | Confidence |
|---|---|---|---|
| Total theoretical customers | Reports, registries, platforms, public data. | Low / medium / high | |
| Customers matching your narrow segment | Filters, directories, associations, communities. | Low / medium / high | |
| Customers you can name | Prospect list. | Low / medium / high | |
| Customers you can reach | Email, phone, intro, community, partner, event. | Low / medium / high | |
| Customers with urgent trigger | Recent hiring, compliance, growth, complaint, migration, budget. | Low / medium / high | |
| Customers likely to pay now | Discovery, pilots, past spend, purchase intent. | Low / medium / high |
If a market has 100,000 theoretical customers but only 50 you can name and 5 you can reach, the immediate market is not 100,000. Your first job is distribution learning, not scale hiring.
India Data Caveat
Section titled “India Data Caveat”Indian market data can be noisy. Categories may be informal, public datasets may lag, and businesses may not describe themselves the way software founders segment them. Use multiple weak signals rather than pretending one report is precise:
- Public registries and directories.
- Trade associations.
- GST or compliance maturity signals where appropriate and lawful.
- Job postings.
- Marketplace listings.
- Local consultants and service providers.
- WhatsApp, community, and regional networks.
- Payment behavior and invoice reality from discovery.
Do not turn noisy data into fake precision. Mark confidence openly.
Revenue-Weighted Sizing
Section titled “Revenue-Weighted Sizing”Early founders often count customers equally. That hides the business reality. A customer who is easy to reach, pays faster, needs little support, and renews is not equal to a customer who looks large but takes months of founder time.
Build a revenue-weighted sizing view:
| Segment | Theoretical Count | Reachable Count | Likely Price | Sales Effort | Support Load | Gross Margin Risk | Confidence |
|---|---|---|---|---|---|---|---|
| Low / medium / high | Low / medium / high | Low / medium / high | Evidence / estimate / guess |
Then add a founder-hours view:
Expected first-year revenue per customer- expected acquisition effort- onboarding/support effort- discounting/payment delay risk= practical attractiveness of the segmentThis is not a finance model. It is a reality check. In many Indian markets, the segment with the biggest logo value may not be the best first market because sales cycles, payment terms, implementation, and support can consume the company.
Use revenue-weighted sizing when choosing between:
- Enterprise versus SMB.
- Tier 1 versus Tier 2 or smaller-city customers.
- Software-only versus service-assisted delivery.
- Direct sales versus partner-led distribution.
- India-first versus global-from-India wedge.
A small reachable segment with high urgency, fast sales, repeatable onboarding, and references can be a better first market than a giant theoretical market with slow trust and unclear payment.
Sizing-To-Burn Guardrail
Section titled “Sizing-To-Burn Guardrail”Market sizing should control how aggressively the company spends. A founder should not hire, raise, or expand as if the future market is already proven when only the first wedge is understood.
Use a sizing-to-burn guardrail:
| Market evidence | What it supports | What it does not yet support |
|---|---|---|
| Report-level TAM only | Discovery, interviews, small experiments. | Hiring a large team or claiming repeatable GTM. |
| Named reachable accounts | Founder-led sales, narrow product wedge, low-burn validation. | Paid scale or broad market expansion. |
| Pain-qualified buyers | MVP, paid pilots, sharper positioning. | Heavy sales team or multi-city rollout. |
| Paid pilots or early contracts | Small customer success motion, onboarding investment. | Assuming retention, expansion, or venture-scale economics. |
| Retained customers with repeatable acquisition | Hiring around a known motion. | Expanding into unrelated segments. |
| Segment expansion proof | More aggressive fundraising and GTM. | Treating every adjacent market as automatically unlocked. |
The founder’s budget should match the evidence level. If market evidence is low-confidence, keep burn low and learn. If market evidence is strong, spend to exploit what is working.
The hiring test
Section titled “The hiring test”Before hiring for growth, ask:
| Hire | Market-size proof needed |
|---|---|
| SDR or outbound team | Named reachable accounts, clear ICP, working message, repeatable response signal. |
| Sales leader | Founder has closed enough similar deals to show process, objections, cycle, and pricing. |
| Customer success | Onboarding and retention require repeatable human effort, not random custom rescue. |
| Paid marketing | Channel can produce qualified buyers, not only cheap leads. |
| Implementation team | Implementation is part of the model and priced into gross margin. |
| Expansion or partnerships role | First wedge references transfer to adjacent segment or channel. |
If the answer is “we need the hire to discover the market,” be careful. That may be valid for a short experiment, but it is not the same as hiring into a proven market.
The fundraising claim test
Section titled “The fundraising claim test”When fundraising, separate three claims:
| Claim | Evidence required |
|---|---|
| The market can be large | Top-down context, adjacent budgets, structural change, expansion logic. |
| We can enter it | Named accounts, interviews, pilots, first sales, founder access, channel signal. |
| We can scale inside it | Repeatable acquisition, retention, gross margin, sales cycle, references, expansion proof. |
A deck can show all three. But the founder should know which claim is proven and which is still a hypothesis. This honesty improves the pitch because it shows command of the business, not lack of ambition.
India burn caution
Section titled “India burn caution”In India-first markets, a large theoretical market can tempt founders into premature field sales, support hiring, local language expansion, city launches, channel partnerships, or heavy implementation capacity. These costs can arrive before the market has proven willingness to pay.
Use this rule:
Do not build a cost structure for the TAM. Build a cost structure for the evidence-backed wedge.Then expand the cost structure only when the next segment has earned proof: reachable buyers, paid demand, retention, references, and manageable support economics.
Common Mistakes
Section titled “Common Mistakes”- Using huge top-down numbers without a wedge.
- Claiming “1% of a huge market” as strategy.
- Ignoring willingness to pay.
- Treating users as buyers.
- Forgetting sales and support cost.
- Combining unrelated segments into one number.
- Making a VC-scale claim for a non-VC market.
- Ignoring gross margin.
- Forgetting that reachable customers are fewer than theoretical customers.
- Treating a service-heavy opportunity as software-like revenue.
- Assuming global ARPU applies to Indian segments.
- Hiding weak first-market size behind a giant future market.
Reader Action
Section titled “Reader Action”Build a one-page sizing model:
| Segment | Customers | Reachable % | Price/Year | Adoption % | Revenue Potential |
|---|
Fill it with your best current assumptions. Mark each assumption as evidence, estimate, or guess. Your next research task is to replace guesses with evidence.
First-Market Demand Filter
Section titled “First-Market Demand Filter”After sizing the market, filter it down to demand you can actually reach, sell to, serve, and learn from. A large market is not useful if the first reachable customers are not ready to change.
Use this filter:
| Assumption | Current value | Evidence quality | How to test |
|---|---|---|---|
| Number of target customers | Evidence / estimate / guess | Directory, industry data, scraped list, associations, manual count. | |
| Reachable percentage | Evidence / estimate / guess | Outreach tests, channel tests, referral path, search volume. | |
| Buyer budget | Evidence / estimate / guess | Discovery, current spend, invoices, procurement conversations. | |
| Willingness to pay | Evidence / estimate / guess | Paid pilots, price tests, proposal reactions. | |
| Adoption rate | Evidence / estimate / guess | Conversion from outreach, pilot-to-paid, onboarding completion. | |
| Retention | Evidence / estimate / guess | Repeat usage, renewal intent, churn calls, cohort data. | |
| Gross margin | Evidence / estimate / guess | Delivery effort, support load, infra cost, services component. | |
| Sales cycle | Evidence / estimate / guess | Days from first conversation to payment or signed pilot. |
The most important column is not the number. It is evidence quality. A founder should know whether the company is acting on a real market, a reasonable estimate, or a story.
First-market sizing
Section titled “First-market sizing”Separate the first market from the future market:
| Market | Purpose | Question |
|---|---|---|
| Beachhead | Where you get proof. | Can this segment produce real customer evidence within months? |
| Expansion | Where proof can travel. | Which adjacent segment trusts the first segment’s proof? |
| Long-term market | Where the company could become large. | What must become true before this larger claim matters? |
Investors may care about the large market. Founders must care about the first market. You cannot compound into the future market if the beachhead does not buy, use, retain, or refer.
India sizing caution
Section titled “India sizing caution”For India, do not count need as demand. Many people may need a solution but still not have budget, trust, workflow readiness, payment behavior, or decision authority. Mark the gap between:
- People/businesses with the problem.
- People/businesses aware of the problem.
- People/businesses willing to change.
- People/businesses reachable by you.
- People/businesses able and willing to pay now.
The last number is usually much smaller, and much more useful.
Sizing Evidence Ladder
Section titled “Sizing Evidence Ladder”Treat market sizing as an evidence ladder, not a single spreadsheet.
| Level | Evidence | Founder confidence |
|---|---|---|
| 1. Theoretical count | Reports, directories, public databases, broad industry estimates. | Useful for orientation, weak for operating decisions. |
| 2. Reachable count | Named accounts, communities, associations, search results, channel lists. | Useful for first GTM planning. |
| 3. Pain-qualified count | Customers who show recent pain and current workaround. | Useful for narrowing segment. |
| 4. Buyer-qualified count | Pain plus budget owner, approval path, and trust requirement. | Useful for sales planning. |
| 5. Commercially qualified count | Pricing, pilot, proposal, paid test, or procurement signal. | Useful for revenue forecast. |
| 6. Retained count | Customers who continue using and paying. | Useful for real market quality. |
Most early founders stop at level 1. Useful founders climb toward levels 3-5 before making big product, hiring, or fundraising claims.
Bottom-Up Wedge Model
Section titled “Bottom-Up Wedge Model”Build the first market from the bottom up.
Exact segment:Named reachable accounts:Expected response rate:Discovery-qualified accounts:Pilot-qualified accounts:Expected close rate:Average first-year revenue:Expected gross margin:Expected sales/support effort:Then translate to a simple model:
| Input | Value | Evidence quality |
|---|---|---|
| Named accounts reachable in 90 days | Evidence / estimate / guess | |
| Useful conversation rate | Evidence / estimate / guess | |
| Pilot/proposal rate | Evidence / estimate / guess | |
| Close rate | Evidence / estimate / guess | |
| Average first-year revenue | Evidence / estimate / guess | |
| Support/load risk | Evidence / estimate / guess |
Example:
We can identify 600 export manufacturers in two clusters, reach 200 through associations and founder outreach, speak to 40, run 8 paid diagnostics, close 3 annual customers at Rs 3-5 lakh each, and use those references to expand into adjacent clusters.
This is a better first-market claim than “India has millions of SMEs.”
Investor Slide Translation
Section titled “Investor Slide Translation”A market-size slide should connect the big market to the first wedge.
Use three layers:
| Layer | What to show |
|---|---|
| Big market | Why the problem can become large if the company wins. |
| Serviceable market | Which segments have the budget, workflow, and adoption readiness. |
| Beachhead | Which first customers are reachable now and why they will produce proof. |
The slide should answer:
- Why is the opportunity large enough eventually?
- Why is the first segment narrow enough to win?
- What proof from the first segment can travel to the next segment?
- Which assumptions are still unproven?
Do not hide a weak beachhead behind a huge TAM. A serious investor or advisor will ask how the founder gets from first customer to large market.
Market Size Confidence Levels
Section titled “Market Size Confidence Levels”Not every market-size number deserves the same confidence. Label your numbers so the team does not treat guesses like facts.
| Confidence | Source | How to use |
|---|---|---|
| Low | Reports, broad assumptions, social media, rough estimates. | Directional story only. Do not hire or spend heavily from this. |
| Medium | Named prospect list, customer interviews, budget clues, channel data. | Useful for beachhead planning and experiment design. |
| High | Paid pilots, conversion rates, retained customers, sales cycle, gross margin. | Useful for operating plan and fundraising narrative. |
The confidence note
Section titled “The confidence note”For every sizing model, write:
The number we believe:Source:Confidence:Largest assumption:What would make this number smaller:What evidence will improve confidence:Decision this number supports:The last line is important. A market-size number should support a decision: enter, narrow, fundraise, hire, build, expand, or stop. If it supports no decision, it may be decoration.
Serviceable First Market
Section titled “Serviceable First Market”TAM can be huge while the first serviceable market is small. Founders need both.
Define the serviceable first market:
| Filter | Question |
|---|---|
| Reach | Can we identify and contact these customers within 90 days? |
| Pain | Do they have the problem now, not someday? |
| Budget | Can someone approve payment? |
| Trust | Can we create enough credibility to start? |
| Workflow | Can our product or service deliver value without heavy custom work? |
| Support | Can we support them at current team size? |
| Reference | Will one win help sell the next similar customer? |
If the first serviceable market cannot produce enough learning, revenue, or proof, the company may need a different wedge even if the long-term market is large.
Founder warning
Section titled “Founder warning”Do not say:
The market is 10,000 crore, so getting 1 percent is enough.Say:
There are 800 reachable accounts in our first wedge. We can reach 200 this quarter, expect 40 serious conversations, 8 pilots, and 3-5 paying customers if the pain and trust assumptions hold.That second statement is smaller, but it can be tested.