A sample Customer Health Check.
This sample uses fictional data. Foxglove Learning is a made-up EdTech company.
Every account scored, with the revenue attached.
The portfolio view. Who carries a churn signal, who is ready to grow, and how much recurring revenue rides on each.
The book is the active account list, each with an individual customer health score. Expansion signals identify accounts with room to grow. Churn signals identify accounts showing warning signs. Both are tested independently of the customer health score, which is why an account can score well and still appear in the pages that follow.
Accounts triggering both appear once, under churn.
The book
Expansion signals
within 90 days
Churn signals
within 90 days
while carrying a churn signal.
Prepared by Seren for Foxglove Learning248 accounts scored · data as of August 7, 2026
What a score is made of, and why it ranks where it does.
The same account from the Snapshot, taken apart: the score, the data behind it, the signal it carries, its place in the queue, what the data could not say, and the next step.
35% of score
24% of score
24% of score
18% of score
flag only
The score
3.53 places this account in the light green band, which is where most of the book sits. The score ranks accounts for attention; it does not predict that this one will churn.
Adoption and engagement read healthy; support sits at a neutral 3.00 with nothing on record, and champion coverage at 1.67 is low enough to pull the average down and not low enough to move it out of green.
What feeds the score
Four weighted categories, each read from a different export file, averaged at the weights shown on the card. Every input below is a field in the export, so each one can be checked against the source.
Adoption 4.50 72 percent of rostered seats active at peak; 145 core actions per active user across the school year. Engagement 4.00 Last in-season activity 5 days before the May 31 cutoff; second half of the year at 100 percent of the first. Support 3.00 No tickets on record. Scored neutral, since silence is ambiguous. Champion coverage 1.67 229 days since either listed contact last wrote in, 241 days since the last meeting, 2 contacts on file. Payment behavior is computed and reported as a flag rather than averaged in, because it sits on one value for nearly every account in a healthy book.
Why this account is flagged
Observed: the product was in use in every in-season month through May, and neither listed contact has sent a message since December 21, 2025.
Interpretation: usage this steady is usually driven by someone inside the district, and that person is no longer talking to the account team. The signal fires when the two are true together: adoption at 3.25 or higher with no inbound message in more than 150 days.
What the signal does not say is that the district has decided to leave. It finds an unattended relationship, not a decision.
Why it gets this priority
The account renews in 7 days, which puts it first among the 38 accounts carrying a churn signal regardless of how it scores. The contract is $10,193, so the urgency comes from the date rather than the dollars.
Priority combines renewal timing, contract value, usage and engagement; health and priority are not the same thing. A worse score with a renewal six months out ranks below a milder signal on a contract renewing this month, and a larger contract with the same signal and the same date would rank above this one.
What the data can't tell us
The helpdesk has no tickets for this account at all, so it can neither confirm nor deny that the district is still in touch; that absence is not a good sign or a bad one.
The one invoice on file shows Open with no payment date 12 months after it was issued, which may be a payment never recorded rather than a payment never made. The commercial category reads Open as neither paid nor overdue, so it counts for nothing either way.
The contact log is maintained by hand, so a conversation that happened outside logged email would not appear here. Missing data was not scored against the account and was not taken as evidence that all is fine. The Gap List below records the limits of the contact log and of payment data across the whole book.
What to do next
Action: before the renewal date, send the district's Chief Academic Officer a short report on what its teachers did with the product this year, using the usage above, and ask who is handling the renewal.
Owner: the account owner on file. Purpose: to establish whether the district still has someone who owns the product and who is deciding the renewal, with 7 days to find out. Writing to the Chief Academic Officer rather than the day-to-day contact is deliberate: both have been equally silent, and the renewal decision sits with budget authority.
The patterns behind the scores and the actions to take.
The executive summary opens the Insight Report: what was found, what could move retention or expansion, how far each finding can be trusted, and what leadership does in the next 30 days.
Executive summary
- Champion gone quiet. On 18 accounts the product is in regular use and the contact log records no inbound message in more than 150 days. If those people have moved on, the renewal has no relationship behind it. Evidence: adoption 3.25 or higher; between 153 and 268 days since the last inbound message. $958,714 in ARR.
- Champion gone quiet with payment behavior. 5 accounts record no inbound message in more than 150 days and carry two or more unpaid or disputed invoices, usually because the person who handled the account has moved on. Evidence: between 154 and 284 days since the last inbound message; 2 to 4 open invoices per account. $526,675 in ARR.
- Room to add product. 79 accounts use one platform heavily and hold no second platform on the contract, so a proposal starts from evidence rather than argument. Evidence: more than 40 core actions per active user; Foundations or Keys absent from the contract. $3,589,090 in ARR.
| Pattern and confidence | Why |
|---|---|
| Champion gone quiet Low | Kept by hand in the contact log; on 12 of 18 accounts a recent helpdesk ticket is missing from it, so who at the district is still in touch is unresolved. See the Gap List below. |
| Champion gone quiet with payment behavior Low | Kept by hand in the contact log; on 1 of 5 accounts a recent helpdesk ticket is missing from it, so who at the district is still in touch is unresolved. See the Gap List below. |
| Room to add product Medium | Kept by hand in the account list, present on every account, with no other source disagreeing. |
- Contact every churn-signal account renewing within 90 days before the renewal conversation starts.
- Champion gone quiet on the accounts not covered above: send each district a report on its most active schools, so the listed contact has a reason to reply and the district shows who still owns the product, largest first.
- Confirm each expansion account renewing within 90 days before any offer, and bring its usage evidence to the renewal.
What the data could not answer and what it would take to close the gaps.
Every Health Check ends with this. Some items are faults in the data. Others are limits of reading a single export once.
The gap list records each gap in the data supplied, why it matters to the findings, and what to do about it. Some items are faults in the data. Others are limits of reading a single export once.
Prepared by Seren for Foxglove Learning5 items · data as of August 7, 2026