
Tools and providers
Part of Buy local service marketing tools outright or rent a managed supplier?
How to implement local service marketing tools in stages
How to run local service marketing tool implementation in stages, from job statement and pilot scope to data migration and a stop rule you set at signature.
What to take away
- Bundled monthly plans make it easy to keep paying for features nobody switches on, so implementation discipline now decides whether a tool earns its place.
- Start with a written job statement naming one workflow and one measure.
- Pilot one service line or one town, so failures stay cheap and comparisons honest.
- Test the mobile landing page before buying more traffic, since most local enquiries arrive on a phone.
- Fix the review date at signature, with a stop rule you are willing to enforce.
Write the job statement first
A tool implementation begins as a written job statement: one paragraph, one owner, one measure.
Job statement example
- 40missed calls per month
- 15target missed calls
- 1quarter to achieve
For example, a plumbing firm might write: cut missed calls on emergency work from 40 a month to 15 within a quarter. That sentence settles most later arguments about scope.
It names the workflow you are changing and the number that proves it worked. Without it, every supplier demonstration looks convincing, because demos show software at its best rather than your busiest Tuesday.
Keep the statement short enough to read aloud. If it needs a second page, the scope is too wide to pilot.
Copy this into your notes and fill it in:
- Job statementcut [measure] on [workflow] from [now] to [target] by [date].
- Owner[name]. Weekly user: [name]. Review date: [date].
- Stop ruleif [measure] has not moved by [review date], cancel or replace.
Decide who owns the tool day to day
Name one person who logs in weekly and one person who can switch the tool off. The weekly user usually sits closest to the work: a dispatcher, branch manager or senior technician.
Tool ownership roles
- Name one weekly user
- Name one switch-off owner
- Record both names
- Record hours each will spend
- Weekly user sits closest to work
The owner needs authority to change how enquiries are handled. A tool that routes leads into an unread inbox is an expensive form builder.
Record both names in the job statement, along with the hours each will spend on it. Underestimate that time and the pilot quietly dies in week three.
Choose the pilot boundary
Pick one service line, one town or one team. A pilot boundary should be small enough to compare against a control you already understand.
Pilot boundary choices
- Pick one service line
- Pick one town
- Pick one team
- Start where enquiry volume is steady
- Write down exclusions
Start where enquiry volume is steady. Seasonal peaks distort early results and make a mediocre tool look good.
Write down what the pilot excludes as well as what it includes, so nobody assumes the rollout has already happened.
Common supplier categories are call tracking, enquiry management (CRM), online booking and review requests. Named examples include CallRail for call tracking, HubSpot for a free CRM tier, and Google Business Profile for local listings.
Costs depend on seats, tracked numbers and call volume. Free tiers cover a first pilot for some categories, while paid plans are usually billed monthly per user or per number. Ask each supplier for a 90-day pilot price before you sign an annual contract.
For a wider view of how categories and suppliers fit together, the local service marketing tools and supplier guide sets out what to compare and what to ignore.
Prepare the data before switching anything on
Export your current enquiry list, tidy duplicates and agree which fields matter. Migration is where most implementations stall.
Check consent and retention rules before moving anything. Importing contacts simply because they sit in an old spreadsheet is a common and avoidable mistake.
The ONS business demography release is published annually and tracks how quickly the small firm population turns over; check the most recent edition for current UK business births and deaths. Clean records you own beat a bought list every time.
Run the old and new processes side by side for a fortnight before cancelling anything, and note where the new one is slower.
Fix the mobile journey before adding traffic
Most local searches happen on a phone, often on a weak signal. Slow forms and small tap targets waste leads you already pay for.
Google's guidance on optimising your website for mobile covers page speed, form length and how landing pages affect ad quality and cost. Work through that list before raising budget.
TikTok's help on creating a catalogue explains feed structure and the local targeting options inside its ads manager, useful if you plan to run short video.
Test the whole path on a mid-range Android phone using mobile data, not office wifi. Ask someone outside the business to try it and watch where they hesitate.
Before and after: what good implementation looks like
Before and after
Before
- Job statement
- "Get more leads"
- Ownership
- Shared inbox
- Scope
- All towns at once
- Data
- Old spreadsheet, unverified
- Mobile form
- Nine fields, slow load
- Review
- None scheduled
After
- Job statement
- One named workflow and measure
- Ownership
- Named weekly user and switch-off owner
- Scope
- One town, one service line
- Data
- Fields agreed, consent checked
- Mobile form
- Four fields, tested on 4G
- Review
- Fixed date with a stop decision
Set the review date and the stop rule
Agree the review date when you sign, not when the renewal notice arrives. Ninety days suits most local pilots.
At review, ask three questions. Did the measure move? Did the weekly user keep logging in? Would you buy it again at the same price?
Two yes answers mean continue. One or none means stop, renegotiate or replace. Write the decision down, because renewal inertia is the real cost.
For a structured way to compare replacements, the local service marketing software selection guide covers scoring criteria you can reuse at the next decision.
Common questions
How long should a pilot run before a rollout?
Ninety days is a practical default for most local service firms, long enough to cover a full enquiry cycle.
What if the tool works but nobody uses it?
That is an ownership problem, not a software problem. Reassign the weekly user, retrain them, or accept that the tool should be cancelled.
Do we need new consent to move old enquiries into the tool?
Often yes, depending on how the data was collected and what you plan to send. Check your lawful basis before importing and record the decision.



