Skip to content

Foundation

Data and AI platforms

We test your data first, ground every answer in it, and keep both the data and the model bill under your control.

The data verdict

Every stage 01 ends with a verdict on the data the use case depends on: it supports the case, it does not, or it will once a named problem is fixed. The verdict comes before anyone builds anything. Learning in week three that a key field is filled in a third of the time costs far less than learning it in month four of a build. Industry data shows the same risk: in February 2025 Gartner forecast that through 2026, organisations will abandon 60% of AI projects not supported by AI-ready data, from a global survey of 248 data management leaders.

The Data Readiness Review

When the data is the main risk, stage 01 includes the Data Readiness Review, a fixed-scope diagnostic of 1-3 weeks inside stage 01, not a stage of its own. It scores every source the use case depends on:

DimensionThe question it answers
CompletenessAre the needed fields filled in, across the period and scope that matter?
AccuracyDoes the data match what happened, checked against a sample?
AccessibilityCan the system reach it, legally and technically, with access your IT team will grant?
LineageWhere did each value come from, and what changed it on the way?

You receive a scorecard per source and a remediation plan for anything below the bar, with the fix and a rough effort. We work with the owner of each system of record, because reporting layers built on top often hide the gaps.

Retrieval and grounding

An answer drawn from your documents must show its source.

  • Retrieve when the step needs it, and keep the rest of the context small.
  • Cite or abstain: every answer points to the passage it rests on, and when nothing supports an answer the system says so and hands the question to a person.
  • Quote or discard: in extraction, a claim needs a verbatim quote from the source, or it is thrown away.

Tenderix, our procurement tool, applies quote-or-discard to tender documents in German, French and Italian, and reports a missing score as missing. FoodHalo’s coach looks up nutrition figures through tools against the product database and may not state a figure it did not retrieve.

Anonymise before inference

Many processes contain personal data that the model does not need to see. Our internal build replaces every name, address and identifier with a stable alias before content reaches a model; the same person keeps the same alias within a run, so the model can still reason about who did what. A separate check inspects everything about to leave and fails the run if it finds a value that should have been aliased. The aliases are reversed only at the end, locally, on your side.

Cost-aware routing and budgets per tenant

Each task goes to the cheapest model that passes its evaluation, and budgets are set before the first request.

PatternWhere we built itWhat it does
Tiered modelsA tiered document intelligence pipeline (Working prototype)A stronger model for clause extraction, risk flags and redlining; a cheaper one for summaries and classification
Budgets per tenantThe same pipelineRate limits and budget caps per tenant, enforced before a request reaches the stronger model
Routing across providersA multi-channel AI concierge (In production)Cost-aware routing across model providers, with fallback when one is slow or unavailable
Cost on the dashboardThe same conciergeStaff see estimated cost per channel and the questions customers ask most
Spend per tenantAtrium (Working prototype)Token spend per tenant as a first-class metric

We report cost per completed task: the number that tells you whether the system still pays for itself.

Integration with your systems

  • Start read-only. Write access comes one action at a time, each with its own approval path.
  • Give every connector the smallest scope that does the job.
  • Keep the decision path deterministic where it matters: in kredis, the decision endpoint other systems call reads precomputed state, with no language model in the path.
  • Keep case history append-only, so any past state can be reconstructed.
  • Isolate tenants, with row-level security enforced in the database.

kredis assembles counterparty files from GLEIF, Companies House and embedded OFAC, EU, UK and UN sanctions lists.

In the six stages

StageData and platform work
01 · Ground the caseData verdict; Data Readiness Review where needed; hosting option chosen
02 · Prove the valuePrototype on your data or realistic data; retrieval and grounding tested
03 · Engineer the systemConnectors, anonymisation, routing and budgets for the pilot footprint
05 · Scale what worksIntegrations, capacity and budgets extended across the full scope
06 · Run and evolveCost per task and data drift on the dashboard; quarterly review

Built in the lab

BuildLabelWhat it shows
Anonymise before inferenceInternal buildAliases before any model call, an independent check that fails the run, local rehydration
A tiered document intelligence pipelineWorking prototypeTiered models with rate limits and budget caps per tenant
A multi-channel AI conciergeIn productionCost-aware routing across providers on five channels
A grounded knowledge copilot for field serviceWorking prototypeRetrieval that cites or abstains, and knowledge-base updates a person approves
TenderixLiveQuote-or-discard extraction from tender documents in three languages

Questions

Do we need a data platform before we can start?

No. Stage 01 tells you whether the data you have can carry the use case. Often it can run on the systems of record you already have, read through narrow, read-only access.

What is the difference between the data verdict and the Data Readiness Review?

The verdict is part of every stage 01: a first read on whether the data exists, who owns it and whether anything blocks access. The Data Readiness Review is a deeper diagnostic you commission when the data is the main risk. It scores every source and comes with a remediation plan.

Does the Data Readiness Review fix the data?

No. It tells you what is ready, what is not and what fixing it takes. The remediation is separate work, done by your team, ours or a third party.

How do you keep model costs predictable?

Each task goes to the cheapest model that passes its evaluation, and budgets and rate limits are enforced per tenant before a request reaches a model. Cost per completed task is on the dashboard from day one.

Can the system answer from our documents without making things up?

Retrieval is designed so that an answer cites the passage it came from, and the system abstains when it finds no support. Extraction can be stricter still: a claim without a verbatim quote from the source is discarded.

Start with the verdict

An AI Opportunity Assessment gives you a first read on the data in 1-2 weeks. If the data is the open question, the Data Readiness Review scores every source in 1-3 weeks.

See the AI Opportunity Assessment