Model your own domains.

The platform in your perimeter, your domains modelled by your own team. Pick the domains you'd model first and see exactly what you'd send, and what your team, your applications and your AI get back. Our private cloud, your private cloud, or on-premise.

Pick your domains.

Click the wheel or the list. A model needs at least two domains, because the answers live in the connections.

What you'd send · sources5
3 to 5 procedures or policies
Handoff and escalation notes
Systems list, an Excel is fine
Schema export, structure only
Code export, optional
How the work runsThe rules that govern itSystems & dataWho owns whatProducts & servicesCustomers & channels2OF 6 DOMAINS1 CONNECTED

click a slice, or use the list

What you'd get · deliverables4
How the work runs, modelled step by step
Where work actually gets stuck
What breaks if we retire this
Systems & data × How the work runsEvery process that touches a table
start with documentation · scale with access1 connection unlocked · one correction propagates to every dependent answer

In your perimeter, and kept true.

In your perimeter
  • The platform itself, one deployable unit
  • Your domains modelled by your own team
  • Every answer carrying the file it came from
What it computes
  • What a change touches, before you make it
  • Whose accountability moves with it
  • Two counts: what is confirmed, and what is still proposed
Kept true
  • Anchored elements flag themselves when reality moves
  • Drift reviews on a cadence
  • The model re-certified each quarter

The roles required from your side.

One sponsor, one owner per domain, two or three of your own specialists in the Studio, and IT once for an export. No steering committee, no workshops.

Your sponsorHolds the second gate: nothing changes a live system without their signature. About half an hour a week.
One owner per domainHolds the first gate, and gives verdicts only. The platform does the reading and the extraction, and brings them decisions to make.
Two or three in the StudioYour own modellers. They train on the first domain with us, then add the next ones without us. This is the role that makes this tier cost less than the one above it.
A handful of contributors"I don't know" is a legitimate answer and gets recorded as one. One routed question at a time, answered in minutes, asynchronously.
Your IT, onceA one-time export. No credentials and no live access, and it reads only what you export.
Our engineer, fractionalDrift, re-certification, and onboarding each new initiative onto the model you already have. Not a seat on your team, a few days a month.
The two gates

The publish boundary is held by a named person: a domain goes live only once published. The per-decision gate requires two signatures, from two different people, before anything changes reality. An AI can never sign its own work.

You keep everything

The model, the exports, the proof, and the modelling skill, which your Studio team keeps whether we are still here or not. Stop whenever you like and it stays yours.

The three plans, side by side.

Same platform underneath. What changes is the scope, the domains that sit in it, who does the modelling and where it runs, and you can move between them as your own team takes more of it on.

Tier 1Consultancy
What it isYour methodology, as a model.
Who models itWe do, for your practice. Your seniors validate the output.
Our peopleWe run the first engagements, then your consultants certify as operators.
Where it runsPer client engagement, under NDA.
What you getDeliverables that generate with evidence attached.
It closes withThe firm's knowledge compounds.
Tier 2Businessyou are here
What it isModel your own domains.
Who models itYour own team, in the Studio.
Our peopleA fractional engineer: drift, re-certification, onboarding.
Where it runsYour perimeter: our private cloud, your private cloud, or on-premise.
What you getYour domains modelled and queryable by your team, apps and AI.
It closes withOne correction improves every answer that leans on it.
Tier 3Enterprise
What it isAny initiative, run on the model.
Who models itYour engineers, embedded with ours.
Our peopleA forward-deployed engineer, embedded for the programme.
Where it runsYour landscape, in waves.
What you getThe transformation map, gated execution, and the work packages that land the change.
It closes withEvery change gated, and auditable while it happens.

Tiers are not module bundles · nothing here is a feature you unlock

Not sure which one is yours?

Answer a few questions and we will tell you. Or hand over your first documents and see for yourself.

Get the fact sheet

This site uses cookies

We use essential cookies for the site to function and analytics cookies (Google Analytics) to understand how you use it. Analytics cookies are only activated with your consent. We do not track you across other websites. Your data is stored in the EU and processed in accordance with GDPR. Read our Privacy Policy