11. Understanding Markets

A market is not a large number in a pitch deck. A market is a group of customers with a painful need, money or attention to spend, alternatives they already use, channels through which they can be reached, and timing that makes change possible. If you cannot describe the people, workflow, budget, and trigger, you do not yet understand the market.

Founders often say, “The market is huge.” That may be true and still useless. A huge market with no reachable wedge is worse than a small market where customers are desperate, accessible, and willing to pay now.

The core market question is: who is already trying to make progress, what are they doing today, and why would they change now?

What This Chapter Covers

• What a market really includes.
• How to identify market categories.
• What makes a market high quality.
• India-specific market realities.
• How to turn market understanding into a decision.

What A Market Really Is

A market has more moving parts than “customers.”

Part	Founder Question
Customers	Who has the problem?
Buyers	Who approves or pays?
Users	Who uses the product daily?
Influencers	Who shapes trust or recommendations?
Competitors	Who sells a similar solution?
Substitutes	What do customers use instead, including Excel, WhatsApp, interns, agencies, or doing nothing?
Channels	How can you reach customers repeatedly?
Regulations	What rules shape behavior, risk, or adoption?
Trust networks	Whose recommendation matters?
Workflows	Where exactly does the problem appear?
Budgets	Which existing spend can shift to you?

The most common early mistake is ignoring substitutes. Your competitor may not be another startup. It may be a spreadsheet, a family member, a CA, a local agent, a manual process, or the customer’s willingness to tolerate pain.

Market Is Behavior, Not Labels

Labels are useful shorthand, but they can hide reality. “Healthcare,” “SMB,” “edtech,” “fintech,” “D2C,” “logistics,” or “AI tools” are not markets by themselves. They are arenas. A real market is visible in behavior:

• People search for a solution.
• Teams hire someone to handle the problem.
• Businesses buy tools, agencies, consultants, or services.
• Customers create spreadsheets, WhatsApp groups, workflows, or hacks.
• Communities discuss the pain repeatedly.
• Budgets are assigned.
• Regulators or platforms force action.
• Existing vendors disappoint customers in patterned ways.

When founders cannot describe behavior, they usually compensate with market-size claims. That is backwards. Start with behavior, then size the opportunity.

The Market Map

Build a market map before building a product roadmap.

Layer	What To Capture	Why It Matters
Customer	Who feels the pain?	Product and messaging start here.
Buyer	Who pays or approves?	Sales and pricing depend on this.
Workflow	Where does the pain appear?	Product scope comes from workflow.
Trigger	Why now?	Timing creates urgency.
Alternative	What do they use today?	Competition is the status quo.
Channel	How can you reach them?	Markets without channels are hard to enter.
Trust	Who influences adoption?	Especially important in India.
Budget	What spend can move?	Willingness to pay beats compliments.

The map should be specific enough that a salesperson, product person, and founder would make the same first-100-customer list.

Market Evidence Levels

Not all market evidence is equal. A founder should separate claims from behavior.

Evidence Level	What It Looks Like	How Much To Trust It
Opinion	”This market is big” or “people need this.”	Weak. Useful only as a prompt.
Complaint	Repeated frustration in calls, reviews, communities, or support threads.	Better, but still not budget.
Workaround	Customers use Excel, WhatsApp, agencies, staff, scripts, or manual checks.	Stronger. Pain has created behavior.
Spend	Customers already pay tools, people, consultants, or vendors.	Strong. Budget exists somewhere.
Switching attempt	Customers tried alternatives and can explain why they failed.	Very strong. The category is active.
Pull	Customers ask for a pilot, data review, implementation, or commercial terms.	Strongest early signal.

Market understanding improves when you move from opinion to behavior. Do not build a company on opinion-level evidence.

Market Pull Versus Founder Push

Every market requires some push. Founders must sell, explain, and earn trust. But if every step requires founder force, the market may be weak or too early.

Signs of pull:

• Customers ask for next steps without being chased.
• Prospects introduce similar prospects.
• Buyers compare you to existing alternatives.
• Customers share messy workflow details because they want help.
• Deadlines, regulation, growth, or cost pressure create urgency.
• One customer success story makes the next sale easier.

