13. Customer Segmentation

Customer segmentation is the discipline of choosing which customers are similar enough that one product, message, channel, price, and sales motion can work repeatedly. Without segmentation, you do not have a market; you have a crowd.

Early founders often resist segmentation because it feels like reducing ambition. In reality, segmentation increases speed. A narrow segment gives you clearer discovery, simpler product decisions, better references, more relevant positioning, and faster sales learning. You can expand later. You cannot learn from everyone at once.

The core segmentation question is: which group of customers is similar enough that one product, message, channel, price, and buying process can repeat?

Good segmentation is a speed tool. It tells the founder where to learn, whom to ignore temporarily, and what evidence should count. Without it, every conversation feels important and every feature request feels tempting.

What This Chapter Covers

• Types of segmentation.
• How B2B and B2C segmentation differ.
• How to choose a beachhead.
• India-specific segmentation realities.
• Mistakes that make startups look busier than they are.

Segment Types

Use more than one lens. A useful segment is rarely just “young people” or “SMBs.”

Segment Lens	What It Means	Example
Demographic	Age, income, education, household type.	Working women in Tier 1 cities aged 25-35.
Firmographic	Company size, industry, revenue, location.	Indian SaaS companies with 20-100 employees.
Behavioral	What customers actually do.	Teams that still reconcile payments manually every week.
Psychographic	Motivation, identity, belief, aspiration.	Parents who value English fluency as career insurance.
Job-to-be-done	The progress customers are trying to make.	Sales managers trying to improve follow-up discipline.
Budget-based	Ability and willingness to pay.	Clinics already spending on practice-management tools.
Maturity-based	Sophistication of process or technology.	Exporters moving from WhatsApp orders to ERP.
Channel-based	How customers can be reached.	Founders active in SaaS communities and LinkedIn.
Urgency-based	Strength and timing of pain.	Companies facing a compliance deadline.

The best early segments combine behavior, urgency, and reachability.

Strong Segments Have Four Forms of Similarity

An early segment is useful when customers are similar in four ways:

1. Pain: the same problem hurts for the same reason.
2. Workflow: the problem appears in a similar process.
3. Buying: the same kind of person approves or pays.
4. Reachability: the customers can be found through similar channels.

If customers share only a label, the segment is weak. “Restaurants” is a label. “Cloud kitchens in Bangalore doing 300+ daily orders and reconciling Swiggy/Zomato payouts manually every week” is closer to a segment.

Segment Hypothesis

Write a segment hypothesis before changing the product or GTM.

Template:

We believe [specific segment] has [specific pain] in [specific workflow], triggered by [specific event], and can be reached through [specific channel]. We will know this segment is promising if [specific behavior] happens within [time period].

Example:

We believe Indian SaaS companies with 20-80 employees struggle to maintain sales follow-up discipline after founder-led sales becomes team-led, triggered by hiring the first two account executives, and can be reached through founder communities and LinkedIn outbound. We will know this segment is promising if 10 of 25 qualified prospects agree to a discovery call and 3 commit to a paid pilot.

The hypothesis should include pain, workflow, trigger, channel, and evidence. If one of these is missing, the segment may be too vague to test.

Bad Segments Look Large

Weak segments often sound impressive:

• “SMBs.”
• “Students.”
• “Doctors.”
• “Founders.”
• “Women.”
• “Enterprises.”
• “Tier 2 India.”
• “Finance teams.”

These may be starting points for research, but they are too broad for product and sales decisions. Narrow until you can predict where the customer spends time, what they use today, who they trust, and why they would buy now.

B2B Segmentation

In B2B, the company is not the only customer. You need to understand the account, buyer, user, and process.

Segment by:

• Company size.
• Industry.
• Revenue or funding stage.
• Geography.
• Department.
• Tech stack.
• Compliance needs.
• Budget owner.
• Buying process.
• Trigger event.

Example of weak segmentation: “We sell to Indian SMEs.”

Better: “We sell to GST-registered distributors with 20-200 retailers, using Tally plus WhatsApp, where the owner or finance head spends more than five hours per week on collections and reconciliation.”

