When to rebuild your prospecting software planning template

What to take away

Rebuild the template when targeting, lawful basis, budget or review cadence changes, not on a fixed annual date.
The ICO's lawful basis guidance anchors consent and legitimate interest decisions, which most templates still handle loosely.
Aim for one page per planning area. Length is a sign the template is doing too much.
Set a review trigger as well as a review date, so the plan keeps pace with pricing and audience shifts.
Treat the template as a living document. If nobody has edited it in a quarter, it is not being used.

Why the template needs a trigger, not just a date

Most teams rebuild their prospecting software planning template once a year, before budgets are set. That rhythm suited predictable buying cycles. It fits less well now, when targeting rules, platform costs and consent expectations move between planning rounds.

Define triggers instead. A trigger is an event that forces a review: a new market segment, a change to your lawful basis for email capture, a platform pricing change, or a fall in reply rates that no small fix explains.

The prospecting software strategy and planning guide sets out the wider planning cycle this template sits inside, so read it before restructuring anything.

What the template should contain

Keep it to six areas, each on its own page: objective, audience, lawful basis and data sources, channels, budget, and review triggers. Six pages is a good sign; a document that runs to a dozen is one nobody edits.

Six template sections

Objectiveone sentence, with a number
Audiencenamed segments and exclusions
Data and consentsource and lawful basis
Channels and toolsin scope, out of scope
Budgetline per channel, contingency
Review triggers and owners

For an illustrative example, a team paying £400 a month for its core platform might split that across two channels and hold £50 back as contingency. The figure is illustrative, not a benchmark.

Name the tools on that page. A budget line that reads "prospecting platform" tells the next reader nothing and makes the plan impossible to audit when pricing moves. Write down the product, the plan, the seats and the renewal date. Names such as LinkedIn Sales Navigator, Apollo.io, Cognism, Hunter.io and Outreach each bill on their own basis, so the same headcount can produce very different bills.

Get the data and consent section right

This is the section most templates rush. Under UK GDPR you need a lawful basis before processing contact data, and you must be able to name it. The ICO's guidance on lawful basis lists the six options — consent, contract, legal obligation, vital interests, public task and legitimate interests — and explains how to document them.

Recording lawful basis

Name the lawful basis before processing
Write it in plain words in the template
Record source and date for bought lists
Record consent capture and withdrawal handling

Write the basis into the template in plain words. For example: "Business contact data processed under legitimate interests, with an opt-out honoured within 48 hours." That beats a link to a policy nobody opens.

Where you buy lists, record the source and the date. Where you rely on consent, record how it was captured and how withdrawal is handled.

Our prospecting software strategy framework for England shows how this connects to segmentation and channel choices, which helps when two teams disagree about which records belong in scope.

Choose channels with evidence, not habit

List the channels you will actually run, then delete any channel with no owner. A template naming six channels but staffing two is a wish list.

LinkedIn's advertising resources and benchmarks publish guidance teams use to sanity-check reach and cost assumptions before committing budget.

If you sell into construction, the ONS construction industry statistics cover business counts and output, giving a defensible basis for sizing a segment rather than guessing.

Set the review cadence

Put two dates in the template: a light quarterly check and a full annual rebuild. Add the triggers from above.

Assign one owner per section. Shared ownership means no ownership. Record decisions in the template, with the date and the reason, so the next rebuild starts from evidence rather than memory.

Template checklist

One objective, with a number and a deadline.
Named audience segments and explicit exclusions.
Lawful basis recorded for every data source.
Channels listed with a named owner each.
Budget split by channel, plus contingency.
Review dates and review triggers written down.
Version number and last-edited date on page one.

Common questions

How often should the template be rebuilt?

A light check each quarter and a full rebuild once a year suits most teams. Trigger events override both.

Who should own the template?

Usually the sales or revenue operations lead, with one named owner per section. Marketing should review the data and consent section.

Can we use one template across several markets?

Yes, but keep lawful basis and channel notes per market. Consent rules and platform costs differ, and a blended section hides that.

What is the most common mistake?

Leaving data and consent vague. If the template cannot name a lawful basis for each source, fix that before adding channels.