Signs of too much push:

• Prospects agree in conversation but never follow up.
• Every buyer needs education from zero.
• You cannot find current spend or workarounds.
• The use case changes for every customer.
• Customers want the product only if it is free.
• The founder must personally convince every stakeholder.

A good market does not remove sales work. It makes sales work compound.

Market Categories

Existing Market

Customers already understand the problem and spend money. This is easier to explain but harder to differentiate. You must show why your product is meaningfully better, cheaper, faster, simpler, or more focused.

New Market

Customers do not yet have a clear category. This can create huge upside but requires education. Education is expensive. If you are a small startup, be careful about markets where every sale begins with explaining why the problem matters.

Re-Segmented Market

You enter an existing market with a sharper wedge: cheaper for a specific customer, simpler for non-experts, India-first, mobile-first, AI-native, compliance-ready, or built for a neglected segment.

Low-End Disruption

Incumbents overserve some customers. You offer a simpler, cheaper, good-enough option. This can work well in India where many customers cannot afford enterprise-grade solutions but still need better workflows.

Niche Wedge

You solve one painful problem for one narrow segment. This is often the best starting point. A narrow market can be a doorway, not a ceiling.

Regulated Or Platform-Dependent Market

Regulation and platforms can create opportunity but also dependency. If a rule, API, marketplace, or platform changes, your business may change overnight.

How Market Category Changes Strategy

Different market types require different founder behavior.

Existing market strategy

You do not need to explain the problem. You need to explain why you are better for a specific customer. The risk is competing head-on with companies that already have brand, distribution, and features.

Founder focus: differentiation, wedge, distribution, and switching.

New market strategy

You must teach the customer how to think. This can create a big company, but it requires education, patience, proof, and often more capital.

Founder focus: urgent use case, evangelism cost, category language, and survival wedge.

Re-segmented market strategy

You take a known market and serve a neglected segment better: smaller customers, a vertical, India-first, mobile-first, compliance-heavy, AI-native, lower-cost, or simpler.

Founder focus: clear contrast with incumbents and proof that the neglected segment is valuable.

Platform-dependent strategy

You benefit from another ecosystem: Shopify, WhatsApp, ONDC, Google, Apple, Salesforce, Zoho, AWS, OpenAI, or a marketplace. Distribution can be easier, but dependency is real.

Founder focus: platform risk, integration depth, data portability, and alternate channels.

Regulated strategy

Regulation can create pain and defensibility. It can also slow adoption and require credibility.

Founder focus: compliance expertise, trust, sales cycle, and customer risk tolerance.

Market Quality

A good market has several of these traits:

• Demand is growing.
• Customers already spend money or time on the problem.
• Pain is frequent or expensive.
• Existing solutions are fragmented, outdated, or distrusted.
• Customers are willing to switch.
• You can reach buyers through identifiable channels.
• Margins can support growth and support.
• The product can become more valuable with scale, data, integrations, brand, or network effects.
• Regulation or infrastructure creates a tailwind instead of only friction.

Use this simple filter:

Question	Good Sign	Bad Sign
Is there current spend?	Customers already pay someone or hire people.	They only say they like the idea.
Is pain urgent?	Delays cost money, time, compliance, or reputation.	The problem is annoying but ignored.
Can you reach customers?	There are clear communities, lists, channels, or referrals.	You do not know where buyers gather.
Can you win a wedge?	A specific segment is underserved.	You must beat everyone everywhere.
Is timing improving?	New behavior, technology, regulation, or budget creates change.	Nothing has changed except your interest.

Market Quality Scorecard

Score each item from 1 to 5:

1. Pain intensity.
2. Frequency of pain.
3. Existing spend.
4. Reachability.
5. Switching willingness.
6. Competitive dissatisfaction.
7. Margin potential.
8. Timing tailwind.
9. Trust path.
10. Expansion potential.

A market with a modest size but high urgency, reachability, and willingness to pay can be a better startup market than a huge category where nobody trusts new vendors.

Market Learning Plan

Before building heavily, run a market learning plan. The goal is to move from category opinion to customer evidence.

