Our approach · working agentically

Orchestration is an organisational question.

New platforms that string processes together arrive every month. We are doing something else. We work on the question underneath: how do you get an organisation of agents to actually finish work, at a quality you would put your name to, without losing control of it.

noxilla governancerunning
One decision through the organisationlive
Role with its own domainpreparesactive
Own knowledge consultedits own sources onlyactive
Challengesecond agent refutesverification
The boundaryfixed in place, not in the brief
Inside its domainthe role decidesautonomous
Going outsidecustomer, money, namehuman approval
Autonomous inside the boundaryand that boundary is enforced, not agreed
The distinction

Automation is about speed. We are about decision quality.

That difference sounds subtle and is not. It determines what you build, what you measure and where you stop.

What orchestration usually means

A chain of steps you map out in advance. The AI fills in the steps, the whole thing gets faster and cheaper, and the outcome is only as good as the chain somebody designed. Valuable work, and we do it too. But it is a workflow, not an organisation.

What we mean by it

Roles that are handed a piece of the business and decide within it. Not because autonomy sounds impressive, but because work that waits for a human after every step is not work you have handed over. So the question is not how fast it runs, but how much of it can safely run without you.

Built ourselves

Anyone can switch agents on. That is not what we do.

There are popular open platforms you can have running as a hosted version within the hour, for a few tenners a month. Fine to experiment with, and exactly what it is: agents that run. What it does not come with is an organisation that finishes work, and that happens to be the hard part.

What a few clicks gets you

Agents that start, tasks that run and a demo that impresses. The layer deciding what an agent may do usually sits inside the agent's own instructions there. That reads nicely and it does not hold: in the public vulnerability records of these platforms, that very approval layer has been bypassed more than once.

Why we built it ourselves

Because the part that matters was not for sale. Authority that sits beyond the agent's reach, knowledge that stays separated per role, a handover that does not quietly go stale, and a learning loop that produces better context every day. The individual parts we simply buy in wherever the market does them well. The layer that decides, we build and govern ourselves.

What we steer on

Four principles that shape everything we build.

They sound obvious. In practice, almost every agent project comes apart on at least one of them.

1. Authority does not come from the brief

Most systems tell an agent in its instructions what it may and may not do. That is a request, not a boundary: language can be argued with, and an agent fed the wrong input will talk its way around it. With us, which tools belong to which kind of work is fixed in the layer beneath the agent. It cannot widen that boundary, not even when it believes it should.

2. Verification beats deliberation

It is tempting to have agents meet, the way people do. The catch is that agents on the same model agree with each other quickly, so you get more conviction without more truth. What does work is someone trying to refute what is on the table, on the basis of something the first one never saw. We build challenge, not layers of meetings.

3. Every role its own knowledge

Two agents with the same information are the same agent. A role only becomes a voice of its own once it holds something the others do not: different documents, different sources, different tools, a different number it is judged on. A title or a personality description does nothing. That is why most of our attention goes into separating knowledge, not into drawing an org chart.

4. Going outside goes past a human

Inside its domain a role decides for itself, and that is the entire point. But anything touching your customers, your money, your name or your legal position stops at a human first. That is not temporary caution we remove later. It is the reason the rest is allowed to be autonomous.

The bottleneck

Agents talk fine. They hand over badly.

When something goes wrong in an AI organisation, it is almost never an agent reasoning badly. It is the state of play not being passed on: someone starts work that is already finished, a decision gets made on an outdated picture, or a result sits somewhere without anyone acting on it.

In a real company most communication is not deliberation either, it is handover: who is doing what, where things stand, what has already been decided. That is exactly the part agent systems skip, because it is dull and does not demo well. We have made it the heart of our work and we develop on it continuously.

  • State comes from the source, not from a summary someone once wrote
  • A handover also names what the next one must NOT assume
  • Limits on how much may be open at once, because everything open goes stale
Who is doing whatrecorded
What has been decidedrecorded
What is ready and waitingrecorded
What you must not assumerecorded
Reading state out of a narrative
Deciding inside its own domain
Finishing work itself
Visible in the record
A way back exists
Touching customer, money, name or law
The safe environment

Letting agents decide requires a hard floor first.

It sounds contradictory, but the reason our agents genuinely get to decide something is that the environment beneath them is strict. What a role may do is fixed and cannot be widened by a good argument. Every action can be traced back to who took it and why. For anything with consequences, there is a way back.

Without that floor you have two bad options: approve everything, in which case you have handed over nothing, or let go and hope. We build the third.

  • Boundaries sit beyond the agent's own reach
  • Every decision traceable, every intervention reversible
  • Failures fall over loudly instead of running on quietly
Where our thinking comes from

More than twenty years of building companies sits in the design.

What we add to an AI organisation does not come from the AI world. It comes from more than twenty years of setting up companies and getting teams to work together. The questions there are exactly the same: who owns what, who needs which information, where does a handover break, and when is something done.

The answers do differ, and that is the interesting part. What works for people often does not work for agents. We test that piece by piece rather than redrawing an org chart, and we keep only what survives.

  • What transfers: specialising on a domain, appointed challenge, separation of duties
  • What does not: rank as a source of quality, seniority, rotating people around
  • Every choice tested against what measurably changes, not against what sounds sensible
During the day: work, outcomes, correctionsrecorded
End of day: distilled into knowledgeconsolidated
Next morning: every role starts sharperbriefing
Knowledge stays separated per role
Quietly losing yesterday
Honest about where we are

We are not finished with this, and that is the point.

This is not a finished product we unleash on you. It is a line of work we push on every week, first inside our own company and then with clients heading the same way.

Running a whole company without people is beyond everyone today. In the best known independent measurement on real office work, the strongest model finishes about a third of the tasks on its own. That holds for the entire market, so it holds for us too. Anyone promising otherwise is selling you something.

First
on ourselves, on our own brands
Then
with clients making the same choice
Measured
on work actually finished, not on activity
Never
removing a gate to make it look faster
Who this is for

Companies making the choice deliberately.

Working agentically is not a tool you add on the side. It changes who in your company takes which decision. That only works when it is a choice rather than an experiment parked at the edge.

You want to genuinely hand work over

Not clicking through faster, but tasks that finish without you. That takes trust in the boundaries, and that is where the conversation starts.

Quality outweighs volume

Ten good outcomes are worth more than a thousand mediocre ones. Steer on counts and counts are what you get.

You work in an environment that demands it

Traceability, ways back and separation of data are not an afterthought. With us they sit in the foundation, not in a later project.

Up for a conversation that goes beyond a demo?

Tell us what keeps piling up at your end. We will tell you honestly whether this is built for it, and where the limit sits on what can responsibly run today.