That sharper segment tells you where to find them, what language to use, what workflows to inspect, who buys, and what proof matters.

B2B Trigger Segmentation

Trigger events often matter more than industry labels. A company may not care about your product until something changes.

Common B2B triggers:

• Raised funding.
• Crossed a headcount threshold.
• Opened a new location.
• Entered a compliance deadline.
• Adopted a new tool.
• Changed leadership.
• Started selling internationally.
• Hit operational volume that breaks spreadsheets.
• Received customer security or audit requirements.
• Hired the first person for a function.

Trigger-based segmentation improves timing. You are not just targeting companies that could buy; you are targeting companies that have a reason to act now.

B2C Segmentation

In B2C, do not stop at age and income. Consumer behavior in India can change dramatically by city, language, family structure, trust, community influence, payment comfort, and frequency of need.

Segment by:

• Use case.
• Frequency.
• Motivation.
• Trust level.
• Payment ability.
• Language.
• Location.
• Family influence.
• Community influence.
• Current alternative.

Example of weak segmentation: “Students.”

Better: “Final-year engineering students from Tier 2 colleges who want off-campus software jobs, have weak interview confidence, can pay under a monthly subscription, and rely on YouTube, Telegram, and peer groups for learning.”

B2C Segmentation Beyond Demographics

For consumer startups, segment by behavior and motivation:

• What event creates need?
• How often does the need repeat?
• Who influences the decision?
• Who pays?
• What proof creates trust?
• What language or format feels natural?
• What current habit can the product attach to?
• What community or creator can reach the user?

A 22-year-old in Pune and a 22-year-old in Patna may share age but not trust channels, willingness to pay, family influence, language preference, or career path. Segmentation must capture behavior, not just demographics.

Choosing A Beachhead

A beachhead is the first segment where you try to win seriously. It should be narrow enough to dominate and important enough to expand from.

Choose a beachhead with:

• Reachable customers.
• Similar pain.
• Similar workflow.
• Similar buying process.
• Similar willingness to pay.
• High reference value.
• Expansion potential.
• A clear trigger event.

Use this scorecard:

Question	Score 1-5
Can we reach this segment repeatedly?
Do they share the same urgent pain?
Do they use similar alternatives today?
Can one product solve most of the problem?
Is the buyer identifiable?
Will one customer reference help close another?
Can this segment lead to adjacent segments later?

If a segment scores low on reachability or urgency, it is a poor starting point even if the market is large.

Segment Experiment

Run a segment experiment for 30 days before declaring a target customer.

Step	Work
Build list	Create a list of 50-100 real prospects in the segment.
Test message	Send one specific problem statement, not a generic pitch.
Interview	Talk to at least 10 qualified prospects.
Observe	Collect current workflows, screenshots, tools, or artifacts.
Test commitment	Ask for pilot, data, internal intro, paid trial, or follow-up.
Review	Compare response, urgency, willingness to pay, and support burden.

A segment is not validated because people fit your description. It becomes promising when the same pain, language, trigger, and buying logic repeat.

Do not run segment experiments across five segments at once unless you have enough capacity to learn properly. A small team usually learns faster by testing two candidate segments deeply than ten shallowly.

Segment Comparison Lab

When multiple segments look attractive, compare them through evidence, not through debate. A common founder mistake is to choose the segment that sounds largest, has the most exciting logo, or gave the warmest meeting. The better question is: where does repetition appear fastest?

Run a two-segment comparison lab for 10 working days.

Day	Work
1	Define two candidate segments in one sentence each.
2	Build 50 real prospects for each segment.
3-5	Send the same problem-led message to both groups.
4-8	Run discovery calls with qualified responders.
6-9	Ask for the same commitment: paid pilot, data share, intro, trial, or follow-up.
10	Compare response, urgency, workflow similarity, willingness to pay, and support load.

Use the same level of effort for both segments. If you spend three days carefully reaching one segment and 20 minutes spamming the other, the result only proves your execution was uneven.

Score each segment with real evidence:

