consulting / agentic-readiness-audit
Agentic Readiness Audit — Scope & Deliverables
The front-door engagement: a structured audit of everything agents will touch, before they touch it.
The topical background — what the discipline covers and why — is at AI Production Readiness Audit. This page is the engagement.
Best fit
- A pilot worked; leadership wants production; engineering is not sure it is safe.
- Agents already run internally (coding agents especially) and nobody has audited what they can reach.
- A customer or partner is asking the security questions and the honest answers are uncomfortable.
Scope — what is reviewed
| Area | The question answered |
|---|---|
| Architecture | What are the agents, boundaries, and blast radii? |
| Agent permissions | What may each agent read, write, call, and spend? |
| Tool & MCP access | What happens when each tool misbehaves? |
| Secrets | What could an agent — or a prompt injection — exfiltrate? |
| CI/CD | How does AI-written code reach production, and who stops it? |
| Model dependencies | What breaks on a provider change? |
| Context & memory | What do agents remember, and who can read it? |
| Observability | Can anyone answer "what did the agents do last night"? |
| Rollback | An agent broke it — now what? |
| Human approval | Which actions require a human, enforced by what? |
| Cost controls | Where are the ceilings, and what hits them first? |
| Failure modes | Retry storms, silent loops, context poisoning — contained how? |
Deliverables
- Architecture findings — where the system is thin, ranked by blast radius.
- Risk matrix — likelihood × damage, actionable by your leadership.
- Production readiness score — criteria-backed and re-runnable after remediation.
- Prioritized remediation plan — what to fix first, with the reasoning attached.
- 30/60/90-day roadmap — remediation sequenced into engineering-sized steps.
How it runs
Read access to the repos, configs, and pipeline in question; a kickoff session; then the audit itself, then a findings walk-through with your engineers and (usually) a separate leadership read-out of the same findings in different words. Remediation can follow under the stabilization engagement when wanted.
Engagements are scoped by quote after a short call — the shape above is the shape, the size depends on your system. Start with a deep dive or email directly.