What the platform actually does.
Not a chat window with a consulting veneer. A model of your IT estate, a fixed analysis pipeline over it, and a result whose reasoning you can read back.
The estate is the foundation
Everything the analysis claims is anchored to an element of this model. Without an estate there is no statement, only an opinion.
Applications
Your application estate with technology, hosting, criticality and dependencies. From documents, questionnaires, or a catalogue you already maintain.
Capabilities
What your organisation is able to do, linked to the applications that carry it. Industry catalogues provide the starting point; you sharpen it.
Processes
A process map down to execution level, linked to capabilities and applications — the bridge between what gets done and what it is done with.
Classification
Protection requirements, data classes and regulatory scope per element. This grading reaches all the way into the recommendation: it helps decide whether a workload may move at all.
A pipeline, not a prompt
Every module carries a fixed sequence. The steps are named, their outputs are schema-bound, and none of them sees more data than it needs.
How an analysis runs
capture & classify
targeted, not exhaustive
every element on its own
from findings to a picture
findings fed back in
ranges, not point values
three horizons
document or tool
What you end up with
Not a deck, but a reasoned position you can keep working from.
A disposition per element
For every application, capability or process a decision — keep, renew, replace, relocate — with the reasoning next to it.
Target state
The intended state, derived from the individual decisions rather than placed beside them.
Roadmap & actions
Prioritised initiatives across three horizons, with dependencies, effort and ownership.
Business case
Economics as a distribution, including the drivers that move the outcome most.
Structured data
Every output is validated against a schema — queryable, comparable and machine-processable, not merely readable.
Chain of evidence
From the recommendation back to the assessment, the answer, and the document it came from.
Operations, sovereignty and security
The platform comes to your data, not the other way round.
In your infrastructure
You receive a package you operate yourself: database, application and workers all run on your side. We host nothing and have no access to your projects.
Your model keys
AI calls run through your own accounts with the provider, under your contract. Which provider that is, is your choice — the platform works with several.
Frozen versions
A published module version does not change again. A project is pinned to the version it started with — further development reaches it only when you move it.
Tenant separation
Projects, documents and results are separated per tenant, with role-based permissions and a record of who changed what.
Hardened administration
Platform administration has its own sign-in, and two-factor authentication there is not optional but a precondition for every action.
AI that can be switched off
A per-tenant switch halts every model call — for maintenance windows, budget limits, or an audit in progress.
And the modules?
The mechanism described here is the same in all 15 modules. What differs is the dimensions the assessment runs along, and the decision it leads to.
Let's talk about your estate.
We'll show you on one of your own topics how far the analysis carries — and what it needs.