Every week someone asks me whether their organization is “ready for AI.” It’s the right question — but most people expect the answer to be about technology: which model, which platform, which tool. It almost never is.

After building intelligent systems for nonprofits, colleges, and operations teams, I’ve found that readiness comes down to four unglamorous things. None of them require a data-science degree to assess.

1. Your data

AI is only as good as the data it can reach. The single biggest blocker I see isn’t model quality — it’s that the relevant information is scattered across a dozen spreadsheets, three inboxes, and someone’s memory.

You don’t need a perfect data warehouse. You need to be able to answer: could this data live in one place, is it consistent enough to trust, and do we know what’s sensitive and who’s allowed to see it? If the honest answer is “our data is a mess,” that’s not a reason to avoid AI — it’s the first project.

2. Your process

The best early AI use cases are boring on purpose: a repetitive, rules-based task that eats real hours every week. High volume and repeatability are where AI pays back fastest.

The test I use: can you describe the process step by step? If a new hire could follow your written instructions, AI probably can too. If the process only lives in an expert’s head and changes case by case, automate the documentation first.

3. Your people

This is the one most projects underestimate. I’ve watched well-built tools get quietly abandoned because no one owned them and the people doing the work were never brought along.

Two questions decide it: is there a clear internal owner who will champion the work, and are the people who actually do the job open to changing how they do it? Adoption — not the model — determines whether any of this delivers value. It’s why I start every engagement with the people running the process, not the org chart.

4. Your goal

“Use AI” is not a goal. “Cut our grant report from two weeks to one day” is. If you can name the outcome and how you’d measure success, you can scope a focused first project — and know whether it worked.

Start narrow. A single, well-chosen use case that succeeds builds the credibility and momentum for the next one. Trying to boil the ocean is how AI initiatives stall.

Where do you stand?

If you can say yes to most of those, you’re ready — and the hard part is just choosing the right first use case. If you can’t yet, that’s useful too: it tells you the foundations to build before you spend a dollar on AI.

I turned this into a one-page, 10-point checklist you can work through in a couple of minutes — grab it here. And if you’d like a second pair of eyes on your score, book a free discovery call and I’ll tell you, honestly, what’s worth building first.