Revenue Precision · internal
Customer Success Key measures whether the software we build for a client is actually delivering — usage from the app itself, feedback from the people using it, and our own failures on the record. One score per client, and every point of it traceable to something you can show them.
What a score is made of
What actually happened in the app, against what we expected.
What they told us. Management and end users, never averaged.
This period against last. Flat is fine; decline is not.
Our own failures. Unresolved costs double.
Weights are editable, and normalised across whichever inputs a client actually has.
One endpoint, one event per action. Retries can't inflate the numbers, and a metric key nobody defined is stored and flagged rather than silently dropped.
A one-click link, no login, under two minutes. Management and the people using it day to day are asked separately and reported separately — the disagreement between them is the useful part.
Outages, bugs, complaints and missed deadlines logged against the client and visibly pulling the score down. Three incidents this month can't show as green.
Usage, what they said, what broke and how we fixed it, and the assumptions behind every number. The thing you bring to a renewal instead of an opinion.
The difference
Switch between what activity alone says and what the whole picture says. Both numbers are computed live by the same scoring engine the app uses — on sample clients, so nothing real is on display.
Casa Verde Retail
Healthy88 of an expected 80 orders this week.
Orders planned: 88 this week vs 83 last (+6%).
None in the last 90 days.
This is what activity alone says. It can tell you the app is being used — it cannot tell you whether anyone thinks it was worth paying for.
Walk into a renewal knowing whether they're happy, holding the evidence.
Catch a client going quiet months before it becomes a cancellation.
Never logs in. Gets a short question, and a report worth reading.
Answers “how is this client doing?” over MCP, with the evidence attached.
Because usage tells you the app is being opened, not that anyone thinks it was worth paying for. Someone opening it every day and the manager who regrets the purchase are perfectly compatible. Usage is objective but shallow; feedback is deep but sparse. The product holds both and never presents one as the other.
Contact
Questions or ideas? Send a note — it reaches a person, not a queue.
hello@revenueprecision.comDefine what counts, point the app at the endpoint, ask the people using it, and let the report do the talking at renewal.