Week	Work	Output
1	List customer types, alternatives, channels, and triggers.	First market map.
2	Interview buyers, users, and people using substitutes.	Pain, workflow, and language notes.
3	Observe the current workflow or collect artifacts.	Screenshots, spreadsheets, scripts, invoices, or process maps.
4	Test reachability through one or two channels.	Response rate and qualified conversations.
5	Test commitment: data, time, pilot, payment, or referral.	Evidence level above opinion.
6	Decide whether to continue, narrow, change segment, or stop.	Market decision memo.

This plan prevents founders from spending months “researching the market” without increasing evidence quality. Every week should produce something more concrete than confidence.

Market Interview Questions

Use interviews to understand behavior, not to receive compliments.

Ask:

• When did this problem last happen?
• What triggered it?
• Who was involved?
• What did you do first?
• Which tools, people, vendors, or workarounds did you use?
• What did it cost in time, money, risk, delay, or stress?
• What happens if you do nothing?
• Who approves spend for this problem?
• What have you already tried?
• Why did the current solution survive despite its problems?
• What would make switching worth the effort?
• Who would you ask before trusting a new solution?

Ask for artifacts whenever possible: screenshots, reports, spreadsheets, invoices, emails, WhatsApp flows, SOPs, dashboards, proposals, or support tickets. Artifacts reveal the real market better than polished answers.

Continue, Narrow, Or Stop

After enough discovery, make an explicit market decision.

Decision	Choose when	Next move
Continue	Pain, spend, reachability, and timing are visible.	Build or sell a focused MVP.
Narrow	Pain exists but only in one subset.	Rewrite segment, use case, and outreach list.
Change wedge	Market is real but your entry point is weak.	Pick a different workflow, persona, channel, or trigger.
Pause	Evidence is interesting but not urgent.	Keep watching timing signals while working elsewhere.
Stop	No urgent pain, no spend, no reachability, and weak timing.	Document learning and move on.

Stopping is not failure. It is saved time. The founder’s job is not to defend the original idea; it is to find a market where the company can earn pull.

Red Flags

Be careful when:

• Everyone says the idea is interesting but nobody has tried to solve it.
• There is no existing spend, workaround, or urgent behavior.
• Buyers and users disagree about the pain.
• The product requires a behavior change that customers do not want.
• You cannot name a channel to reach 100 prospects.
• The market depends on one platform you do not control.
• Adoption requires many stakeholders before value appears.
• Customers only want a free tool.
• The problem is real but happens too rarely.

Red flags do not always mean stop. They mean the founder must narrow, change wedge, or gather stronger evidence.

India Angle

India has many markets that look small on paper but are large in informal behavior, and many markets that look large in reports but are hard to monetize. Watch for:

• Formal vs informal spend.
• Offline workflows hidden behind digital language.
• Regional variation in language, income, trust, and channel behavior.
• High price sensitivity combined with high service expectations.
• Long payment cycles in B2B.
• Trust built through references, community, founders, and support.
• Compliance or documentation gaps that affect adoption.

For India-first products, market understanding often requires fieldwork. Spend time with shops, clinics, factories, schools, agents, accountants, sales teams, and operators. The spreadsheet will not show the workaround.

Also watch the difference between digital adoption and software adoption. A customer may use UPI, WhatsApp, Instagram, and smartphones daily but still resist paying for a SaaS dashboard. Digital comfort does not automatically mean software budget.

Trust networks matter. In many Indian markets, a CA, consultant, distributor, senior operator, teacher, doctor, community leader, or peer founder can shape buying more than your website. Market maps should include these trust nodes.

Practical Process

1. Define the customer segment in one sentence.
2. Write the workflow where the problem appears.
3. List current alternatives and substitutes.
4. Identify buyer, user, influencer, and blocker.
5. Find evidence of current spend or serious time cost.
6. List the channels through which you can reach 100 prospects.
7. Name the timing change that makes now better than before.
8. Decide whether to continue, narrow, or leave the market.

Market Understanding Memo

Write a one-page memo before committing serious build time:

