Sales Prospecting Plan: A 30-Day B2B Operating Template

A prospecting target is not a prospecting plan. “Book more meetings” says nothing about which accounts deserve attention, what a seller should verify before reaching out, or when to stop a weak experiment. A usable sales prospecting plan makes those decisions explicit.

The template below runs for 30 days. It is deliberately smaller than a quarterly sales plan: one segment, one account cohort, named owners, a bounded contact test, and a weekly decision. The account and contact numbers in the example are illustrative, not performance benchmarks.

Start with the decision, not the channel

Decide what the month needs to establish. Is a segment reachable? Can you identify the buying role? Does your problem hypothesis earn a conversation? These are different questions. Pick one primary learning objective, then write the evidence that would change your mind. A reply is useful, but it is not the same as a qualified opportunity.

For example: “We will test whether operations leaders at growing B2B service firms own the lead handoff problem.” The decision rule could be: continue only if real conversations confirm ownership and a current consequence. This is a hypothetical test, not a claim about any market.

The one-page prospecting plan

1. Segment and exclusions. Describe company type, size, geography, trigger, and the accounts to exclude. A broad ICP without exclusions creates a list that cannot be worked well.
2. Account cohort. Record the source and verification date for each company. Separate confirmed facts from assumptions and leave uncertain accounts in a review queue.
3. Buyer hypothesis. Name a likely role and the problem it may own. Do not treat a title match, website visit, or model score as proof of buying intent.
4. Capacity and ownership. Allocate realistic research and follow-up time per seller. Assign an owner before outreach so responses cannot fall between teams.
5. Contact rule. Choose channels by relevance and permission, not by a fixed touch quota. Define the first useful observation, a neutral question, and an exit condition.
6. Learning loop. Review accepted accounts, valid contacts, conversations, qualified meetings, and disqualification reasons every week. Decide what to keep, revise, or stop.

A four-week operating rhythm

Week 1: build and verify. Assemble one account cohort. Check whether companies fit the segment, whether the contacts are current, and whether the apparent signal is attributable to the right account. Do a manual quality review before scaling any list.

Week 2: test the opening. Use a small, reviewable set of accounts. Write one observation grounded in a source, label the inference, and ask a question the recipient can answer easily. Record unanswered, wrong-person, not-now, and active-problem replies separately.

Week 3: examine the bottleneck. If records are wrong, fix sourcing. If the right people say the problem is irrelevant, revisit the segment or hypothesis. If they discuss the problem but do not accept a meeting, inspect the proposed next step. Changing copy cannot repair every upstream defect.

Week 4: decide and document. Keep the cohort and expand only if the evidence supports it. Otherwise narrow the segment, change the role, or stop. Save the reasons, not just the final counts, so next month's plan begins with learning rather than a reset.

Measure the chain, not just activity

Use a simple chain: sourced accounts → accepted accounts → valid contacts → conversations → qualified meetings → opportunities. Each transition answers a different question. A high activity count with few accepted accounts signals a targeting or data issue; many valid contacts with no conversation may signal a relevance or channel issue. Small samples should be treated as diagnostic, not statistical proof.

Keep a short reason code for every rejection and reply. “No budget,” “wrong owner,” and “not relevant” imply different actions. The weekly review should choose one constraint to fix, rather than change the list, copy, channel, and schedule at the same time.

Use AI for preparation, not invented certainty

AI can help organize account research, highlight missing fields, and draft a concise brief. Every factual claim still needs a source and date. Have a person validate the target role, outreach rationale, and final message. If the evidence is weak, mark it as a hypothesis or do not contact the account yet.

Salesforce describes prospecting as a process of research, prioritization and outreach in its sales prospecting guide. The plan above makes the decisions between those activities explicit. For the broader revenue context, see our 90-day sales plan; for the evidence needed before one conversation, use the pre-call planning guide. A prospecting plan is the bridge between the two.

If you need a way to research and prioritize a target list before sellers take over, explore Lead Scorer. Start with a small verified cohort and retain human approval of contact decisions.