← All insights

You've Been Told to Use AI. Here's Where to Actually Start.

Maybe it came from your board. Maybe a funder asked about it, or a member asked why your newsletter still takes a week to put together. However it arrived, the message is the same: "We should be using AI."

What usually doesn't arrive with that message is a plan, a budget, or an hour of anyone's time to figure it out. So the question lands on a small team that is already stretched thin.

The good news is that you don't need to become an AI expert to make real progress. You need a sensible order of operations. Here is the one we use with associations and nonprofits over a first 90 days.

First, a few things to let go of

You do not need to buy a new platform. You do not need to automate your whole organization. And you do not need to keep up with every announcement. Most of the value early on comes from using tools you may already have access to, on work your staff already does, with a few simple rules in place.

Days 1–30: Find out where you really are

Before you add anything, take stock. Chances are some of your staff are already using AI tools on their own. That is not a problem to punish. It is useful information.

• Ask, don't audit. Run a short, no-blame survey or a few conversations. Which tools are people using? For what? What has worked, and what has gone wrong?
• List your repetitive work. Meeting notes, first drafts of member emails, event descriptions, grant report sections, FAQ answers, summarizing long documents. Write down the tasks that eat hours every month.
• Check your data situation. Where does member and donor information live? Who can see it? This matters before anyone pastes it into a tool.
• Look at what you already pay for. Many office suites and CRMs now include AI features. You may have options sitting unused.

At the end of the first month, you should be able to say in plain words how AI is being used today and where the biggest time drains are.

Days 31–60: Set simple rules and run small pilots

Now put a light structure around it. This does not have to be a long document. A one- or two-page acceptable-use guide is a strong start. It should answer:

• Which tools are approved for staff use, and which accounts to use them under.
• What information must never go into an AI tool (for example, member records, donor details, personnel matters).
• That a person reviews anything AI helps produce before it goes out.
• Who to ask when something isn't clear.

Then pick two or three small pilots from your list of time drains. Good first pilots are low-risk, easy to check, and done often. Drafting a recurring newsletter section or turning meeting recordings into action items are typical examples. Avoid anything that makes decisions about people, like membership eligibility or hiring, at this stage.

For each pilot, name an owner, decide how you will judge it ("Did this save time? Was the quality acceptable?"), and set a check-in date.

Days 61–90: Train, decide, and write down the plan

By now you will have real experience instead of opinions. Use it.

• Train the whole team. A short, hands-on session built around your actual work does more than any general webinar. People need to see good prompts, bad outputs, and how to check results.
• Keep, change, or stop. Look honestly at each pilot. Keep what worked. Adjust what almost worked. Drop the rest without guilt.
• Write a short AI plan. One to three pages: your goals, your rules, the uses you are supporting, who owns what, and what you will look at next. This is also what you show your board.

What "good" looks like at day 90

You are not finished at 90 days. But you should have:

• A clear picture of how AI is being used across your organization.
• Written, practical rules your staff understand.
• Two or three uses that are saving real time.
• A team that has been trained on your own work, not generic examples.
• A simple plan you can share with leadership and update each quarter.

That is a solid, defensible place to be. It answers the board's question, protects your members, and gives your staff something useful instead of something else to worry about.

Where outside help fits

Some teams can do all of this on their own. Others don't have the hours, or want an independent view before they commit. That is why our work starts with an AI Readiness Check: a short, structured look at where you stand today and what to do first. We don't sell software, so our advice is about what fits your organization, not what we need to sell.