Week ending Friday · illustrative
This week, in one page.
The page leads with the decisions needed, not the data available. Everything else is evidence for those decisions.
Decisions needed
- 1
Approve a second installer for one region
Waiting on one installer is the largest internal blocker. A second cuts the wait from about 3 weeks to about 1.
Owner · Delivery leadBy · Fri - 2
Clear 3 live sites that are not billing
Three sites have been live for more than 30 days with no invoice schedule. Revenue is being left on the table.
Owner · Finance leadBy · Wed - 3
Decide: customer-owned blockers over 20 days
Eight projects wait on customers. Option A: weekly executive outreach. Option B: pause and reschedule.
Owner · Head of operationsBy · Next review
The scoreboard
Eight numbers, each with a direction.
Week-over-week change shown under each figure. Green is better, amber needs watching. Figures are recreated and illustrative.
Live versus billing
Revenue can leak in both directions.
Crossing “is it live?” with “is it billing?” gives four boxes. Tap either exception box, Live, not billing or Billing, not live, to filter the sample list below it.
Sample exceptions, with an owner and a next action
| Site | Condition | Days | Owner | Next action |
|---|---|---|---|---|
| S-0142 | Billing, not live | 31 | Delivery lead | Install rescheduled; customer confirmed for Tuesday |
| S-0207 | Billing, not live | 24 | Delivery lead | Waiting on customer network change |
| S-0388 | Billing, not live | 12 | Procurement | Hardware in transit; ETA Thursday |
| S-0119 | Live, not billing | 34 | Finance lead | Invoice schedule missing; draft created for approval |
| S-0261 | Live, not billing | 33 | Finance lead | Contract line not linked; fix in CRM |
| S-0075 | Live, not billing (approved pilot) | 60 | RevOps | Approved pilot; review date set |
A sample of the oldest exceptions: 3 of the 6 live-but-not-billing sites and 3 of the 11 billing-but-not-live sites. Each has an owner, an age and a next action.
Why work is stuck
Separate their blockers from ours.
Blockers by cause · 21 open
Customer-side blockers get customer outreach. Internal blockers get an owner and an escalation date.
How much to trust this page
Data confidence, stated.
- 3 open data issues, each with an owner
- Definitions version 4, unchanged this week
- Reconciliation run Thursday night; exceptions re-checked Friday morning
Escalation order when everything is on fire: business impact, then customer impact, then revenue impact, then operational risk, then everything else.
Also on this page
Related tools folded into this page. Each opens in place; tap Close when done.