← The notebookField notes · 5 MIN READ

Is my company ready for AI? How to tell

Is my business ready for AI? I'd say you are when you can point to one piece of work, explain how it runs today, put a number on it, and name the person who owns the result.

Most companies already have someone using ChatGPT. Some have paid for licenses. A few have run a pilot that nobody remembers ending. None of that tells you if the business is ready.

If you can't do those four things yet, you're not behind. You just know what to fix first.

If you'd rather walk through this with someone, that's what we do at AI Answered. Here's how we work as a growth partner. It starts with your numbers.

These are the checks I'd use.

1. You can name the work, not just the department.

"We want AI in sales" isn't a starting point. "Our reps spend Monday morning rebuilding the same pipeline report" is. Readiness starts with a task you can describe in one sentence, with an input and an output.

If every answer is a department or a buzzword, the company isn't ready to buy anything yet. It's ready for a conversation about how the work actually runs. I wrote more about picking that first task in where to start with AI in your business.

2. You know the number before you start.

This is the one most companies skip. What does the task cost today? Hours, errors, how long things wait, what it costs when it goes wrong. If there's no before, there's no after. Every result will sound like a win because nobody can check it.

The UTS Human Technology Institute put out a practical framework for AI ROI in September 2026. For organizations early in their AI maturity, the first discipline it lists is to define specific business improvements for each use case before deployment, set target metrics you can actually track, and get the board and management to agree on them. That's the same idea in more formal words. I've said it more bluntly before: AI won't fix a business that doesn't know its numbers.

3. The process is written down, or could be by Friday.

AI is good at repeating a process. It's bad at guessing one. If five people do the same job five different ways, a model will just make the confusion faster.

You don't need a binder. A page or two that says what happens first, what good looks like, and what happens when something breaks. If nobody can write that page, that's your first project, and it costs a few hours, not a software contract. It's the same reason I do the work manually before I automate it.

4. Someone owns it.

Not "IT" and not a committee. One person whose job gets better if this works and who will notice if it doesn't. That person should also be able to say who checks the output before it reaches a customer, because the model will be wrong sometimes.

Microsoft's AI readiness checklist for businesses starts with clear business goals, then employee training, then data that is accurate and accessible, then policies for responsible AI use. Infrastructure and devices come at the end of the list. I think that order is right.

5. Your people are curious, not just told to use it.

If the team thinks AI is a plan to replace them, they'll quietly route around it. If they've had a chance to try it on their own work, they'll tell you where it helps and where it doesn't. Adoption is a people problem first. I keep coming back to start with the person, not the tool.

What "not ready" actually means

Failing a few of these isn't bad news. It's a plan. Most of the work that makes a company ready for AI is just good operating work: knowing your numbers, writing down how things run, giving someone ownership. It pays off even if you never buy a single AI product.

What I'd avoid is the opposite. Buying a stack of software first and hoping the results show up somewhere later.

How we approach it

I'm Co-founder of AI Answered. We work with established companies as a growth partner. The first thing we do is look at the business and its numbers, agree on what we're trying to move, and only then decide what to build. We price on the value we can deliver, so the price is tied to the result, not a package.

If you're weighing whether to bring someone in, here's what to look for in an AI consultant, including us. And if you want to see if we're a fit, start on our growth partners page. If we're not the right fit, you should know that early.

For anyone on your team who wants the simple version of the tools themselves, Noah Kruthaupt and I wrote AI for Boomers. It teaches AI through everyday tasks, step by step. The idea is the same as this post. Technology should make things simpler, not more complicated.

More from the notebook ↗