Course 14 · Lesson 5 of 13
The weekly dashboard
One page, prepared by John Cooper before the weekly review. He answers for each number being right, not good. Dom Watts has no weekly reporting duties: any product data report is a one-off build.
| Line | Shows | Source |
|---|---|---|
| Pipeline | Opportunities per stage, by motion and sector; win and no-decision rates (counts until 20 closed) | CRM |
| Source of each opportunity | Channel tag plus the buyer's "How did you hear about us?" | CRM |
| Qualified first conversations | Held this week, by sector, and how many ended with a dated next step | CRM |
| Slipped and stalled | Past next-step date; in one stage over 7 days (direct), 30 (considered), 45 (law firms) | CRM |
| Paid accounts and seats | By band, sector, motion; self-serve wins; band fill | Billing (when available) |
| Activation, habit, risk | 48-hour connection; 14-day activation; seats posting days 60 to 90; scheduler-only use; no posts in two weeks | Product analytics (when available); by hand until then |
| Cancellations and refund requests | This week, with reasons | Billing; support inbox |
| Design partner health | Weekly call held; success criteria on track | Product owner's notes |
| Beachhead review counter (D5) | Qualified recruitment conversations to date; review at about 20, or at public launch, whichever is first | CRM |
| Sales-hire trigger counter (D25) | Consecutive weeks where qualified conversations waited over two working days for a first call; John's open qualified opportunities. Trigger: three weeks, or more than 15 | CRM |
| Guardrails | Anything on the guardrail list, and the correction made | Call review; partner post sample |
Progress is saved in this browser only.