57. Prospecting

Prospecting is the discipline of finding people likely to have the problem you solve.

It is not scraping a huge list and hoping volume saves you. It is not adding every LinkedIn connection to a CRM. It is not “networking” without a point. Good prospecting starts with a narrow customer hypothesis, looks for evidence of pain, and creates a reason to start a relevant conversation.

For early founders, prospecting is also market research. A bad list tells you your ICP is vague. A good list makes your outreach sharper, your discovery calls better, and your product learning faster.

The core prospecting question is: which specific buyers are most likely to feel the pain now, and what evidence makes them worth a focused sales attempt?

What It Covers

This chapter covers:

• Prospect sources
• Prospect qualification
• List building

The goal is to build a small, high-signal sales pipeline before trying to scale anything.

Prospecting Starts With A Hypothesis

Prospecting is not “find anyone who might buy.” It starts with a testable sentence.

Use this format:

We believe [buyer role] at [company type] will care about [specific pain] when [trigger] happens because [cost or consequence].

Examples:

• We believe finance heads at D2C brands selling on multiple marketplaces will care about payout reconciliation when month-end closing gets delayed because founders and finance teams lose days matching reports.
• We believe HR leaders at 200-1,000 employee companies will care about offer-drop tracking when hiring ramps up because candidate leakage becomes expensive.
• We believe engineering leaders at SaaS companies expanding to enterprise customers will care about audit logging when security reviews start blocking deals.

This sentence keeps the founder honest. If you cannot write it clearly, you are not ready to build a big list.

The first list should be small enough to review manually. Fifty good prospects teach more than five thousand guessed contacts.

Prospect Sources

A prospect source is useful only if it helps you find people with a reason to care now.

LinkedIn

LinkedIn is useful for B2B because roles, company size, hiring signals, posts, mutual connections, and job changes create context. Do not start by searching generic titles. Start with the workflow owner.

For example:

• If you sell finance reconciliation software, search for finance heads, controllers, marketplace operators, and founders of companies with many payout sources.
• If you sell developer tooling, search for engineering leaders, platform teams, DevOps roles, and companies hiring for relevant infrastructure.
• If you sell sales automation, search for founders, revenue leaders, SDR managers, and teams hiring outbound roles.

LinkedIn works best when you combine role plus trigger, not role alone.

Email and Company Websites

Company websites reveal positioning, customer type, hiring, integrations, pricing, case studies, and sometimes pain. A company hiring three support roles may have support volume. A company advertising “manual onboarding” may have implementation pain. A company with many regional pages may have localization complexity.

Use websites to build a pain hypothesis, not just to collect an email address.

Communities

Communities can reveal repeated pain before customers search for software. Founder groups, operator groups, Slack communities, WhatsApp groups, Reddit threads, niche forums, industry associations, and local meetups often contain raw language.

Be careful: communities are not just lead databases. Contribute before extracting. If you enter only to sell, people will feel it.

Directories and Review Sites

Directories, marketplaces, app stores, SaaS comparison sites, Shopify apps, Chrome extensions, Product Hunt, G2-style review sites, startup databases, and industry directories can show both customer categories and competitor pain.

Competitor reviews are especially useful. Look for:

• Complaints about missing features.
• Pricing frustration.
• Poor support.
• Integration gaps.
• Implementation difficulty.
• Segment mismatch.

These clues help you find prospects who may be dissatisfied with current tools.

Job Postings

Job postings are underrated prospecting signals. A company hiring for a function often has a workflow problem or scaling pressure.

Examples:

• Hiring sales ops may signal CRM or process pain.
• Hiring compliance roles may signal regulatory pressure.
• Hiring support agents may signal ticket volume.
• Hiring data engineers may signal reporting or pipeline complexity.
• Hiring implementation managers may signal onboarding burden.

Use job postings as trigger events.

Existing Network

Your first prospecting asset is usually your network: classmates, ex-colleagues, investors, advisors, customers, vendors, alumni groups, founder communities, and friends of friends.

Do not ask vaguely: “Do you know anyone?” Ask specifically:

“Do you know a founder or finance head at a D2C brand doing more than 1,000 orders a month and struggling with marketplace payout reconciliation?”

Specificity makes referrals easier.

Events, Referrals, and Partners

