90-day program · Day-90 value gate

The AI Transformation Toolkit

A 90-day AI transformation program that proves your rollout is working — in the numbers you already take to the board. You get the written baseline before day one.

An operator who sits in the room with your team — not a firm that arrives with a playbook and leaves a deck.

The problem

Your rollout is working. You still cannot prove it.

This program does that. Not a new dashboard, not a new North Star, and not a scorecard that lives beside the real one. The same numbers you already take to your board, moving faster, with the work to make them move.

  • Adoption is not the problem anymore. People are using the tools. In some departments the return is obvious — support is faster, engineering ships more. In the rest, nobody can say with a straight face how much of the improvement was AI and how much was everything else.
  • That gap used to be survivable. It is not anymore. Software companies that were exiting at eight or nine times revenue are now looking at three to five unless they are clearly one of the winners in their market. Boards stopped asking whether you are doing something about AI. They started asking what it returned.
  • Almost nobody has an answer, because almost nobody wrote down a before. The companies that will be able to prove it in six months are the ones that start measuring now, on the metrics they already report.

What you get

Eight things, all of them nouns

Every item below is an artifact you keep, not an activity you attend.

01 · Day 0–14

A written baseline, before we start

Your departmental metrics in one place, with a pre-AI column and a monthly roll-forward after it. Built from the numbers you already run, never from token counts or seat logins.

02 · Day 0–14

A maturity read on every department

Each function placed on a six-level deployment stack based on what it does, not what it bought — plus the one decision that unblocks the next level.

03 · Day 15–90

Three facilitated sessions

One half-day with leadership that ends in a written decision log. One round of department-specific working sessions. One reconvene near day 90 where teams show what they built.

04 · Day 15–45

The fluency rubric, built for your functions

Levels by role, with observable behaviors and the specific tools each function should be using — so nobody is guessing what "good" means in a performance review.

05 · Day 15–45

A live workflow registry

The mechanism that turns one team's working process into every team's tool: entry template, promotion path from personal to enterprise, and an owner. Stood up in five days.

06 · Day 15–45

Access, governance, and policy

A staged rollout model that gates access on completed training, plus an acceptable use policy assembled from a 15-section clause library and a review path for regulated systems.

07 · Day 90

A board narrative you can forward

The metrics you already take to the board, with a before and an after, written so it survives a follow-up question. Not a deck about the future of AI.

08 · Ongoing

The library, for your champions

Course access across four programs, 15 working agent templates, the frameworks as print-ready one-pagers, and a private Slack room. Fuel for the people building — not a completion target for all 200 employees.

The program

Ninety days, four phases

The first artifact lands before the first meeting. That is deliberate — reacting to a draft is faster than building one together from nothing.

01 · Days 0–14

Baseline

A short pre-work survey, whatever data exports you can pull, and the baseline tool. You get the filled-in draft before the first session — a document to react to, not a blank page to fill in together.

You keep: Written baseline · stack placement per department · ranked workflow candidates

02 · Days 15–45

Install

Leadership session first: where each department actually sits, which numbers move, who owns what. It ends with the decision log read back out loud so nobody leaves with a different version of what was agreed. Then department sessions — the specific answer to "I run support, what do I do differently on Monday."

You keep: Decision log · fluency rubric · registry live · policy signed

03 · Days 46–75

Prove

Your champions build on real workflows. Each one gets a before-and-after measurement before it counts — emotion is not evidence. The first monthly roll-forward ships in this window.

You keep: Working workflows in the registry · roll-forward report #1

04 · Days 76–90

The board moment

Teams show what they built and what broke. We check the rollout against the failure modes that kill these programs in month four. Then the numbers go into a narrative you can hand to your board or your sponsor.

You keep: Board narrative · day-90 review · continue-or-stop decision

Measuring fluency

Six levels, and they look different in every function

“Are we good at AI yet?” is unanswerable. This is what replaces it. A department sits at the level it can sustain — not its best day, and not what it has licenses for. The level tells you which decision has been avoided.

LevelSalesSupportFinance
1Individual

