Scope: what this audit covers and what it does not
The question this audit answers is whether the leads marketing produces reach the right person quickly, get worked or nurtured, and come back as outcomes the business can count, and where the process leaks most. It covers everything between an enquiry and a won or lost deal: stage definitions, form, call and chat capture, the sync between the marketing platform and the CRM, routing and response, scoring, nurture and sales alerts, the agreement between sales and marketing, and the outcomes sent back to reporting and ad platforms. It suits a business that sells to companies and one whose consumers enquire, ask for a quote or book a visit before they buy.
The pages that capture leads are scored by the landing page audit, the analytics set-up by the analytics implementation audit and the email content of nurture by the email programme audit. A LinkedIn account that feeds the pipeline is scored on the same scale by the LinkedIn Ads account audit; this scorecard picks up its leads once they arrive.
It does not re-teach the work or repeat how it is run. The inbound lead handling playbook runs capture, routing, response, nurture and closed-loop reporting week to week, the lead routing QA checklist tests routing after a change, and the lead scoring model template writes a scoring model. The guide to MQL, SQL and lead stages owns stage design. Every scorecard sits in the audit library.
Before you score: access and evidence
Ask for read access to the CRM, the marketing platform, the call and chat tools and the reports both teams use. Without access to the CRM's timestamps you cannot see how long leads wait, so the routing and response rows stay provisional until you have it. Fix an evidence window long enough for recent leads to have reached a sales outcome, which for a long sales cycle means looking at older cohorts as well as new ones, and keep the same window for every rescore.
Collect:
- the written stage definitions, if any, and the CRM's lifecycle and pipeline fields;
- a sample of recent leads traced from form, call or chat to their current stage, with timestamps;
- the routing rules and the record of who received each lead and when they first responded;
- the scoring model, nurture workflows and sales alert rules as configured;
- the agreement between sales and marketing and the notes of recent pipeline reviewsA short regular meeting where sales and marketing read the same opportunities from the same data and agree an owned action for each stuck deal.;
- pipeline and revenue reports by source, and any outcomes uploaded to ad platforms.
Trace the sample yourself rather than reading a dashboard: a lead that never reached the CRM does not appear in any report. Where channels are judged on cost per qualified lead or per won deal, the CPA calculator helps check that the target is consistent with what a deal is worth to the business.
Criteria and scoring
Rate each row missing (absent or broken), partial (present but incomplete, inconsistent or out of date) or solid (matches the "what good looks like" column). The scale is your judgement against that column, not a number. Rows marked gate decide the band on their own when they score missing. A row that does not apply, such as call capture for a business that takes no calls, is marked not applicable rather than missing.
Definitions
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Stage definitions (gate) | Each stage from enquiry to won has a written definition that marketing and sales both use, with a sales-accepted step | Missing: no written definitions, or each team uses its own / Partial: written but not agreed, or no sales-accepted step / Solid: written, agreed and used by both teams |
| Stages enforced in the CRM | Lifecycle and pipeline stages are CRM fields with rules for moving between them, not labels in a slide | Missing: stages exist only in a presentation / Partial: fields exist, moved by hand without rules / Solid: fields with exit criteria, owners and recycling rules |
The guide to MQL, SQL and lead stages explains what each stage means, from the MQLA lead that marketing judges ready for sales follow-up against agreed criteria. to the Sales-Qualified LeadA lead that sales has reviewed and accepted as a genuine opportunity to pursue., and the lead stages and pipeline guide shows how definitions, exit criteria and recycling rules become CRM fields.
Capture
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Form design | Forms ask only what qualification needs and carry consent wording that matches how the lead will be contacted | Missing: long forms, consent bundled into the submission / Partial: fields trimmed, consent wording vague / Solid: qualification fields only, consent separate and matching the follow-up |
| Form submissions tracked | Every form submission is tracked with its source and campaign | Missing: button clicks counted as leads / Partial: successes tracked, source lost on some forms / Solid: every form, success-based, with source and campaign |
| Calls and chats counted | Phone calls and chat enquiries that start a lead are counted and attributed alongside forms | Missing: forms are the only leads anyone counts / Partial: calls counted, source unknown or outcome not recorded / Solid: counted, attributed and recorded with outcomes |
Forms are scored against the forms guide, which keeps marketing consent separate from the main action as the applicable rules require; this scorecard rates the habit and is not legal advice. Tracking is scored against the form tracking tutorial and calls and chats against the guide to measuring calls and chats.
CRM, routing and response
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Platform and CRM sync (gate) | Leads, consent and stage changes move between the marketing platform and the CRM without loss or duplicates | Missing: leads lost or duplicated, consent not synced / Partial: leads sync, consent or stage changes travel one way only / Solid: field ownership written, consent travels both ways, errors watched |
| Routing and assignment | Each lead is assigned an owner by an agreed rule, with a task and a notification, and nothing waits for a meeting | Missing: leads collected in a shared inbox or a weekly meeting / Partial: rules exist, some leads fall to nobody / Solid: every lead owned, tasked and notified |
| Follow-up seen | First responses are timed and slow or missing follow-up is visible to both teams | Missing: nobody knows when leads were first contacted / Partial: timed, but only sales sees it / Solid: timed, visible to both teams and reviewed |
Score the sync against the guide to syncing the CRM and the marketing platform, which explains, as general practice and from the ICO's direct marketing guidance and the GDPR as it states them, why consent and objections must travel in every direction and the most restrictive value wins. Routing is scored against the lead stages and pipeline guide, and Lead RoutingRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source. after a change is tested with the routing checklist above. The diagnosis of sales not following up leads sets out why Lead Response TimeAverage time between a new lead arriving and the first contact from sales. needs a target someone measures and how untouched leads are found.
Scoring and nurture
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Scoring model | Scores combine fit and behaviour, are checked against won and lost deals and are reviewed | Missing: no scoring, or points nobody can explain / Partial: fit and behaviour mixed, never calibrated / Solid: separate fit and intent, calibrated against outcomes, reviewed |
| Nurture for the not-ready | Leads not ready for sales enter nurture with written entry, exit and re-entry rules | Missing: not-ready leads dropped or sent the newsletter / Partial: sequences without exit or re-entry rules / Solid: stage-based sequences with written rules |
| Sales alerts | Sales is alerted to activity that signals readiness, without alerts so frequent they are ignored | Missing: no alerts, or an alert for every click / Partial: alerts on sensible events, routed to the wrong people / Solid: few, meaningful, routed to the owner and checked for follow-through |
The lead scoring guide covers fit and intent, decay and calibration against what closed, the nurture sequences guide sets out Lead NurturingKeeping in useful contact with leads who are not yet ready to buy until they are. with entry, exit and re-entry rules, and the guide to sales alerts from marketing activity explains which events justify an interruption and how alert fatigue builds.
Sales agreement
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Service-level agreement | A written agreement sets what marketing delivers and how sales follows up, and both teams review it | Missing: no agreement / Partial: agreed once, never reviewed or reported on / Solid: written, reported on and reviewed by both teams |
| Rejection reasons fed back | Rejected leads come back with a reason, and reasons are read in a regular pipeline review | Missing: leads rejected silently / Partial: reasons recorded, never read / Solid: a reason on every rejection, read in the review and acted on |
The agreement is scored against the sales and marketing alignment guide and feedback against the weekly pipeline review tutorial.
Closed loop
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Outcomes sent back | Qualified and won outcomes reach analytics and ad platforms so bidding and reporting learn from them | Missing: platforms optimise towards form fills / Partial: won deals uploaded occasionally, consent unchecked / Solid: qualified and won outcomes sent on a rhythm, consent checked |
| Pipeline by source | Reporting shows pipeline and revenue by source, not lead counts alone | Missing: lead volume by channel only / Partial: pipeline by source, revenue not joined / Solid: pipeline and revenue by source, read by cohort |
| Lead value by stage | Each stage carries a value the business agrees, so channels can be compared before deals close | Missing: every lead treated alike / Partial: values guessed, never refreshed / Solid: values agreed with finance from deal margin and refreshed |
Score outcomes against the guide to connecting the CRM to ads and analytics, which covers Offline Conversion ImportUploading outcomes recorded outside the website, such as closed deals, to an ad platform. and the consent checks before anything leaves for an ad platform, reporting against the business-to-business measurement guide and values against the guide to valuing a lead by pipeline stage.
How to score and prioritise
Score the gates first. Without shared stage definitions and a working sync, leads cannot be counted, routed or reported, and every other score is guesswork. If definitions score missing, the argument about lead quality has no answer, so mark the agreement, scoring and closed-loop rows provisional. If the sync scores missing, the sample you traced is the only reliable evidence, and any report built on the CRM is incomplete.
Then rank the remaining weaknesses in this order:
- The leaks closest to revenue: unassigned leads, slow follow-up and rejections with no reason. Each one loses enquiries the business has already paid for.
- The closed loop, because channels and ad platforms keep optimising towards form fills until outcomes come back.
- Scoring and nurture refinements next.
- Form copy and alert tuning last, unless a test shows they cost leads.
Within each group, rank by the volume of leads the weakness touches. A routing gap on the source that brings most enquiries outranks the same gap on an occasional event list.
Reading the result: what to do with each band
Red means a gate scored missing. Hold changes to campaigns and budgets, write and agree the stage definitions, repair the sync so leads, consent and stages travel without loss, and retrace a fresh sample before trusting any report. Rescore once leads captured after the repair have had time to reach a sales outcome.
Amber means the gates hold at least partially but several other rows are partial or missing. This is the usual outcome. Work a short ordered list, starting with routing and follow-up, and bring each fix to the pipeline review so both teams see its effect.
Green means the gates are solid and most rows are too. Move effort into calibrating scores and lead valuesWhat a lead is worth at a pipeline stage: what a closed deal contributes times the share of leads there that close; a planning figure, never revenue. against closed cohorts and into sending richer outcomes to ad platforms, and rescore each year or after a change of CRM, sales team or main channel.
From findings to a prioritised fix list
Write each partial or missing row as a finding in plain words: what you saw, the evidence and why it matters. A traced lead is the most persuasive evidence, so record its source, the time it arrived, who received it and what happened next. Then turn the findings into one fix list with a line per fix: the finding, the fix, the owner, the guide that explains it and the rescore date. Order the list by the priorities above, not by how easy each fix is.
Group the lines by who does the work, because definitions and the agreement sit with the heads of sales and marketing together, the sync, routing and outcome uploads with whoever administers the CRM and the marketing platform, capture with the web and analytics owners, and scoring and nurture with marketing operations. Present the band, the gate findings and the first few fixes to both teams at once, so the result settles the lead quality argument rather than restarting it, and keep the full scorecard as the working copy for the rescore.
Illustrative example
A commercial cleaning contractor traces its enquiries
Huzzaret Cleaning, an invented commercial cleaning contractor, runs the audit after sales said marketing's leads were poor. Over the last 13 weeks the website produced 180 quote requests and the office logged roughly 120 phone enquiries. Stage definitions score missing: nobody has written what a qualified enquiry is, so sales judges each one by feel. The sync scores partial and calls and chats score missing, because phone enquiries are written in a notebook and never reach the CRM, so the 120 calls appear in no report. Routing scores missing: quote requests wait in a shared inbox for the Monday meeting, and a traced sample of 20 shows a median wait of 4 days before first contact. Rejection reasons score missing and outcomes sent back score missing, because the ad platforms still optimise towards form fills. The band is red. The fix list puts a written definition of a qualified enquiry agreed by both teams first, logging calls into the CRM with their source second, assigning every quote request to an owner on arrival third and recording a reason on every rejection fourth, and holds any change to campaigns. After 13 more weeks, both gates score solid, routing scores partial and the band moves to amber.
Common mistakes
- Arguing about lead quality before definitions exist. Without a written definition both teams use, neither side can be right. Score the gate first.
- Reading the dashboard instead of tracing leads. A lead that never reached the CRM is invisible in every report. Trace a sample by hand.
- Counting forms only. The calls and chats guide notes that for many service businesses the phone and the chat window carry more enquiries than the form. Score them alongside forms.
- Blaming sales for slow follow-up. Leads routed to nobody, or to someone who has left, look the same as leads ignored. Check the routing record before scoring the response row.
- Sending form fills to ad platforms as success. Bidding then finds more people who fill in forms, not more customers. Score the closed loop on qualified and won outcomes.
- Rescoring too soon. Leads need time to reach an outcome. Rescore on the same evidence window once the repaired process has had that time.
