Most enterprises are discovering the same thing IT leaders now say openly: agents fail not because the models are weak, but because the workflow underneath them was never designed to be operated by anything except a human with tribal knowledge and a browser. The data isn't shaped for machine consumption, the process has undocumented human judgment baked into every third step, and nobody can answer the question that decides everything: what is this agent allowed to do, as whom, and who owns what it produces?
Book the scoping call Read the field guideCan an agent actually consume what this workflow runs on?
What should it read, draft, decide, or execute — and at what temperature?
As whom does it act, with what privileges, accountable to whom?
The agent summarizes, observes, and impresses — on preselected data, with controlled exceptions, under a borrowed login. Nothing has actually moved, so nothing has actually been proven.
The agent performs a defined share of the work — with shaped context, deliberate autonomy per action, its own identity and permission envelope, and an accountability trail that survives an audit.
One workflow, end to end. You pick it — invoice handling, campaign QA, RFP response, customer onboarding, vendor compliance. We map it as it actually runs, not as the process doc claims.
We assess structured and unstructured sources, where knowledge lives only in people's heads or inboxes, and what needs restructuring before an agent can act rather than merely summarize.
Which steps carry human judgment that should stay human, which are mechanical and should move, and where the handoffs break. We redraw the workflow as a human–agent operating model using the Action Heat Ladder: what the agent reads, drafts, decides, and executes — and at what temperature.
The layer everyone skips and the reason most pilots die in security review. Cross-functional workflows need access no single employee has, which means the agent needs its own role, its own privileges, and its own accountability trail. We define the agent's identity, its trust tier, its permission envelope, and the authorship layer that makes its output auditable. Agents can't keep things secure on their own — the architecture around them has to.
The workflow's current state versus its agent-ready state — where operability breaks, layer by layer, attached to specific steps.
What the agent can consume today, what's trapped in tribal knowledge, and a prioritized fix list tied to the actions being delegated — not a generic cleanup backlog.
The workflow redrawn: what the agent reads, drafts, decides, and executes, at what heat, with which approvals — and where humans stay load-bearing.
The one-page operating contract defining the agent's role, trust tier, permission envelope, escalation paths, and review lifecycle — the artifact security review actually wants to see.
An evidence-backed decision with a scoped implementation path. "Wait" is a legitimate answer — it means not funding a pilot whose constraints are already visible.
Delivered as a working session with your IT and business owners — not a PDF that dies in a drive.
Fixes are prioritized against the delegation case — the smallest shaping work that makes the action safe, not a multi-year transformation.
One workflow, mapped as it actually runs. Operability lives at the level where work happens — not in an enterprise-wide readiness claim.
It's the diagnostic that tells you whether the pilot you're about to fund will survive contact with your permissions model — before you spend two quarters finding out.
If the workflow turns out to be agent-ready, you'll know exactly why. If it isn't, you'll have the shortest path to making it so — with the gaps tied to specific actions and the owner for each fix. Either way, you leave with the first reusable piece of your delegation architecture.
The Agent-Operable Enterprise — the free field guide behind this audit — covers the full three-layer model, the Action Heat Ladder, the Agent Identity Card, the permissions problem, headless vendor readiness, the 90-day path, and the scored 42-item self-assessment. We give away most of the methodology deliberately: the value isn't knowing the steps exist. It's running them with rigor and cross-functional accountability.
Each auxfirst audit answers one question with evidence. This one asks whether your workflow is ready. Its siblings ask about your agent — and about your brand.
Invoice handling, campaign QA, RFP response, customer onboarding, vendor compliance — or the one that's been stuck in "pilot" for two quarters. Book the scoping call and bring the workflow's owner if you can.
Book the scoping callIn the message, mention "Agent Operability Audit" plus the workflow you have in mind — that's all we need to scope it.
Audits are led personally by Emil Krzemiński, founder of auxfirst, the agentic experience design agency — and author of The Agent-Operable Enterprise, the field guide this audit runs with rigor. Read the launch note: What is agent operability — and why your enterprise needs it.