AI Readiness Audit: two weeks to find where AI fits your operations

$3,500 · Start here

Two weeks, one or two of your workflows, a fixed $3,500. I map how the work really moves, check whether your data, permissions and tooling can carry an AI step, and rank the gaps by value and effort. You finish with a single recommended build and its price, or a clear reason not to build yet.

Key takeaways

  • The fee is credited in full against a deployment that starts within 90 days, so the audit costs nothing extra if you go ahead.
  • Permissions get checked before anything else, because retrieval that ignores them is one of the quickest ways an AI pilot exposes data it should not.
  • A "not yet" is a valid result: if a configuration change or an existing app solves the problem, the report says so.

What gets checked in two weeks

Each audit covers the same five areas, applied to the workflows you pick:

  1. The process as it runs. Who starts it, who touches it, where it waits, where people work around the system.
  2. Data. Where the inputs live, how clean the fields are, and whether an agent could find what it needs without guessing.
  3. Permissions. Who can see what, and how those rules would carry into an AI that retrieves or acts on their behalf.
  4. Tooling and automation. What is already automated, who owns each rule, and what breaks if one changes.
  5. AI already in use. Assistants, plugins and side projects people adopted on their own, and what they can reach.

The two weeks, day by day

Days 1 and 2
Kickoff with the process owner, read-only access through accounts you control, and the list of people to talk to.
Days 3 to 6
Short sessions with the people who do the work, then a process map of each workflow, including the workarounds.
Days 7 and 8
The readiness check: data, permissions, automation ownership and audit logging, tested in your systems rather than asked about.
Day 9
Gaps ranked by value and feasibility, with one recommended build scoped and priced.
Day 10
A readout with the process owner and whoever signs off budget. You keep the report whatever you decide.

What the report contains

The deliverable is a written report you can forward to whoever has to approve the next step, without me in the room:

  • A process map for each workflow, marked where AI would change the work and where it would not.
  • The gap list, ranked by value and by feasibility, each gap with the evidence behind it.
  • A readiness verdict on data, permissions and tooling, with the fixes that come first.
  • One recommended build: what it does, which systems it touches, what stays human, a fixed price and a timeline.

Proof from AI work already shipped

Two recent builds started exactly where an audit starts, with the process rather than the model:

Auditlab

70 h/month

of audit work saved, with full traceability built into the audit

Audit · plain-language queries over accounting exports, answered inside Jira

Read the case

Leathwaite

5 h/week

saved, and the Excel process it ran on replaced

Professional services · two Forge apps, one feeding Jira automation

Read the case

At Auditlab the engine reads accounting database exports, works out their structure, loads them into a queryable database and answers plain-language questions inside Jira, converting each one to SQL. It never trains on the data, never gets full direct access to the tables, and confirms complex queries with the auditor before running them.

Price, credit and payment

AI Readiness Audit

$3,500 USD, fixed

2 weeks. Credited in full against a Deployment that starts within 90 days. Invoiced after a short scoping call; pay by card through Paddle or by bank transfer.

The audit is invoiced after a short scoping call, once we have agreed which workflows it covers. If you already run on Jira, the Jira version of the audit lists the extra checks it adds.

When an audit is the wrong purchase

Skip the audit if you already know the exact build you want and only need hands to make it; a fixed-price Systems project is cheaper. Skip it as well if nobody on your side can own the process for two weeks, because the map would be guesswork. People searching for an AI implementation consultant or an AI automation consultant often need one of those two instead, and I will say so on the call.

Questions

Is the audit fee really credited?
Yes. The full $3,500 comes off the price of a deployment that starts within 90 days of the readout.
How much of our time does it take?
About two hours from the process owner in week one, short sessions with the people who do the work, and the readout on day 10.
Do you need admin access?
No. Read access through an account you create and control is enough for almost every check, and you can revoke it the day the audit ends.
What if the answer is that we should not use AI?
Then the report says so and names what to fix instead. A configuration change that makes an AI build unnecessary is a good outcome, not a failed audit.

Book a 30-minute call. We pick the workflows, and you get the scope and the invoice the same week.

2 weeks

$3,500 fixed

Book a call

About the author

Ben Friedman runs Viter, a forward-deployed AI engineering service. He has spent over ten years running Atlassian and operations tooling, including as internal Jira lead at Aroundtown, and holds the ACP-610, ACP-620 and ACP-120 certifications. He builds JAMES, the AI Jira administrator.