Events can work when your customer segment is concentrated. Referrals work when the referrer understands your ICP. Partners work when they already have trust with the customer.

Do not confuse a partner conversation with a channel strategy. A partner source is useful when it produces qualified customer conversations, not polite enthusiasm.

Trigger Library

A trigger is evidence that the problem may be active now. It makes outreach feel relevant.

Trigger	What it may indicate	Example outreach angle
Hiring for a role	Function is scaling or under pressure	”Saw you are hiring sales ops. Curious how CRM hygiene is handled today.”
New funding	Growth, hiring, or process change	”After a fundraise, finance/reporting workflows often get stretched.”
New market launch	New operational complexity	”Expanding to GCC usually changes compliance and support workflows.”
Public complaint or review	Current solution frustration	”Noticed teams in your category mention slow implementation with existing tools.”
New regulation	Compliance urgency	”With the new reporting requirement, teams may need cleaner audit trails.”
Tool migration	Budget and change window	”Hiring a RevOps lead often means sales tooling is being reconsidered.”
Spike in volume	Manual process strain	”At 10,000 monthly orders, reconciliation usually stops being a small admin task.”
Leadership change	New priorities and openness	”New finance leaders often review month-end workflows in the first quarter.”

Do not invent triggers. If the trigger is weak, keep the message modest.

Prospect Qualification

A prospect is qualified when there is a reason to believe they have the pain, can act, and might trust you enough to speak.

Use this qualification table before outreach:

Factor	Question	Weak signal	Strong signal
ICP fit	Do they match the segment?	Similar industry	Same workflow, size, and buyer
Pain	Is there evidence of the problem?	Guess based on title	Trigger, complaint, hiring, tool usage, or public clue
Budget	Can they pay?	Company exists	Role, scale, category spend, or current paid alternative
Authority	Are you near the decision?	Junior user only	Buyer, influencer, or strong path to buyer
Timing	Why now?	No trigger	Hiring, growth, compliance, migration, funding, launch, churn, manual burden
Current solution	What do they use today?	Unknown	Competitor, spreadsheet, agency, manual team, internal tool
Trust path	Why might they respond?	Cold generic message	Mutual link, relevant proof, sharp insight, credible founder story

Weak qualification creates wasted calls. Strong qualification makes outreach feel like help rather than interruption.

The Qualification Threshold

Before adding a prospect to your active list, ask:

1. Do they match the ICP closely?
2. Is there visible evidence of pain or a trigger?
3. Can you identify the likely owner of the problem?
4. Is there a plausible budget category?
5. Is there a trust path: referral, credibility, proof, or strong relevance?

If you cannot answer at least three of these, the prospect may belong in research, not active outreach.

Qualification is not elitism. It is focus. Early founders have limited energy. A poor-fit call consumes the same calendar slot as a high-fit call.

List Building

Start with small lists. A founder should learn from the first 50 prospects before building 5,000.

For each prospect, capture:

• Company.
• Segment.
• Contact name.
• Role.
• Trigger event.
• Evidence of pain.
• Current likely workaround.
• Personalization note.
• Source.
• Outreach message.
• Status.
• Next step.
• Disqualification reason.

The disqualification reason is important. If ten prospects are wrong because the buyer is too small, the pain is not urgent, or the role lacks authority, update the ICP.

Account Research Notes

For each high-priority account, write a short note before outreach.

Company:
Segment:
Why this account:
Trigger:
Likely pain:
Likely buyer:
Current workaround or tool:
Trust path:
First question to ask:

This note prevents fake personalization. “Loved your post” is not personalization if it has nothing to do with the buyer’s problem. A useful note connects the prospect to the pain.

Contact Data Hygiene

The list should be clean enough for follow-up:

• Use one row per person and one company identifier.
• Separate company status from contact status.
• Record channel: email, LinkedIn, phone, referral, event, partner.
• Record last touch and next touch.
• Record reply category: interested, not now, wrong person, not a fit, no response.
• Keep disqualification reasons visible.

Even a spreadsheet is enough if it is maintained. A CRM that nobody updates is worse than a simple sheet the founder actually uses.

Prioritization

Not all prospects deserve equal effort. Score them simply:

