The answers a buyer looks for first.
17 answers in four groups, a glossary of 22 words the site uses, the company and its partners today, and where every guide, register and working surface opens.
Four groups, each answer resting on a fact you can check.
The product
The offers, how far each has been taken, and how the pieces fit together.
The offers available to buy
Ten offers, each built from the same sixteen canonical products and each stating where it stands today. Every offer is at Level 2 of 5 — a journey runs end to end on sample data, including its refusal and failure states. Pilots on an operator's own systems are the next step for each.
Offers, products, streams and definitions, told apart
An offer is the thing you buy: ten of them, each with a buyer, the decision it makes and a measured outcome. A canonical product is a building block of an offer: sixteen, each stating how far it has been taken. A stream is a family of the catalogue: thirty, in five areas. A definition is one entry of the catalogue: 597, each a decision pattern with its buyer, its data and its authority — a description, not a built product.
The five levels
Every offer and product names its level. Level 1: The problem, buyer and design are defined and reviewed. Level 2: A journey runs end to end on sample data, including its refusal and failure states. Level 3: Integration contracts, data boundary and a bounded cohort are agreed with an operator. Level 4: Proven against an operator's real systems in a bounded scope, with measured outcomes. Level 5: Serving subscribers on operator systems, under the operator's change control. The offers hold Level 2 today; the evidence that takes each to the next level is on its page.
The offer that fits you
Five short choices — the result you want, your kind of organisation, the systems that hold your customer truth, the team that would run it and the commitment you can make today — bring up the offers that fit, each with its reasons. Or start from your kind of organisation and read the offers that apply to it.
The business results the offers serve
Six business results: grow customer revenue, reduce avoidable service cost, improve customer acquisition, launch and monetise digital services, reduce fraud and identity risk and turn network capabilities into enterprise services. Each has its own page with the journeys, the products and the offer that carries it.
Trust and authority
The people and systems that decide, the records kept, and the limits of any claim.
Your systems and your people decide
Every action passes seven steps: signal, options, limits, consent, authority, result and proof. HeuriTel holds one of them — ranking the options, including no action. Limits are your policy, consent is the customer's, authority belongs to your system of record, and a second person approves wherever your policy asks for one.
The record kept for every decision
A replayable receipt: assignment, execution, receipt, cost, exception, remedy and the comparison it is measured against — reopened as stored, never recomputed. Across the ten offers there are 32 kinds of evidence, and each offer's page lists its own.
External assurance
The records on this site are HeuriTel's own; no third party has audited or certified them yet. In a delivery engagement, assurance and handover evidence are contractual deliverables with named acceptance owners.
The conditions that stop an action
Limits: A limit is reached, consent is missing, or the service state says otherwise. A stop produces a reason, not silence. Consent: The customer does not confirm. Authority: The approver refuses, or the maker tries to approve their own work. Proof: The source system has not confirmed. Then there is no receipt, and the gap is on the record.
Integration
The systems HeuriTel connects to, the ones it leaves in place, and the prerequisites of a pilot.
Your BSS, CRM and charging stay in place
HeuriTel sits between customer moments and your systems of record. It reads each fact from the system that owns it and writes an action back through that system's own authority; charging, CRM, consent and the network keep their control.
The systems an offer reaches
Between them the ten offers name 24 kinds of system, each offer only its own few: charging or billing (airtime, mobile money, postpaid), subscriber identity, notification channels, an inference provider, entitlement store, billing, partner settlement feed and consent store, and the rest on each offer's page. No offer assumes a system you do not own; the finder asks which you have.
The prerequisites of a pilot
Each offer states its own, and each is something only you can grant — for example signed pack economics with a real inference price (Operator-branded Consumer AI Packs), or a reconciliation run against two real operator sources with Finance confirming at least one finding (Revenue Assurance and Anomaly Operations). A pilot is Level 3 to Level 4: integration contracts, data boundary and a bounded cohort are agreed with an operator.
The data an offer needs, and where it stays
The minimum each offer names, in the shape of its own template — for instance three ledgers and the known differences. Your data stays with the system that owns it; the public demonstrations run on demonstration data, and your own data enters only when an entitled member of your organisation loads it.
A demonstration, and its limits
The view a demonstration opens, the data it runs on, and the proof it does and does not give.
A demonstration, defined
An offer's decision logic run end to end on demonstration data — Kenya, in KES and Kiswahili unless you configure another market — including the cases it declines and the cases it cannot complete, with the result computed live on the page. The offer page, the demonstration and the workspace run the same logic, so they agree.
The data a demonstration runs on
The public demonstrations run on demonstration data. Your own data is loaded only by a member of your organisation with a verified work email and the entitlement for that offer, inside the workspace, where a second person checks the first's proposal.
The limits of a demonstration
A demonstration is not a pilot, an integration or production. It proves that the decision logic runs and stops where it should; the proof about your systems, your data and your outcomes comes from a pilot.
Production use today
Every offer stands at Level 2 of 5; pilots on an operator's own systems are the next step, and the first client engagement will be reported here when it exists. Ten delivery pods are defined and ready to be scoped.
22 words, each meaning one thing on this site.
Every definition names the page where the word is used.
- Offer
- One of the ten things you can buy: a buyer, a decision it makes, a measured outcome and a level. The ten offers
- Canonical product
- One of the sixteen products the offers are built from, each stating how far it has been taken and what proves it. Products
- Stream
- One of the thirty families of the catalogue, in five areas. Streams
- Definition
- One entry of the catalogue: a decision pattern with its buyer, data, authority and stop conditions. A definition is not a built product. Every definition
- Outcome
- One of the six business results an offer carries or serves. Outcomes
- Level
- Where an offer or product is today, 1 to 5. Level 2: a journey runs end to end on sample data, including its refusal and failure states. Every offer, with its level
- Signal
- A relevant customer, commercial or operational event that may deserve a response. Held by your systems. The seven steps
- Options
- The controlled step that ranks an action, its alternatives and no action. Held by heuriTel. The seven steps
- Limits
- The checks that decide whether the proposed action is allowed to continue. Held by operator policy. The seven steps
- Consent
- The permitted choice and its exact consequence, deliberately accepted by the customer or an authorised operator. Held by the customer. The seven steps
- Authority
- The charge, entitlement or fulfilment performed by the system that holds the right to perform it. Held by the system of record. The seven steps
- Result
- The declared outcome unit, its cost and the comparator it was measured against. Held by measurement. The seven steps
- Proof
- A replayable receipt linking the source, rule, actor, approval, transaction, outcome and any remedy. Held by evidence. The seven steps
- Maker–checker
- One person proposes and a different person approves; nobody approves their own work. Where your policy requires it, no action executes without the second person. Trust Centre
- Evidence record
- The replayable receipt written for a decision: assignment, execution, receipt, cost, exception, remedy and comparator, reopened as stored. One decision as it is recorded
- Sample
- The demonstration data a public demonstration runs on — Kenya, in KES and Kiswahili unless another market is configured. Demonstrations
- Demonstration
- An offer's decision logic run on demonstration data, including the cases it declines, computed live on the page. Configure a demonstration
- Workspace
- Where a member of an entitled organisation works with their own data, behind a verified work email. Sign in
- Pilot
- A bounded run against an operator's own systems: integration contracts, data boundary and a bounded cohort are agreed with an operator. Request a working session
- Pod
- One of the ten delivery teams the operating model defines, with a duration, a role mix, deliverables and a commercial model. How it is delivered
- Handover
- The end of a pod: code, configuration, runbook, evidence and training transferred to your own owners, accepted against a checklist. How it is delivered
- Connector requirement
- A kind of system an offer reaches — charging, CRM, consent, the network — named in its contract; nothing is assumed that you do not own. Architecture
HeuriTel today.
HeuriTel is the decision layer between customer moments, operator authority and measurable outcomes: it reads context from the systems that own it, ranks safe options including no action, checks limits and consent, lets the system of record execute, and writes a replayable receipt.
The product today
- Ten offers, all at Level 2 of 5.
- Sixteen canonical products across thirty streams.
- Ten delivery pods defined, ready to be scoped.
- Pilots on an operator's own systems are the next step for every offer.
Coming as it happens
Client engagements and their results will be published here as they happen; company details beyond the product — registration, team, offices — follow once confirmed.
The partners a delivery draws on.
Partner agreements will be listed here as they are signed. A consultant, an integrator or an AI partner reads the offers that apply to them on their own page.
- Prime vendors
- Systems integrators
- BSS/OSS/CCaaS vendors
- Local delivery partners
- Operator group functions
For a Consultant / Systems Integrator For an AI / Inference Harness
Every page, by purpose.
Each entry names its kind and its page; a working surface names the access it asks for.
Start here
- Business outcomesSix results, each naming the journeys and products that serve it.Guide
- Find your productFive questions, three to five offers with their reasons, a shortlist you can share.Tool
- Solutions by organisationSeven kinds of organisation: which offers apply to each, and why.Guide
- ScenariosThe situations an operator recognises, each with its readiness and the one action that fits.Guide
- ProductsThe sixteen canonical products, each stating how far it has been taken and what proves it.Register
- StreamsThirty streams in five areas and nine families, each previewing the decision it makes.Catalogue
- Configure a demonstrationYour market, the kind of organisation you are, and optionally whose name it wears.Tool
Reference
- The platformHow the decision layer reads context, decides inside policy and writes evidence.Reference
- ArchitectureHeuriTel as an overlay: what the operator keeps control of, and where the record is kept.Reference
- How it is deliveredThe ninety days, the pod and your own roles, the ten pods with their commercial models, the handover.Reference
- Trust and governanceOne decision as it is recorded, with authority, approval, provenance and remedy read off it.Reference
- DefinitionsEvery definition under every stream, searchable, with stable anchors.Reference
- API consoleThe 45 CAMARA and GSMA Open Gateway entries, arranged the way a developer looks for them.Reference
Working surfaces
- The customer's own screenThe operator-branded experience a decision produces: quote, charge, entitlement, receipt.Customer screen
- Growth CommandDecisions needing attention, with every measure qualified by dataset, period and population.Workspace · Verified work email
- Trust replayA blocked action, the approval it needs and the remedy path, replayed from the record.Workspace · Verified work email
- Use-case builderAssemble a journey from the moment to the evidence, in five stages.Workspace · Verified work email