A half-day working session for executive directors and their staffs. You bring the real inbox, the grant that's due, the donor list, the books. You leave with three workflows running, a one-page policy your board will approve, and a written playbook for the rest.
Not enterprise AI strategy. The practical version, for the people who do the work and the board that has to sign off on it.
Two to thirty staff. You've tried ChatGPT, got a paragraph that sounded like a stranger, and went back to writing the grant report at 11pm. You also have a board asking what your AI policy is.
The person who runs the inbox, the thank-yous, the funder reports, and the bookkeeping. Usually one person. Usually underwater. This is the most leverage in the building.
Volunteer schedules, intake forms, outcome reports, the newsletter story. Short lessons you can use between shifts, with a hard line around client information.
Fifteen modules in the Adept Library, fifty-three written lessons, including a deep dive on every major AI platform. The session covers the first six live; your staff works through the rest with every prompt saved as a recipe.
What a model actually is, how to tell when it's wrong, and which tool your organization should pay for, if any.
One page about who you are that you paste into every conversation, so the tool stops sounding like a stranger.
Triage across donors, volunteers, board, and funders. Drafts you'd actually send. The follow-ups that slipped.
Go or no-go from the funder's guidelines. The narrative from your program brief. The report from your program data, in the funder's order.
The thank-you inside 48 hours, the appeal in your voice, and the note to the donors who quietly stopped.
What never goes into a tool, what not to automate, and the one-page AI policy your board approves in a single meeting.
The ED report from your notes, minutes from a recording, and a month of transactions by fund and program, read back in plain English.
Intake forms without client data, outcomes from activity logs, volunteer procedures, the donor complaint, and the grant you didn't get.
ChatGPT, Claude, Gemini, Copilot, Grok, and the rest, one by one: what each costs a nonprofit, what it does with your data, and how to decide in a single meeting.
Cleaning the export, the one-page dashboard your board reads, what the numbers mean, and the funder who wants cost per outcome. Aggregates only, never a person.
The event plan from one paragraph, the sponsor ask that stays on the right side of the IRS, the year-end calendar built backward from December 31, and the post-event report written in the first week.
One page about your nonprofit that you paste into every real conversation, so the tool never starts from zero and nothing about the people you serve ever has to go in. It is the first thing we build in every session. Get the guide and write yours this week.
Start with the session. Add the board if they need to see it. Keep me around if the tools keep changing, which they do.
Pricing is flat and quoted up front. If a session doesn't produce at least one workflow you'll keep using, you don't pay for it. Capacity-building and technology grants from community foundations often cover this work; ask and I'll give you a one-paragraph description to paste into the request. Need the workflows built for you rather than taught? A 30-day build is quoted per organization. The Adept Library is the written version of the session: fourteen modules, forty-nine lessons, every prompt as a copy-paste recipe, each ending with an exercise on your own material. It comes with every engagement; it isn't sold on its own.
I spent nine years on the money side, as a banker, a loan officer, and a financial advisor, before I taught myself to build software. Now I do both at once: I write the queries, ship the apps, and stand up the infrastructure that money runs through.
That's the background I teach from. Not "AI is going to change everything," but which of the twenty things your staff does every week it can take off their plate this month, which ones it must never touch, and how to tell the difference before it costs you a donor or a client's trust.
Sessions are small on purpose. I'd rather do one a week well than five badly.
Correct, and that is the first hour of every session. You leave with a written rule for what never goes in (names, case notes, health, immigration, housing status, minors, donor giving history tied to names) and a set of workflows built so the rule is easy to follow. The tool is for the form and the process, never the person.
Whichever fits your organization and budget. Most sessions end up on Claude or ChatGPT for the writing work, on a paid plan with training turned off, plus whatever your accounting and email already are. I'm not reselling software and I don't take referral fees.
No. If you can send an email and open a spreadsheet, you're ready. The technical part is my job; the session is about your judgment, not your keyboard skills.
Often, yes. Capacity-building, technology, and professional development grants from community foundations and some corporate funders cover exactly this kind of work. Ask and I'll give you a paragraph describing the engagement in the language those requests use, or take it from the grants page.
Both. In the Phoenix metro I'll come to you. Anywhere else, we run it over video with screen sharing, and it works nearly as well.
The members area at members.adeptadvisors.com. Twelve modules, from knowing the tool through the inbox, grants, donors, the board, the books, programs, volunteers, and what to do when it goes wrong, written so your staff can work through them without me in the room, with every prompt saved as a recipe and a worksheet at the end of each lesson. Access comes with every engagement.
Thirty minutes on a video call. You tell me what you do, how many staff, and the one task you'd most like to stop doing by hand. I tell you what a session would cover and whether it's worth your budget. No pitch deck.