Score	Meaning	Action
3	Strong fit, visible trigger, reachable buyer	Personalized outreach now
2	Good fit, weak trigger or unclear buyer	Research more or lighter outreach
1	Possible fit, mostly guesswork	Park for later
0	Wrong segment	Remove

Early founders should spend most energy on 3s and 2s. Chasing 1s is often emotional avoidance after rejection from better prospects.

Prospecting Board

Create a prospecting board before scaling outreach. This can be a spreadsheet, Notion table, Airtable base, or CRM view. The tool matters less than the fields.

Use these columns:

Field	Why it matters
Company	Account being tested.
Segment	Which ICP hypothesis it belongs to.
Buyer role	Who likely owns the problem.
Contact name	Person to approach.
Source	Where the prospect came from.
Trigger	Evidence the pain may be active now.
Pain hypothesis	One sentence on why they may care.
Trust path	Referral, proof, content, event, community, or none.
Outreach angle	Pain-led, trigger-led, role-led, referral-led, or proof-led.
Status	Not contacted, contacted, replied, booked, qualified, nurture, disqualified.
Disqualification reason	Why it is not a fit.

This board prevents random selling. If a founder cannot fill “trigger” and “pain hypothesis,” the prospect is probably not ready for outreach. If every row says “no trust path,” expect lower reply rates and stronger proof requirements.

The 50-Account Rule

For early B2B sales, build 50 accounts in one narrow ICP before deciding the segment does not work. Ten accounts is usually too small. Five hundred is usually too unfocused.

For each 50-account batch, keep the ICP constant enough to learn:

• Same buyer role or buying center.
• Similar company size.
• Similar trigger.
• Similar pain.
• Similar outreach channel.

After 50, review:

• How many accounts had real triggers?
• How many contacts were reachable?
• How many replies were relevant?
• How many discovery calls had real pain?
• How many had budget or authority?
• How many were disqualified and why?

If the list was bad, fix prospecting before blaming the market. If the list was good and the pain still did not appear, change the ICP or problem hypothesis.

Referral Mapping

In India especially, referral paths can beat cold outreach. But referrals work only when the ask is specific.

For each target segment, map five trust routes:

Trust route	Example ask
Existing customer	”Do you know another finance head dealing with marketplace reconciliation?”
Ex-colleague	”Can you introduce me to one RevOps leader who owns CRM hygiene?”
Investor or advisor	”Which portfolio company recently hired sales ops?”
CA, consultant, or agency	”Which clients repeatedly struggle with this workflow?”
Community operator	”Is this a recurring problem members discuss?”

Do not ask for “leads.” Ask for a person with a specific pain. A vague referral wastes social capital. A precise referral makes the introducer feel useful.

Referral Message Template

I am looking to speak with [role] at [company type] who is dealing with [specific pain], especially when [trigger].

This is not a demo request. I am trying to understand how they solve it today and whether our product may be relevant.

If one person comes to mind, would you be comfortable introducing us?

This works because it is narrow, honest, and low pressure.

Prospecting Cadence

A founder prospecting cadence can be simple:

Day	Activity	Output
Monday	Add and score 15-20 accounts	Fresh pipeline
Tuesday	Send first-touch outreach to best accounts	New conversations
Wednesday	Ask for referrals and follow up on prior touches	Warm paths
Thursday	Research and improve weak accounts	Better segmentation
Friday	Review replies, non-replies, and disqualifications	ICP learning

Do not prospect only when pipeline is empty. That creates feast-and-famine sales. Prospecting should run every week until inbound demand is strong enough to replace it.

Cleaning The List

A sales list decays quickly. People change jobs, priorities shift, companies close hiring, and your ICP improves.

Clean the list every week:

• Remove companies outside the ICP.
• Move weak-fit prospects to later.
• Update roles and contacts.
• Mark no-response accounts after the planned sequence.
• Add new trigger events.
• Convert repeated disqualification reasons into ICP changes.

The list is a learning system. If it never changes, you are not learning.

ICP Breakpoints

An ICP becomes useful when it has breakpoints. A breakpoint is a clear condition that changes urgency, budget, or workflow pain.

Examples:

