Skip to content
HeuriTel
Sign in
A cross-functional team around a table mid-discussion.

We run your value-management engine and prove what it earned, with your team in the approval loop.

Operators run many campaigns and cannot separate what earned money from what would have happened anyway; CVM skills are scarce.

Demonstration availableLevel 2 of 5 — A journey runs end to end on sample data, including its refusal and failure states. Bought by CVM and Commercial director. Nothing here has run against an operator system.

Open the demonstration

A team around a table — the kind of CVM review the measurement is for. The campaigns here are the sample's; nothing was sent.

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

1 of 2 campaigns measured on a trusted holdout; incremental value 722 KES after contact cost; 1 contaminated holdout subscriber(s) excluded.

HeuriTel default synthetic sample — Kenya, in KES, Kiswahili; sample campaign-incrementality-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 campaigns — Campaignsrows on the Campaigns sheet
  • 1 campaigns — Measured on a trusted holdoutholdout at or above the campaign's own guardrail after contamination is excluded
  • 722 KES — Incremental value (trusted)uplift in spend per subscriber × treated, minus contact cost, over trusted campaigns
  • 1 subscribers — Contaminated holdoutsholdout subscribers a contact reached

Continue Data top-up nudge (incremental 722 KES after contact cost); Re-run Lapsed win-back with a holdout of at least 20 % before deciding. If nobody acts: Every campaign continues as budgeted, with its value claimed from the treatment arm alone and nothing held out to say what would have happened anyway. No contact was sent. No campaign was started, paused or stopped. No subscriber was moved between arms.

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 nowWe run your value-management engine and prove what it earned, with your team in the approval loop.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 nowcohort, campaigns and responses as three sheets: every subscriber is in one arm (treatment or holdout) of one campaign; responses name a subscriber in the cohort; contamination — a holdout subscriber with a treatment contact — is an exception. 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/campaign-incrementality/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 workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
  6. 07 · EvidenceEntitled workspaceincremental value per campaign with its holdout; guardrail and contamination checks; campaign decision record; 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: an agreed holdout design on operator data; a signed measurement method. 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 across CRM, campaign management, billing or revenue mart, data warehouse; 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: incremental margin against the revenue mart; contacts against the campaign system's send log. 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
Managed CVM and Experimentation
Buyer
CVM and Commercial director
Problem
Operators run many campaigns and cannot separate what earned money from what would have happened anyway; CVM skills are scarce.
Outcome a pilot would count
Incremental margin against a held-out group.
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 campaign-incrementality-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
Campaigns (campaign_id, name, objective, contact_cost, minimum_holdout_pct); Cohort (assignment_id, campaign_id, subscriber_ref, arm, segment); Responses (assignment_id, contacted, responded, spend). cohort, campaigns and responses as three sheets: every subscriber is in one arm (treatment or holdout) of one campaign; responses name a subscriber in the cohort; contamination — a holdout subscriber with a treatment contact — is an exception. 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 incrementality v1, on the public sample: 1 of 2 campaigns measured on a trusted holdout; incremental value 722 KES after contact cost; 1 contaminated holdout subscriber(s) excluded. 4 measures with their basis, 2 sections, 2 exceptions with owners. Recommendation: Continue Data top-up nudge (incremental 722 KES after contact cost); Re-run Lapsed win-back with a holdout of at least 20 % before deciding. If nobody acts: Every campaign continues as budgeted, with its value claimed from the treatment arm alone and nothing held out to say what would have happened anyway. Simulated; nothing ran against an operator system.
Approval model
Maker-checker: the person who accepted the data or requested the run cannot decide its recommendation; a client administrator does. Approval applies to a simulated recommendation.
Evidence
incremental value per campaign with its holdout; guardrail and contamination checks; campaign decision record; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
Pilot requirements
an agreed holdout design on operator data; a signed measurement method. None is evidenced; no pilot is requested or agreed.
Live requirements
Connected under a separate authorisation: CRM, campaign management, billing or revenue mart, data warehouse — none connected; reconciled before any outcome is claimed: incremental margin against the revenue mart; contacts against the campaign system's send log. Not built.

Beneath the offer: Managed CVM and Experimentation, Customer Intelligence, Decisioning and Next Best Action, Journey Activation, Experimentation and Value, Customer Growth & CVM.

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

3 sheets, checked before anything is read from them.

cohort, campaigns and responses as three sheets: every subscriber is in one arm (treatment or holdout) of one campaign; responses name a subscriber in the cohort; contamination — a holdout subscriber with a treatment contact — is an exception. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused and never echoed back.

  • Campaignseach campaign: the offer, what a contact costs, and the smallest holdout share the measurement accepts. Columns: campaign_id, name, objective, contact_cost, minimum_holdout_pct.
  • Cohortevery subscriber in a campaign, in exactly one arm. Columns: assignment_id, campaign_id, subscriber_ref, arm, segment.
  • Responseswhat each subscriber did in the measurement window, and whether a contact reached them. Columns: assignment_id, contacted, responded, spend.
A pilot’s measure and prerequisites — 6 things that would have to be true
What a pilot would count, and needs

Incremental margin against a held-out group.

Nothing is counted until it is reconciled against your own records: incremental margin against the revenue mart; contacts against the campaign system's send log.

  • an agreed holdout design on operator data
  • a signed measurement method
  • Connected under authorisation: CRM. Not connected today.
  • Connected under authorisation: campaign management. Not connected today.
  • Connected under authorisation: billing or revenue mart. Not connected today.
  • Connected under authorisation: data warehouse. Not connected today.
Built on 5 governed products and 3 catalogue streams
What it draws on

5 governed products and 3 catalogue streams.

The offer is a commercial view onto the same platform every other offer runs on. Its workbench opens with Managed CVM and Experimentation.