Professional Services

Overview#

Most customers do not need a generic AI strategy deck. They need a specific decision validated, a specific cluster designed, a specific migration executed, or a specific bottleneck unblocked. Professional Services is the Yobitel engagement model for that work — structured around a named deliverable, scoped through a Statement of Work, and staffed with the same senior engineers who run the Yobitel platform.

Engagements come in four shapes. Architecture engagements design or review a customer's target-state infrastructure — typically a GPU cluster, a sovereign AI platform, or a hybrid estate. Build engagements deliver the target state, from facility coordination through cluster commissioning, platform deployment, and production hand-off. Migration engagements move a customer from a current-state estate (legacy VMware, hyperscaler-Bedrock, in-house Kubernetes) to a target state inside the Yobitel stack or alongside it. Accelerate engagements drop senior engineers into a customer's team for a defined sprint to unblock a specific bottleneck.

Yobitel Communications, the UK-headquartered AI infrastructure company that delivers Professional Services, treats the engagement model as a complement to the platform, not a parallel business. The same engineers who would otherwise be running a NeoCloud region or extending Yobibyte are who the customer is buying. The recommendation has to survive being operated by the team that made it — there is no consulting practice that hands off code to operations and disappears.

Most engagements end in a defined handover: to Managed Operations for ongoing 24/7 watch, to the customer's own SRE team after a knowledge-transfer sprint, or to a Yobibyte / NeoCloud production subscription. The Statement of Work names the handover path at kickoff so the engagement is built toward it from day one.

Quick start — typical engagement flow#

A Professional Services engagement follows a structured five-stage flow that takes most customers from initial conversation to delivered work over four to twenty weeks depending on engagement type. The stages are sequential; the customer's executive sponsor and Yobitel's named delivery lead are the joint owners throughout.

Stage one — scoping. The customer's executive sponsor and Yobitel's account architect walk through the problem, the target outcome, the existing constraints (sovereignty pin, budget, timeline, in-flight projects), and the desired handover path. Output is a one-page scoping note that drives the formal Statement of Work.

Stage two — Statement of Work. The SOW names the engagement type (Architecture, Build, Migration, or Accelerate), the deliverables, the acceptance criteria, the team composition, the rate or fixed price in USD, the timeline, the assumptions and dependencies, and the handover path. The SOW is signed by both parties before any delivery work starts.

Stage three — kickoff. A joint kickoff brings the customer's team, the customer's executive sponsor, and Yobitel's delivery team together. The kickoff produces the working rhythm (weekly delivery sync, biweekly steering, escalation path), the shared workspace (Git, Confluence, Slack or Teams channel, ticket board), and the first sprint plan.

Stage four — delivery. The team executes against the SOW with a weekly delivery rhythm, transparent progress tracking, and explicit risk-and-issue management. Customer-facing milestones map to the acceptance criteria in the SOW.

Stage five — handover. The engagement closes with formal acceptance against the SOW criteria, a knowledge-transfer pack (runbooks, architecture decisions, code, deployment artefacts), and the agreed handover to Managed Operations, the customer's own SRE team, or a Yobibyte / NeoCloud production subscription.

How engagement works#

Professional Services exposes a small set of concepts that match how a customer's procurement and delivery teams think about engineering engagements. The mental model is the Statement of Work at the centre, with the engagement type, deliverables, acceptance criteria, and handover path around it.

• Statement of Work (SOW) — the signed contract for the engagement. Names the engagement type, deliverables, acceptance criteria, team composition, rate, timeline, assumptions, dependencies, and handover path. Reviewed and signed before delivery starts.
• Engagement Type — one of Architecture, Build, Migration, or Accelerate. Drives the typical duration, team size, deliverable shape, and acceptance criteria.
• Deliverables — the named artefacts the engagement produces (architecture document, deployed cluster, migration runbook, accepted code, signed-off runbook library, etc.). Every deliverable carries an acceptance criterion.
• Acceptance Criteria — the explicit measurable conditions for each deliverable. Phrased as a test the customer can run. Acceptance closes the deliverable.
• Team Composition — the named Yobitel engineers on the engagement. Roles include delivery lead, principal architect, senior engineers, and (for Build engagements) a facility coordinator. Team composition is named in the SOW.
• Knowledge Transfer — the explicit plan for handing operational ownership to the customer's team or to Managed Operations. Covers documentation, paired-engineering sessions, runbook authoring, and post-engagement Q&A.
• Handover Path — the destination of the engagement output. Common paths are Managed Operations (most common), the customer's own SRE team (with knowledge-transfer plan), or a Yobibyte / NeoCloud production subscription.
• Change Window — for Build and Migration engagements, the window during which production changes are allowed. Aligned with the customer's existing change-approval process and recorded in the SOW.

Engagement types#

Engagement type drives duration, team size, deliverables, and typical handover. The table below covers the four standard types; bespoke shapes are accommodated by combining types or extending duration.

Typical engagement footprint#

Engagement footprint scales with the customer's estate and the engagement type. The table below is indicative for mid-2026; the SOW carries the actual composition for a given engagement.

Scope envelope — in and out#

Professional Services is a contracted engagement, so the relevant question is 'what is in scope?'. The default envelope below is what the standard engagement types cover; the SOW documents customer-specific inclusions and exclusions.