Market	Breakpoint	Why it matters
D2C brand	Crosses 2+ marketplaces or 5,000 monthly orders	Reconciliation, returns, and operations get messier.
SaaS company	Crosses 10 salespeople	CRM process and pipeline reviews break.
School	Admission season starts	Lead follow-up and parent communication become urgent.
Clinic chain	Adds second location	Scheduling, records, and reporting need process.
Manufacturing business	Adds large enterprise customer	Compliance, documentation, and delivery discipline rise.
Marketplace	One side grows faster than the other	Liquidity and quality problems appear.

Prospecting improves when you search for breakpoints instead of generic titles. “Finance head at D2C brand” is acceptable. “Finance head at D2C brand that just added Myntra and is hiring finance ops” is much better.

Account Tiering

Split your list into tiers so effort matches potential.

Tier	Definition	Founder effort
A	Strong ICP fit, visible trigger, likely buyer, trust path	Deep research, personalized outreach, referral attempts.
B	Good fit, weaker trigger or unclear buyer	Light research, specific outreach, nurture.
C	Possible fit, mostly hypothesis	Park or use for broad learning.

Do not spend A-tier effort on C-tier accounts. Do not send C-tier generic outreach to A-tier accounts. Early founders often waste the best prospects with lazy messages because they are moving too fast.

Disqualification Taxonomy

Record why prospects are not a fit.

Reason	What it teaches
Too small	Pricing, support, or urgency may not work below a threshold.
Too large	Security, procurement, or integration bar may be too high right now.
Wrong role	Buyer mapping is weak.
No trigger	Timing is weak even if category fit is real.
No current workaround	Pain may be theoretical.
No budget path	Value may not map to an owner.
Existing solution good enough	Differentiation is weak for this segment.

Patterns in disqualification are as useful as wins. They tell you where the market is not.

India Angle

Indian prospecting often depends on trust routes. Alumni networks, local business communities, CA and consultant networks, founder groups, WhatsApp communities, investor portfolios, industry events, and customer referrals can open doors faster than cold email.

For Indian SMBs, the decision maker may not be active on email. Phone, WhatsApp after context, events, reseller networks, and referrals may work better. For Indian enterprises, vendor onboarding, references, procurement, and internal champions matter.

For global sales from India, your list must work harder. The buyer has less context about you, so prospecting should include proof: customer logo, case study, founder credibility, clear website, useful content, or a sharp observation.

Useful Indian prospecting routes include:

Segment	Often useful source
Startup founders	Founder groups, VC portfolio pages, accelerators, alumni groups, operator communities
SMB owners	Local business associations, CA networks, WhatsApp groups, trade events, referrals
Enterprise teams	Conferences, partner networks, LinkedIn, procurement-friendly references
Developers	GitHub, technical communities, meetups, job postings, DevRel content
D2C and commerce	Marketplace seller communities, Shopify ecosystems, logistics partners, agency networks

When using WhatsApp or phone, create context first. A cold WhatsApp pitch from a stranger can feel invasive. A referred WhatsApp introduction after a mutual contact is different.

Common Mistakes

• Scraping huge lists before defining ICP.
• Prospecting by title without a pain trigger.
• Contacting users who cannot influence purchase.
• Ignoring current workaround.
• Treating every reply as qualified.
• Failing to record disqualification reasons.
• Prospecting outside the segment because rejection hurts.
• Asking for referrals with vague customer definitions.
• Building the list once and never improving it.
• Treating a famous company as qualified only because the logo looks good.
• Ignoring small companies that have urgent pain and fast decisions.
• Researching forever to avoid rejection.
• Mixing too many ICPs in one list.

Reader Action

Build a 50-prospect list for one narrow ICP.

For each prospect, write:

• Why they match the ICP.
• What trigger suggests pain.
• Who likely owns the problem.
• What current workaround they may use.
• Why they might trust you enough to respond.

Send outreach to 10. After every reply or non-reply, update the ICP. Prospecting is not admin. It is where your sales theory meets reality.

Then write a one-page prospecting review:

• Which source produced the best prospects?
• Which trigger created the best replies?
• Which role was closest to the pain?
• Which accounts looked good but were not qualified?
• What should change in the next 50-prospect list?

Repeat this until the list starts to feel obvious. That is when the market is becoming clearer.

Prospect Quality Review

At the end of each prospecting batch, review the list quality before judging the outreach.

