THE BUSINESS AI PLAYBOOK
The practical AI readiness audit for business owners
Assess AI readiness across workflows, data, permissions, ownership and economics, then identify the smallest useful pilot your business can support.
Discuss with Oliver and his team 
An AI readiness audit should determine whether your business can support a specific useful workflow, not assign a vague maturity score. Review the process, source data, access permissions, decision authority, staff capacity and expected economics together. Identify the gaps that would stop a pilot from working. Finish with one prioritized opportunity, a named owner, a baseline and explicit conditions for proceeding. Readiness is about execution, not how many AI subscriptions you own.
What to take away
- Assess a real workflow rather than rating the company in the abstract.
- A missing process owner can be a larger obstacle than a missing integration.
- Separate prerequisites from improvements that can wait until after the pilot.
Start with evidence of repeated work
Ask department leads to show recent examples of a process that consumes time or loses opportunities. Measure the number of cases, handling time, exceptions and delays. Observe the work rather than relying only on estimates. Identify where information is copied, interpreted, checked or handed off.
Write the desired outcome in operational terms: reduce incomplete intake, improve response quality or shorten report preparation. Do not begin with a goal such as deploy agents across the company. That describes a technology decision, not the business result that would justify the effort and ongoing responsibility.
Inspect data, access and authority together
Find the authoritative records and determine who may read or change them. Check whether the relevant data is current, consistently structured and accessible through a supported route. Identify personal or sensitive information and the policies that apply to its use.
Then map decisions. Which actions can be automated, which require review and who handles exceptions? A technically accessible system does not imply permission to perform every action within it. Include maintenance ownership, vendor dependencies and what happens if the system stops. NIST’s framework is useful background for organizing risk review, but your audit still needs concrete workflow evidence.
Illustrative audit: a quote follow-up opportunity
Suppose a distributor wants AI to follow up on every open quote. The audit finds that quote status is reliable, but customer replies live in individual inboxes and some salespeople already follow up manually. Launching immediately could create duplicate or contradictory messages.
The first prerequisite is a shared conversation state and clear account ownership. A draft-only assistant can still prepare useful follow-up briefs while that gap is addressed. The pilot success measure becomes timely, accurate follow-up on eligible quotes, with duplicates tracked as failures. The audit has produced a practical sequence rather than a sweeping declaration that the company is not ready.
End with a decision memo and a limited pilot
Summarize the opportunity, evidence, expected value, prerequisites, risks and owner on a page the business can review. Label time savings as estimates until measured. Include implementation cost, review effort and ongoing maintenance in the economics. Decide what would cause the pilot to stop or remain in draft mode.
Prioritize fixes that unlock the chosen workflow. Do not require a company-wide data cleanup when a small approved source set is sufficient. Conversely, do not ignore a material access or quality problem just to start quickly. A good audit narrows uncertainty enough to make the next investment reviewable.
FROM READING TO ACTION
Your first steps
- Choose one repeated workflow and observe representative real cases.
- Record its baseline volume, effort, errors and delays.
- Map authoritative data, permissions, action limits and exception ownership.
- Separate launch prerequisites from later improvements.
- Approve a pilot brief with measurable success and stop conditions.
What to measure
| Measure | How to track it |
|---|---|
| Evidence coverage | Material workflow assumptions supported by observed records divided by assumptions in the pilot brief. |
| Prerequisite closure | Required launch gaps resolved and verified divided by required gaps identified. |
| Pilot ownership coverage | Critical operations and exception paths with named accountable owners divided by critical paths. |
Common questions
Do we need perfect data before starting?
No. You need data good enough for the chosen scope, with known limitations and review where necessary. A narrow pilot can work while broader cleanup continues.
Is an AI readiness score useful?
It can summarize discussion, but it should not hide the reasons behind the rating. Decisions are easier when the audit names specific gaps, owners and actions instead of only presenting a number.
Sources & further reading
These sources provide background. The workflow designs are Palnau Systems implementation guidance; examples are illustrative, not reported client results. Product capabilities and requirements can change.
Prepared with AI assistance for business owners and managers. For a recommendation based on your actual systems and requirements, work directly with Oliver and his team.
