The lead-status field is the single most-touched field in most CRMs and the single most degraded. Reps stop updating it, status values proliferate, transitions blur. Strkr's approach is a 7-status reference model with transition rules, automation, and clean-up patterns that keep the data trustworthy.
Lead status breaks in predictable ways. The first 6 months after a CRM goes live the status values look clean. By month 18 the status list has 23 values ("Attempted - LVM - 3", "Working - Scheduled Follow-up - Interested"), reps have given up on updating it, and nobody can run reliable reporting. The pain points below are the failure modes that produce this outcome.
The initial 5 to 7 status values grow to 20 to 40 within 18 months as reps and managers add granular variants ("Working - LVM 1", "Working - LVM 2", "Working - Email Sent Awaiting Reply"). Reporting breaks because every status has a tiny sample size. The intended workflow gets lost in the noise.
The pipeline shape (which status flows to which) was clear at design time. 2 years later nobody remembers. Reps move leads from "New" to "Qualified" skipping "Working" because the workflow was never enforced. Reporting on time-in-stage becomes meaningless because leads skip stages.
Reps leave leads in intermediate statuses long after the actual engagement stopped. "Working" accumulates thousands of leads that have gone silent. The queue is clogged with cold leads and the hot leads get lost. No automated cleanup means the status data decays silently.
The lead-status pipeline is useful for enforcing SLAs (new lead responded to within 1 business hour, qualified lead disposition set within 3 business days). Most CRMs do not surface SLA compliance so the data goes nowhere. Teams miss the one metric that most tightly correlates with pipeline conversion.
The pipeline funnel reports (how many leads at each stage, conversion rate stage-to-stage, average time in stage) are only as reliable as the status discipline. When status proliferates and reps skip stages the funnel reports show noise. Teams stop trusting the data and the function loses credibility.
In most CRMs the status field is a label the rep updates. It does not drive automation (route the lead when it hits a status, create tasks on transitions, alert the manager on SLA miss). The missing automation means the status field has to earn its keep purely as a reporting artifact, which does not justify the overhead of keeping it accurate.
The 7-status model below is the standard reference pipeline for most B2B sales motions. Each status has a clear definition, a clear transition rule, and a clear exit condition. Teams that stay close to this model keep the data clean over long horizons.
A fresh lead that has entered the system (form fill, enrichment, import, chat conversion) and has not received a rep touch yet. SLA: first touch within 1 business hour for hot leads, 1 business day for standard. Exit: moves to "Working" on first rep touch. Enters from marketing automation, chat, enrichment, or manual add.
A lead the rep has touched and is actively engaging through a cadence. The lead is in a defined sequence with upcoming scheduled touches. Exit: moves to "Qualified" (positive disposition), "Nurture" (not now, revisit later), or "Disqualified" (not a fit). SLA: cadence completion within 10 business days.
A lead the rep has qualified as fitting the ICP with current buying intent. Discovery call booked or completed. The lead is ready for conversion to an opportunity. Exit: converted to opportunity (becomes a deal), or moves back to "Nurture" if timing not right. SLA: conversion to opportunity within 5 business days of qualification.
A lead with fit but no current intent (budget cycle wrong, project not approved, incumbent contract not expired). Lead stays warm through marketing nurture until a trigger event (budget cycle, incumbent renewal) brings them back. Exit: back to "Working" on trigger event, or moves to "Dormant" after 12 months with no engagement.
A lead that is not a fit (wrong ICP, out of territory, individual not a buyer). Rep documents the reason (one of 6 to 8 disqualification reasons). Exit: terminal status, lead stays disqualified unless manually reopened. Reporting tracks disqualification reasons for marketing-source attribution.
A lead that was in "Nurture" for 12+ months with no engagement. Auto-transitioned by Strkr based on last-touch date and engagement score. Exit: back to "Working" on specific reactivation triggers (form fill, high-intent page visit, intent-data spike). Dormant leads stay queryable for cold-reopen campaigns.
A lead that converted to an opportunity. The lead record stays for attribution but the active workflow moves to the deal record. Exit: terminal status. The lead's source attribution flows to the deal for marketing-source reporting. Reopening is rare; typically a new lead is created rather than reopening a converted lead.
The transitions below define how leads move between statuses. The rules are enforced by Strkr's workflow engine with validation, automation, and alerts. Reps cannot skip stages and the data stays trustworthy.
Any logged activity (call, email sent through Strkr, meeting booked, LinkedIn task completed) moves the lead from "New" to "Working" automatically. The transition is logged with timestamp and rep attribution. The first-touch latency metric starts here.
Rep manually marks the lead as qualified after a positive discovery call. Required fields (ICP fit confirmed, pain validated, authority confirmed, budget range, timeline) enforced via validation. Transition cannot complete without the required disposition data. The qualified lead becomes available for opportunity conversion.
Rep marks the lead as not currently buying but a fit for future. Required fields: nurture reason (budget, timing, incumbent, project status), expected re-engagement date. The lead enters marketing nurture automatically. A task is created for the expected re-engagement date to prompt rep follow-up.
Rep selects from a controlled list of disqualification reasons (wrong ICP, individual not a buyer, out of territory, duplicate, bad data, competitor incumbent long-term). The controlled list drives marketing-source reporting. Free-text reasons are not allowed; the controlled list prevents proliferation.
Rep creates an opportunity from the qualified lead. The conversion is a one-click action that copies lead context to the deal, creates the deal record, and transitions the lead to "Converted". The deal takes over as the active record; the lead stays for attribution.
Triggers that automatically move Nurture leads back to Working: form fill, high-intent page visit (pricing, security, implementation), intent-data spike, email high-engagement pattern. Rep can also manually move a Nurture lead back to Working on account activity (new champion identified, incumbent contract expiring).
Automatic transition after 12 months in Nurture with no email engagement, no page visits, no rep touches. The transition cleans up stale Nurture leads so the active list stays meaningful. Dormant leads stay queryable but drop out of marketing automation and rep queues.
Disqualifying a lead is a one-way action from Strkr's default workflow. Reopening a disqualified lead requires manager approval and documents the reason. The prevention of silent reopening keeps the disqualification data trustworthy.
The SLAs below define the response times reps commit to at each stage. Strkr tracks compliance automatically and surfaces alerts on breach. The SLAs are the primary accountability layer on top of the status pipeline.
The strongest known conversion lever in B2B sales. Published lead-response-time research (InsideSales, Harvard Business Review, Chili Piper) shows a 5-minute response outperforms a 5-hour response by 10 to 100x on connect rate. Strkr enforces the SLA with real-time alerts and dashboard visibility.
Leads in Working status complete the assigned cadence or get a disposition within 10 business days. The SLA prevents leads from aging indefinitely in Working. Breach triggers an alert to the rep manager with the lead and the days-in-stage count.
Once a lead is qualified it should convert to an opportunity within 5 business days. The SLA ensures qualified leads do not stall in a qualifying limbo. Breach triggers a manager alert and surfaces the lead on the stale-qualified queue.
When a Nurture lead gets a trigger event (form fill, high-intent visit) the lead moves back to Working automatically and the rep is notified. SLA: rep touch within 2 business days of the trigger. The window is tight because trigger events have decay; a response 2 weeks later is often too late.
Manager reviews 10 percent of disqualifications weekly to validate the reason and look for patterns (over-disqualification by rep, specific sources producing bad leads). The review is a 15-minute weekly cadence and catches both rep behavior and marketing-source issues.
The SLA dashboard shows breach percentage by rep (identifying reps who need coaching), by segment (identifying segments where SLA is unrealistic), and by lead source (identifying sources producing leads that cannot be worked within SLA). The dashboard drives the weekly rep 1-on-1 agenda.
The comparison is against the default lead-status setup in HubSpot, Salesforce, or Pipedrive. The transition rules and SLA enforcement are the structural difference.
| Feature | Strkr | Default HubSpot or Salesforce |
|---|---|---|
| Reference pipeline | 7-status standard model | Teams build from scratch |
| Transition rules | Enforced with required fields | Not enforced by default |
| Status proliferation prevention | Admin-only status list | Any user can add |
| SLA tracking | Native per-stage SLA engine | Requires custom workflow build |
| Auto-dormant transitions | Default 12-month auto-rule | Manual or absent |
| Disqualification reasons | Controlled list, mandatory | Free text common |
| Nurture re-engagement triggers | Form, visit, intent, engagement | Form-only typical |
| Status change audit | Full change log per lead | Partial, varies by tool |
| Manager review workflow | 10 percent disqualification sample | Not standard |
| Stale-queue cleanup | Automatic with alerts | Manual, often skipped |
The playbooks below are real lead-status designs on Strkr customers in 2026. Each solved a pipeline-data problem.
A B2B SaaS at $70M ARR had 31 lead statuses by month 24 of their Salesforce deployment. Reporting had become unreliable. The team migrated to Strkr and collapsed to the 7-status reference model with transition rules and controlled disqualification reasons. Within 6 months pipeline reporting accuracy (reconciled against deal source) lifted from 68 to 94 percent. Marketing-source attribution became usable again.
An enterprise B2B team had a 1-hour SLA on hot leads but no tracking or enforcement. Breach rates were around 55 percent. After implementing Strkr's SLA dashboard with real-time alerts and manager visibility, breach rates fell to 15 percent in 60 days. Hot-lead conversion to opportunity lifted from 22 to 31 percent, roughly a 40 percent lift.
A mid-market SaaS had 11,000 leads in Nurture status, most of them inactive for 2+ years. The team turned on Strkr's auto-dormant rule (12-month no-engagement). Within one week, 7,200 leads transitioned to Dormant. The active Nurture list dropped to 3,800 and marketing automation engagement rates on the cleaner list lifted 180 percent (fewer unsubscribes, higher opens, more trigger events).
An agency team using Strkr noticed one specific lead source accounted for 42 percent of "Not a fit" disqualifications across all reps. Investigation showed the source's lead-gen criteria had drifted; the vendor had been serving the agency unfit leads for 3 months unnoticed. The controlled disqualification list and the per-source reporting surfaced the pattern. The agency cut the source and saved an estimated $120K in annual lead-vendor spend.
A B2B marketplace company configured Strkr's nurture-trigger rules to detect form fills, high-intent page visits, and intent-data spikes on Nurture leads. In the first 90 days, 420 Nurture leads re-engaged via triggers. 68 converted to opportunities and 12 closed to $410K in revived ARR within 6 months. The team now treats the nurture-trigger surface as a primary pipeline source.
Start a 14-day trial with the 7-status reference pipeline, transition rules, controlled disqualification reasons, SLA tracking, auto-dormant transitions, and the manager review dashboard.
Teams that keep their existing status list typically do so because changing it feels disruptive. In practice the existing list is usually degraded (proliferated, inconsistent, non-enforced) and keeping it preserves the degradation. The migration to a reference pipeline (7 clean statuses with transition rules) takes 2 to 4 weeks and typically produces 20 to 40 percent lift in reporting accuracy and 15 to 25 percent lift in rep productivity within the first quarter. The disruption cost is bounded; the ongoing cost of a bad pipeline compounds year after year.
The 7-status reference model fits roughly 80 percent of B2B sales motions. Some teams extend to 8 or 9 for specific needs (adding a "Discovery Scheduled" sub-status, a "Trial" status for PLG motions, a "Partner Referral" source status). Teams that stay at 7 to 10 statuses tend to have accurate data over long horizons; teams that grow past 15 statuses almost always have data-quality issues. The number of statuses is less important than the discipline of transition rules and controlled vocabulary.
The published research (InsideSales, Harvard Business Review, Chili Piper) is unambiguous: faster is better up to the limit of your rep capacity. A 5-minute response outperforms 5-hour response by 10 to 100x on connect rate; a 1-hour response outperforms 24-hour by 2 to 5x. The right SLA for your team is the fastest you can hit reliably across hot leads: typically 5 to 60 minutes for hot leads during business hours and 1 to 24 hours for standard leads. Strkr's round-robin and workload-balancing routing can hit tight SLAs even on small teams.
Disqualified is intended as a terminal status for leads that are not a fit (wrong ICP, individual not a buyer, duplicate, bad data). For leads that are a fit but not currently buying, use Nurture instead. The distinction matters because Nurture leads stay in marketing automation and get re-engagement triggers; Disqualified leads do not. If a Disqualified lead later becomes a fit (reorg, new role, new company), create a fresh lead rather than reopening the disqualified one. The practice keeps the attribution model clean.
That is specifically what the Working status is for. A lead where the rep has made contact but has not yet made a disposition call (not yet confirmed fit, not yet confirmed intent) stays in Working. The SLA ensures the lead does not stay in Working indefinitely: cadence completion or disposition within 10 business days. The structure forces the rep to make a call (Qualified, Nurture, or Disqualified) rather than letting leads age in a soft "working on it" state.
Yes, and the migration is a core Strkr onboarding workflow. The migration maps your existing statuses to the 7-status reference pipeline using an AI-assisted mapping tool. The tool reviews each of your statuses, suggests the closest reference match, and flags ambiguous cases for human review. Historical lead data preserves the original status in a legacy field for reporting continuity. The migration typically takes 2 to 4 weeks for a mid-size CRM with 100,000+ leads.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