Review question	Why it matters
Did every account match the ICP?	A weak list makes good messaging look bad.
Did every account have a trigger?	Triggerless prospects often reply politely but do not move.
Did we contact the right role?	Users, buyers, approvers, and influencers behave differently.
Did the source create trust?	Warm, community, event, and outbound sources convert differently.
Did we over-index on logo value?	Famous accounts can hide weak urgency.
Did disqualified prospects share a pattern?	The ICP boundary may need tightening.
Which accounts deserved more research?	A-tier accounts need sharper context.

Prospecting improves when the founder learns which prospects should never have been on the list.

Trigger-Based List Examples

Useful triggers include:

Trigger	Possible sales hypothesis
Hiring for a role	The company is formalizing a workflow.
Funding announcement	Growth, reporting, or team expansion may create new pain.
New market launch	Operations, compliance, sales, or support may be stretched.
Tool migration	Existing process may be breaking or becoming expensive.
Bad review of alternative	Buyer may be unhappy with current workaround.
New regulation or platform change	Old processes may no longer work.
Rapid headcount growth	Manual coordination may be failing.

A trigger does not prove pain. It gives the founder a respectful reason to start a relevant conversation.

The 50-Account Quality Bar

Before launching a prospecting batch, inspect the first 50 accounts.

Each account should have:

• A specific reason it matches the ICP.
• A suspected pain or trigger.
• A likely role to contact.
• A trust path: mutual connection, community, proof, local context, public signal, or clear relevance.
• A disqualification note if it is excluded.

If more than 15 of the 50 feel uncertain, the ICP is too broad or the data source is weak. Fix the list before testing messaging. Bad lists produce false negatives.

Prospecting Source Scorecard

Track source quality, not just volume.

Source	Accounts found	Reply rate	Qualified call rate	Strong-fit rate	Notes
LinkedIn search
Referrals
Events
Communities
Job posts
Review mining

The best source is not always the one with the most accounts. It is the one that creates qualified conversations with the least wasted effort.

Referral Ask System

Indian founder networks can be powerful when the ask is precise. Do not ask, “Do you know anyone who might need this?” Ask for a specific profile.

Weak ask:

Do you know any companies that may need sales software?

Stronger ask:

Do you know any B2B SaaS founders in India with 5-30 people where the founder is still doing sales calls and CRM hygiene is starting to break?

Give the referrer:

• The exact customer profile.
• The pain you are studying.
• Why the intro is useful.
• A short forwardable note.
• Permission to say no.

A good referral ask should make the other person think of names immediately. If they look confused, your ICP is not clear enough.

Account Tiering System

Not every prospect deserves the same research, personalization, or founder time. Tier accounts before outreach so the team spends energy where learning and revenue quality are highest.

Tier	Account profile	Founder action
A	Exact ICP, strong trigger, reachable buyer, clear trust path.	Deep research, personalized message, founder-led follow-up.
B	Good ICP fit, some trigger, buyer likely but trust path weaker.	Light research, focused message, normal sequence.
C	Possible fit, weak trigger, unclear owner or budget.	Park, nurture, or use for low-cost learning only.
D	Outside ICP, no visible pain, or poor strategic fit.	Remove from active list.

This keeps prospecting honest. If most of the list is C-tier, the founder does not have a sales list yet. They have a research database.

Tier Review

After each batch, compare outcomes by tier:

• Did A-tier accounts reply at a higher rate?
• Did B-tier accounts become qualified after better discovery?
• Did C-tier accounts waste time?
• Did any D-tier accounts tempt the founder because the logo looked attractive?
• Which source produced the highest percentage of A and B accounts?

Prospecting improves when the founder learns which accounts are worth careful pursuit and which should never enter the pipeline.

Account Research Dossier

For high-priority accounts, do not begin with a generic message. Prepare a small dossier. The goal is not to stalk the prospect. The goal is to understand whether the account has a real reason to care.

Use this dossier for A-tier accounts:

Field	What to capture
Company context	Segment, size, geography, business model, funding or growth signal.
Trigger	Hiring, expansion, compliance pressure, new product, recent complaint, tech migration, market change.
Likely pain	The specific workflow or outcome that may be broken.
Current solution	Tool, manual process, agency, internal team, competitor, spreadsheet, WhatsApp, legacy system.
Buyer hypothesis	Role likely to own budget or consequence.
User hypothesis	Role likely to feel daily pain.
Trust path	Referral, mutual connection, relevant proof, founder credibility, local context, community, partner.
First question	The question that would reveal whether the pain is real.
Disqualification reason	What would make this account not worth pursuing now.

