| Stage | This Mo. | Prior Mo. |
|---|---|---|
| Pending Qualification | — | — |
| CPP Verified — Pending Prov. | — | — |
| Provisioned — Onboarding Active | — | — |
| Portal Active — Awaiting Key | — | — |
| On Hold / Pending CPP | — | — |
| Metric | This Month |
|---|---|
| Emails Sent (all waves) | — |
| Responses Received | — |
| MSP Form Submissions | — |
| Opportunities Created | — |
| Dealers Provisioned | — |
The template is the preparation. The monthly meeting is the opportunity. Here's how to get both right.
Block 30 minutes on the first business day of each month. Pull all six pulse metrics from Salesforce. Fill the pipeline stage table using the MSP Pipeline by Stage report. Update the activation funnel from the all-time Opportunities report. Fill the platform split from the Active Orgs dashboard. Then write the three narrative boxes and the strategic signal. The data collection takes 15 minutes. The writing takes 15 minutes. The document should never take more than 30 minutes to complete.
The discipline of doing this every single month — regardless of whether the numbers are strong or disappointing — is what builds the track record that earns a raise. Consistency is more impressive than a single good month.
The prior month column is the most important addition over a weekly update. Month-over-month movement tells a story that a single snapshot cannot. Three dealers moving from "Provisioned" to "Portal Active" in one month is a trend. Seeing it alongside last month's numbers makes the momentum visible without you having to explain it.
Every narrative box should open with a number. Not a feeling, not a qualitative observation — a number. Numbers command attention before context does. They also force precision, which prevents the vague language that makes updates forgettable.
Most people hide this number. Don't. Owning the "provisioned but never activated" metric proactively — and showing that it's decreasing over time — demonstrates that you're managing the whole lifecycle, not just celebrating provisioning completions. A Senior Director who sees this number going down month over month knows you're solving the right problem.
The four priority slots are not a task list — they are commitments. Each should be specific enough that your Senior Director could check on it next month and know immediately whether it was completed. Vague priorities are unmeasurable and unmemorable.
This is where you demonstrate that you are not just managing a process — you are interpreting it. What does this month's data mean about where things are heading? What are you seeing before leadership needs to ask? This is the field that separates a status reporter from a strategic contributor.
Send the brief 24 hours in advance. Never walk into the meeting and present the document cold. Your Senior Director should have read it before you sit down. The meeting is for discussion, not data delivery. If they've read it, you start at a much higher level of conversation.
Open with the strategic signal, not the metrics. The metrics are in the document they've already read. Open with the interpretation: "The big thing I want to flag this month is…" and go from there. This signals immediately that you're operating at a strategic level.
End with next month's priorities. The last thing you say should be your four commitments for next month. Say them out loud. That creates a specific, named accountability that both parties carry into the next meeting — and the next meeting starts with your director asking about progress on things they remember you committed to.