Know whether your business is ready for AI — before you spend a dollar building.

What it is

A diagnostic engagement. We do not write code, train your people, or build AI features during a Readiness review. We examine the underlying business and write what we find.

Most "AI readiness" engagements end with a slide deck and a recommendation to do more work with the same firm. This one ends with a written report you can hand to your board, your investors, or another firm. We are explicit about that up front.

How you control the depth

Most consulting engagements ask for full access up front, then quietly retain it afterwards. We invert that. You grant access on a ladder. Each rung produces a sharper diagnosis; you can stop at any rung. We do not retain access after the engagement ends.

1. Tier 0 — what you can show us externally. Public materials, screenshots, an operator walkthrough you control. We can characterize the surface but not verify the substrate beneath it.
2. Tier 1 — an operator login to your live system. A read-only login at an everyday operator's permission level. We can confirm what the system actually does, page by page, end to end.
3. Tier 2 — source code and your operator issue backlog. Read access to the repository and to the bugs and requests your team has been logging against the system. The backlog is the highest-signal artifact in the engagement — it tells us exactly which problems are real and which are noise.
4. Tier 3 — a database backup. A restored copy of your production database in a private environment we control. Required only if the next step is a transformation; the Readiness review itself can land at Tier 2.

The deliverable is the same shape at every tier — a written report and a decision tree. What changes is how grounded our claims are. We tell you on the intro call which tier we recommend for your situation and why.

How it works

1. Week 1

   Inventory phase

   We map the seven areas as they exist today. Interviews with your leaders, read-only access to the systems that run your business, review of how decisions get made. No recommendations yet — just an honest picture of the current state.

2. Week 2

   Analysis phase

   We test the foundation against three pressures: any AI work that's already stalled, the AI work you want to do in the next 12 months, and the cost of doing nothing. We identify which gaps will block the AI you have in mind, and which won't.

3. Week 3

   Synthesis & delivery

   We write the Readiness Report, walk it through with your leadership team, and answer questions in writing afterward. If a Business Transformation is the right next step, we attach a written scope; if it isn't, we say so and explain why.

What you receive

1. Readiness Report — a 30-to-50-page written diagnosis covering each of the seven business areas. Plain language. No jargon. Read-aloud-at-a-board-meeting quality.
2. Seven-area scorecard — a one-page summary your leaders can scan in five minutes.
3. Business Transformation Scope — if a transformation is the right next step, a written proposal with fixed timeline, fixed price, and clear success criteria.
4. Decision Memo — a 3-page summary your leadership can read in one sitting and act on.
5. Walk-through — a 90-minute session where we present the report to your leadership team and answer questions in writing afterward.

What it costs

A fixed fee, quoted at the intro call after we understand the company size and foundation complexity. No change orders. Paid in full at engagement start.

What happens after

Three outcomes — listed so you see the decision tree before you buy.

• A Business Transformation is the right next step. We hand you a written scope. You decide whether to engage us, take the report to someone else, or do the work in-house.
• A Business Transformation is not the right next step. Your business is healthy enough that a transformation would be over-investment. We tell you.
• A Business Transformation is the right step, but the timing isn't right. Internal alignment, budget, or sequencing isn't there yet. We map what needs to happen first and step back until it does.