Question	Segment A	Segment B
Can we list 100 reachable prospects without guessing?
Did the problem statement get replies?
Did calls reveal the same workflow repeatedly?
Did prospects already use a workaround?
Did anyone commit effort, money, data, or internal access?
Was the buyer identifiable?
Would one success story help close another prospect?
Could we serve them without custom chaos?

Do not overreact to one exciting customer. A segment is attractive when the pattern repeats across several customers. One large prospect can fund learning, but it should not silently become your entire strategy unless you consciously choose an enterprise-led company.

From Segment To Operating Choices

Segmentation is only useful if it changes company behavior. Once you pick a beachhead, translate it into operating choices.

Company area	Segment decision should change
Product	Which workflows, integrations, permissions, and defaults matter first.
Positioning	The language used on the homepage, decks, demos, and outbound messages.
Sales	Who the buyer is, how long the cycle is, and what proof is needed.
Pricing	Whether value is per seat, per transaction, per location, per usage, or per outcome.
Onboarding	What setup help, migration, templates, and training are needed.
Support	Which issues repeat and what self-serve assets should exist.
Metrics	Which activation and retention behaviors prove segment fit.

If the segment choice does not change product, sales, onboarding, pricing, and metrics, it is probably just a label.

Example:

Weak choice	Stronger operating choice
”We target founders."	"We target seed-stage B2B SaaS founders hiring their first sales team.”
Product implication	Sales pipeline handoff, CRM discipline, demo follow-up, founder-to-AE transition.
GTM implication	Founder communities, LinkedIn outbound, sales hiring content, sales ops templates.
Onboarding implication	Import current pipeline, define stages, set follow-up rules, review first 20 opportunities.
Proof implication	More reliable follow-ups, clearer pipeline, shorter founder review meetings.

The sharper segment tells the whole company what to do next.

Segment Refusal Rules

A real segment choice includes refusal.

For the next 60-90 days, write down:

• Customer types you will not sell to.
• Feature requests you will not accept.
• Geographies you will ignore.
• Channels you will not test yet.
• Pricing structures you will not support.
• Custom integrations you will not build.

This is hard because early revenue feels precious. But if every off-segment customer changes the product, the company loses the learning advantage of focus.

Refusal is not arrogance. It is how a small team creates enough repetition to learn.

Beachhead Operating Rules

After choosing a beachhead, protect it with simple operating rules for 60-90 days.

Rule	Why it matters
All discovery calls must be tagged by segment.	Prevents generic learning.
Sales pipeline must show segment and trigger.	Reveals which customers move.
Product requests must include segment evidence.	Stops the loudest customer from driving roadmap.
Pricing exceptions require a reason.	Avoids hidden segment mismatch.
Onboarding effort must be tracked.	Shows whether the segment can be served repeatably.
References must be segment-specific.	Tests whether one win helps another win.
Every off-segment deal gets reviewed.	Makes exceptions explicit instead of accidental.

This is especially important when revenue is scarce. Early teams naturally chase any customer who says yes. That is understandable, but the hidden cost is loss of learning. One unrelated customer may bring revenue and still slow the company if it changes roadmap, support, onboarding, and positioning.

Use exceptions deliberately. If an off-segment customer pays meaningfully, teaches something strategic, or opens a better segment, accept it consciously. If the only reason is fear, the company may be buying short-term comfort with long-term confusion.

Beachhead Selection Process

Use a 30-day process:

1. List five candidate segments.
2. Interview 10 customers in each of the top two.
3. Map current workaround, buyer, trigger, and channel.
4. Estimate willingness to pay and support load.
5. Score urgency and reachability.
6. Pick one segment for the next 60-90 days.
7. Write what you will refuse during the test.

The refusal list matters. If you keep accepting customers outside the beachhead, you will not learn whether the segment works.

Segment Drift

Segment drift happens when early revenue pulls the company away from the chosen beachhead.

Warning signs:

• Every new customer requires a different onboarding flow.
• Sales calls use different positioning each time.
• Support questions do not repeat.
• Roadmap items come from unrelated customer types.
• Pricing varies because value is different for every account.
• References do not help close the next customer.
• The team cannot name the best segment without debate.