Delivery rhythm#

Professional Services engagements run on a transparent delivery rhythm visible to both the customer and Yobitel. Progress is tracked against the SOW's deliverables and acceptance criteria, surfaced through a weekly delivery sync (Yobitel delivery lead plus the customer's project owner), a biweekly steering review (joint executive sponsorship), and an always-available shared dashboard.

For Build and Migration engagements, the same dashboards and runbooks Managed Operations will inherit are authored during delivery. Handover is a transition rather than a discovery: the customer's team and Yobitel's operations team see the same surface from day one.

• Weekly delivery sync — 30-60 minutes, Yobitel delivery lead + customer project owner. Progress, risks, blockers, next-week plan.
• Biweekly steering review — 60 minutes, executive sponsor on both sides. Strategic alignment, scope changes, executive escalation.
• Shared dashboard — burndown, deliverable status, open risks, named issues. Always available.
• Shared workspace — Git, Confluence or Notion, Slack or Teams channel, ticket board. Customer has full read access from day one.
• Acceptance log — every deliverable signed off explicitly by the customer's named approver before closure.
• Post-engagement Q&A — 30-day window after handover for customer questions; embedded in the SOW.

Pricing#

Professional Services engagements are priced per-day in USD on time-and-materials engagements or fixed-price in USD on fixed-scope engagements. Pricing scales with engagement type, role mix, sovereignty pin, and (for Build engagements) facility coordination needs. The rates below are indicative for mid-2026; the SOW carries the actual rate or fixed price for the engagement.

Fixed-price engagements bill on milestone acceptance; time-and-materials engagements bill weekly or monthly per the SOW. Where the engagement runs alongside an existing Yobitel subscription, spend rolls into the customer's FinOps pipeline as a standard line item.

Security and compliance#

Professional Services engineers operate under the same controls as the rest of the Yobitel platform team. UK NCSC OFFICIAL alignment is the default posture; ISO 27001 and SOC 2 Type II cover the operational control set. Customer-side access is read-only by default; write access is requested through the customer's standard change-approval workflow.

Engagement-specific compliance posture (HIPAA, FedRAMP-equivalent, EU AI Act high-risk, NHS DTAC) is documented in the SOW. For engagements that touch PHI or other regulated data, the relevant Business Associate Agreement and data-processing agreement are signed before delivery starts.

• NCSC Cloud Security Principles — default posture for the engineering team.
• G-Cloud — listed under Cloud Support (Lot 3); orderable through the Crown Commercial Service framework.
• Cyber Essentials Plus — current certificate.
• ISO 27001:2022 — current certificate covering the engineering team and tooling.
• SOC 2 Type II — annual third-party audit.
• GDPR / UK DPA 2018 — DPA, sub-processor list, EU SCCs available.
• Background checks on all engineering staff to BS 7858 (UK) and equivalent jurisdictions.
• Read-only customer-side access by default; write through customer-approved runbooks.
• HIPAA BAA available for engagements that touch PHI.
• EU AI Act — for engagements designing or building high-risk AI systems, evidence collection is part of the deliverable.

Alternatives#

Professional Services is one option for delivering bespoke engineering work. The honest read: a Big Four consulting practice covers strategy and change-management depth but rarely operates AI infrastructure, so handover usually lands with a separate MSP or the customer's own SRE team; a hyperscaler professional-services arm covers cloud-native build well but is single-cloud and lighter on GPU specifics; an in-house build gives full control at the cost of 6-18 months of hiring and the opportunity-cost of platform engineers writing runbooks instead of features. Yobitel Professional Services is delivered by the same engineers who operate the platform, with a direct handover path into Managed Operations, and UK NCSC OFFICIAL as the default sovereignty posture.

Common engagement risks and how they are managed#

Professional Services is a service contract rather than a product, so 'troubleshooting' is reframed as the common risks engagements encounter and how the structured engagement model manages them.

Where Professional Services fits in the Yobitel stack#

Professional Services is the day-zero and day-one engineering layer of the Yobitel stack. Customers buy it to design the target state (Architecture), build the target state (Build), move from current state to target state (Migration), or unblock a specific bottleneck (Accelerate). Most engagements end with a defined handover to Managed Operations for ongoing 24/7 watch, a Yobibyte production subscription for managed inference, or a NeoCloud reservation for sovereign capacity.

The boundaries with other Yobitel surfaces are deliberate. Customer Excellency owns the strategic relationship and the executive sponsor's experience; Professional Services owns the engineering delivery. Training Services delivers multi-cohort knowledge transfer to broader customer teams; Professional Services delivers paired-engineering knowledge transfer to the specific team adopting the delivered work. Managed Operations runs the day-two watch; Professional Services builds what Managed Operations watches. NeoCloud Operations is a specific engagement type for partner-built sovereign clouds; Professional Services delivers the wider customer-build envelope.

Most enterprise customers run Professional Services engagements multiple times across an adoption lifecycle. An initial Architecture engagement scopes the target state. A Build engagement delivers it. Subsequent Accelerate engagements unblock specific issues over the years that follow. Each engagement carries its own SOW, its own deliverables, and its own acceptance — there is no rolling consulting retainer that consumes hours without a named outcome.