How to Build a 90-Day AI Strategy Without Losing Your Mind
I talk to a lot of church leaders and nonprofit directors who know they need to do something with AI but have no idea where to start. They've read the articles. They've seen the headlines. They know that organizations around them are starting to use these tools. But every time they sit down to figure it out, they get paralyzed by the options.
Should we use ChatGPT? What about Claude? Do we need custom software? Should we hire someone? Is there a free version? Will this replace our staff? How do we keep member data safe?
Too many questions. Not enough time. So nothing happens.
Here's the thing — you don't need to figure it all out. You need a plan for the next 90 days. That's it. Not a five-year digital transformation roadmap. Just 90 days of focused, practical progress that gets your team comfortable with AI and saves real hours every week.
Before You Start: The Honest Assessment
Before you build a plan, you need to know where you actually are. Not where you think you are, not where you want to be — where you are right now.
Sit down with your team and answer these questions honestly:
What tasks eat the most time every week? Not the important strategic work. The repetitive stuff. The formatting. The rewriting. The data entry. The same email you write slightly differently to three different groups. Make a list.
What's your team's comfort level with technology? Not with AI specifically — with technology in general. Do they use Google Docs or are they still emailing Word documents back and forth? Do they use project management tools or is everything tracked in someone's head? This baseline matters because it tells you how fast you can move.
What are your real concerns? Not the concerns you think you should have — the ones keeping you up at night. Is it data privacy? Is it cost? Is it the fear that AI will make communication feel impersonal? Name them. Unspoken fears don't get addressed. Spoken ones do.
What would "success" look like in 90 days? Be specific. "Our team uses AI" is too vague. "Our weekly bulletin goes from four hours to one hour" is concrete. "Grant report drafts start with AI-generated first drafts instead of blank pages" is concrete. Pick two or three wins that would genuinely make people's lives easier.
Days 1-30: Foundation
The first month isn't about AI. It's about understanding your workflows well enough to know where AI fits.
Week 1-2: Document Your Workflows
Pick the three tasks from your "what eats the most time" list. Now actually document how they get done today. Step by step.
For example, if weekly church communication is on your list, write down exactly what happens: Who writes the bulletin? Where does the content come from? How does it get formatted? Who reviews it? How does the email version differ? What about social media? How long does each step take?
This isn't busywork. When you understand a process step by step, you can see exactly which steps AI can handle and which ones need a human touch. Without this clarity, you'll either try to automate the wrong things or miss the biggest opportunities.
Week 3: Choose Your Tools
You don't need many tools. For most small organizations, you need one general-purpose AI assistant and maybe one specialized tool. That's it.
For general writing and communication tasks, a tool like ChatGPT or Claude works well. The free versions are enough to start with. Don't spend money until you know what you actually need.
If you have specific needs — like transcribing sermons, generating social media graphics, or organizing volunteer data — look at one specialized tool for that. Just one. Not five. One.
Set up accounts. Figure out the basics. Get comfortable with the interface. You're not trying to become an expert this month. You're just getting familiar.
Week 4: Set Up Safety Guidelines
Before anyone on your team starts using AI tools for real work, establish some ground rules. These don't have to be complicated:
- What types of information are okay to put into AI tools? (Generally: public information, draft content, general questions. Not okay: personal member data, financial details, confidential counseling notes.)
- Who is responsible for reviewing AI-generated content before it goes out?
- Where will AI-generated drafts be stored?
- How will you label or track content that was created with AI assistance?
Days 31-60: Implementation
Month two is where things get real. You've documented your workflows, you've chosen your tools, and you've set safety guidelines. Now you start doing the work.
Pick One Workflow and Automate It
Don't try to transform everything at once. Pick the one task that has the biggest impact-to-effort ratio — the thing that takes a lot of time but is relatively straightforward.
For most churches, this is weekly communication. For most nonprofits, it's report drafting or donor communication. For most small businesses, it's customer follow-up emails or social media content.
Set up a repeatable process. Here's what this might look like for church communication:
- 1. Write your core message for the week (sermon summary, announcements, upcoming events). This is the human part — the substance that matters.
- 2. Feed that core message into your AI tool with a prompt like: "Take this information and create a church bulletin format. Keep the tone warm and welcoming. Include all announcements with dates and times."
- 3. Review the output. Edit as needed. Approve it.
- 4. Use the same core message with a different prompt for email format, social media posts, and website updates.
Train Your Team
Not a big formal training. Just sit with each person who will use the tool and walk them through the process you've set up. Let them try it themselves while you watch. Answer their questions. Address their concerns.
The biggest thing people need at this stage isn't technical knowledge — it's permission. Permission to experiment. Permission to make mistakes. Permission to say "this didn't work" without feeling like they failed.
Track Your Results
Keep a simple log. How long did the task take before AI? How long does it take now? What's working? What's not? You need this data for month three, and you need it to justify expanding the program.
Days 61-90: Expansion and Refinement
By month three, your team has been using AI for real work for four to six weeks. They've hit some bumps. They've also had some wins. Now you build on that.
Add a Second Workflow
Take what you learned from the first workflow and apply it to a second task on your list. The process is the same — document the current workflow, identify where AI fits, set up the process, train the people, track the results.
This goes faster the second time because your team already understands the basics. They've gotten over the initial anxiety. They know what the tools can and can't do.
Create Your Prompt Library
By now, your team has figured out which prompts produce good results and which ones don't. Collect the good ones. Organize them by task type. Save them in a shared document.
This is one of the most valuable things you'll build. New team members can pick up this document and start producing quality work immediately. Prompts are recipes — once you know the good ones, you don't have to experiment every time.
Assess and Plan Next Steps
At the end of 90 days, sit down with your team and review:
- How many hours per week are we saving?
- What's working well?
- What's been frustrating?
- What should we tackle next?
- Do we need to upgrade any tools or invest in anything new?
Common Mistakes to Avoid
Don't try to do everything at once. This is the most common mistake. People get excited and try to implement AI across every workflow simultaneously. That leads to chaos and burnout. One thing at a time.
Don't skip the safety guidelines. I've seen organizations rush past this step because they're eager to see results. Then someone puts sensitive member data into a public AI tool and it becomes a real problem. Slow down and set the guardrails.
Don't expect perfection from AI. AI generates drafts, not finished products. Every piece of AI-generated content needs human review and editing. The value isn't in replacing human judgment — it's in eliminating the blank page and the repetitive formatting.
Don't ignore the skeptics on your team. Some people will be resistant. That's normal and often healthy. Listen to their concerns. Address them honestly. Sometimes the skeptics identify real problems that the enthusiasts miss. And when a skeptic comes around, they often become your strongest advocate.
This Isn't About Technology
The biggest misconception about AI strategy is that it's a technology project. It's not. It's a people project. The technology is the easy part — it's already built, it's getting cheaper, and it keeps getting better.
The hard part is helping real people with real concerns and real workloads change how they do things they've been doing the same way for years. That takes patience, clarity, and a plan that respects their time.
Ninety days. One workflow at a time. Start where the pain is greatest.
That's the whole strategy.
SimpleNow AI helps churches, nonprofits, and small businesses develop and implement practical AI strategies. We walk alongside your team through every step — from assessment to adoption.