Some drift is normal while searching. Persistent drift means the company is not learning in a compounding way.

Hold a monthly segment review:

Question	Answer
Which segment activated fastest?
Which segment paid most naturally?
Which segment needed least custom work?
Which segment retained or returned?
Which segment created useful references?
Which segment should we refuse for now?

Focus is not a one-time decision. It is maintained.

Segment Metrics

Track by segment, not averages:

• Response rate.
• Discovery call quality.
• Activation.
• Conversion.
• Sales cycle.
• Price accepted.
• Retention.
• Support load.
• Referral likelihood.
• Expansion potential.

Average metrics hide segment truth. One segment may love the product while another drains support.

Segment Quality Matrix

Score each candidate segment:

Dimension	Question
Pain	Does the segment feel the problem sharply?
Workflow similarity	Do customers solve the problem in similar ways today?
Buyer clarity	Is the person with authority identifiable?
Reachability	Can you reach 100 prospects without fantasy channels?
Willingness to pay	Is there current spend or clear value?
Trust path	Can a new startup earn permission to sell?
Reference value	Will one win help close another similar customer?
Expansion	Does this segment lead to adjacent segments or workflows?
Support load	Can you serve them without drowning the team?

The best beachhead is rarely the largest segment. It is the segment where learning, sales, product, and references can repeat fastest.

Segment Interview Sampling Plan

Do not validate a segment using only friendly intros. Friendly conversations are useful for vocabulary, but they often hide distribution, urgency, and willingness-to-pay problems.

For each candidate segment, run a small but deliberate sample:

Interview Type	Target Count	Why It Matters
Users	5 to 8	Understand daily workflow and pain.
Buyers	3 to 5	Understand budget, priority, and timing.
Champions	2 to 3	Learn who can push adoption internally.
Blockers	2 to 3	Find risk, compliance, procurement, operations, or politics.
Lost or inactive prospects	2 to 3	Learn why interest did not become action.

For B2C, replace the buying committee with household, peer, community, and trust influence. A student, parent, teacher, spouse, friend group, or local adviser may shape adoption even when only one person uses the product.

Track source quality:

Source	What It Proves	What It Does Not Prove
Warm founder network	Vocabulary and early openness.	Scalable reach.
Cold outbound	Reachability and message clarity.	Deep willingness to pay by itself.
Community or WhatsApp group	Concentrated pain and peer influence.	Long-term conversion economics.
Paid ads	Search or demand signal.	Trust, retention, or enterprise buying.
Partner intro	Channel trust.	Whether the customer would buy without the partner.

The goal is not a perfect research study. The goal is to stop fooling yourself with one easy channel.

Segment Decision Meeting

After research, choose one operating segment for the next 30 days. Do not leave the decision vague.

Use this meeting format:

1. List the segments tested.
2. Show evidence, not opinions.
3. Score each segment on pain, reachability, buyer clarity, price, trust path, support load, and reference value.
4. Choose one segment to focus on.
5. Write the exact customer you will refuse for 30 days.
6. Write the one metric that would make you continue.
7. Write the one signal that would make you narrow or stop.

A good segment decision creates relief and discomfort at the same time. Relief because the team knows where to aim. Discomfort because focus means saying no to tempting distractions.

India Angle

India makes segmentation both harder and more important. “SMB” can mean a funded startup, a family-owned distributor, a local manufacturer, a clinic, a coaching center, or a shop with three staff. Their budgets, workflows, trust signals, and decision cycles are not the same.

Regional and language differences matter. Tier 1, Tier 2, and smaller-town customers may share the same problem but require different onboarding, support, pricing, and channel strategy. Do not pretend one English landing page validates all of India.

For India-first B2B, segment by operating reality: owner-led vs professionally managed, GST maturity, digital stack, city tier, language, payment behavior, consultant dependency, and whether the business already buys software.

For India-first B2C, segment by household decision-making, affordability, aspiration, language, payment comfort, trust source, and current offline alternatives.

Segment Kill Criteria

Focus becomes real only when you know when to stop pursuing a segment. Before a 30-day or 90-day segment test, write kill criteria.

