Name the job + decision
Mutual NDA, workflow-owner and systems-owner kickoff, then a map of the current trigger, decisions, actions, exceptions, handoffs, and the build decision this audit must support.
Agentic
Readiness Audit
A five-day audit of one business workflow, its systems, and the evidence needed to make one agent build decision.
- Price
- From $5K
- Working time
- 5 working days
- Unit
- One business workflow
Bring the real workWe inspect the workflow
We inspect the workflow
before we prescribe the agent.
Bring the work as it runs today, the people and systems that own it, representative cases, and the decision you are prepared to make. Across five working days, we trace the job, authority, handoff, acceptance boundary, and operating evidence.
A bounded working sequence
The build decision earns its shape.
Each day resolves a different uncertainty. We do not begin with a preferred vendor, automation rate, or implementation promise.
Trace evidence + authority
Representative cases, source systems, data boundaries, integrations, allowed and prohibited actions, human work, exception paths, and outcome evidence. Code and repositories are reviewed when they are part of the workflow.
Define the build boundary
Accepted intents, required context, tool and credential scope, human handoff, acceptance cases, stop conditions, observability, operating assumptions, and phased implementation options.
Make the decision
A 60-minute readout and one explicit recommendation: proceed, narrow the first release, repair prerequisites, or do not build.
Six views of the same jobNo workflow is ready
No workflow is ready
until its edges are visible.
- Trigger, inputs, decisions, and actions
- Accountable workflow owner
- Systems owner and build decision
A current-workflow map with the owner, handoffs, exceptions, and decision boundary made explicit.
- Systems of record and available APIs
- Required context and data boundaries
- Identity, credentials, and integration constraints
A source-system, data, and integration inventory that separates available access from assumed access.
- Allowed and prohibited actions
- Approval and escalation rules
- Human takeover and recovery path
An authority boundary that states what the agent may do, what it must never do, and when a person takes over.
- Representative successful cases
- Exceptions, refusals, and unsafe actions
- Stop conditions and evidence receipts
An acceptance and stop-case set written before implementation, with missing evidence left visible.
- Outcome, cost, latency, and quality evidence
- Tracing, incident response, and rollback
- Change ownership and support boundary
Operating assumptions and a release path without invented performance or ROI claims.
- Proceed, narrow, repair, or do not build
- Phased scope and USD bands
- First release and acceptance boundary
A decision memo and build brief the buyer can fund, narrow, defer, or reject.
What you receiveA decision dossier.
A decision dossier.
Not a generic roadmap.
You leave with six retained artifacts and a direct recommendation: proceed, narrow the first release, repair prerequisites, or do not build. The fee credits 100% into any build within 30 days.
The audit fee credits 100% into any follow-on engagement signed within 30 days.
One workflow.
One fundable decision.
- 01Current-workflow map
- 02Source-system, data, and integration inventory
- 03Allowed-action, permission, and human-handoff boundary
- 04Representative acceptance, exception, and stop-case set
- 05Agent build brief with operating assumptions and phased USD bands
- 06Decision memo + 60-minute readout
- 0730 days of async Q&A
Three owners, one decisionThe agent belongs in the business,
The agent belongs in the business,
not outside it.
Deciding whether one recurring workflow should become an agent
A build/no-build decision grounded in the real work, systems, exceptions, and ownership.
Accountable for calls, leads, support, content, or internal operations
A clear boundary for what the agent owns, where a person takes over, and how accepted work is judged.
Responsible for the data, APIs, credentials, and production path
An implementable scope with explicit authority, failure controls, observability, and handoff.
The boundary is part of the offer
Questions, answered.
Not in scope
- Enterprise AI strategy or teams without one named workflow
- Multiple workflows or departments (scope separately)
- Implementation (a separate engagement)
- Security penetration testing or compliance certification
- ROI, accuracy, latency, or automation-rate guarantees
Common questions
Start with one workflowMake the build decision
Make the build decision
before the build investment.
We sign a mutual NDA before any source-system, customer, revenue, or code data is shared.
From $5K · 5 working days