Section	What To Write
Market	The exact customer and workflow, not a broad category label.
Current behavior	What customers do today and how often.
Existing spend	Money, staff time, agency spend, or opportunity cost.
Buyer map	User, buyer, influencer, blocker, and budget owner.
Channel	Where the first 100 prospects can be reached.
Timing	What changed recently and why it creates urgency.
Trust path	Why customers would trust a new company.
Wedge	The first segment or workflow you can win.
Risk	The assumption most likely to break the market thesis.

If the memo reads like a pitch deck, rewrite it. This is an operating document, not marketing.

Founder Fieldwork

For two weeks, do this:

• Interview 15 customers in one narrow segment.
• Observe at least three workflows in the real environment.
• Collect screenshots or examples of current workarounds.
• Ask what they already pay for.
• Ask what they tried and abandoned.
• Ask who they trust for advice.
• Ask what would make switching risky.
• Write the exact words customers use for the problem.

You are looking for repeated patterns, not one dramatic anecdote.

Market System Map

Before you decide a market is attractive, draw the system around the customer. A founder often sees only the user and the problem. The market includes everyone who shapes whether money, trust, data, and workflow can move.

Map five flows:

Flow	What To Map	Founder Question
Money flow	Who pays whom today, and from which budget?	Where does the budget already exist?
Trust flow	Who does the customer trust before trying something new?	Whose approval lowers perceived risk?
Workflow flow	Where does the work start, move, pause, and finish?	Which step is painful enough to change?
Decision flow	Who can say yes, who can say no, and who can delay?	Who must be convinced before adoption?
Data flow	What information is created, copied, verified, and reported?	What data access or accuracy risk could block the product?

This map prevents shallow market thinking. For example, a school product is not only sold to teachers. It may involve principals, parents, trustees, fee collection, regional language support, WhatsApp groups, exams, local reputation, and procurement timing. A clinic product is not only sold to doctors. It may involve reception staff, patients, lab partners, insurance, compliance, and daily queue pressure.

If one flow is unclear, the market is not yet understood. Do not solve that gap with confidence. Solve it with fieldwork.

Budget And Trust Flow

Markets open faster when budget and trust already move in your direction. Markets stay slow when the user has pain but the buyer has no budget, or when the buyer has budget but does not trust a new vendor.

Use this worksheet before committing to a segment:

Question	Strong Answer	Weak Answer
Who pays today?	A named role already spends money on the problem.	Nobody owns the cost clearly.
What budget does it come from?	Software, operations, marketing, compliance, training, procurement, or founder discretionary spend.	”They will create a new budget if we explain it.”
Who must trust us?	A clear buyer, operator, adviser, partner, or community gatekeeper.	”The user will convince everyone.”
What proof reduces risk?	Reference, pilot result, data security note, ROI, migration plan, founder credibility, local support.	”They will understand after the demo.”
What channel carries trust?	Existing relationship, community, consultant, partner, customer referral, founder network, event, content.	Random cold traffic with no credibility.

In India, trust often travels through people before it travels through a website. This does not mean the product can be weak. It means the first market may need a relationship path, reference path, community path, or local proof path before a scalable channel works.

Market Reality Review

Run this review after every 10 serious customer conversations:

1. What did we believe about the market before these conversations?
2. Which belief got stronger?
3. Which belief got weaker?
4. Which buyer, blocker, or influencer did we miss?
5. What current workaround appeared more than three times?
6. What evidence of existing spend did we find?
7. What trust concern repeated?
8. What segment now looks easier to reach?
9. What segment looked attractive but is not urgent?
10. What one change should we make to the wedge?

The discipline is not to collect quotes. The discipline is to change the market map when reality disagrees with the founder.

Market Risk Register

A market can look attractive and still be dangerous. The danger usually hides in one of eight places. Create a risk register before committing serious product, hiring, or fundraising effort.