Signal	Continue If	Kill Or Narrow If
Pain	Customers describe the same painful workflow without prompting.	Pain is polite, theoretical, or different in every call.
Buyer clarity	A specific role owns budget or decision.	Nobody knows who would pay.
Reachability	You can create repeated qualified conversations.	Every conversation depends on personal favors.
Urgency	A trigger makes action likely this quarter.	Customers agree but keep postponing.
Willingness to pay	Customers discuss price, budget, or procurement seriously.	Interest disappears when payment is mentioned.
Workflow similarity	One product and onboarding path can serve many customers.	Every customer needs a different service project.
Reference value	One customer story helps with another.	Customers do not recognize each other as peers.
Support load	Early customers can be supported without breaking margin.	Every account needs heavy custom work.

Kill criteria protect the founder from ego. If the segment fails, the work is not wasted. You learned which assumptions were wrong and can choose a better wedge.

Segment Narrowing Moves

When a segment is almost working, do not immediately pivot. Narrow first.

You can narrow by:

• Industry.
• City or region.
• Company size.
• Buyer role.
• Workflow.
• Trigger event.
• Compliance need.
• Tech stack.
• Payment capacity.
• Channel or community.
• Language or support requirement.

Example:

Instead of "SMBs", narrow to "owner-led diagnostic labs in two cities that already use digital billing and lose revenue because patient follow-up is manual."

That sentence is less glamorous than a huge market label. It is also easier to sell to, build for, and learn from.

Segment Sequencing Map

A beachhead should create the next segment, not trap you forever. After choosing the first segment, map the sequence.

Sequence Step	Segment	Why This Segment Now?	Proof Needed To Move There	Risk
1	Beachhead	Strongest pain, reachability, trust path, and repeatability.	5-10 wins, clear usage, paid adoption, repeatable story.	Too small or service-heavy.
2	Adjacent segment	Similar workflow, buyer, channel, or proof requirement.	References transfer from beachhead.	Differences hidden by surface similarity.
3	Expansion segment	Larger market or higher contract value.	Product, support, pricing, and credibility have matured.	Premature scaling.
4	Strategic segment	Opens category, platform, geography, or enterprise value.	Company can handle complexity.	Distraction from core business.

Write the transfer logic explicitly:

If we win [segment 1], it helps us win [segment 2] because ______.

Bad transfer logic sounds like this:

• “They are both SMBs.”
• “They both use software.”
• “Investors will like the bigger market.”
• “The product can technically serve both.”

Good transfer logic is more specific:

• The same buyer owns the budget.
• The same workflow creates the pain.
• The same channel can reach them.
• The same reference story builds trust.
• The same onboarding path works.
• The same pricing model makes sense.

If the second segment needs a different product, buyer, channel, proof, and support model, it is not an expansion. It is a second startup hiding inside the first.

Segment Promise

For each beachhead, write the promise in one sentence:

For [specific segment], we help [specific role] improve [specific workflow/outcome] when [trigger], without [main adoption fear].

Examples:

• For export-focused manufacturers, we help operations heads reduce shipment-documentation errors when order volume increases, without replacing their entire ERP.
• For coaching institutes, we help owners improve parent communication during admission season, without forcing teachers into a complex new system.
• For early-stage B2B SaaS founders, we help founders run better discovery calls before building, without hiring a research team.

If the promise cannot be written specifically, the segment is probably still too broad.

Common Mistakes

• Segmenting by market label instead of behavior.
• Calling the user and buyer the same person when they are not.
• Choosing a segment only because it sounds impressive.
• Expanding before one segment works.
• Ignoring willingness to pay.
• Treating “India SMB” as one customer.
• Confusing community enthusiasm with purchase intent.
• Changing segments every week because one prospect asked for something.
• Choosing a segment only because investors like the category.
• Ignoring support cost differences between segments.
• Treating early adopters and mainstream buyers as the same segment.

Reader Action

List five possible customer segments. For each, write:

