TL;DR
- Customer Excellency is Yobitel's customer-success function — the team that owns the post-sales relationship across every Yobitel subscription and measures customer outcomes against the success plan agreed at the start of the engagement.
- Three engagement tiers — Standard, Premium, and Strategic — with Customer Success Manager (CSM) ratios, review cadence, and executive sponsorship scaling per tier.
- Health Score is the customer-facing telemetry: rolling adoption, performance, and satisfaction signals that catch a stalling relationship before it escalates. Customers see their own health score; CSMs use it to time interventions.
- Customer Excellency is included with every Yobitel product subscription rather than purchased separately. The function complements (not competes with) the Managed Operations TAM, who owns operational matters.
- UK NCSC OFFICIAL alignment is the default posture for the team; CSMs operate under the same access controls and audit posture as the rest of the Yobitel platform organisation.
Overview#
Buying AI infrastructure is the easy part. Realising the outcome that justified the spend is the hard part — and it is the part that almost every vendor under-invests in. Customer Excellency is Yobitel's structured response to that gap: a named function with a named role (the Customer Success Manager), a defined cadence (kickoff, health check, QBR), a measurable signal (the customer health score), and a clear boundary against the rest of the Yobitel stack (Managed Operations owns running it; Customer Excellency owns the customer succeeding with it).
Every Yobitel customer is assigned a Customer Success Manager (CSM) at contract signature. The CSM understands the customer's business, owns the success plan, tracks the agreed KPIs, advocates inside Yobitel for customer needs, and is the single point of contact for strategic concerns that do not belong in operational escalation. On Premium and Strategic tiers, a Yobitel executive sponsor is also named so the customer has a senior point of contact above the CSM.
The CSM and the Managed Operations TAM are deliberately separate roles. The TAM owns operational matters — incident response, change management, capacity reviews, runbook ownership. The CSM owns the relationship and outcomes — adoption, value realisation, expansion, escalation, strategic alignment. A customer should be able to raise a strategic concern without it being routed through operational escalation; equally, an operational incident should not need to wait for a relationship conversation to resolve. The two roles work the same customer but on different cadences and against different metrics.
Yobitel Communications, the UK-headquartered AI infrastructure company that delivers Customer Excellency, includes the function with every product subscription. Standard tier comes bundled with every Yobibyte, NeoCloud, AI Applications, or Managed Operations subscription. Premium and Strategic tiers carry an additional uplift in the subscription contract for the higher CSM ratio, named executive sponsor, and faster response times. UK NCSC OFFICIAL alignment is the default posture for the team.
Quick start — onboarding as a Yobitel customer#
Onboarding follows a structured four-stage flow that takes most customers from contract signature to a working rhythm over 60 - 90 days. The customer's executive sponsor and Yobitel's named CSM are the joint owners; specific operational milestones (Yobibyte workspace stood up, NeoCloud reservation live, first AI Application deployed) are owned by the relevant delivery team.
Stage one — kickoff. Within ten business days of contract signature, the CSM convenes a kickoff with the customer's executive sponsor, the customer's named technical lead, and the relevant Yobitel delivery owners. The kickoff produces the success plan: the named KPIs that define success, the timeline, the dependencies, the escalation path, and the agreed cadence (weekly during onboarding, biweekly after).
Stage two — health check. At day 30, the CSM runs the first health check. The health check is a structured conversation backed by the customer health score (adoption, performance, satisfaction) and the success plan KPIs. Any drift from the plan is surfaced and addressed before it becomes an escalation.
Stage three — roadmap alignment. At day 60, the CSM brings the customer's executive sponsor into a roadmap-alignment session. The session covers Yobitel's product roadmap, the customer's roadmap, dependencies between the two, beta-programme opportunities, and any strategic shifts that need a roadmap response.
Stage four — QBR rhythm. At day 90, onboarding closes and the customer moves into the ongoing QBR (Quarterly Business Review) rhythm. The QBR runs every 13 weeks, refreshes the success plan, and is attended by the executive sponsor on both sides on Premium and Strategic tiers.
Kickoff lands best when the customer's executive sponsor attends in person. The success plan KPIs need executive sign-off to be enforceable, and the relationship that gets a customer through their first escalation is the relationship built at kickoff, not the one built at the first incident.
Concepts#
Customer Excellency exposes a small set of concepts that match how a customer's executive sponsor and CSM think about a structured customer-success programme. The mental model is the success plan at the centre, with the CSM, the health score, the QBR cadence, and the escalation path around it.
- Customer Success Manager (CSM) — the named Yobitel relationship owner for the customer. Owns the success plan, tracks KPIs, runs the cadence, advocates inside Yobitel. Distinct from the Managed Operations TAM.
- Executive Sponsor (Yobitel-side) — a named Yobitel executive who pairs with the customer's executive sponsor on Premium and Strategic tiers. Provides senior-level continuity and escalation continuity.
- Success Plan — the document signed at kickoff that names success KPIs, timelines, dependencies, escalation path, and review cadence. Refreshed at every QBR.
- Health Score — the rolling customer-facing telemetry covering adoption (workspace usage, replica utilisation, learner certification), performance (SLA adherence, incident frequency), and satisfaction (NPS, escalation history). Customers see their own health score; CSMs use it to time interventions.
- Quarterly Business Review (QBR) — the ongoing 13-week review cadence that refreshes the success plan, surfaces opportunities and risks, and aligns on the next quarter. On Premium and Strategic tiers, attended by executive sponsors on both sides.
- Adoption Plan — the structured plan for moving from initial deployment to full production utilisation. Owned by the CSM during onboarding; transitions to the customer's own team at the end of onboarding.
- Escalation Path — the documented escalation chain when a strategic concern needs to move above the CSM. CSM -> CSM lead -> Yobitel executive sponsor -> Yobitel CEO. Times to acknowledge and response scale per tier.
- Beta Programme Access — the formal channel for participating in early access to Yobitel platform features. Included by default on Strategic tier; available on request on Premium.
Engagement tiers#
Three tiers cover the bulk of customer needs. Tier drives CSM ratio, review cadence, executive sponsorship, response times, and beta-programme access. The tier is part of the product subscription contract rather than a separate purchase.
| Tier | CSM ratio (named accounts per CSM) | Review cadence | Executive sponsorship | Strategic concern acknowledge SLA | Beta access |
|---|---|---|---|---|---|
| Standard | Up to 25 | Quarterly QBR | On request | 1 business day | On request |
| Premium | Up to 10 | Quarterly QBR plus monthly check-in | Named Yobitel executive sponsor | 4 business hours | Available on request |
| Strategic | Up to 4 | Quarterly QBR, monthly check-in, biweekly working session | Named Yobitel executive sponsor plus CEO-level continuity | 1 business hour | Included by default |
| Partner / NeoCloud-operator | Custom | Per partner agreement | Named partner executive | Custom | Custom |
CSM ratio by customer size#
CSM ratio (named accounts per CSM) is the operational lever that drives how much attention each customer gets. The table below reflects mid-2026 ratios and the typical customer profile at each tier.
| Tier | CSM ratio | Typical customer profile | Subscription size band (USD/year) |
|---|---|---|---|
| Standard | Up to 25 | Mid-market, single product, single business unit | $50K - $500K |
| Premium | Up to 10 | Enterprise, multi-product, multi-business unit | $500K - $5M |
| Strategic | Up to 4 | Multi-region, multi-product, beta-programme involvement, board-level outcome tracking | $5M+ |
| Partner / NeoCloud-operator | Custom | NeoCloud Operations partners running branded sovereign clouds | Custom |
Response-time commitments#
Response times scale per tier and per concern class. Strategic concerns (relationship, roadmap, expansion, escalation) flow through the CSM and the executive sponsor; operational concerns (incidents, change management, capacity) flow through the Managed Operations TAM on the schedule defined in the Managed Operations contract.
| Tier | CSM strategic acknowledge | CSM working response | Executive sponsor escalation acknowledge | Beta-request acknowledge |
|---|---|---|---|---|
| Standard | 1 business day | 5 business days | 5 business days | 10 business days |
| Premium | 4 business hours | 2 business days | 1 business day | 5 business days |
| Strategic | 1 business hour | 1 business day | 4 business hours | 2 business days |
Customer health score#
Customer Excellency publishes a rolling customer health score that the customer can see in their Yobitel console. The score combines three signals: adoption (how much of the subscribed surface is in use), performance (whether the deployed estate is healthy and the SLA is being met), and satisfaction (NPS and escalation history). The score is intentionally legible — there is no opaque magic number — and each component is drillable to the underlying telemetry.
CSMs use the health score to time interventions. A drop in the adoption component triggers a working session to unblock usage. A drop in the performance component triggers a joint review with the Managed Operations TAM. A drop in the satisfaction component triggers an escalation path conversation before the issue compounds.
- Adoption signal — Yobibyte workspace usage, NeoCloud reservation utilisation, AI Application deployment count, certification completion rates. Published to the customer's console.
- Performance signal — SLA adherence, incident frequency by severity, change-management throughput, runbook coverage. Sourced from Managed Operations telemetry.
- Satisfaction signal — quarterly NPS, escalation history, beta-programme participation, executive sponsor session attendance. Customer-reported plus relationship-tracked.
- Composite score — a 0-100 rolling number with each component visible. Components are weighted equally by default; weighting is customisable on Premium and Strategic tiers.
- Threshold alerts — automatic alerts to the CSM when the composite drops by more than 10 points in a 30-day window, or when any component drops below 50.
Pricing#
Customer Excellency is bundled with every Yobitel product subscription. There is no separate purchase for the Standard tier; Premium and Strategic tiers carry an uplift on the subscription that funds the higher CSM ratio, the named executive sponsor, and the faster response times. The uplift is itemised in the standard billing export so customers can see what they are paying for the function.
| Tier | Pricing model | Indicative cost (USD/year) | Notes |
|---|---|---|---|
| Standard | Included with subscription | $0 | Bundled with every Yobibyte, NeoCloud, MediQuery, or Managed Operations subscription. |
| Premium | Uplift on subscription | $45,000 - $120,000 | Scales with subscription size and number of products. |
| Strategic | Uplift on subscription | $150,000 - $500,000+ | Scales with subscription size, regions, and beta-programme participation. |
| Partner / NeoCloud-operator | Per partner agreement | Custom | Folded into the partner operating agreement. |
| Additional executive sponsor session | Per session | $5,000 - $15,000 | Available across all tiers for one-off needs. |
| Joint customer event (Yobitel-hosted) | Per event | $15,000 - $75,000 | Customer briefing, roadmap session, or executive workshop. |
Security and compliance#
Customer Excellency operates under the same control set as the rest of the Yobitel platform organisation. UK NCSC OFFICIAL alignment is the default posture; CSMs access only the customer relationship surface (the success plan, the health-score telemetry, the QBR notes, the beta-programme history) and have no read access to the customer's data or production observability surface unless the customer explicitly grants it.
All customer relationship data is held under GDPR and the customer's data-processing agreement. CSMs are background-checked to BS 7858 (UK) and equivalent jurisdictions; access is logged and immutable; the customer can request the full access log at any time.
- NCSC Cloud Security Principles — default posture for the team.
- G-Cloud — listed under Cloud Support (Lot 3).
- Cyber Essentials Plus — current certificate.
- ISO 27001:2022 — current certificate covering the customer relationship data set.
- SOC 2 Type II — annual third-party audit.
- GDPR / UK DPA 2018 — DPA, sub-processor list, EU SCCs available.
- Background-checked CSMs — BS 7858 (UK) and equivalent jurisdictions.
- Read-only access to the customer relationship surface; no access to production data or workload telemetry unless explicitly granted.
- Immutable access log — customer can request at any time.
- Confidentiality — CSMs are bound by per-customer NDAs as part of the subscription contract.
Alternatives#
Customer Excellency is one option for structured customer-success management. The honest read: a hyperscaler TAM programme covers the cloud's own services well but stops at the cloud boundary and rarely separates strategic from operational concerns into distinct roles; an MSP's account-management function bundles with the MSP contract but usually has neither AI-infrastructure depth nor a published health-score telemetry; an in-house customer-success function is the most flexible but requires the customer to build CSM frameworks, health-score telemetry, and QBR rhythm internally. Yobitel Customer Excellency sits in the middle as a function bundled with the subscription, covering the full Yobitel stack, with the CSM and the Managed Operations TAM as distinct roles so a customer can raise a strategic concern without routing through operational escalation.
| Concern | Yobitel Customer Excellency | AWS / Azure / GCP TAM programme | MSP account management | In-house customer-success |
|---|---|---|---|---|
| Coverage of full AI infrastructure stack | Yes (Yobibyte, NeoCloud, AI Applications, Managed Ops) | Cloud-only | Variable | DIY |
| Sovereignty posture | UK NCSC OFFICIAL default | Cloud's posture | Variable | Whatever you build |
| Health-score telemetry | Customer-visible, drillable to source signals | Internal to cloud | Variable | DIY |
| Named executive sponsor | From Premium tier | Enterprise-tier only | Variable | DIY |
| CEO-level continuity | Strategic tier | No | No | DIY |
| Bundled with product subscription | Yes | Enterprise-tier uplift | Bundled | N/A |
| Beta-programme access channel | Included from Strategic tier | Variable | Variable | DIY |
| Distinct from operational TAM | Yes (CSM vs Managed Ops TAM) | Single TAM covers both | Variable | DIY |
| Pricing | Bundled with subscription; Premium / Strategic uplift | Per-account uplift | Bundled with MSP | Salaries |
| QBR cadence with executive sponsor | Standard from Premium tier | Enterprise-tier only | Variable | DIY |
Common relationship issues and how they are handled#
Customer Excellency is a service function rather than a product, so 'troubleshooting' is reframed as the common relationship issues that come up and how they are handled.
| Issue | Symptom | Mitigation |
|---|---|---|
| Adoption stalled | Subscribed surface is under-used; adoption-signal drop on the health score. | CSM convenes a working session with the customer's technical lead to identify the blocker; targets a runbook, training, or Professional Services Accelerate engagement to unblock. |
| Expansion roadblock | Customer wants to expand but is blocked on internal procurement or technical dependency. | CSM brings the executive sponsor into a roadmap-alignment session; engages relevant Yobitel delivery owners to unblock the dependency. |
| Escalation timeline missed | Customer's strategic concern not acknowledged within the tier's SLA. | Health-score satisfaction signal drops; auto-alert to CSM lead; CEO-level escalation engaged on Strategic tier. |
| Renewal at risk | Subscription renewal approaching with declining health score. | CSM convenes a renewal-risk session with the executive sponsor; brings in any required corrective actions before renewal decision. |
| Executive sponsor change (customer-side) | Customer's executive sponsor leaves or rotates. | CSM convenes an introduction with the new sponsor; success plan reviewed and re-signed. |
| Beta-programme conflict | Customer-requested beta feature conflicts with another customer's roadmap need or with platform stability. | CSM brings the customer into a roadmap-alignment session with Yobitel product; transparency on the trade-off; alternative timelines or workarounds proposed. |
| TAM-CSM boundary confusion | Customer routes operational issues through the CSM or strategic concerns through the TAM. | CSM and TAM run a joint working session to clarify boundaries; documented in the success plan. |
| QBR pattern decay | QBR attendance from the executive sponsor drops; meetings start being delegated downward. | CSM convenes a relationship reset with the executive sponsor; cadence and format adjusted to fit the executive sponsor's actual availability. |
| Strategic-tier expansion request | Customer at Standard or Premium needs Strategic-tier attention for a specific initiative. | CSM proposes either a tier upgrade or a time-bounded Strategic-tier extension scoped to the initiative. |
Where Customer Excellency fits in the Yobitel stack#
Customer Excellency is the relationship and outcomes layer that wraps every other Yobitel surface. Professional Services delivers the build; Managed Operations runs the result; Training upskills the team; Customer Excellency makes sure the customer is actually getting the value that justified the spend in the first place. The roles are deliberately separated so a customer can raise a strategic concern without routing through operational escalation and vice versa.
Practically, every Yobitel customer has both a CSM (Customer Excellency) and a TAM (Managed Operations, from Premium tier). The two roles work the same customer but on different rhythms and against different metrics — the CSM owns the QBR, the success plan, and the renewal; the TAM owns the incident response, the change management, and the capacity review. Both report into Yobitel's customer-facing organisation under the same UK NCSC OFFICIAL-aligned control set; both are bound by the same per-customer NDA.
For partners running their own NeoCloud, Customer Excellency operates as part of the partner agreement rather than a per-end-customer contract. The Yobitel CSM works the partner; the partner's own customer-success team works the partner's end customers. The boundary stays clean and the partner's brand stays in front of the end customer.
References
- Customer Excellency page · Yobitel
- Managed Operations · Yobitel
- Professional Services · Yobitel
- Training and Enablement · Yobitel
- Yobibyte platform · Yobitel
- NCSC Cloud Security Principles · NCSC