Readiness
Each prerequisite as scored, and whether it blocks the start.
5 rows · Prerequisite · State · Blocks start · Owner (role)
Bought by CTIO and Chief Digital Officer
A telecom-specialist AI team that delivers a working capability in 90 days and hands it over.
Operators cannot hire telecom-specialist AI engineers fast enough, and generalist consultancies do not know telecom's systems or its regulatory constraints.
Demonstration available — A journey runs end to end on sample data, including its refusal and failure states. Runs today on a sample of your market; its workspace opens with Telecom AI Team-as-a-Service.
The result, on the sample
The plan cannot start: 2 blocking prerequisite(s) not met; 1 of 5 milestones accepted with evidence; handover in week 12 needs 7 more thing(s).
Sample. Choose your market to see this page, the workbook and the review in your currency and language.
Telecom AI Team-as-a-ServiceYour market · units
The plan cannot start: 2 blocking prerequisite(s) not met; 1 of 5 milestones accepted with evidence; handover in week 12 needs 7 more thing(s).
Prerequisites met2of 5
Can startno
Progress20%
Handover week12week
Decision Do not start: close RD-DATA, RD-SECURITY first (Head of data platform, CISO). If nobody acts: The pod starts on goodwill: work proceeds without security sign-off or full data access, and handover is accepted on a slide.
The other 2 measures the run holds
- 12 week — Handover weekthe HANDOVER milestone
- 7 items — Needed before handoverunmet prerequisites, milestones not accepted with evidence, access revocation
See the product
The workspace, screen by screen.
The 7 screens a demo walks through, captured from the built product on sample rows. Sign in to run it on your own market and your own numbers.
1 of 7 · Overview The workbench: the tiles, the run, the ladder, the last run and the next step. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
2 of 7 · Sample The result on the sample: the headline and the tiles, each with its basis. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
3 of 7 · Sample The decision the engine proposes, and what happens if nobody acts. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
4 of 7 · Sample The checks the engine refused, each with its reason and its owner. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
5 of 7 · Your data Your data: the sheets, the template to download, and the review of what comes back. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
6 of 7 · Runs Every run, as it was computed, with the version it ran on. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
7 of 7 · Decide The proposal to an approver, and what the approver sees. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows.
Three things it decides
Each on your rows, each with its reason written.
Plan check per scope item
Every scope item needs a milestone with a gate, and access that outlasts the handover.
3 rows · Scope · Deliverable · Owner (role) · Milestones
Delivery plan
Milestones in week order with their gates and states.
6 rows · Milestone · Week · Scope · Deliverable
What it needs from you, and how a pilot proves it
Capability delivered and handover accepted by your own team.
scope, readiness and milestones as three sheets: every scope item names a product and a market; every readiness item scores a named prerequisite; every milestone names an acceptance gate, a week and an owner; access expiry is a date. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused, and the refusal names the column.
- The data you supply
- Scope, Readiness, Milestones — your own rows, on your own subject keys, through the same review the sample passes. Bring your data — the workbook out and back, after sign-in. Download the sample workbook
The 3 sheets, column by column
- Scopewhat the pod delivers: a capability, a market, the owner on your side, the access it needs and when that access ends. Columns: scope_id, deliverable, product, market, operator_owner_role, starts_on, access_expires_on.
- Readinessthe prerequisites the pod depends on, scored, and whether each blocks the start. Columns: prerequisite_id, prerequisite, state, blocking, owner_role.
- Milestonesthe plan: week, deliverable, the gate it must pass, who accepts, the state, and whether evidence is filed. Columns: milestone_id, week, scope_id, deliverable, acceptance_gate, accepts_role, state, evidence_filed.
- The measure
- Counted once reconciled against your own records: milestones accepted by the operator's named owner.
- The approval
- The person who accepted the data decides, and the role is on the record. The decision is audited with its reason.
The products and the streams it draws on
Runs on Telecom AI Team-as-a-Service; draws on Opportunity and Data Readiness Sprint, Excel-to-Simulation Product Studio, AI Assurance, Governance and Handover and the Global Telecom AI TaaS & Deployment Services, Telecom AI Engineering Services streams of the catalogue. The lifecycle to live operation and the twelve-line contract are in the workbench, after sign-in.
See it on your own numbers.
Sign in with your work email; the sample is generated for your market and currency; change the values and run again. Or book a demo and we walk it with you.