How agentic process specification works in practice
Our method rests on one principle: a process can be automated only once it has been described precisely enough. That is why the work always starts with specification, not with a technology choice. In a specification workshop, the people who run the process describe their own work; our platform turns the description into a machine-readable specification; and human approval points and reviews are built into the spec before a single line of implementation exists. You choose the implementer: your own team, a partner of your choice, or us. Finally, we verify that the implementation in production matches the specification.
The specification workshop makes hands-on expertise visible
The people who know a process best are the ones who run it daily. In the workshop they describe their workflow step by step, and our platform structures the description into a model as they go: a process decomposes into workflows, workflows into agents, and agents into technical tasks. Participation requires no technical skills. Being able to explain how the work is done is enough.
The machine-readable specification is technology-independent
The workshop produces a specification that states unambiguously what each agent must do, where its data comes from, where it goes, and under what conditions a step counts as done. The specification binds you to no platform or vendor, and it is the client's property. Process diagrams, work instructions and the implementation baseline are generated from the same source, so documentation cannot drift away from what the system actually does.
The human is in the structure, not in an appendix
Approval points are designed into every process before implementation: where a human reviews, approves or decides. A significant share of the steps in an agentic process are deterministic tools and human tasks, not language-model calls. This is a deliberate design choice: it keeps the process predictable, the costs controlled and the responsibility with people.
Reviews and an auditable trail
The specification advances to production through review gates that check coverage, risk classification and the sufficiency of approval points. A running process produces a trail showing what was done, who approved it and which version of the specification the implementation is based on. Compliance documentation (including foundations for EU AI Act assessments and ISO 42001 work) is a by-product of specification, not a separate project.
The delivery model states who builds and owns what
Delivery divides into four layers: the specification platform, process building, the runtime environment, and cloud, security and compliance architecture. Typically we supply all layers at the start and hand them over as the client matures.
Explore our insights
Our insights explain what durable, auditable agentic AI is built on.
Frequently asked questions
Q:Do we need to have chosen an AI platform before starting?
No. The specification is technology-independent, and the platform decision is best made once you know what you are building.
Q:Our processes are not documented. Is that a problem?
No, it is the starting point. The specification workshop exists precisely to capture undocumented work.
Q:Does this replace our current IT partner?
No. We specify and verify; the implementer can be your current partner, your own team or us. A clear division of roles usually improves the partner's output.
Q:How long does specifying one process take?
A single workflow typically goes from workshop to a production-ready specification in weeks, not months. The exact duration depends on the scope, and we estimate it in the discovery call.
Q:Where is our data?
In your runtime environment, on your cloud accounts. The specification platform handles process descriptions, not production data.