Mission telemetry in, renewal evidence out. Portfolio health, value ledgers and AI account briefs for the HubX / Curo / ROC customer base β a working prototype built with Claude Code.
Flag Β· renewal proximity Β· ARR. Tap to open.
Six weighted signals from live telemetry. Tap an account.
| Account | Products | ARR | Renewal | Missions / wk (12 wk) | Health | Signals |
|---|
Five stages, Sign β Renew, for every account. Everything is driven from the pill below, and it stays with you as you scroll: pick an account for its tailored plan (or stay on the generic template), tap a stage to open it, and use β Scenario to stress-test the template β term, sector, operating model, risk.
Likelihood from the flag Β· amount from the CSM. Set expected next-term value per account in the table below.
Follows the filter above Β· at-risk = health below 60.
Actions triggered by signals β the CSM decides.
| Renewal | Account | ARR | Health | CSM forecast β next term | Next best action |
|---|
The one-stop answer kit: cold hard facts, objection reframes you can copy straight into an email, honest battlecards, and 30-second client explainers. In production this page is role-gated β customers never see it.
Tap an objection for the reframe, the proof and the honest caveat. Copy puts the whole answer on your clipboard, ready for an email.
Stack ownership vs service depth. The top-right corner β full stack, fully managed β is the position nobody else in Australia holds.
Honest cards β their real strengths listed first, because credibility is the weapon. Tap to expand.
Client-education snippets for the moments a customer asks "what actually isβ¦". Tap a term.
Built as a lightweight internal pipeline with Claude Code. In production each box wires to systems Sphere already runs.
Curo / ROC mission telemetry Β· helpdesk tickets Β· CRM notes & contracts Β· cert registry
Nightly sync into one account-level table: utilisation, SLAs, adoption, support, compliance
Explainable weighted score + playbook triggers (utilisation drop, champion change, cert expiry, ceiling)
Renewal briefs, QBR packs, ROI narratives, ticket sentiment & expansion-signal mining
Acts on a ranked queue instead of a calendar. Every renewal starts prepared.
Sphere sells both ways β fully managed through the ROC, or hardware the customer operates themselves. The tool ingests the deepest data available in each mode, so no account is invisible.
| Signal | ROC-managed accounts | Self-managed accounts |
|---|---|---|
| Mission telemetry | Native β CuroROC flight logs, abort & weather codes, pilot notes | DJI FlightHub 2 / Dock API sync; Wingtra flight-log ingest |
| Hardware health | ROC maintenance schedule, dock uptime & environmental sensors | Battery cycle counts & health, firmware state via API; care-plan RMA records |
| Compliance | CuroRPA β approvals, logs, pilot currency managed by Sphere | CuroRPA logging gaps + CASA cert registry = earliest going-dark signal |
| Data consumption | CuroInsights logins, report views, deliverable acceptance | Insights processing volumes + raw-data export events (competitive-trial detector) |
| Commercial pulse | Both: consumables & spares order cadence, training bookings, ticket sentiment, contract & payment data from the CRM | |
Every score decomposes into six weighted components. Weights are a starting hypothesis β tuned against real churn outcomes once wired to live data.
| Component | Example inputs | Weight |
|---|---|---|
| Utilisation | Mission completion vs plan, dock uptime | 30% |
| Data delivery | Time-to-data vs SLA, deliverable acceptance | 20% |
| Adoption | Curo weekly active users, Insights reports viewed | 15% |
| Support | Ticket severity load, RMA turnaround | 15% |
| Relationship | Exec engagement recency, champion status | 10% |
| Commercial | Payment health, term length, expansion signals | 10% |
Cost: CSM time plus Claude API usage β no Gainsight/Catalyst licence, no consultants, and it's shaped exactly around HubX/Curo rather than a generic SaaS template.
Wins, losses, objections and escalations, clustered into themes. Nothing learned leaves with the person who learned it. Tap a theme.
Lost a deal, hit an objection, took an escalation, found something that works β file it.
Drop a PDF or photograph the paper copy. ACV, term dates and inclusions land on the profile β after CSM review.
Demo note: extraction is simulated on-device. In production the document goes to the Claude API (vision + PDF), and the confirmed terms sync back to the CRM as the source of commercial truth.
Bring the existing book across from the CRM. Paste CSV or load a file β data stays on this device.
Accounts CSV β columns: name, sector, products, arr, renewal (YYYY-MM-DD), mode Β· download template
Touchpoints CSV β columns: account, date (YYYY-MM-DD), type, note Β· download template
In production this is a one-time migration script plus a nightly CRM sync β imported accounts start with contract + touchpoint history, a placeholder health score, and a value ledger that fills itself as telemetry lands.