Orbit Commerce
Mid-Market · E-commerce Retail · £58,000 ARR · Owner Priya Nair
- Lifecycle stage
- Onboarding
- Renewal
- 07 Jun 2027 (268 days)
- Last contact
- 5 days ago
- Last refresh
- 2 days ago
- Previous score
- 59/100
- Assessment confidence
- High
Customer context
- Customer goal
- Consolidate order exception handling into one queue before peak season.
- Original purchase reason
- Peak-season exception backlog caused refunds and support spikes last year.
- Primary use case
- Order exception triage and fulfilment SLA monitoring.
- First-value milestone
- First exception queue live — achieved late (week 9 against a week 4 plan).
- Current success milestone
- Historic order migration completed (blocked on customer data extract).
- Executive sponsor
- Leanne Carter, Ecommerce Director
- Day-to-day champion
- Dev Shah, Fulfilment Manager
- Stakeholders
- Data engineer, Customer service lead
- Contract start
- 08 Jun 2026
- Renewal date
- 07 Jun 2027
- Expansion potential
- Possible once peak season is proven. Not a current conversation.
- Main blocker
- Strong relationship but narrow feature adoption and an onboarding blocker before peak season.
What changed?
- Product adoption 45 → 48 (+3)
- Business outcomes 48 → 50 (+2)
- Customer engagement 82 → 84 (+2)
- Support experience 68 → 70 (+2)
- Customer sentiment 72 → 74 (+2)
- Improving from a slow start, but adoption breadth is lagging the relationship strength.
Why this matters
Strong relationship but narrow feature adoption and an onboarding blocker before peak season.
£58,000 ARR renews in 268 days. Recommended next action: Agree a dated migration plan with the customer's data engineer and book feature enablement training.
Five signals
Product adoption
+3 pts48/100
Previous 45 · Weight 30% · Contribution 14.4 pts
- • Only 2 of 5 key features are in use
- • Exception triage used daily, reporting and automation untouched
Business outcomes
+2 pts50/100
Previous 48 · Weight 25% · Contribution 12.5 pts
- • One of two onboarding milestones achieved
- • Migration blocker means no full-history reporting yet
Customer engagement
+2 pts84/100
Previous 82 · Weight 20% · Contribution 16.8 pts
- • Weekly onboarding calls fully attended
- • Champion responds same day and runs internal training
Support experience
+2 pts70/100
Previous 68 · Weight 15% · Contribution 10.5 pts
- • One medium ticket open on the migration tooling for 6 days
Customer sentiment
+2 pts74/100
Previous 72 · Weight 10% · Contribution 7.4 pts
- • Recent meeting sentiment neutral-positive
- • Champion frustrated by internal data delays, not by the product
Six-month health history
Improving from a slow start, but adoption breadth is lagging the relationship strength.
AI risk analysis
Deterministic, context-aware analysis generated locally from this account's signals — no external API. The service layer is isolated so a real model can be connected later.
Recommended actions
Next 7 days
- • Re-baseline the onboarding plan with named owners and dates for every open blocker.
- • Pull a user-level activity export and identify the top three inactive teams.
Next 30 days
- • Run targeted enablement for the unused features tied to their primary use case, then re-measure weekly active users.
Support issues
- ORB-2210 · Medium · Open · 6 days
Historic order import fails above 250k rows
Activity timeline
No recorded activity yet. Log a touchpoint, draft a re-engagement message or add a task and it will appear here.