1. Who has the pain?
2. What workflow creates the pain?
3. Who pays?
4. Where can you reach 100 of them?
5. What trigger makes the pain urgent?
6. Why would they trust you?

Pick one beachhead for the next 30 days. Do not change it unless evidence forces you to.

Segment Operating Dashboard

Once you choose a segment, track whether reality supports the choice.

Metric	What it reveals
Prospects identified	Whether the segment is findable and large enough for the current stage.
Outreach reply rate	Whether the access path and problem language work.
Useful discovery calls	Whether the segment is willing to talk about the pain.
Repeated pain count	Whether the problem is shared, not one-off.
Buyer conversations	Whether you are reaching decision authority.
Concrete next steps	Whether customers will act beyond polite conversation.
Sales cycle length	Whether the segment matches your runway and model.
Support or implementation load	Whether the segment is operationally expensive.
Reference potential	Whether wins in this segment can create trust with similar customers.

Review the dashboard weekly for 30 days. If access is weak, fix the channel before judging the segment. If conversations are good but next steps are weak, test urgency and willingness to pay. If every customer needs different product work, the segment may be too broad or the workflow may not be standardized enough yet.

Beachhead Segment Decision Memo

When several segments look attractive, write a decision memo instead of debating forever. The memo should make tradeoffs visible.

Section	Prompt
Segment	Who exactly are we choosing for the next 30-90 days?
Pain	What repeated painful workflow do they have?
Access	Where can we reach them repeatedly?
Buyer	Who pays, approves, blocks, and uses?
Urgency	What trigger makes the problem matter now?
Trust	What proof do they need before acting?
Economics	What price, sales cycle, support load, and margin seem plausible?
Reference value	Will wins in this segment help us win similar customers?
Expansion path	Which adjacent segment could come next?
Refusals	Which segments and requests will we intentionally ignore for now?

Then make a clear decision:

For the next 60 days, we will focus on ______ because ______.
We will say no or delay ______.
The evidence that would make us change segment is ______.

This protects the founder from random opportunity. A famous logo, warm intro, investor suggestion, or urgent custom request can be useful, but it should not silently change the segment strategy.

Segment switching rule

Switch segments only when evidence says the current segment is structurally weak or another segment is clearly stronger.

Good reasons to switch:

• You cannot reach enough of the segment.
• The pain is not urgent.
• Buyer and user incentives are misaligned.
• Sales cycles are too long for runway.
• Support load destroys margin.
• Another segment shows stronger payment, retention, and referrals.

Bad reasons to switch:

• One customer asked for a different product.
• A competitor raised money in another category.
• The current segment feels boring.
• The founder is tired of rejection.
• An investor likes a larger market label.

Focus is not romance. It is a learning strategy.

Segment Evidence Ladder

Segments become real through evidence.

Level	What you know	Founder action
Label	”Fintech”, “SMBs”, “students”, “manufacturers”.	Too broad. Break into sharper groups.
Observable group	You can list names, companies, communities, or channels.	Build a prospect list.
Shared pain	Multiple people describe the same recent problem.	Run focused discovery.
Shared workflow	They solve the problem in similar ways today.	Design a repeatable MVP or pilot.
Shared buyer path	Budget, approval, trust, and payment path are similar.	Build a sales motion.
Shared retention driver	The same value makes them return or renew.	Focus product and onboarding.
Shared reference value	One win helps sell to the next similar customer.	Scale within the segment.

If a segment does not share workflow, buyer path, and retention driver, it may be a market label, not an operating segment.

ICP Anti-Profile

Define who you will not serve right now. This is as important as defining the ideal customer.

Bad-fit signal	Why it matters	Response
Needs custom workflow outside the chosen use case	Creates product and support drag.	Defer or price as services.
Buyer cannot explain urgency	Long sales cycle and weak adoption.	Nurture, do not forecast.
Payment path is unclear or too slow for deal size	Cash and follow-up burden.	Require paid pilot or simpler segment.
Wants discount before value is proven	Weak willingness to pay or poor positioning.	Requalify buyer/problem.
Requires trust proof you cannot provide yet	Deal may stall late.	Build references or choose lower-risk segment.
Product would need heavy language, compliance, or ops changes	Segment may be valid but premature.	Park for future expansion.

