New book: Leading AI-Native Teams is out now. Get it on Amazon

AI strategy and readiness

AI Readiness Sprint

Most leadership teams I talk to already know AI matters. What they’re stuck on is where to start, how much to spend, and in what order. I’ve sat in more than a hundred of those conversations with enterprise teams, and the ones that got to production usually did a few simple things early: they picked a small number of workflows, they were honest about the data, and they planned for the people side from day one.

The AI Readiness Sprint is how I help a team do that. It starts with a short paid intensive, and if it makes sense, it turns into a four-week sprint that ends with a ranked plan your leadership team can fund.

Who it’s for

  • Leadership teams that have a few pilots going and aren’t sure which ones deserve real money
  • Executives whose board or owners are asking “what’s our AI plan?” and want a straight answer
  • Operations leaders in document-heavy work (claims, underwriting, benefits, intake, back office) who suspect agents could help but want to see it on their own workflows first
  • Mid-size companies without a full-time AI leader who need senior help for about a month

If you’re looking for someone to build a production system right away, that’s usually a Build engagement, and we can talk about that too.

Step one

The Readiness Intensive

This is the front door. It’s a focused working session on one AI decision or one business area, and it’s priced so it’s easy to say yes to.

  • A short intake questionnaire before we meet
  • A 90-minute to half-day working session, virtual or in person in Colorado
  • A written readout within two business days: the opportunities I see, the risks, and what I’d do first
  • The full fee credits toward the four-week sprint if you go ahead within 30 days

Step two

The four-week sprint

The sprint follows the same way I work on everything: Listen, Frame, Build and Hand off. I’ve also built the people side into it, because in my experience the technology is rarely why a pilot stalls.

Week 1

Listen

  • Interviews with 6 to 12 folks across leadership and the teams that actually do the work
  • A walk-through of two or three workflows the way they really run today, with the time and the handoffs written down
  • A quick look at your data, your current tools and anything you’re already paying for

Week 2

Frame

  • A use-case portfolio ranked by business value, feasibility and risk
  • Build, buy or partner recommendations for the top few, kept vendor-neutral
  • A SCARF read on each use case: who might feel their status, certainty, autonomy, relationships or fairness threatened, and what we’ll do about it

Week 3

Build

  • A working prototype or a clickable walkthrough of the top use case, built on your own tools where possible
  • A simple evaluation so we can see whether it’s actually any good, with real examples from your work
  • Governance basics: data boundaries, where a person reviews the output, and responsible-use guardrails

Week 4

Hand off

  • A sequenced 6 to 12 month roadmap with success measures leadership can track
  • An adoption plan using the Ice Mold Leadership Model: the skills the team needs to build, the behaviors and habits that make it stick, and who owns what
  • An executive readout with your leadership team, plus the documents so your people can run with it

What you get

  • The Readiness Intensive readout
  • A ranked AI use-case portfolio
  • A prototype or walkthrough of your top use case, with an evaluation
  • Governance basics written for your business
  • A SCARF-based adoption plan and an Ice Mold team plan
  • A 6 to 12 month roadmap and an executive readout

Price

You’ll get a fixed price for the Intensive and the sprint before we start, based on the number of workflows and interviews. Half of the sprint is due at kickoff and half at the readout, and there aren’t hourly add-ons.

How I work

I keep it small, senior and hands-on. You work with me directly the whole way through. I’ll be honest if I think AI isn’t the right answer for a workflow yet, and I’ll tell you if a simpler fix would do more.

I don’t sell software licenses or take referral fees from vendors, so my recommendations are based on what fits your business.

Questions folks ask

Before you reach out

Do we need to be technical?

No. I’ll translate as we go. It helps to have one person on your side who knows your systems, but it’s not required.

Which AI tools do you work with?

I’ve built on Amazon Bedrock and Azure AI, and I work with the major model providers. I’ll start with what you already own before suggesting anything new.

What if we only want the Intensive?

That’s fine. Plenty of teams get what they need from the readout and run with it themselves.

Is our data safe?

I work inside your accounts and under your policies, and I’m happy to sign your NDA. I won’t put your data into any tool you haven’t approved.

What happens after the sprint?

Some teams take the plan and go. Others ask me to stay on as a part-time AI leader or to help build the first use case. Either way, the plan is yours.

Do you work remotely?

Yes. I’m in Colorado and work with clients across the U.S. I’m happy to be in the room for the kickoff and readout if that helps.

Let’s talk.

Start with a 30-minute conversation. Bring the pilot that’s stuck, the board question or the workflow that keeps coming up. You’ll leave with a next step, whether or not we work together.