Find out what your software actually returns We measure who uses it and what it moves, then close the gaps
Claims portalOctober
- Licences, 400 seats$18,400
- Hosting$3,100
- Support contract$7,500
Total$29,000
- Weekly active users142 of 400
- Cost per active user$204
Should moveDays to settle a claimNot measured
Start with who actually opens each department's software Use says more than the license count, and most contracts never measure it
FinanceExpense toolOpened at month end, then left alone
Should moveDays to close the books
SalesCRMUpdated on Mondays, for the forecast call
Should moveDeals forecast correctly
OperationsPlanning toolUsed every day by every planner
Should moveOrders shipped on time
PeopleLearning platformBusy at launch, quiet since
Should moveWeeks to bring a new hire up to speed
ClaimsClaims portalAdjusters still work most claims from email
Should moveDays to settle a claim
Then choose what your support contract pays for Each monthly report shows it, and only one shows days to settle a claim
Maintenance contractOctober
212Tickets closed
- Hours billed
- 1,480
- Urgent tickets
- 6
- Good for
- Stable software that only needs fixing
- When use rises
- More tickets, and more hours billed
Managed serviceOctober
99.95%Uptime
- Service levels met
- 14 of 14
- Incidents
- 2
- Good for
- Systems that have to stay up
- When use rises
- The report looks the same
Outcome contractOctober
318 of 400Weekly users
- Days to settle a claim
- 9.1
- Changes shipped
- 11
- Good for
- Software that should move a number
- When use rises
- It shows on the first line
See both numbers in the report we send monthly Adoption and value for the claims portal, and what we changed because of them
How use decides the next releaseClaims portalOctober report
Adoption318 of 400Adjusters who used it this month
Value9.1Days to settle a claim
The two numbersAdoption comes from your sign-in data, and value from your own claims system.
What we changed
- Cut the claim form to two steps, because adjusters left at the third
- Pre-filled each claim from the policy record
The changesEach one names the number that chose it.
What we'd switch off
- The old document upload page, opened 3 times this month
The retirementsWe say when to stop paying for something.
Then turn your support contract into an outcome contract Four steps, and the report moves from hours to adoption and value
- 1Measure
We add usage tracking to the software you already run.
- 2Baseline
We record use and the business number before anything changes.
- 3Agree
Two targets go into the contract, like weekly users and days to settle a claim.
- 4Report and tune
Every month we report both, and fix what held them back.
Bring the software you're least sure is paying off
We'll measure who uses it and what it moves, and tell you whether to fix it or retire it.