Risk	What It Sounds Like	How To Test It
Budget risk	”Users love it, but nobody owns the budget.”	Ask who paid for the current workaround and what budget line would change.
Workflow risk	”They like the concept, but daily use is unclear.”	Shadow the workflow and map the exact before/after steps.
Trust risk	”They need to know someone else has used it.”	Test whether references, pilots, guarantees, or local support reduce hesitation.
Timing risk	”This will matter soon.”	Look for behavior change today: hiring, spend, compliance, migration, or active search.
Distribution risk	”We can reach them online.”	Run channel tests and count qualified conversations, not impressions.
Switching risk	”Our product is better.”	Ask what would make them abandon the existing workaround this quarter.
Implementation risk	”The buyer says yes, but rollout is hard.”	Identify who configures, trains, imports data, and handles exceptions.
Economics risk	”The market is huge.”	Check acquisition cost, support load, gross margin, and realistic price.

Rate each risk as green, yellow, or red. A market with one red risk can still work if you know how to reduce it. A market with many yellow risks is often more dangerous because the founder keeps explaining them away.

Risk Owner

Every market risk needs an owner. If everyone owns “go learn more about the market,” nobody owns it.

Use this tracker:

Risk	Owner	Next Evidence Needed	Date	Decision It Affects
Budget				Pricing, segment, buyer persona.
Workflow				Product scope, onboarding, MVP.
Trust				Channel, proof, references.
Timing				Burn, launch timing, wedge.
Distribution				GTM plan, hiring, marketing spend.
Switching				Positioning, migration, sales process.
Implementation				Customer success, support, product design.
Economics				Business model, fundraising, scale plan.

The purpose is not paperwork. The purpose is to stop market risk from becoming a vague feeling.

Non-Consumption Map

Founders study competitors but often ignore non-consumption: people who have the problem but do not buy anything.

Non-consumption can mean:

• The pain is annoying but not urgent.
• The customer does not know a better solution exists.
• The current workaround is free enough.
• The buyer has no budget.
• Trust is too low.
• Setup feels too hard.
• The customer has been disappointed before.
• The problem is real but politically unsafe to admit.

Map non-consumers separately from active buyers:

Non-Consumer Group	Problem They Have	Why They Do Not Buy	Trigger That Could Change Behavior	Founder Action

This matters especially in India, where many markets are large in need but small in paid adoption. A founder who mistakes need for market demand will overbuild. A founder who understands non-consumption can design the right wedge: education, trust, lower setup friction, financing, services, channel partnership, or a narrower urgent segment.

Market Evidence Dossier

Before you raise, hire, or build heavily for a market, create a short evidence dossier. This is the document that keeps the team honest when confidence starts running ahead of reality.

Evidence Area	What To Capture	Strong Evidence
Customer pain	Recent stories, frequency, severity, current workaround.	Multiple customers describe the same painful workflow without prompting.
Buyer reality	Budget owner, approval path, current spend, procurement friction.	A named buyer explains how money would move and what approval is needed.
Workflow shape	Current tools, handoffs, exceptions, data, people involved.	You can draw the workflow and identify the exact step your product changes.
Trust path	References, partners, credentials, pilots, local proof, compliance comfort.	Customers tell you what proof would reduce risk and then respond to that proof.
Distribution path	Where prospects gather, search, ask, compare, or take advice.	You can repeatedly create qualified conversations without relying only on friends.
Willingness to pay	Price reaction, paid pilot, invoice path, budget tradeoff.	Customers discuss payment, not only interest.
Timing	Trigger, regulation, cost change, new role, operational pressure.	Customers are acting this quarter, not saying “someday.”

Add a confidence level to each row: evidence, estimate, or guess. The goal is not to eliminate all guesses. The goal is to know which guesses are dangerous.

Use the dossier in weekly founder review. Ask:

1. Which assumption moved from guess to evidence this week?
2. Which assumption got weaker?
3. Which market risk still has no owner?
4. Which decision should change because of new evidence?

Markets become clearer through repeated contact, not through one perfect strategy session.

Common Mistakes

• Using TAM numbers before understanding the first customer.
• Calling everyone a potential customer.
• Ignoring the buyer-user split.
• Underestimating substitutes.
• Assuming India behaves like the US with lower price points.
• Entering regulated markets without understanding timelines and trust.
• Mistaking investor excitement for customer urgency.

Reader Action

