Before you write a prospecting software ninety day plan

What to take away

Most teams build the plan around tools they have already bought, then wonder why nobody follows it. Start from the decision the plan must change.
Three horizons beat three equal months: days 1 to 30 fix data and access, days 31 to 60 test the motion, days 61 to 90 prove or stop it.
One primary metric per horizon, agreed before the first message goes out, is enough to judge the plan.
A written scoring rubric stops the review drifting into opinion when results are mixed.
Compliance sits inside the planUK GDPR and PECR, the Information Commissioner's Office direct marketing checklist, and the Telephone and Corporate Telephone Preference Services decide which lists you may contact.

Why does a ninety day plan usually fail?

The usual failure is a plan built backwards from a licence renewal. Nobody names the decision the plan should change, so nothing gets prioritised when the quarter turns busy.

Failing plan vs workable plan

Failing plan

Starting point: Licence renewal
Prioritisation: Nothing gets prioritised
What it tracks: Activity, e.g. emails sent
Result: Nobody knows if it worked

Workable plan

Starting point: Decision to change
Prioritisation: One question drives it
What it tracks: Progress against decision
Result: Quarter can be judged

A workable plan starts with one question: what will we stop doing if this works? A vague answer means it is a shopping list rather than a plan. The prospecting software strategy and planning guide covers how to fix that decision before you commit dates to a calendar.

Planning context still matters. Plans that ignore budget cycles and existing pipeline commitments get rewritten by week three.

Teams that skip this step often buy licences to answer a symptom. Their plan then tracks activity, such as emails sent, rather than progress against the decision. Activity rises and nobody can say whether the quarter worked.

Who owns each horizon?

Name one owner per horizon. Shared ownership across revenue and marketing is the fastest route to a stalled plan.

One owner per horizon

Days 1-30
Data access owner cleans records
Days 31-60
Motion owner tests sequences
Days 61-90
Budget holder scales, adjusts or stops

Budget an hour a week for each owner, and put a review in the calendar at every horizon boundary.

Days 1 to 30 belong to whoever controls data access. Their job is unglamorous: clean records in the CRM the team already runs, whether that is HubSpot or Salesforce, then screen the list against the Telephone Preference Service and the Corporate Telephone Preference Service before anyone calls. Where enrichment is needed, use a named provider such as Cognism, Clearbit, Lusha or ZoomInfo rather than a scraped file, and run the file through a verification tool such as ZeroBounce or NeverBounce before the first send. Confirm the lawful basis as well: under UK GDPR and PECR that is usually a recorded legitimate interests assessment, with consent records kept for any contact who has opted in.

Days 31 to 60 belong to the person running the motion, testing sequences in a sales engagement tool such as Outreach, Salesloft, Lemlist or Apollo.io and reporting against the primary metric. Intent data from a provider such as Bombora can decide which accounts enter that test first. The test belongs to the plan, not to the tool: the software holds the sequence, the owner holds the decision.

Days 61 to 90 belong to the budget holder, who decides whether to scale, adjust or stop, on a date written into the plan. That decision covers the licence as well as the motion: how many seats are renewed, which tools are dropped and what the next quarter's spending is allowed to reach.

Where several teams touch the same data, a light framework prevents duplicated effort. The prospecting software strategy framework sets out how to split ownership without splitting accountability.

What does the ninety days look like week by week?

The horizons stay labels until they are dated. A workable shape for the first one: in the first week, agree the decision the plan must change and name the owner; in the second, audit the CRM, screen the list against the TPS and the Corporate TPS and record the lawful basis; in the third, choose the enrichment, verification and sequencing tools and run a test file through them; in the fourth, work through the ICO direct marketing checklist and write the threshold and the review date into the plan.

The second horizon repeats a shorter cycle. Launch the first sequence in the engagement tool, review the primary metric every week, and change one variable per test so the result means something.

The third horizon belongs to the budget holder. Assemble the evidence, hold the boundary review on the date already in the calendar, and record the scale, adjust or stop decision with its reasoning.

What should the scoring rubric measure?

Score the plan, not the vendor, so review meetings stay honest when early numbers look flat.

Criterion	What good looks like	Weight
Decision clarity	The plan names one decision it must change	25%
Data readiness	Lawful basis and suppression confirmed before contact	20%
Metric discipline	One primary metric per horizon, agreed in advance	20%
Ownership	A named person per horizon, with time allocated	20%
Review trigger	A dated scale, adjust or stop decision	15%

Score each row out of five, multiply by the weight, total the result. Below 3.0 overall, rewrite the plan before spending further. Above 4.0, it is ready to run.

How do compliance rules shape the plan?

Consent and claim rules determine which lists you may contact and what you may say. In the UK the regime is UK GDPR and PECR: consent or a recorded legitimate interests assessment for the lawful basis, and screening against the Telephone Preference Service and the Corporate Telephone Preference Service before any call. Channel rules differ, and the organisation you contact matters as much as the message, so a single blanket policy rarely survives a live sequence. Build those checks into days 1 to 30 rather than treating them as a legal afterthought.

The Information Commissioner's Office publishes a direct marketing checklist that works as an audit tool during the first horizon. Work through it before the first sequence goes live, and pay the data protection fee that registration requires unless the organisation is exempt.

Advertising claims are covered separately by the advertising self-regulation system run through the Committee of Advertising Practice. Check any performance claims against the relevant code before launch.

If the plan targets a specialist audience, such as veterans or defence-adjacent buyers, population data can inform sizing. The Office for National Statistics publishes armed forces community statistics for that purpose, not for individual targeting.

How do you know whether to scale or stop?

Set the threshold on day one. For example, a team might agree that a 4% reply rate across 500 contacts justifies scaling to 2,000. Those figures are illustrative, not benchmarks.

Name the person who makes that call and the date they decide. A decision without a date drifts into the next quarter and takes the plan with it.

At day 90, three outcomes are possible: scale, adjust or stop. Write all three into the plan with their conditions, because a plan that describes only success cannot be acted on.

Record the decision and the reasoning, so the next ninety days start from that record.

Common questions

How long should the plan be?

One page per horizon is enough. Length signals effort, not clarity.

What if the primary metric is wrong?

Change it at a horizon boundary and note why. Mid-horizon changes usually hide a weak test.

Does the plan need legal sign-off?

Get a compliance check on lists and claims before day 31. That means screening against the TPS and the Corporate TPS, confirming the lawful basis under UK GDPR and PECR, and working through the ICO direct marketing checklist. That is faster than fixing problems later.