The conversation about AI usually starts with the technology. The useful part starts with the work.

Most of the businesses we talk to aren't behind on AI. They're just not sure where it earns its place. The technology is moving fast. The question worth slowing down for is where it actually matters for how your business works today.

AI

Let's Talk

What does AI actually look like inside a growing business?

There's a version of the AI conversation that starts with what the technology can do. Features. Demos. Possibilities. It's exciting for about a week.

Then the business goes back to running the way it always has.

We've seen this enough times to notice the pattern.

The problem is rarely that the technology doesn't work. It's that nobody connected it to the work that actually needs to change.


After a while, the same patterns begin to appear.

Sometimes the business knows AI could help but can't point to where. Leadership has read the articles, attended the webinars, maybe had a few internal conversations. But the gap between "AI could be useful" and "here's what we'd build first" is wider than anyone expected. Without a clear starting point, nothing starts.

Sometimes the team has already tried. A few people picked up ChatGPT or a writing tool or an automation platform. Some of it helped. Most of it faded. The tools weren't bad. They just weren't connected to anything the business needed to do repeatedly. Nobody built them into the workflow. So the experiment ended quietly.

Sometimes adoption is uneven. One person on the team is deep into it. Everyone else is somewhere between curious and skeptical. There's no shared understanding of what AI is for, no agreement on where it belongs, and no way to tell whether what's being done is actually useful. The enthusiasm is real. The coordination isn't.

And sometimes the business is clear on what it wants. It wants to move faster. Handle more with less. Reduce the manual work that drains the team's best hours. But every solution seems to come with its own complexity. More integrations. More tools. More things to manage. The goal was simplicity. The path keeps feeling like the opposite.


When the real issue is one of these, buying another AI tool doesn't help.

It just adds another thing the team has to figure out on its own.

The work we find most valuable isn't recommending technology. It's understanding the work first. Where time goes. Where quality depends on a person being available. Where a process is clear enough that something else could carry part of it. And then building AI into those places so it actually stays.

The goal isn't to introduce AI into the business. It's to make the business better at the work it already does.

That's where AI earns its place.

Where is work getting stuck?

Which of these is closest to where you are right now?

You've already sensed that something about how work moves through your business isn't working. These are the patterns we see most often underneath that.

01

My team keeps asking me the same questions.

02

Everything seems to depend on one or two people.

03

We have too many tools but work still feels messy.

04

We spend more time coordinating than actually doing the work.

05

None of these exactly, but things that used to be simple aren't anymore.

We've heard some version of this in almost every business we've worked with.

Patterns We See

01

The Direction Problem

The business knows AI is relevant. Leadership talks about it. The team is open to it. But nobody can name the first project. There's no shortage of interest. There's a shortage of specificity. Without a clear starting point, the conversation keeps circling without landing.


02

The Adoption Gap

Tools have been tried. Someone set up an automation. A few people used ChatGPT for a while. But nothing stuck. Not because the tools failed. Because they were never built into how the team actually works. The experiment ran. The workflow didn't change.


03

The Consistency Problem

One person on the team has gone deep. Everyone else is somewhere between curious and skeptical. There's no shared vocabulary for what AI is for, no agreement on which use cases matter, and no way to tell whether the experiments are helping. The energy is scattered. The learning isn't compounding.


04

The Complexity Trap

The business wants AI to simplify things. But every implementation seems to introduce its own overhead. New integrations. New dashboards. New things to maintain. The team wanted fewer steps. They got more. The technology works. The experience of using it doesn't feel simpler.


What looks like a systems problem is usually a business that's outgrown the way it shares what it knows.

HOW WE HELP

What does working with an AI consultant actually look like?

It depends on where you are.

For some businesses, the work starts with clarity. Understanding where AI fits before introducing any technology. We map how work moves through the business, identify where time goes, and find the places where AI can do something genuinely useful. Before building anything, we make sure the starting point is right.

For others, the starting point is known but the build hasn't happened. The work is designing the right solution, connecting it to existing tools, and making it part of how the team actually operates. Not a demo. Not a proof of concept. Something that runs.

For businesses that already have experiments underway, we often work alongside the team. Evaluating what's been tried, building shared standards, and turning scattered efforts into a coherent approach that compounds over time.

The engagement shape depends on the business. But the work always starts with the process, not the technology.

Related Thinking

01

AI magnifies the quality of the process it's given.


02

The experiment ran. The workflow didn't change.


CHANTAL CREATE THESE BLOG POSTS and swap below

03

Start with the work, not the tool.


SELECTED THINKING

Ideas Worth Sharing

See All

If any of this sounds familiar, that's a good place to start.

You don't need an AI strategy before reaching out. Most of the businesses we work with started with a question about where AI fits, not a plan for how to use it.

Or explore how we think about operations or AI.