AI consulting / practical digital transformation

Your team already uses AI. The business cannot see it yet.

I find the workflow where AI pays, ship the first working system with your team, and leave you able to run it without me.

Operating history

6,000+ people in AI data operations209% year-over-year growth3 → 2 city pilots to countries

Do not start with a tool. Start with the work.

Buying another AI subscription will not transform your business. Choose a costly, slow, or inconsistent workflow. Improve it. Measure the result. Then build the muscle to do it again.

Operating history, not borrowed credibility.

These are systems I built and scaled in operating roles. They are not testimonials from consulting clients.

Place your company on the maturity framework.

Read left to right. Pick the stage that best describes how work gets done today, then use its next move as your starting point.

  1. 01

    Stage 01

    Experimenting

    Some of us use ChatGPT sometimes.
    You are here if

    Individuals choose their own tools and methods. Useful work happens, but leadership cannot see the value or risk.

    Next move

    Choose one repeated workflow and measure how it works today.

  2. 02

    Stage 02

    Standardizing

    Teams have approved tools and shared habits.
    You are here if

    People use AI regularly with basic guidance. Results still depend on who knows the best prompts and workarounds.

    Next move

    Document one owned workflow with inputs, review steps, and a target.

  3. 03

    Stage 03

    Operationalizing

    AI runs inside owned, measurable workflows.
    You are here if

    AI connects to company knowledge and tools. Owners track speed, quality, cost, and exceptions against a baseline.

    Next move

    Connect proven workflows and manage them as an operating portfolio.

  4. 04

    Stage 04

    Transforming

    AI changes how the business operates and competes.
    You are here if

    Products, roles, and decisions are redesigned around AI. Company data and feedback loops create a durable advantage.

    Next move

    Keep evaluation close to customers and protect the learning loop.

Move one stage forward.

Each engagement produces a decision, a working capability, or both. No transformation theater.

Strategy that survives Monday morning.

  1. 01

    Observe the real work

    Follow the handoffs, exceptions, data, and decisions that process diagrams miss.

  2. 02

    Choose the valuable constraint

    Score opportunities against value, effort, data readiness, and risk.

  3. 03

    Build with the owner

    Define where people decide, where AI assists, and how the team catches failure.

  4. 04

    Prove and transfer

    Measure the result, document the system, and leave the team able to improve it.

Interest is real. The path is not.

You have roughly 10 to 500 people. Employees already experiment with ChatGPT, Claude, or copilots. Leadership sees the potential but lacks a prioritized use case, safe operating model, or path from demo to daily work.

Especially useful when:

  • Pilots stall after the demo
  • Teams use AI without shared standards
  • Tool choices outrun workflow decisions
  • Leaders cannot see measurable return

The silent no's, answered.

The first workflow should reduce uncertainty, not create another program to manage.

01We ran a pilot and it fizzled. Why would this be different?

Pilots usually die from a missing owner, baseline, or review step. This engagement ships all three. Measurement is part of the deliverable.

02Our data is a mess.

Useful workflows exist at every level of data maturity. The Opportunity Map scores readiness so we do not choose work your data cannot support.

03Do we need engineers?

No. The first workflows use tools your team already has. If integration is needed, I specify the work clearly enough for a capable developer to build.

04What does it cost?

Each engagement is a scoped fixed fee after a conversation about the workflow. The Pilot guarantee puts the risk of a poor measured result with me.

05How much of our time does it take?

The workflow owner should expect a few hours a week. They participate so they can run and improve the system after I leave.

One useful conversation

Bring me the workflow that wastes your team's time.

Describe where you are today, the workflow you want to improve, and what a good outcome would look like.

I take on a small number of engagements. If capacity is full, you will get a date, not a waitlist.Start the conversation

Contact →