Create a market map for your idea with five columns: customer, buyer, current workaround, channel, and reason now. Fill at least 20 rows. If you cannot find 20 plausible customers and their current workarounds, you are still at the topic stage.

Market Readiness Scorecard

Before committing heavily to a market, score it like a founder, not like a consultant. The question is not “Is this market large?” The question is “Can this startup enter, learn, sell, and compound here before running out of cash or attention?”

Factor	Weak signal	Strong signal	Current evidence
Pain	Customers describe generic interest.	Customers describe recent, repeated, costly pain.
Buyer	No clear budget owner.	You can name who approves, pays, and blocks.
Workflow	Problem is abstract.	You can draw the current workflow and failure point.
Substitute	”No competitor.”	You know the real workaround: Excel, WhatsApp, people, agency, internal tool, doing nothing.
Access	You do not know how to reach customers repeatedly.	You have a repeatable path to conversations.
Trust	Customers hesitate for unclear reasons.	You know what proof, reference, compliance, or relationship reduces risk.
Timing	Trend is interesting.	Customers are changing behavior or budget now.
Economics	Revenue is theoretical.	Price, sales effort, support load, and margin are plausible.

Use three labels:

• Evidence: seen directly in customer behavior, payment, workflow, or repeated conversations.
• Estimate: plausible but not proven.
• Guess: attractive story with weak evidence.

A founder can act on guesses, but only if they know which guesses could kill the company. The most dangerous market is not a small market. It is a market that looks obvious from a distance and becomes expensive only after you enter.

Market entry question

End the scorecard with one sentence:

We should enter this market first because [specific segment] has [specific urgent pain], can be reached through [specific channel], trusts [specific proof], and can produce [specific early business evidence] within [time window].

If the sentence is vague, the market is still a topic. Keep discovering before building heavily.

Market Pull Signals

Market pull is different from founder enthusiasm. Look for behavior that happens without heavy persuasion.

Signal	What it means	What to verify
Customers ask for next steps	Pain is active enough to continue.	Is the buyer serious or only polite?
Buyers reveal current spend	The problem already has budget.	Is that budget accessible to your category?
Prospects introduce colleagues	The problem crosses functions.	Are introductions to decision makers or curious observers?
Users send real data or workflows	They trust you with operational context.	Is there urgency to change the workflow?
Customers ask about implementation	They are imagining adoption, not just learning.	Is procurement, security, or integration a blocker?
People pay before full product	Value is strong enough to overcome incompleteness.	Is payment repeatable outside warm networks?

Do not over-read compliments. The market speaks most clearly through time, access, money, and internal urgency.

Market Map By Budget Owner

A market is easier to understand when you map who controls money.

Budget owner	Typical concern	Founder implication
CEO/founder	Growth, survival, speed, visibility.	Sell strategic urgency and direct business impact.
CFO/finance	Cost, control, compliance, reporting, risk.	Sell accuracy, savings, auditability, and predictability.
Sales/revenue leader	Pipeline, conversion, productivity, forecasting.	Sell revenue impact and adoption by reps/managers.
Operations leader	Efficiency, process, throughput, reliability.	Sell workflow improvement and implementation ease.
HR/people leader	Hiring, retention, compliance, employee experience.	Sell trust, adoption, and measurable employee outcomes.
IT/security	Risk, integration, access, data protection.	Sell security posture, documentation, and control.

If the user and budget owner are different, market understanding must include both. Many early products fail because the user feels pain but the budget owner does not care enough.

Market Timing Evidence Calendar

Timing is not a slogan. Build a calendar of market events that could increase urgency.

Timing driver	Evidence to watch
Regulation	New compliance deadlines, penalties, audit pressure, reporting changes.
Platform shift	API changes, ecosystem growth, distribution changes, new default behavior.
Cost pressure	Hiring slowdown, margin pressure, vendor consolidation, automation mandates.
Talent shift	New roles, skill shortages, remote/hybrid changes, outsourcing patterns.
Customer behavior	New channels, payment habits, trust expectations, workflow migration.
Capital environment	Funding availability, buyer spending discipline, payback expectations.

