Skip to content
HeuriTel
Sign in
Two technicians working on a street cabinet, one testing with a handheld meter.

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 availableLevel 2 of 5 — A journey runs end to end on sample data, including its refusal and failure states. Bought by CTIO and Chief Digital Officer. Nothing here has run against an operator system.

Open the demonstration

Technicians working in the field — delivery, not a slide. The engagement here is the sample's; no pod is contracted.

Public nowAnyone can do this from this page, without signing in, and the page keeps no record of it. This page, its sample workbook and the sample's review need no sign-in; the steps below say which need more.

The sample, computed

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

HeuriTel default synthetic sample — Kenya, in KES, Kiswahili; sample engagement-readiness-plan-sample v1. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it. Configure a market and this page, the workbook and the review recompute for it.

  • 2 of 5 — Prerequisites metreadiness rows in state met
  • 2 prerequisites — Blocking, not metblocking rows in state partial or missing
  • no — Can startno blocking prerequisite unmet
  • 20 % — Progressmilestones accepted with evidence filed over milestones planned, handover excluded
  • 12 week — Handover weekthe HANDOVER milestone
  • 7 items — Needed before handoverunmet prerequisites, milestones not accepted with evidence, access revocation

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. No work was scheduled. No access was granted or revoked. No milestone was accepted.

From this page to live operation

10 steps: 3 public now, 1 after sign-in, 3 in an entitled workspace, 1 a request form, 1 needing an authorised sandbox, 1 not implemented.

Each step says who can take it today. A route existing is not the same as an action being available: the state beside each step is decided by the same rules that refuse a request.

  1. 01 · What you can buyPublic nowA telecom-specialist AI team that delivers a working capability in 90 days and hands it over.All ten offers
  2. 03 · The sample, as a workbookPublic now3 data sheets, a manifest and the generated guide, dictionary, validation lists and expected outputs — downloadable without signing in, in the sample's market and currency.Download the sample workbook
  3. 04 · Validation, on the samplePublic nowscope, 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. The public review checks a returned workbook against the sample it was issued from, answers with the result before and after, and stores nothing.POST /api/sample/engagement-readiness-plan/review
  4. 05 · Acceptance and the stored simulationEntitled workspaceYour organisation's own workbook, reviewed, accepted as an immutable version with its original retained, and the engine's result stored whole — never recomputed on reopening.Open the workbench
  5. 06 · Decision and approvalEntitled workspaceThe acceptor decides, and the role is on the record. Approval applies to a simulated recommendation.The approvals queue
  6. 07 · EvidenceEntitled workspacereadiness assessment with blocking items; delivery plan with milestones and acceptance gates; access expiry and handover checklist; run register export. The register export, the retained original, the run history, the dry-run plan and the pilot package are downloadable from the workbench.Evidence on the workbench
  7. 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: one pod scoped and contracted with an operator, with agreed handover criteria. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
  8. 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make; nothing is called and no receipt exists, because no authorised sandbox is registered.
  9. 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: milestones accepted by the operator's named owner. Not built; no connector exists.
Public now
Anyone can do this from this page, without signing in, and the page keeps no record of it.
A verified sign-in sees it on sample data; it reads nothing private and stores nothing.
Entitled workspace
A member of an organisation that holds the owning product and has the journey configured; the role decides which actions.
Pilot request available
The request form is available. A pilot is scoped in writing afterwards; the pilot itself is not demonstrated.
Requires an authorised sandbox
Needs an authorised operator sandbox, which no organisation has registered. The permission that would reach one is refused to everyone.
Requires production authorisation
Needs a production authorisation from the operator and a connected operator system. No such authorisation exists.
Not implemented
No code performs this.
On demand

The contract, the data, the pilot and the products beneath.

Four things a technical or commercial evaluation asks for, each in the same terms as the other nine offers.

The offer in twelve lines
The offer, in twelve lines

The offer in the same terms as the other nine.

Read from the offer contract and the engine's own run; the same twelve fields on every offer page.

Commercial offer
Telecom AI Team-as-a-Service
Buyer
CTIO and Chief Digital Officer
Problem
Operators cannot hire telecom-specialist AI engineers fast enough, and generalist consultancies do not know telecom's systems or its regulatory constraints.
Outcome a pilot would count
Capability delivered and handover accepted by your own team.
Current availability
Demonstration available — level 2 of 5: A journey runs end to end on sample data, including its refusal and failure states. Of 10 steps, 3 are public now, 3 need an entitled workspace, 2 need what does not exist yet. Public now Entitled workspace Not implemented
Public sample
HeuriTel default synthetic sample: Kenya, in KES and Kiswahili (sample engagement-readiness-plan-sample v1). Download the workbook. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it.
Data requirements
Scope (scope_id, deliverable, product, market, operator_owner_role, starts_on, access_expires_on); Readiness (prerequisite_id, prerequisite, state, blocking, owner_role); Milestones (milestone_id, week, scope_id, deliverable, acceptance_gate, accepts_role, state, evidence_filed). 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 never echoed back.
Executable result
Engine engagement-plan v1, on the public 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). 6 measures with their basis, 4 sections, 4 exceptions with owners. Recommendation: 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. Simulated; nothing ran against an operator system.
Approval model
Single approver: the acceptor decides, and the role is on the record. Approval applies to a simulated recommendation.
Evidence
readiness assessment with blocking items; delivery plan with milestones and acceptance gates; access expiry and handover checklist; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
Pilot requirements
one pod scoped and contracted with an operator, with agreed handover criteria. None is evidenced; no pilot is requested or agreed.
Live requirements
No operator system to connect; reconciled before any outcome is claimed: milestones accepted by the operator's named owner. Not built.

Beneath the offer: Telecom AI Team-as-a-Service, Opportunity and Data Readiness Sprint, Excel-to-Simulation Product Studio, AI Assurance, Governance and Handover, Global Telecom AI TaaS & Deployment Services.

Your data — 3 sheets, checked before anything is read
Your data

3 sheets, checked before anything is read from them.

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 never echoed back.

  • 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.
A pilot’s measure and prerequisites — 1 things that would have to be true
What a pilot would count, and needs

Capability delivered and handover accepted by your own team.

Nothing is counted until it is reconciled against your own records: milestones accepted by the operator's named owner.

  • one pod scoped and contracted with an operator, with agreed handover criteria
Built on 4 governed products and 2 catalogue streams
What it draws on

4 governed products and 2 catalogue streams.

The offer is a commercial view onto the same platform every other offer runs on. Its workbench opens with Telecom AI Team-as-a-Service.