Skip to content
All articles
AI6 min read

What Actually Happens in an AI Readiness Audit (And What To Demand)

Most AI consultants will sell you a $12K 6-week audit that ends with a PDF concluding 'AI isn't ready for your industry yet.' That's a robbery. Here is what an AI Readiness Audit should actually deliver and how to evaluate any vendor's audit before signing.

The Trap

The dominant pattern for AI consulting in 2025-2026 looked like this:

  1. Pay $12,000.
  2. Wait 6 weeks.
  3. Receive a 40-page PDF.
  4. PDF concludes that AI implementation will require another $200,000 engagement.
  5. Repeat with next consultant when you don't sign.

This is not an audit. It is a sales mechanism dressed up as discovery. Real audits look different.

What An Audit Should Deliver

A proper AI Readiness Audit produces four things, not one.

1. A workflow audit.

Plain English. 5-10 pages. Maps your actual operations. Names which steps take the most time, which produce the most errors, which depend on tribal knowledge. No buzzwords.

2. A prioritized opportunity roadmap.

A ranked list of where AI fits. Each opportunity includes:

  • The specific workflow it addresses
  • Estimated impact (hours saved, errors reduced, revenue lifted)
  • Estimated build cost
  • Estimated ongoing operations cost
  • Payback window
  • Build complexity (low/medium/high)

If the audit doesn't have estimated dollars, it isn't an audit. It's brochure copy.

3. ROI projections that can survive scrutiny.

For the top 3 opportunities, the audit should include a model showing:

  • Current cost (time × loaded rate, plus error cost where applicable)
  • Projected cost post-implementation
  • Implementation cost (one-time + ongoing)
  • Net cash flow by month for 24 months
  • Sensitivity analysis (what if savings are only 50% of projected?)

This is the difference between "AI might help" and "implementing this specific capability will pay back in month 9 assuming 25% adoption."

4. A working demo on your real data.

Non-negotiable. The audit should end with a functioning prototype of one AI capability running on your actual operational data (or a sample with PII scrubbed). Not a slide showing what it would look like. The real thing.

If the audit ends with a slide deck, you got a brochure, not an audit.

What To Demand From Any Vendor

Before signing any audit engagement, demand:

  • Fixed scope and fixed price. No "we'll see what we find" pricing.
  • One to two week duration max. Anything longer is a sales process disguised as work.
  • The four deliverables above, named explicitly in the SOW.
  • The working demo, named explicitly with the data source identified.
  • An audit-to-build credit policy. If you continue to a build engagement, the audit cost should credit to it. (This is how we structure it at Kastling: the audit credits to your first Project within 60 days.)
  • IP transfer on the audit deliverables. Including the demo code.
  • A signed disclaimer that the audit is a real deliverable on its own. You should be able to take the roadmap and ship the work yourself if you choose.

Red Flags

  • "Audit starts at $50K." (Too expensive. This is a discovery process in disguise.)
  • "8-12 weeks for the audit." (Too long. The work doesn't take that long.)
  • "We don't do demos in the audit." (Then it's not a real audit.)
  • "We can't share past audits because of NDAs." (Sometimes true. Push for anonymized examples.)
  • "We don't quote prices for the build until after the audit." (Reasonable. But you should get rough ranges in the audit deliverables.)

What The Audit Looks Like

For context, our audit at Kastling is structured like this:

  • Day 1-2: Workflow + tech stack interview. We map current operations.
  • Day 3-5: Opportunity scoring and ROI modeling. We rank the top 5 opportunities.
  • Day 6-8: Working demo build. We pick the highest-ROI quick win and build it on your data.
  • Day 9-10: Roadmap drafting and 90-minute walkthrough call. You leave with everything.

Total duration: 10 business days. The audit credits to your first Project if you convert within 60 days.

This is not a marketing pitch. It is what the audit literally is. If you want to vet us specifically, the methodology page has the seven principles every engagement signs.

What To Do Right Now

If you've been quoted $12K+ for an "AI Readiness Audit" that doesn't include a working demo:

  • Push back on the price
  • Push back on the scope
  • Push back on the timeline
  • Ask explicitly for the working demo as a contractual deliverable

If they won't budge, walk. A proper audit exists. Don't pay for a slide deck.

If you want to start with the Kastling audit, the link goes to the audit details.

Start an audit

Tell us what you are building. We will tell you if we can help.

A brief takes three minutes. We read every one. If there is a fit, you hear back within one business day with a scope call and a proposal. If there is not, we say so and point you somewhere better.

Email the team
Code in your repoEvals as the contractModel-agnosticNo token arbitrageIP yours at the end