Inland Revenue · Te Tari Taake

Sign in

Access is limited to Tilicho Labs and named partners.

Indicative planning estimate · not measured results
Inland Revenue · Te Tari Taake
What this is

A financial model for AI at Inland Revenue.

Pick a business area and the work it needs doing, and this prices it three ways: build it alone, adopt a build that already works, or join a shared service. The workloads are drawn from Inland Revenue's own published statements about its use of AI, priced against 3,895 systems four governments have published.

Business areas and their work

Start from the part of Inland Revenue you run

Each business area has a handful of workloads that come up again and again. Pick the one you recognise and the model opens on it, already set up — volume, time saved and the closest published systems.

The underlying tasks

Most government agents are built from the same fifteen tasks

Whatever a system is called, underneath it is doing one of a short list of jobs — reading documents, answering questions, sorting a queue, checking a claim. The same handful turn up inside almost every government agent, which is why they are worth building once. Pick one to see every published system doing that job, and what it costs.

See all patterns ›
Evidence base

AI systems in operation across four governments

Download the data

The full case base and the current selection, as they sit behind this page. CSV opens in Excel or Sheets.

← Back to all systems
System

How this system was classified

The pattern is read from the published description. Complexity and replication follow from the pattern, and together they set the cost model below.

Indicative cost

Demand & value

Model & token pricing

Annual running cost

Decomposed on the FinOps cost schema. Confidence reflects the strength of the source, not the precision of the figure.

How the build cost is derived

Both routes are priced the same way: people × months × working days × day rate. Nothing here is a constant — change any figure and the totals move with it.

LineWorkingAmount
Delivery day rate per day blended across roles
One person-month working days × the day rate
Shared model · first build people months
Conventional · delivery people months
Conventional · RFP and contracting people months
Conventional · totaldelivery plus procurement
Each agency after the first % reusable % reuse factor % local adaptation
Shared model · annual maintenance % of build a year % shared agencies
Conventional · annual support % of build a year per agency

Procurement options

Setup cost across 10 agencies

Under conventional procurement each agency funds a full build. Under the shared model the first build produces a reusable pattern which subsequent agencies inherit.

Traditional, per agencyFactory, per agency

Basis of estimate

← Home
Model a workload

What would this cost your business area?

Three steps. Pick the business area, pick the work, and see what it costs to build alone, adopt a build that already works, or join a shared service.

← Home
Analysis

Recurring patterns

Classified by the function the system performs, the case base reduces to a small number of recurring patterns. Cross-agency reach indicates replication potential: the more agencies already running a pattern, the lower the expected cost of each subsequent build. Select a pattern to carry it into the cost model.

Reach is the share of agencies across all four countries running at least one case of the pattern. Case counts come from what the governments published. Complexity class and replication character are Tilicho classifications applied to the observed pattern.

← Home
Assumptions

Basis of estimate

The calculation is set out below in four stages, using the parameters currently selected in the cost model. Adjusting any input there updates these figures. Each input is stated with its source and an assessment of confidence.

1 · Addressable demand

Total task volume is reduced at three stages: suitability for automation, staff take-up, and acceptance of the output. Benefit accrues only at the final stage.

2 · Unit running cost

Full annual running cost by layer. Token charges are one component of seven.

3 · Build and replication cost

The lead agency funds the initial build. Subsequent agencies fund adaptation only, at a proportion determined by the replication factor.

4 · Basis and confidence

Case counts and token prices are published and verifiable. Delivery and volume figures are planning estimates and should be substituted with agency data before commitment.

← Home
Precedent

Comparable programmes and published evidence

Shared government AI platforms elsewhere, assessed against the same architecture. Only elements confirmed by a government, audit-office, parliamentary, intergovernmental or peer-reviewed source are recorded. Where a figure is not published in such a source, that is stated rather than estimated.

Closest comparable programmes

Ranked by how much of the architecture is confirmed in a qualifying source, not by size or ambition.

The clearest instance of build once, adopt many

One programme in the survey publishes both an adopter count and a before-and-after time measurement.

Published funding and cost figures

The complete set of platform cost and funding figures located in qualifying sources.

What no government publishes

Metrics sought across ten jurisdictions and seven enterprise programmes, and whether any qualifying source reports them.

Implications for programme design