The Trust Ladder: how to onboard AI agents like new colleagues
In this article
What data should we let them access? What if the agent gets it wrong? What holds organisations back is rarely the technology — it's the uncertainty. Think of AI agents as new colleagues and extend their remit one rung at a time, along the Trust Ladder.
What data should we let them access? What if the agent gets it wrong? These are the questions that most often stop organisations from getting started with AI agents. What holds them back is rarely the technology — it's the uncertainty.
Like hiring someone new
An AI agent is like a star intern. Knowledgeable, quick-thinking, eager to help — but with no experience of how your business actually works.
No sensible manager gives an intern full authority on day one. You start with well-defined tasks. You let them show what they can do, then extend their responsibility one rung at a time.
The same logic works for AI agents. The question then isn't which agent should we build? It's what level of responsibility feels reasonable for us today?
The Trust Ladder: four steps
Step 1: Public data, internal use
The agent works with public or synthetic data, and only your team uses it. It reads, summarises, suggests — but accesses nothing sensitive. The risk is minimal, and you learn how agents actually behave.
Example: A competitive intelligence agent that tracks what your competitors are doing and flags changes worth watching.
Step 2: Protected internal data, internal use
Now the intern can read internal documents — but only standardised or anonymised ones. The same GDPR rules and access controls that apply to any employee apply here too. Still internal use. The agent suggests; the human acts.
Example: An HR support agent that answers employees' questions about policies and procedures, drawing on your internal HR documents.
Step 3: Real data, read-only
The agent gets access to real business data, but can't change anything. It reads, analyses, flags — and a human decides what happens next. At this step, the agent can start to be used in customer-facing processes, as long as there's a human in the loop.
Example: A month-end close agent that reads accounting data and flags variances against budget — but the accountant decides what action to take.
Step 4: Real data, the agent acts
The agent gets write access within clear boundaries. This isn't about giving up control — it's about moving it, from each individual decision to the rules and guardrails you set around the agent.
Example: An invoice agent that creates and sends invoices automatically from delivery data, within agreed rules.
Common objections
"We need an AI strategy first."
You don't need an AI strategy to get started. Your first agent project often becomes the start of the strategy, not the result of it. It's hard to build a strategy around something you've never tried.
"What if it makes a mistake?"
That's why you start at step 1. And that's why there's still a human in the loop all the way through step 3. At the lower steps, mistakes are reversible — the agent suggests, you decide.
"We don't have the budget for it."
An agent at step 1 costs less than you think. Often less than a couple of meetings about whether to do it.
The core principle
Trust is built step by step. It's true of new colleagues. It's true of AI agents too. You don't need to know where you're going to take the first step — and the first step is usually less disruptive than it sounds.
Curious which rung you're on today? We'd be glad to talk it through.
