The buyer's view: who hasn't started?
The one report a corporate buyer actually wants, that almost nobody sends — and the situation it prevents.
A corporate buyer — the L&D head who signed off ten seats — has never once asked what is in your course. They read the brochure before they bought it.
What they actually want to know, every week, is one thing: "who on my team hasn't started?" And almost nobody sends it to them.
The one idea. The buyer and the learner are different people with different questions. Every onboarding email you send goes to the learner. The person who chose you, pays you, and decides whether to renew gets nothing at all.
What the buyer is actually managing
Put yourself on their side of it. They spent budget, they told their manager it would help, and they have no idea whether it is working. They cannot see logins. They will not chase their own colleagues without a reason. So they wait until renewal, look at a vague feeling, and decide.
Meanwhile you are sitting on the exact number they need, and it costs you nothing to send it.
The build
Desk — the buyer's Monday digest
Weekly, grouped by account owner, each buyer receiving only their own rows. One query, one gate, one send.
Scroll for all 5 steps →
The query carries two numbers per account, and the second one is the one people forget: how much of the course the people who did start have actually consumed. A digest that only counts logins reports an account as healthy the moment everybody has logged in once.
The three accounts, and why they are three different problems
| Account | Bought | Started | Consumption | What the buyer should be told |
|---|---|---|---|---|
| Meridian Business School | 45 | 41 | — | Four people to chase. Manageable, and better said now than at the deadline. |
| Vertex Logistics | 10 | 6 | — | 40% of what they bought is untouched. This is the renewal conversation, happening in silence. |
| Nimbus Retail | 10 | 10 | 57% | Fully activated and stalling. A login-only digest calls this account perfect. |
Meridian Business School
- Bought
- 45
- Started
- 41
- Consumption
- —
- What the buyer should be told
- Four people to chase. Manageable, and better said now than at the deadline.
Vertex Logistics
- Bought
- 10
- Started
- 6
- Consumption
- —
- What the buyer should be told
- 40% of what they bought is untouched. This is the renewal conversation, happening in silence.
Nimbus Retail
- Bought
- 10
- Started
- 10
- Consumption
- 57%
- What the buyer should be told
- Fully activated and stalling. A login-only digest calls this account perfect.
Vertex is the obvious one. Nimbus is the interesting one. Every seat activated, so every dashboard that counts activation shows a green row — and consumption is stuck at 57%, against six days when the labs were unavailable. Nothing about that account looks wrong unless you are looking at the right number.
Why this lesson connects to the other course
Nimbus Retail — 10 seats, ₹1,20,000, six days of outage, consumption stuck at 57%, three certificates issued.
That account goes on to demand a full ₹1,20,000 refund, and the flagship path — Building Production-Ready AI Agents — spends an entire module building the control layer that stops an agent handing that refund over. It is a genuinely hard problem and worth the module.
But look at the timeline. The outage happened. Consumption stalled. Nobody told the buyer, so the buyer discovered it themselves, and by the time they wrote in they were four contacts deep and out of patience. This digest, sent in week one, is the cheapest thing in either course.
The honest framing. The flagship teaches you to catch the refund demand safely. This lesson is about the situation not arising. Both are worth building — but a control that prevents costs less than a control that catches, and this one is a scheduled query and a template.
Writing a digest a buyer will actually open
- Lead with the number they can act on. "4 of your 10 seats have not been opened" — not "here is your weekly report".
- Name names, if your contract allows it. A list of four people is actionable. A percentage is a feeling.
- Say what you have already done. "We have emailed them twice" stops the buyer wondering whether it is their job.
- Send it when nothing is wrong, too. A digest that only arrives with bad news becomes a letter people dread and stop opening.
- One account per email. Never let a buyer see another customer's numbers. Group by owner in the query, not in the template.
As in lesson 12, the send step here has not been executed. The digest goes to real addresses in a live integration. Build it, point it at yourself for a fortnight, and read what arrives before any buyer does.
Next: everything you have built, assembled by you, in the capstone.
Related lessons
Base rates — what a piece of evidence is actually worth
A face-recognition system that is 99.9% accurate and almost entirely wrong, and a number that sent an innocent woman to prison. Both are the same arithmetic, and it is the arithmetic that decides what any piece of evidence is worth.
ReadConfirmation and survivorship — what you never looked for
Two questions about evidence you did not go looking for. One is a rule you have to discover, and one is a pattern in five famous people — and in both, the thing that would have told you the truth is the thing nobody checks.
ReadLoss aversion, sunk cost and regression — what it costs you
Four questions you answer about yourself rather than about a scenario, and your own answers are the finding. Then the pattern that makes praise look useless and criticism look like it works, whatever you actually do.
Read