How do you track the decay rate of Marketing Qualified Leads by cohort week?
Start by fixing the workflow gap named in your question on your CRM on one pod or segment for two weeks. Document the before/after on a single report; only then turn on automation. Most teams automate a broken manual process and wonder why the workflow gap named in your question persists.
Context — tied to your question
You asked about the workflow gap named in your question on your CRM. Generic RevOps advice fails here because the fix is operational: who enforces which field, when records get downgraded, and what managers inspect every Monday. Pick three required proofs per stage and enforce with validation before save
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallKory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallWhat to do
- Name an owner for the workflow gap named in your question; publish a one-page definition of done tied to your CRM objects
- Baseline the pain: export 30 recent records where the workflow gap named in your question showed up in forecast or handoffs
- Configure Core object required fields, ownership, stage definitions, activity logging
- Pilot on one segment for 10 business days—no company-wide rollout
- Run manager inspection weekly using one saved report; downgrade or fix records that fail the definition
- Only after fill rate beats 80% on required fields, add automation (routing, alerts, or sync)
Your CRM configuration focus
- Objects to touch: Core object required fields, ownership, stage definitions, activity logging
- Enforcement: validation on save beats post-hoc cleanup for the workflow gap named in your question
- Inspection: one saved report filtered to pilot segment; same view every week
Metrics (pick one primary)
- Primary: Duplicate or routing error queue depth week over week
- Hygiene: % pilot records passing all required fields
- Failure signal: same exception recurring after two inspection cycles
What good looks like
- Managers can open one report and see which deals fail the workflow gap named in your question standards
- Reps know which fields block saves—no surprise at commit time
- Automation is off until manual discipline holds for two weeks
- Handoffs use the same field definitions across teams
Common mistakes
- Buying another point solution before your CRM rules exist
- Optional fields for the workflow gap named in your question—reps skip them under quarter pressure
- Company-wide rollout before the pilot segment proves fill rate
- Inspection meetings that read narratives instead of opening your CRM records
Manager inspection script (15 minutes)
Open the pilot saved report in your CRM. Sort by exception flag. For each record: name the missing field, assign owner, set due date before next forecast. No narrative readouts—only record fixes. Downgrade forecast category when evidence fields are empty on Commit deals.
Rollout phases
| Phase | Duration | Scope | Exit criteria |
|---|---|---|---|
| Baseline | Week 1 | Export 30 failure examples | Written definition of done for the workflow gap named in your question |
| Pilot | Weeks 2–3 | One segment | ≥80% required field fill rate |
| Expand | Week 4+ | Adjacent teams | Same inspection report, same fields |
| Automate | After expand | Workflows/routing | Automation off if fill rate drops 2 weeks straight |
Data & integration notes
Document which objects sync from warehouse or billing before enabling automation. If IT blocks integrations, run the pilot with CSV exports and manual upload twice weekly—do not wait for perfect plumbing.
RevOps without a big team
One owner can run this if they have write access to your CRM validation rules and a manager who enforces the inspection report. Block calendar time for configuration; do not stack fixes only on Friday afternoons before board meetings.
Enablement & documentation
Publish a one-page definition of done for the workflow gap named in your question inside your sales wiki. Link the your CRM report URL, required fields, and two annotated screenshots. New hires should pass a 10-minute quiz on which fields block saves before receiving live opportunities in the pilot segment.
Stakeholder alignment
| Stakeholder | What they need | Cadence |
|---|---|---|
| CRO / sales leader | Pilot metrics vs baseline | Weekly 15 min |
| Finance | Booking rules unchanged | Once at pilot start |
| IT / security | Field list + integration scope | Before automation |
| Reps | Office hours on new validations | Twice during pilot |
Discovery questions for your next inspection
Ask the pilot pod: Which deals failed the workflow gap named in your question rules two weeks in a row? Which field was empty on every loss? What would have blocked the save if validation were on? Capture answers in your CRM notes so the definition of done evolves with real failures—not generic enablement slides.
Post-pilot scale checklist
- Required fields copied to adjacent teams unchanged
- Same saved report URL pinned in the Monday leadership agenda
- Automation tickets list the field API names, not vendor feature names
- Success metric frozen for one quarter before changing again
Your CRM admin notes (copy/paste ready)
Create a validation rule or required-field set on the object where the workflow gap named in your question appears. Name the rule with the problem keyword so admins can find it later. Add a custom field Exception_Reason__c (or equivalent) for temporary waivers—managers must fill it or the record cannot reach Commit. Archive waivers monthly; patterns indicate bad rules, not bad reps.
When leadership pushes back
If executives want a faster rollout, show the pilot fill-rate chart and the forecast error before/after. Offer parallel rollout only after two clean inspection weeks. Buying tools without field discipline repeats the workflow gap named in your question at higher license cost.
Tie to forecasting
Map each required field to a forecast category rule: if economic buyer role is missing, the deal cannot sit in Best Case. Managers downgrade in the same meeting they inspect the workflow gap named in your question—do not allow verbal commits without your CRM evidence. Re-run the baseline export after 30 days to prove the fix held. Share results with finance and RevOps in the same slide.
<!--pillar-weave-->
Related on PULSE
- [How do you track the decay rate of Marketing Qualified Leads by cohort week?](/knowledge/q9764)
- [How does AI in the funnel change your definition of a qualified lead in 2027?](/knowledge/q16456)
- [How do you compensate SDRs in a 2027 model where AI books 80% of qualified meetings?](/knowledge/q16296)
- [What question reveals whether a salesperson has properly qualified a lead before entering the pipeline?](/knowledge/q14410)
- [What is Qualified (Piper the AI SDR) and why is it a hot RevOps tool for 2027?](/knowledge/q12144)
- [Should I pay SDRs on demos booked or only on demos held + qualified?](/knowledge/q08)
Common Pitfalls in MQL Decay Measurement
When tracking decay rates by cohort week, several measurement errors consistently distort the data. The most frequent mistake is using absolute lead count instead of percentage-based metrics. A cohort of 500 MQLs will naturally show more "decay" in raw numbers than a cohort of 50, even if the engagement patterns are identical. Always normalize by cohort size — report the percentage of leads that remain active or convert, not just the declining count.
Another trap is ignoring the lead source when grouping cohorts. MQLs from paid search often decay faster than those from referral programs or content downloads. If you mix sources within a weekly cohort, your decay curve reflects an average that may not apply to any specific channel. Segment cohorts by source or campaign type before calculating decay rates.
A third common error is setting the decay threshold too rigidly. Leads who go dark for 2 weeks but re-engage in week 4 are not "decayed" — they follow a different buying cycle. Use rolling windows (e.g., "no engagement for 4 consecutive weeks") rather than a single missing week to define decay. This prevents false positives that inflate your decay rate and lead to premature lead disqualification.
Practical Implementation Steps for Weekly Cohort Tracking
To set up decay tracking in your CRM or analytics tool, follow this sequence:
- Define your active lead criteria — specify what counts as "alive" (e.g., email open, form fill, demo request, or any sales activity). Document this threshold before collecting data.
- Create weekly cohort buckets — group MQLs by the week they first achieved MQL status. Use ISO week numbers (e.g., 2024-W14) for consistency across years.
- Track week-over-week activity — for each cohort, record the percentage of leads that met your active criteria in week 1, week 2, week 3, etc. A simple spreadsheet works for small volumes; use SQL or BI tools for larger datasets.
- Calculate the decay rate — for each subsequent week, divide the active count by the original cohort size. The decline from week 1 to week 2 is your initial decay. Continue until the cohort stabilizes (typically 8–12 weeks for B2B).
- Visualize as a survival curve — plot the percentage of active leads over time. A steep drop in weeks 1–3 suggests immediate disinterest; a gradual slope indicates longer consideration cycles.
Most CRMs lack native cohort decay reports, so you may need to build a custom dashboard in Looker, Tableau, or even Google Sheets using a pivot table with weeks as columns and cohort IDs as rows.
Interpreting Decay Patterns to Improve Lead Quality
The real value of decay tracking lies in what the patterns tell you about your marketing and sales processes:
- Rapid decay (50%+ drop in week 1–2) typically signals a mismatch between the offer that generated the MQL and the actual product. Review your lead magnets, content offers, or ad copy for overpromising.
- Slow decay over 6+ weeks often indicates high-intent leads who are researching but not yet ready to buy. These may need different nurturing content, not aggressive sales follow-up.
- Sudden spike in decay at week 4–5 frequently correlates with a specific sales action — perhaps a cold call or email sequence that pushes leads away. Audit your sales playbook timing.
- Inconsistent decay across cohorts suggests external factors like seasonality, market shifts, or campaign changes. Compare decay curves from Q1 vs. Q3 to identify patterns.
Use these insights to adjust your MQL definition itself. If 80% of leads decay within 2 weeks, your MQL criteria may be too loose. Tighten qualification requirements until your week-4 retention rate reaches at least 30–40% (varies by industry). The decay rate is not just a metric — it's a diagnostic tool for the health of your entire lead generation engine.
Sources
- HubSpot Blog — best practices for tracking MQL decay and cohort analysis in marketing.
- Google Analytics Help Center — documentation on cohort analysis and user engagement metrics.
- Marketo Product Documentation — guides on lead lifecycle stages and decay rate calculations.
- Harvard Business Review — research on customer lifecycle metrics and cohort-based performance tracking.
- Forrester Research — industry reports on lead scoring, MQL management, and cohort analysis methods.
- MarketingProfs — articles and frameworks for measuring lead decay and cohort retention over time.
FAQ
What exactly is a “cohort week” in MQL decay tracking? A cohort week groups all Marketing Qualified Leads that entered your funnel during the same seven-day period. You then measure how many of those leads remain active or convert each subsequent week, so you can see the natural drop-off pattern.
How do I calculate the decay rate for a specific cohort? For each cohort week, divide the number of MQLs still engaged (e.g., opened an email, visited a page) in week 2, 3, or 4 by the original cohort size. The percentage decline from week to week is your decay rate—most B2B cohorts lose 30–60% of engagement by week 4.
What’s a reasonable decay rate range for B2B MQLs? A healthy decay rate typically falls between 20–50% per week, depending on your industry and lead quality. Rates above 60% weekly often indicate poor targeting or a broken follow-up process that needs fixing before scaling.
How do I set up the tracking in my CRM without custom tools? Use a simple report that filters MQLs by created date (your cohort week) and then checks activity or stage changes in subsequent weeks. Most CRMs let you create a weekly cohort table with counts per week—no coding required, just a few date-based filters.
What’s the biggest mistake teams make when tracking decay? They automate the tracking before fixing the underlying workflow gap—like a slow lead assignment or weak nurture sequence. Always run a manual two-week test on one segment, document before/after numbers, then turn on automation.
How often should I review cohort decay data? Review it at least monthly to spot trends early. If you see a sudden spike in decay (e.g., from 30% to 60% weekly), investigate immediately—it often signals a process change or market shift that needs a fast response.
Bottom line
Fix the workflow gap named in your question on your CRM with owner + enforced fields + weekly inspection. Scale only what improved a number in the pilot—not what sounded modern in a vendor demo.