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 |
|---|
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.