This dossier should take 5-15 minutes, not an hour. If it takes too long, your ICP is probably too vague or the account is not truly A-tier.

Buying Committee Clues

Even small companies have buying committees, though they may not call them that. Look for clues:

• Who posts about the problem?
• Who hires for the workflow?
• Who owns the target or penalty?
• Who signs vendor contracts?
• Who worries about security, compliance, or finance?
• Who will use the product every week?
• Who will complain if implementation fails?

For Indian SMBs and mid-market companies, the owner, founder, family member, finance head, operations lead, and trusted advisor can all influence purchase. For enterprise accounts, procurement, IT, legal, finance, and functional leadership may each slow the deal. Prospecting should discover this map early.

Prospecting By Pain Cluster

Do not only build lists by industry. Build lists by pain cluster:

Pain cluster	Prospecting signal
Hiring pressure	Many open roles for the same manual function.
Workflow chaos	Multiple tools mentioned across job descriptions or reviews.
Customer support load	Public complaints, support hiring, high ticket volume, response-time promises.
Compliance pressure	Audit roles, regulatory mentions, document-heavy workflows, formalization.
Revenue leakage	Discounts, refunds, reconciliation work, collections roles, sales ops hiring.
Expansion strain	New branches, new geographies, partner networks, onboarding roles.

Pain-cluster prospecting produces better outreach because the message can mention a specific operating problem rather than a generic category.

Prospecting Metrics That Matter

Prospecting should be measured by learning quality and qualified opportunities, not only message volume.

Track a simple funnel:

Metric	What it tells you
Accounts added by ICP tier	Whether the list is improving or filling with weak accounts.
Contact accuracy	Whether names, roles, emails, LinkedIn profiles, and phone numbers are usable.
Positive reply rate	Whether the problem and timing resonate.
Qualified conversation rate	Whether replies turn into real discovery or sales calls.
Pain-confirmed rate	Whether prospects describe recent behavior and current workaround.
Buyer-mapped rate	Whether the team identifies who can approve or block.
Next-step rate	Whether conversations produce dated next actions.
Disqualification reason	Whether the ICP, trigger, channel, or message is wrong.

Review by source. A channel that produces many replies but few qualified conversations may be noisy. A channel that produces fewer replies but more buyer-mapped conversations may be better.

Prospecting Quality Review

Every two weeks, review a sample of accounts and messages.

Ask:

• Did we target the right role?
• Was the trigger real or invented?
• Did the message name a specific pain?
• Did we ask an easy first question?
• Did we over-personalize without improving relevance?
• Which objections repeated?
• Which accounts should never have entered the list?

This review turns prospecting from brute-force activity into a learning system.

List Hygiene Rules

A bad list wastes founder time and trains the team to accept weak signal.

Use these rules:

Rule	Why it matters
Every account needs a reason to be on the list.	Prevents generic spraying.
Every contact needs a role hypothesis.	Helps discovery start with buyer/user clarity.
Every outreach batch needs one ICP.	Mixed batches make learning muddy.
Every account needs a status.	Prevents repeated accidental outreach.
Every disqualification needs a reason.	Improves future targeting.
Old lists expire.	Companies, roles, triggers, and priorities change.

Delete or archive accounts that are outside ICP, unreachable, unqualified, duplicate, or only attractive because of logo value.

The best prospecting list is not the longest. It is the one where every name teaches the founder something about a real market.

Prospecting Territory Plan

Prospecting becomes chaotic when every possible customer is treated as equally interesting. Create a territory, even if the “territory” is just a niche.

Define:

Territory element	Example
Segment	B2B SaaS companies with 50-300 employees.
Geography	India, US, Bengaluru, Mumbai, GCC, or remote-first global.
Role	CFO, sales leader, founder, HR head, clinic owner, school principal.
Trigger	Hiring, funding, expansion, compliance deadline, job posts, tool change.
Pain hypothesis	What problem is likely active now?
Trust path	Warm intro, community, event, content, reference, partner.
Exclusions	Companies too small, too large, wrong industry, no budget, poor fit.