Person plus model. One-off prompts, nothing persists.

Which model, and who gets access?

A rep pastes a prospect website in and asks for talking points.An agent rewrites a reply to sound friendlier.Someone asks it to explain a formula.
2Contextual

Model plus your business knowledge. Output is on-brand and specific.

What context does it need, and who maintains it?

Loaded with your ICP, pricing, and objection handling.Knows your product docs and refund policy.Knows your chart of accounts and close calendar.
3Workflow

Repeatable processes anyone can run. Quality holds regardless of operator.

Which workflows get formalized, and who builds them?

A documented account-research workflow every AE runs the same way.A triage flow any agent can invoke on any ticket.A month-end variance review that runs the same way every time.
4System

Tools wired in. It can act, not just draft.

Which systems connect, and who approves integrations?

Writes the call summary and next steps into the CRM itself.Tags, routes, and drafts inside the helpdesk.Pulls from the warehouse instead of a pasted export.
5Distributed

One team's work is discoverable and reusable by other teams.

How do teams find each other's work, and who curates it?

Sales runs the research workflow marketing built.The triage flow gets reused by implementations.Ops adopts the variance review for their own numbers.
6Institutional

Governance, measurement, and evolution. A managed asset.

How do you govern, measure, and evolve it?

Quota per AE is tracked against it in the board pack.Escalation rate is watched for confident wrong answers.Close time is on the scorecard with a named owner.

The most common finding in a mid-market company: nobody is at level five. Every department’s best work stays trapped inside the team that built it. That ceiling caps everything above it, and it is an organizational decision, not a technology one.

For the board

What you can forward, and when

Every artifact is written to be sent onward without a translation layer.

  • Day 30

    The before

    A written baseline on existing metrics, with every gap named. The honest version: which numbers you could not produce is itself a finding worth reporting.

  • Day 60

    The first movement

    The same table with a new column, plus the first workflows measured before-and-after. Small, specific, and defensible rather than impressive and vague.

  • Day 90

    The narrative

    A written summary tying departmental movement to the numbers your sponsor already tracks — with attribution stated honestly, so it survives the follow-up question.

The part most programs skip

What we refuse to measure

The fastest way to make an AI rollout look successful and be worthless is to measure activity. These numbers all go up on their own. The moment you reward them, people optimize for them.

  • Token spend, prompt counts, and the percentage of employees who opened the tool. They go up on their own and tell you nothing about the P&L.
  • "Hours saved" with no departmental KPI attached. If the hours did not show up as more accounts per CSM or a faster close, they were moved, not saved.
  • Seat licenses deployed. Procurement is not adoption.
  • A parallel AI scorecard. A second set of numbers nobody owns dies in a quarter — improve the one already going to your board.
  • Company-wide averages only. The average hides the two departments that are working and the four that are not.

When a measure becomes a target, it stops being a good measure. Improve the scorecard you already have instead of building a second one.

The day-90 gate

If it is not working at day 90, you stop.

The baseline is written down before we start, so there is nothing to argue about later — either the numbers moved or they did not. Most engagements continue into an ongoing cadence, but that should be a decision you make with evidence in front of you, not a renewal you have to negotiate your way out of.

Fit

Is this the right program?

A fit if

  • You already rolled something out and adoption is real, but you cannot prove it moved the business
  • You are 75–500 people, and departments are at wildly different levels
  • Your board or sponsor has started asking what the AI spend is returning
  • You have an executive willing to own this, and a few people already building

Not a fit if

  • You have not started yet — the readiness assessment is a better first step
  • You want a content library your team consumes on their own time
  • You want headcount cuts named and dated in 90 days
  • Nobody on the leadership team will own it between sessions

Not started yet? The free AI readiness assessment is the better first step, and it takes ten minutes.

Start with the baseline

Build it yourself with the free skill — it runs inside your own Claude, against connectors you already approved, and your data never leaves. Or book a scoping call and we will do it together on the way into the program.

Scoped on a 30-minute call, quoted upfront in writing within two business days.

FAQ

The questions you are actually asking