Why now – Palantir alternatives for Europe: what 'sovereign' actually means, and how European public bodies are decidingRegister →
Assessment · one day

Organisational AI Day

Two of our architects, the people who run your operation and the people who own your data and your obligations, and one question: which of your processes are ready to run as Human+AI — people and agents doing the parts each is good at — and what has to be true before they can. You leave with a shortlist of those processes, two of them drawn end to end, and within five business days a written readiness and gap report addressed to a board.

Fixed price
€1,500
Duration
One day, on site or on your video platform
Who it needs
Six to ten people, process owners included

We start from the process rather than from a model, because that is where organisational AI either works or does not. In the AI Operating System a process is a real object: stages, the tasks in each stage, who or what is assigned to each one — a person, an existing system, or an agent — and the gates that have to pass before the next stage opens. Approvals and human judgement are ordinary steps in that flow, not exceptions bolted on afterwards. A day spent finding the two processes where that division of labour actually pays is worth more than a day spent choosing a model.

Intake

1/4
  • Register the request
  • Check it is complete
  • Chase what is missing
Gate · Complete?

Assess

2/4
  • Pull the file and the history
  • Summarise against the rules
  • Judge the edge cases
Gate · Within policy?

Decide

3/4
  • Draft the decision and its reasoning
  • Approve and sign
Gate · Signed?

Close

4/4
  • Notify and file the evidence
  • Spot-check a sample
PersonExisting systemAgent
The anatomy of a process flow: stages, the tasks in each, who or what is assigned to every one, and the gate that has to pass before the next stage opens. Illustrative — by the end of the day two of your processes are drawn this way, with the arguments about which steps stay human written into them.

Sovereignty and regulation run through the whole day, but as constraints on the processes we pick rather than as the subject. If you have just run one of the sovereignty scores, bring the result — it saves us an hour and tells us which options are closed before we start drawing.

Who should be in the room

  • Process, service or operations owners
  • CIO or CTO
  • CISO
  • DPO or legal
  • Whoever owns the AI roadmap
  • One or two architects

Six to ten people, no more. Two or three of them should be people who actually run the work and can say where a case waits and why; the architects are there because they know how the estate is really wired rather than how the diagram says it is. Procurement is welcome in the last hour and not before. If the people who own the processes are not there, the day produces a document instead of a decision.

How the day runs

  1. 09:30

    Where you are

    A short walk through what is already running: sanctioned assistants, the ones nobody approved, models in production, and what all of it touches. We are not here to be impressed or shocked — we are here to write it down.

  2. 10:00

    The process shortlist

    The longest part of the morning. We go through the work your organisation actually does and look for the places where a person is reading, re-keying, chasing, reconciling or waiting rather than deciding — and for the decisions that are made too slowly, too inconsistently, or by whoever happens to be on shift. Each candidate gets scored on three things: the volume and cost of the work today, whether the data and the systems behind it could support it, and what it would mean to get it wrong.

  3. 11:00

    Two processes, drawn

    We take the top two and draw them as process flows: the stages, the tasks in each, who or what does every one, the gates between stages, and the handovers. The interesting argument is always the same one: which steps a human keeps because judgement, accountability or the regulation requires it, and which ones a human is only doing because nobody automated the reading.

  4. 13:30

    What must be true to run them

    Now the constraints, applied to those two flows rather than in the abstract: the five sovereignty tests — jurisdiction, keys, operating staff, disconnected mode and exit — against your estate and your shortlisted vendors, and which obligations under the EU AI Act, NIS2, DORA and GDPR land on these processes, who owns each one, and what evidence you would have to produce if you were asked this quarter.

  5. 15:00

    The target architecture and the sequencing

    On the wall, in front of everyone: what runs where, what data crosses which boundary, what stays in your perimeter, what an air-gapped variant would cost you in convenience — and then which process goes first, what can wait a year, and what should simply be switched off.

  6. 16:30

    Read-back

    We present the conclusions to whoever needs to hear them, including the people who could not spend the day with us.

What you leave with

A ranked shortlist of processes

What they cost you today, what a Human+AI version would change, and what would have to be true for it to run. Including the ones we would leave alone, and why.

Two process flows, drawn end to end

Stages, tasks, what is assigned to a person, to a system or to an agent, and the gates between them.

The five sovereignty tests, scored

Against your current estate and your candidate vendors — including us.

A regulatory mapping

For those processes, in a form you can hand to your DPO or your auditor: obligation, owner, evidence.

A target architecture and a sequencing

What to keep, what to change, what to run where, and in what order.

A recommendation on scale

Whether a six-week pilot is the right next step and, if so, on which process. Sometimes the answer is that you do not need us yet, and we would rather say so on day one than in month six.

What it costs

€1,500
for the day, fixed · both days back to back €2,700
  • Credited in full against a pilot or your first platform year
  • A price, not a rate — it fits a purchase order, not a procurement cycle
  • Travel outside Belgium at cost, agreed up front

The full amount is credited against a pilot or your first year of platform, so evaluating us properly costs nothing if you go ahead. All prices exclude VAT.

Where this sits

  1. 30 minutes
    Organisational AI in 30 Minutes
    Free
  2. One day each
    The assessment days
    €1,500
  3. Six weeks
    The Six-Week Pilot
    €25,000 – €90,000

Above this day is a briefing that costs nothing and is the right start if you are still deciding whether there is anything here for you. Below it is a pilot that proves one process on your data, inside your perimeter. The day exists because most organisations we meet are between those two: past the conversation, not yet able to write down what they would be buying.

The other day
Lakehouse to Ontology in a Day

The same length, the same price, aimed at the data half of the problem — integrating two of your sources, making them discoverable, and turning them into something that means one thing. This day answers which work should we run this way, and what must be true first; that day answers can our data carry it. Run back to back, both days are €2,700. The questionnaire below decides which, on your answers rather than ours.

What we ask before the day

A day is only worth its price when the reading is done beforehand. That is what the questionnaire is: the same ten questions we would otherwise spend the first hour asking, answered in about four minutes. We read the answers, ask for the two or three documents they point at, and arrive with the map half-drawn.

Nothing in it needs to be confidential. If it does become confidential, say so and we will agree a channel — several of our engagements never send an architecture diagram over e-mail at all.

Who runs it

Scrydon's founders and architects have designed and operated sovereign, air-gapped and confidential-compute estates for governments, defence organisations and regulated enterprises. Meet the team.

Tell us where you are

Ten questions, about four minutes. They are the same questions we would ask in the first hour of the day, so answering them now buys that hour back — and the answers decide which of the two days is the right one for you.

1 · What brought you here

What made this urgent?

What is running today?

Tick everything that is true, including the parts nobody signed off on.

Where does the data have to stay?

2 · Your data

Which two systems would you put on the table?optional

Names or descriptions are both fine — “the ERP and the ticketing system” is enough. Leave it empty if you do not know yet.

How reachable — and how trusted — is that data today?

Which process or decision should the day make faster or safer?optional

One piece of work people do repeatedly — approving a claim, releasing a batch, prioritising a repair. On the Organisational AI Day it becomes a process flow; on the data day it is what the ontology gets built around.

3 · Obligations, people and timing

Which obligations are in scope?

Who would be in the room?

When does this have to move?

Anything we should read first?optional

An architecture diagram, a policy, a tender, a vendor shortlist. Do not attach it here — say what exists and we will agree a channel.

What we would propose

Answer a few questions and we will say which day fits — before you ask us for anything.

Who should we reply to?

We only use these details to reply to you and to prepare the day. Privacy policy

A founder or architect reads it and replies within one business day — including “not yet” when a day would not earn its price.