Review timing monthly. If timing is weak, you may need a sharper wedge, a lower-friction entry point, or a customer segment with more immediate pain.

Market Thesis One-Pager

Before building heavily, write a one-page market thesis. It should be specific enough that another founder could disagree with it.

Section	What To Write
Customer cluster	The narrow first group, not the entire market label.
Pain	The repeated problem, current workaround, and cost of delay.
Buyer	Who controls budget and why they care.
User	Who changes daily behavior.
Trust path	What proof, relationship, brand, compliance, or reference lowers risk.
Channel	How the first 50-100 serious prospects can be reached.
Competition	What they use today, including doing nothing.
Timing	What has changed recently that makes action more likely.
First proof	The evidence the startup must create in 30-90 days.
Expansion logic	What adjacent market becomes easier if the first wedge works.

The thesis should include assumptions explicitly:

We believe [customer] has [pain] because [evidence].
They currently solve it with [workaround].
They will trust [proof/channel] enough to try [offer].
The first proof we need is [evidence] by [date].
If this is true, we can expand to [adjacent segment] because [transferable proof].

If this one-pager is vague, do not compensate with a larger product plan. Sharpen the market first.

Market Evidence Room

A market thesis becomes stronger when evidence is collected in one place. Build a market evidence room.

Evidence type	Examples
Customer conversations	Interview notes, exact phrases, buying triggers, objections.
Current workaround	Screenshots, workflows, spreadsheets, agencies, manual processes.
Budget proof	Existing spend, approved budget, paid pilot, procurement path.
Timing proof	Regulation, cost pressure, new behavior, role changes, platform shifts.
Competitive proof	Alternatives considered, win/loss notes, status quo reasons.
Channel proof	Reply rates, community access, partner introductions, search demand.
Retention proof	Repeat usage, renewal intent, expansion, references.

Use three evidence labels:

• Direct: observed in customer behavior, payment, product use, or internal documents.
• Repeated: seen across multiple customers in the same segment.
• Weak: inferred from reports, social media, founder opinion, or isolated anecdotes.

The evidence room protects founders from narrative drift. Every month, ask: “What do we now know that we did not know last month, and what belief became weaker?”

Market Pull Commitment Ladder

Market pull is visible through commitments, not compliments. Create a ladder and track where each prospect or customer sits.

Commitment level	Signal	Meaning
Attention	Replies, attends demo, reads material.	Mild interest; useful but weak.
Time	Gives a serious discovery call or workflow walkthrough.	Problem may be relevant.
Artifact	Shares spreadsheet, data, screenshot, process, contract, ticket, or report.	Trust and pain are increasing.
Internal access	Introduces buyer, user, finance, IT, operator, or decision-maker.	Problem has organizational relevance.
Workflow change	Tries manual process, pilot, import, setup, or new behavior.	Solution may matter.
Money	Pays, deposits, signs LOI with teeth, approves budget.	Commercial pull exists.
Reference	Recommends, gives testimonial, makes intro, expands.	Value is becoming transferable.

Track by segment:

Segment	Attention	Time	Artifact	Internal access	Workflow change	Money	Reference

If many prospects stop at attention, the market may not be urgent. If they give artifacts but not money, buyer discovery is weak. If they pay but do not repeat or refer, value or delivery may be weak.

Market Bottleneck Map

Markets are systems. A product can fail because of one bottleneck even when the pain is real.

Map bottlenecks:

Bottleneck	Founder question
Awareness	Does the customer know this problem can be solved differently?
Trust	Does the customer believe a startup can safely solve it?
Budget	Is there money assigned to this problem?
Authority	Who can approve behavior change or purchase?
Workflow	Can the product fit the customer’s real process?
Data/access	Can the customer provide the data, permissions, or integration needed?
Timing	Is there a current trigger that makes action urgent?
Switching	What makes the current workaround hard to replace?

Then choose the next market action based on the bottleneck. Do not solve trust with more features. Do not solve budget with better UI. Do not solve timing with a bigger market-size slide.

Related Links

• 12. Market Sizing
• 13. Customer Segmentation
• 15. Market Timing
• 132. 7-Day Customer Discovery Playbook