Operations
Part of Running prospecting software operations: workflow, data quality and compliance
Before you switch on the prospecting software operating workflow
A step-by-step guide to running a prospecting software operating workflow in England: owners, entry and exit rules, a scoring rubric and monthly quality checks.
What to take away
- The most common failure is switching on automation before anyone owns routing rules, data hygiene and follow-up quality. Tools without ownership drift within a quarter.
- Write the workflow as a sequence of decisionswhere a record enters, who touches it, what counts as qualified, and when it leaves.
- Build a scoring rubric before you configure lead scores in the tool. The rubric is the policy; the software merely enforces it.
- Treat the workflow as a compliance task as well as a sales task, covering data protection and payroll where staff are paid on outcomes.
- Review it monthly against evidence, not sentiment. Small corrections beat annual rebuilds.
Most teams buy the licence, import a list and expect pipeline to appear. That is the mistake. A prospecting software operating workflow is a set of human decisions, and the software only records them. If nobody owns the routing rules, records sit unassigned, follow-up slips and the reporting tells you nothing useful.
Who owns each step of the workflow?
Name a single owner for each stage before configuration starts. Typical stages are capture, enrichment, scoring, routing and handover.
One Owner Per Stage
- Capture: one named owner
- Enrichment: one named owner
- Scoring: one named owner
- Routing: one named owner
- Handover: one named owner
Ownership means one named person answers for the output. A shared inbox is not ownership. If two people own routing, nobody does.
Write the owner into the tool as a named field or queue, so an auditor can see who acted and when. For broader role design and review cadence, see the operations and delivery guide.
What does this look like in prospecting software?
In HubSpot, map entry source and fit/intent to contact properties, use workflow enrolment criteria and owner assignment, and create a task for handover; in Salesforce, use lead fields, assignment rules and queues for the same steps. For research sourced via LinkedIn Sales Navigator or Apollo, carry the source into the CRM and review permission before outreach: a saved or enriched record is not itself permission to contact.
How should records enter and leave the workflow?
Define entry points precisely. A form fill, a list import, a webinar registration and a manual add are four sources with four different quality profiles.
Entry and Exit Rules
- Entry: form fill
- Entry: list import
- Entry: webinar registration
- Entry: manual add
- Exit: qualified
- Exit: disqualified with reason code
- Exit: dormant for stated period
Set an exit rule too. A record leaves the active workflow when it is qualified, disqualified with a reason code, or dormant for a stated period.
Without an exit rule, the database grows and reporting inflates. For example, a team adding 2,000 records a month with no exit rule may report a healthy pipeline while only 60 records are genuinely workable.
What does a workable scoring rubric look like?
Fit and intent should be scored separately, then combined. Fit describes the account; intent describes the behaviour. Keep the bands few and the definitions plain.
Workable scoring rubric
| Band | Fit signals | Intent signals | Action |
|---|---|---|---|
| A | Sector, size and territory match | Two or more high-intent actions in 30 days | Route to named rep within one working hour |
| B | Partial fit, one gap | One high-intent action | Nurture sequence, review after 14 days |
| C | Poor fit on two or more criteria | None recorded | Suppress from outreach, retain for reporting |
For example, use A for strong fit and intent, B for a fit with weaker or incomplete intent, and C for poor fit or no useful intent. Define the evidence for each band before mapping it to score thresholds in the software, and keep fit and intent visible as separate fields.
Record the reason for every downgrade. A rubric nobody can explain to a new starter is not a rubric.
How do you check quality without slowing the team?
Sample. Pull ten routed records a week and check four things: the correct owner, the correct band, evidence for the band and a logged next action.
Where the workflow feeds a paid landing page, check mobile usability against Google Search Central's Mobile-first indexing best practices. This guidance concerns how Google crawls and indexes mobile pages; it does not set a lead-routing rule.
If outreach or advertising runs through LinkedIn, distinguish prospecting in LinkedIn Sales Navigator from advertising. LinkedIn's Thought Leader Ads guidance is specific to that ad format, not a general guide to connecting a prospecting workflow.
Which UK rules affect the workflow?
Apply the UK GDPR and Data Protection Act 2018 when processing personal data, and the Privacy and Electronic Communications Regulations 2003 (PECR) to electronic marketing. Choose and document a lawful basis, provide required privacy information, and respect the right to object to direct marketing; PECR can require prior consent for marketing to individual subscribers, while rules differ for corporate subscribers. Check whether your organisation must pay the ICO data protection fee and appear on its register. For employee commission or bonuses, follow HMRC's PAYE and Real Time Information (RTI) payroll reporting rules.
Scotland, Wales and Northern Ireland share the same tax authority, so the payroll point applies across the UK.
For service expectations, including response times and complaint handling, see the site's service standards overview for England; treat it as an operating reference, not a substitute for legal requirements.
Common questions
How long does it take to set up the workflow?
For a team of ten, allow two to three weeks for ownership, entry and exit rules, and the rubric. Configuration in the tool usually takes a further week.
Do we need a scoring rubric if the software has one built in?
Yes. The built-in score is a configuration, not a policy. Write the rubric first, then map it to the tool's fields.
Who should own quality checks?
A sales operations lead, not a front-line rep. The check must be independent of the person whose records are sampled.
How often should the rubric change?
Review quarterly, or sooner if qualification rates move sharply. Change one band at a time so you can see the effect.
