Not sure where AI would pay off? Take the 3-minute opportunity check →
Nonprofit organizations · Internal knowledge assistant

When staff turn over, keep what they knew inside the organization

Nonprofits lose institutional knowledge every time a program manager, grants writer or volunteer coordinator leaves. What remains is a shared drive with folders named Final, Final v2 and Old Stuff, an employee handbook from several years ago, and a few long-serving staff who answer the same questions over and over.

How it often works today
  • New program staff ask the same questions about intake procedures, mileage reimbursement and safety protocols, and long-serving colleagues answer them repeatedly.
  • Grant writers search years of old proposals in Google Drive or SharePoint to find the latest approved organizational description and outcome figures.
  • Volunteer coordinators send long orientation emails that volunteers do not read, then field the same questions by phone before every shift.
  • When a key staff member leaves, procedures they handled, such as the annual audit prep or a funder portal login process, are rediscovered from scratch.

We would organize your key documents and set up an assistant that answers staff and volunteer questions from them, with links to the source. Program procedures, HR policies, grant boilerplate, past funder reports and board-approved language become findable in plain language. Sensitive client and personnel files stay out of scope.

The improved workflow

Gather and tidy core documents

Identify the policies, procedures, boilerplate and reports staff use most, retire outdated versions, and mark one current version of each as the approved source.

Set clear boundaries

Exclude client case files, personnel records, donor details and anything confidential, so the assistant only draws on documents everyone in the audience may see.

Answer questions with sources

Staff ask in plain language and get an answer with a link to the source document, so they can confirm the detail before acting on it.

Assign document owners

Each key document has a named owner and a review date, and questions the assistant cannot answer become a short list of gaps to fill.

How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.

What we would measure

Repeat questions to senior staff

The main time cost the assistant is meant to reduce.

Time for grant writers to find approved language

A specific, measurable win for development.

New staff time to independence

Shows whether onboarding is getting shorter.

Answers flagged as wrong or outdated

Keeps document quality visible and owned.

Where people stay in control

  • Client, personnel and donor records are excluded from the indexed sources, and access mirrors existing shared drive permissions.
  • Answers about safety, mandatory reporting or HR matters point staff to the policy and the responsible manager, not just a summary.
  • Document owners review their sources on a schedule, and the assistant shows each source's last-updated date.
Example

A new case manager's first month

For example, in an illustrative case a housing nonprofit hires a case manager who starts the week the program director goes on leave. Instead of waiting for answers, she asks the assistant how to log a rental assistance request, which forms the county requires, and what the mileage policy is. Each answer links to the current procedure. One answer points to a form that was replaced last year, which gets flagged and fixed by the document owner that week.

Tools typically involved

What the first 30 days look like

In the first 30 days we would collect the questions staff and volunteers ask most, inventory the shared drive, identify approved versions of key documents, and agree what is excluded. A small staff group would pilot the assistant with real questions.

Common questions

Do we need to buy a new AI product for this?

Possibly not. Google Workspace and Microsoft 365 both offer AI features, sometimes at nonprofit pricing, that can search documents you already store there. We would test what your current plan supports before suggesting anything new. The bigger task is usually organizing the documents, not choosing the tool.

Can volunteers use it too?

Yes, with a separate, limited set of documents such as orientation guides, shift procedures and safety information. Volunteers would not see staff policies or internal reports. We would design access so each group only reaches what it should, and test it with a few volunteers first.

What if our documents contradict each other?

That is common and one of the most useful things the project reveals. Contradictions get surfaced during the cleanup step, and the responsible manager decides which version is correct. The assistant only works well once there is one approved version of each policy or procedure.

The business case

Does it pay for itself?

Illustrative defaults for a nonprofit. Replace them with your numbers.

What this workflow costs today

a month in staff time, before any lost sales

Monthly fee + assumed tools +
Break-even: new clients a month (at first-year value)
Or: staff hours recovered and redeployed
Break-even additional revenue
Value of +1 point of win rate
First 90 days, service fee

Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.

Next step

Bring one expensive workflow. Leave with a clear next step.

In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.

Book a 30-minute workflow review Not ready to talk? Take the 3-minute check

30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.

Book a 30-minute review