The tighter the territory, the sharper the learning.

Prospect Data Quality Rules

Bad data wastes founder time and damages deliverability.

Rules:

Rule	Reason
Verify company fit before contact fit.	A perfect email at a bad company is still waste.
Keep source and date.	Old data decays.
Record trigger event.	Outreach needs a reason now.
Avoid personal emails unless appropriate and compliant.	Trust matters.
Tag uncertainty.	Do not pretend weak data is strong.
Remove bad-fit accounts quickly.	List quality beats list size.

A small clean list is better than a large lazy list.

Prospecting Weekly Review

Review:

Metric	Founder question
New accounts added	Are they in the ICP?
Accounts researched	Do we know why now?
Contacts found	Are they likely buyers, champions, or influencers?
Outreach sent	Was it personalized by real relevance?
Replies	Which segment and trigger worked?
Meetings booked	Were they qualified?
Disqualifications	What did we learn about the ICP?

Prospecting should make the ICP sharper every week.

Buying Trigger Research

A prospect is much stronger when you know why the problem may be active now. Without a trigger, outreach feels random and sales cycles drift.

Look for trigger evidence:

Trigger	What it may indicate	Where to look
Hiring for a role	Team is scaling, replacing manual work, or fixing a gap.	Job posts, LinkedIn, careers pages.
Recent funding	Growth targets, new systems, or expansion pressure.	Funding news, founder posts, investor updates.
New geography or channel	Operations, compliance, sales, or support complexity.	Website changes, press, marketplace listings.
Customer complaints	Retention, support, quality, or delivery pain.	Reviews, social comments, forums.
Tool adoption	Workflow change already underway.	Job descriptions, integrations, case studies.
Compliance deadline	Urgency and budget may be clearer.	Industry updates, customer announcements.
Leadership change	New owner may revisit old problems.	LinkedIn, company announcements.
Competitor movement	Buyer may be comparing options.	Review sites, community posts, public references.

For each account, write the trigger in one line:

We are reaching out because this company appears to be:
That may create this problem:
The likely owner is:
The first useful question is:

If you cannot name a trigger, the account may still be valid, but the message must be softer: ask for learning or referral, not immediate evaluation.

Prospecting Disqualification Rules

Good prospecting removes bad accounts quickly. Founders often keep weak prospects because deleting them feels like reducing opportunity. It usually increases focus.

Disqualify when:

Signal	What to do
No plausible pain	Archive unless a new trigger appears.
Wrong company size	Move to a different ICP tier or exclude.
User exists but no buyer	Keep for learning, do not forecast.
Buyer exists but no urgency	Nurture around trigger events.
Bad data	Fix source quality before sending more.
Repeated no-response from same source	Review source, trigger, and message.
Logo attractive but workflow mismatch	Archive unless strategic learning is explicit.
Long sales cycle beyond runway	Treat as learning or partnership, not near-term revenue.

This is especially important for Indian founders selling globally. A famous logo can consume months. Early sales should prioritize reachable pain, not social proof fantasies.

Account Priority Score

When the prospect list grows, score accounts so the founder spends energy where learning and revenue are most likely.

Score each account 0-2:

Factor	0	1	2
ICP fit	Weak or unclear.	Partial fit.	Strong match to chosen segment.
Trigger	No reason now.	Possible trigger.	Recent, specific trigger.
Pain likelihood	Generic problem.	Likely pain.	Clear workflow pain visible.
Buyer access	No path.	Possible contact.	Named buyer/champion path.
Trust path	Cold and low credibility.	Some relevance.	Warm intro, reference, community, or proof fit.
Deal value	Too small or unclear.	Useful learning or modest revenue.	Strong revenue/reference/repeatability value.

Interpretation:

• 10-12: priority account.
• 7-9: work in focused batches.
• 4-6: nurture or use for learning.
• 0-3: archive unless new evidence appears.

This prevents the founder from treating every logo as equally valuable. Early sales needs unfair focus, not democratic attention.

Related Links

• 56. Founder-Led Sales
• 58. Cold Outreach
• 59. Discovery Calls
• 138. Founder Sales Call Playbook