Sales Plan: An Evidence-First 90-Day Template for B2B Teams

A revenue target is not a sales plan. “Reach $1 million,” “book 40 meetings,” or “grow enterprise” describes a desired result. It does not say which buyers deserve attention, what the team will do next week, which constraint matters, or what evidence would justify a change.

A useful plan connects the target to capacity, accounts, actions, owners, and review decisions. It also preserves uncertainty. Instead of pretending that the quarter is predictable, it states the assumptions the team will test and the rules for keeping, changing, or stopping a motion.

This guide provides an evidence-first, 90-day template for B2B teams. It is designed to fit on one operating page, with supporting account and pipeline views behind it.

Separate the target, plan, pipeline, and forecast

Four documents often collapse into one spreadsheet. Keep their jobs distinct:

• Target: the outcome the business wants to achieve.
• Sales plan: the choices, resources, actions, and tests intended to reach it.
• Pipeline: the open opportunities moving through a defined sales process.
• Forecast: the revenue likely to close in a period based on current evidence.

The target can exceed the forecast. The plan should explain how the team intends to close that gap. The pipeline should show whether the plan is producing qualified opportunities. Our sales forecasting methods guide explains how to estimate the outcome without turning stage probabilities into certainty.

Start with a baseline, not a blank template

Before choosing tactics, describe the current system. Salesforce's current sales-planning guidance recommends grounding the plan in capacity and historical CRM data, then revisiting it as conditions change. For a small B2B team, the baseline can be simpler, but it still needs evidence.

Record the last comparable period:

• revenue won, average contract value, and sales-cycle distribution;
• qualified pipeline created, won, lost, and still open;
• conversion between stages, using consistent stage definitions;
• accounts contacted, replies, meetings, and qualified opportunities by segment and channel;
• available seller hours, ramp status, tooling, and budget;
• known data gaps, including work tracked outside the CRM.

Use a comparable period, not whichever month makes performance look best. Separate facts from estimates. If a field is unreliable, mark it as unreliable rather than quietly using it in the plan.

The one-page B2B sales plan template

Pipedrive's June 2026 guide connects a sales plan to goals, target customers, responsibilities, timelines, activities, and performance measures. The following version adds evidence and decision rules so the page can run a weekly review rather than become a presentation artifact.

Field	What to write	Control question
Objective	One outcome, one period, one unit	Is it an outcome rather than an activity?
Baseline and gap	Current run rate, capacity, and difference to target	Which inputs are observed, estimated, or missing?
Priority market	Segments, account criteria, exclusions, and named account set	What will the team deliberately not pursue?
Buyer problem	Observable situation and consequences to verify	What evidence would prove the hypothesis wrong?
Motion	Inbound, outbound, partner, expansion, or another defined route	Why does this motion fit the market and available capacity?
Weekly actions	Specific work with owners, dates, and account scope	Can the team complete it with the time available?
Measures	Leading indicators, pipeline evidence, and revenue outcomes	Which measure supports a decision this week?
Resources	People, hours, data, content, tools, and budget	Which constraint limits the plan first?
Risks and dependencies	Assumptions, external dependencies, and fallback choices	What trigger activates the fallback?
Review rules	Weekly cadence plus keep, change, and stop criteria	Who can change scope, budget, or target?

Turn a revenue gap into testable inputs

Do not reverse-engineer activity quotas from an industry benchmark. Start with your own ranges. If the goal is new revenue, identify the average value and number of wins required. Then work backward through observed win rate, qualification rate, meeting rate, and contact rate for the chosen segment.

Use low, base, and high scenarios when the sample is small. For every rate, record the period, population, and exclusions. A conversion rate from warm referrals should not set the activity plan for cold outbound. A large-enterprise cycle should not be averaged with a self-serve motion.

Then test the plan against capacity:

1. Estimate the hours required for research, contact, follow-up, meetings, and CRM updates.
2. Compare those hours with real seller capacity after existing opportunities and customers.
3. Reduce scope or change the motion when the plan requires impossible throughput.
4. Keep the unresolved revenue gap visible instead of hiding it inside a higher activity target.

Capacity makes strategy concrete. If the team can research only 50 high-value accounts well, a plan for 500 “personalized” accounts is not ambitious. It is internally inconsistent.

Days 1–30: establish the market and evidence

The first month should reduce uncertainty before the team scales activity. Select one priority segment and a bounded account set. Define the ideal customer criteria, but also define exclusions: geography, company maturity, business model, technical dependency, contract size, or any condition that makes the offer a poor fit.

Use the ideal customer profile guide to document the segment, then apply account scoring to rank companies without pretending that a company score identifies a willing individual buyer.

