The five metrics to measure (practical, platform‑neutral)
- Lead acceptance rate — Why it matters: shows whether sales are willing to take automated handoffs or the automation is just creating noise.
- How to calculate: accepted leads (sales marks as "accepted"/lifecycle = SQL or sets owner) ÷ leads handed over in the same period. Use a 7‑day window.
- Thresholds/red flags: small teams: target ≥60% within 48 hours; red flag <40% or median time-to-acceptance >48 hours.
- Quick instrument: HubSpot/Salesforce/Marketo: report on lifecycle or status changes with timestamps; Sheets: export handed leads and acceptance timestamp columns and compute percent.
- Fixes: tighten scoring or form fields, add a short pre-handoff validation step, introduce a manual handshake (task assigned) before full automation.
- First contact SLA compliance — Why it matters: a fast human touch turns leads into conversations; automation should speed, not delay, contact.
- How to calculate: leads accepted that have a first outbound activity (call/email/task logged) within X hours ÷ accepted leads (use 24h SLA).
- Thresholds/red flags: aim ≥80% within 24 hours; red flag <60%.
- Quick instrument: HubSpot/Salesforce activities report or a simple sheet comparing accepted timestamp to first activity timestamp.
- Fixes: auto-create tasks on handoff, add reminder alerts, reassign stale leads to a rota owner.
- Lead→Opportunity conversion within window — Why it matters: measures whether handed leads are genuinely sales‑ready, not just processed.
- How to calculate: opportunities created and associated to handed leads within 14 days ÷ total handed leads.
- Thresholds/red flags: realistic small‑team benchmark 10–20%; red flag <5%.
- Quick instrument: HubSpot/ Salesforce: association reports (lead→deal/opportunity); Sheets: join exported lead IDs with opportunity exports.
- Fixes: review qualification criteria, improve qualification questions, run a short coaching session with sales.
- Rejection/exception reason rate — Why it matters: if sales reject leads often, automation is sending the wrong signals.
- How to calculate: rejected leads with a reason selected ÷ leads handed. Track reasons (poor fit, duplicate, wrong contact).
- Thresholds/red flags: aim <20% rejected with actionable reasons; red flag >30%.
- Quick instrument: require a picklist rejection reason in HubSpot/Salesforce/Marketo; in Sheets add a mandatory column for reason and tally values.
- Fixes: add gating checks (mandatory fields, source filters), fix form/source mapping, or add an exception route rather than immediate rejection.
- Handoff data error rate (duplicates & manual fixes) — Why it matters: data fixes waste time and break SLAs; automation should reduce rework.
- How to calculate: number of handed leads that required a manual merge/edit or had a recorded data-fix event ÷ handed leads.
- Thresholds/red flags: target <5% for small teams; red flag >10%.
- Quick instrument: track merge/modify events (HubSpot has merge logs; Salesforce has audit fields) or add a "handoff exception" checkbox for reps; use Sheets to count flagged rows.
- Fixes: add pre-automation dedupe and normalisation, enforce required fields, or run a brief daily de-duplication routine.
Set these up in a day and check quality quickly
Pick one metric as your primary test and build the simplest report: a CRM saved report or a two‑sheet join (handed leads + activity/opportunity exports). Use 14 days of data to smooth noise.
Sampling tip — 20‑record quality check: export 20 consecutive handoffs (most recent). For each record check: correct owner assigned, acceptance time recorded, first contact logged, rejection reason (if any) and whether a manual data fix occurred. Note pass/fail and common root causes. This takes 20–40 minutes and tells you if the numbers reflect reality.
Decide keep/fix/retire quickly: keep if primary metric meets threshold for 2 consecutive weeks; fix if within ~10% of threshold or common, fixable data causes appear in your sample; retire if metric is far below threshold and fixes would require major rework or policy change.
Ownership, cadence and low‑tech fallbacks for small teams
Owner and cadence: assign one person (marketing ops, sales ops or a named rep) as metric owner. Cadence: weekly quick checks for SLA and acceptance rate; monthly review for conversion and rejection reasons. Keep a one‑line runbook next to the report describing actions for red flags (reassign, pause automation, open ticket).
Low‑tech fallback plan (no engineer): use a shared Google Sheet as the handoff queue — columns for handed timestamp, owner, acceptance timestamp, first contact timestamp, rejection reason and exception flag. Use simple filters and a pinned Slack message to signal unaccepted leads older than 48 hours. This is a proven, low‑cost stopgap for Fareham and Hampshire teams while you stabilise automations.
If you want help getting the reports, lists and a one‑page runbook set up for HubSpot, Salesforce, Marketo or Pardot, see our crm-marketing-data-optimisation-fareham.html page — or ask Optira for a short, practical engagement to get you running.