Quick answer
A good SLA meeting is not a campaign update. It is a decision meeting where marketing and sales inspect funnel health, lifecycle-stage evidence, handoff quality, and the specific records or cohorts that need action.
Recommended cadence
- Weekly 30 to 45 minutes: active funnel management, handoffs, routing exceptions, unworked SQLs, stale MQLs, and immediate fixes.
- Monthly 60 minutes: trend analysis, threshold changes, attribution, campaign quality, and definition adjustments.
- Quarterly reset: lifecycle definitions, MQL/SQL criteria, routing rules, targets, and CRM architecture changes.
Weekly SLA meeting agenda
| Time | Topic | Goal |
|---|
| 0 to 5 min | Scorecard check | Revenue pacing, MQL volume, SQL volume, response-time compliance. |
| 5 to 15 min | Lifecycle-stage health | Review supported, stale, unsupported, and contradictory stage labels. |
| 15 to 25 min | Handoff quality | Inspect MQL to SQL conversion, rejected leads, recycled leads, and routing failures. |
| 25 to 35 min | Velocity and pipeline | Review time in stage, stalled records, pipeline created, and opportunity movement. |
| 35 to 42 min | Voice of sales | Discuss strong-fit and weak-fit examples, objections, missing proof, and lead-quality feedback. |
| 42 to 45 min | Decisions | Assign owner, deadline, and success metric for each action. |
Metrics to review
| Metric | Why it matters |
|---|
| MQL quality | Shows whether marketing is sending useful demand or just volume. |
| MQL to SQL conversion | Measures handoff quality and definition fit. |
| SQL to Opportunity conversion | Shows whether sales acceptance turns into real pipeline. |
| Time in stage | Finds stagnation before it pollutes reporting. |
| Speed to lead | Shows whether high-intent records are worked quickly enough. |
| Unsupported MQLs / SQLs | Shows records whose lifecycle label lacks credible evidence. |
| Contradictory Opportunities / Customers | Shows records where stage and deal evidence disagree. |
| Source quality by channel | Shows which campaigns create SQLs and customers, not only form fills. |
Common SLA meeting mistakes
- Reporting MQL volume without quality.
- Letting marketing and sales use separate dashboards or filters.
- Using MQL as the only success measure when the business is account-led.
- Reviewing trends without inspecting real examples.
- Leaving the meeting without owners and deadlines.
- Changing lifecycle definitions without checking how existing records will be affected.
Decision log template
| Issue | Decision | Owner | Success metric |
|---|
| 214 MQLs have no recent engagement. | Create review cohort and inspect source pattern. | RevOps | Review list completed by Friday. |
| Score-only MQLs convert poorly. | Split MQL definition by trigger type. | Marketing Ops | MQL to SQL reviewed next month. |
| SQLs older than 90 days remain open. | Add stale SQL review process. | Sales Ops | Stale SQL count reduced by 50%. |
Before your next SLA meeting, run a FunnelLedger scan. Bring evidence-backed cohorts into the meeting instead of debating lifecycle stages from memory.
Buy report →