Anti-profile sentence:

For the next [time period], we will not actively sell to [bad-fit customer] because [reason], unless [specific exception].

This protects early teams from polite distraction.

Segment Expansion Sequence

Expansion should be sequenced by proof transfer, not only market size.

Expansion path	Good reason	Bad reason
Same buyer, adjacent workflow	Trust and buying path already exist.	Customer asked once in a call.
Same workflow, larger customer	Product value transfers upward.	Larger logos feel impressive.
Same workflow, new geography	Proof and use case travel.	Founder is bored with current market.
Same customer, deeper product	Retention/expansion signal is strong.	New features avoid acquisition work.
New customer, same channel	Distribution advantage transfers.	Channel partner promises vague access.

Before expanding, write:

Current segment proof:
What transfers:
What does not transfer:
New risk:
First test:
Stop rule:

Expansion is healthy when it compounds existing proof. It is dangerous when it resets the company into a new startup without admitting it.

Segment Operating Contract

Once a beachhead segment is chosen, turn it into an operating contract. This prevents the company from quietly serving everyone again.

Contract field	Decision
Segment definition	Who exactly is in the segment?
Inclusion rules	What must be true for a prospect to qualify?
Exclusion rules	Who will we not chase for now?
Primary pain	What urgent pain do we solve first?
Buyer/user map	Who buys, uses, approves, blocks, and supports?
Channel	How will we reach them repeatedly?
Offer	What first commitment are we asking for?
Proof	What proof should reduce trust risk?
Onboarding promise	What must happen for first value?
Review date	When will we continue, narrow, expand, or stop?

The contract should be reviewed every two weeks during early market entry. If the team keeps breaking it, either the segment is wrong or discipline is missing.

Segment discipline rule

Use this:

Every prospect outside the chosen segment must earn an exception with evidence, not excitement.

Evidence can include urgent pain, fast payment, strong reference value, repeated demand, or strategic learning. Without evidence, the opportunity goes into the parking lot.

Segment Health Review

Segment quality changes as the company learns. A segment that looked attractive during discovery may become weak after onboarding or retention.

Review segment health:

Health area	Good signal	Bad signal
Access	We can reach prospects repeatedly.	Every lead is random or founder-network dependent.
Pain	Similar pain repeats.	Every conversation reveals a different problem.
Buyer path	Budget owner and process are predictable.	Deals stall for mysterious reasons.
Trust	The same proof works.	Every customer needs custom reassurance.
Onboarding	First value is repeatable.	Setup is custom every time.
Retention	Value persists.	Customers try once and fade.
Reference	One win helps the next sale.	Customers are isolated wins.

If access, pain, and trust are strong but onboarding is weak, fix delivery before changing segment. If pain and buyer path are weak, the segment itself may be wrong.

Segment Expansion Gate

Do not expand from a weak segment to escape hard work. Expand when proof from the current segment can travel.

Use this gate before adding a new segment:

Gate	Must be true
Current segment proof	At least a few customers have paid, adopted, or repeatedly engaged for the same reason.
Transferable pain	The new segment has the same core pain, not only a similar label.
Transferable workflow	The product can solve the workflow without becoming a custom project.
Transferable proof	Case studies, demos, ROI, and references from current customers are credible to the new segment.
Reachability	The team knows where to find 100 prospects in the new segment.
Buyer path	The buyer, approver, blocker, and payment path are understandable.
Support load	The new segment does not quietly add a new service business.
Stop rule	The team knows what evidence will stop the expansion test.

Write the expansion decision like this:

Current segment:
Expansion segment:
What proof transfers:
What proof does not transfer:
New risk:
First 20 prospects:
First offer:
Success signal within 30 days:
Stop rule:

Expansion should feel like using accumulated learning in a nearby place. If it feels like starting over, admit that honestly and decide whether the company can afford a second discovery cycle.

Related Links

• 11. Understanding Markets
• 14. Customer Personas
• 18. Customer Discovery Fundamentals
• 148. GTM Templates