Knowledge leaves with the person
Someone part-time or on a term contract holds the working knowledge of a programme. When they move on, the documents remain but the understanding of them does not.
For non-profits with 10 to 50 staff and volunteers
The rules are written down. Who has read them?
Programme rules, funder conditions and internal policy sit in documents, and the people who know them best are often part-time or volunteers. Continuity depends on whoever happens to be in today.
A grounded agent answers from the approved documents and cites them, so the answer does not depend on who is on shift. Where a document does not settle the question, it should point to the person who owns it.
Book a readiness assessmentWhat we see in non-profits
Funder conditions live in a separate world
What a grant requires is recorded in the agreement and then reproduced from memory in day-to-day decisions, without anything linking one to the other.
Onboarding repeats, every intake
New staff and volunteers arrive in groups and need the same orientation. It is delivered person to person each time, at a cost nobody counts.
What gets built
Assess
We review the Microsoft 365 tenant, licensing, a representative set of programme and policy documents, and the questions staff and volunteers repeat. You get a written recommendation on where a grounded agent could help, what would block it, and what should stay with a person. Non-profit licensing terms are part of what we check.
Fixed scope and fixed fee. The report can recommend not building anything yet.
Build
One grounded agent in production over the agreed document set, citing what it answered from, so a part-time worker gets the same answer as a full-time one. Questions the documents do not support are refused rather than guessed.
The build scope and delivery window are agreed after the assessment.
Extend and govern
Add scoped automation for the repeating obligations around an intake, where several small tasks are owned by different people. Document who owns each source and how a changed funder condition reaches the people it affects.
Each extension is scoped after the assessment, with its delivery window agreed before work starts.
Apps for non-profits
Policy and Handbook Assistant
Staff get cited answers from your policy library instead of asking HR the same questions again.
Time Off and Request Intake
Requests are captured in Teams, logged in Dataverse and routed for approval without email chains.
Agent Governance Setup
Set who can build agents, what they can connect to, and who owns each one.
Questions from non-profits
Is there non-profit pricing on the Microsoft side?
Microsoft operates non-profit programmes, and entitlements and eligibility change. We check the current terms against your tenant during the assessment rather than quoting them from memory, because what applies to you depends on your registration and your existing licensing.
Can volunteers use it?
That depends on how they are represented in your tenant and what the agent may draw on. Who can reach an agent decides which documents are in scope, and the assessment settles that before anything is built.
We have very little IT capacity. Is this realistic?
Sometimes the honest answer is not yet, and the report will say so. Handover includes documentation aimed at someone maintaining this alongside another job, and if a build would need capacity you do not have, that is better established in the assessment than after go-live.
Start with a readiness assessment
A review of what is worth building on your tenant and what isn’t. There is no obligation to proceed to a build.