Deliverables by day 30:

• a sourced baseline and capacity view;
• a named account list with inclusion and exclusion reasons;
• two or three buyer-problem hypotheses, each with disconfirming evidence;
• a message or conversation angle for each hypothesis;
• stage definitions and minimum opportunity evidence;
• one primary motion and one explicit fallback.

Interview customers, salespeople, and customer-success colleagues when available. Public research can form a hypothesis, but it cannot replace a buyer confirming how the problem works in their context.

Days 31–60: run a controlled sales motion

The second month is for execution with enough control to learn. Use a defined account cohort, a stable qualification rule, and one primary value hypothesis. Variation is useful only when the team records what changed.

For every weekly batch, preserve:

• which accounts and buyer roles were included;
• the source behind each factual personalization claim;
• the channel, message version, and send date;
• replies classified by outcome, not just positive or negative;
• meeting notes, qualification evidence, next buyer action, and date;
• time spent and any manual work that prevents the motion from scaling.

Automate stable, low-judgment work such as deduplication, reminders, and record updates. Keep human review for account fit, sensitive claims, message approval, and consequential next steps. Our sales pipeline automation guide explains which stage transitions should remain evidence-gated.

Days 61–90: reallocate, document, and prepare the next plan

The final month is not a victory lap. Compare the plan with the observed market. Reallocate time from weak segments or channels only when the evidence is comparable. A low reply rate may indicate a list, message, offer, timing, or deliverability problem. Diagnose the broken link before changing everything.

By day 90, decide:

• Keep: which segment, problem, and motion deserve another cycle?
• Change: which assumption needs a new test, and what changes alone?
• Stop: which work consumed capacity without producing useful evidence?
• Standardize: which repeatable step belongs in the sales process or training?
• Escalate: which constraint requires a product, pricing, hiring, or leadership decision?

Carry forward the baseline, the evidence, and the decisions. Do not copy the old task list into the new quarter and call it planning.

Run a 30-minute weekly sales-plan review

1. Five minutes: capacity. What changed in people, hours, budget, or dependencies?
2. Five minutes: execution. Which planned actions happened, and which did not?
3. Ten minutes: evidence. What did accounts and buyers do or say?
4. Five minutes: pipeline. Which opportunities entered, advanced, stalled, or left?
5. Five minutes: decision. Keep, change, stop, or escalate one item with an owner.

Bpifrance Création's framework for a commercial action plan similarly records objectives, actions, target, owner, budget, dates, indicators, and actual results. The operating improvement is to review those fields as a decision system, not only as an annual planning table.

Add a “not this quarter” list

A plan becomes credible when it excludes attractive work. List the segments, channels, features, events, tools, and experiments the team will not pursue during the period, plus the condition that would reopen each decision. This prevents a new idea from quietly consuming the capacity assigned to the plan.

The list is not permanent. It protects the current test. Review it when evidence changes, not whenever a competitor launches a campaign.

Where AI helps, and where it creates false confidence

AI can help a team:

• assemble baseline metrics from approved systems;
• calculate low, base, and high scenarios;
• detect inconsistent assumptions or missing owners;
• summarize sourced account evidence and meeting notes;
• prepare the weekly variance review;
• suggest questions that would confirm or reject a hypothesis.

It cannot validate a market merely by producing a polished document. Require links for factual claims, label inferences, preserve the original data, and keep a human accountable for target, budget, customer exclusions, and outreach approval. A detailed hallucination is still a bad plan.

What the last 30 days add

Recent public discussion was thin and noisy, so it does not support a new benchmark. The usable pattern is operational: small B2B teams continue to describe chaos when plans, CRM workflows, and ownership are disconnected. Current 90-day guides also converge on sequencing definition before execution and reviewing one change at a time.

Treat that as language from the market, not proof of a universal formula. Your plan still needs its own baseline, buyer evidence, and capacity test.

How Lead Scorer supports the plan

Lead Scorer helps turn a priority market into a reviewable account set. Teams can score companies and people separately, retain the evidence behind the score, enrich selected records, and prepare qualified leads for human review. That supports the account-selection and evidence layers of a sales plan.

It does not choose your target, invent buyer intent, or replace the weekly decision. Use it to make inputs more consistent, then use buyer responses and opportunity evidence to update the plan.

Takeaway

A sales plan should show how a team moves from its current baseline toward one objective with finite capacity. Define the priority accounts, buyer problem, motion, actions, evidence, owners, and decision rules. Run the plan for 90 days, review it weekly, and make every change traceable to evidence.

Want a cleaner account set for the next 90-day plan? Try Lead Scorer for free →.