How it works, in one sentence
Running a thin-team nonprofit is, at heart, never dropping any of the thousand balls a small team has to keep in the air at once — member, donor, event, deadline, volunteer. The agent decides no spending and speaks in nobody’s official name — it removes the friction from the operation so the few people you have handle the judgment and the purpose only people can.Concrete flows
1. Answer members and donors and keep records current
Trigger: someone in the base asks something — over WhatsApp, by email, or through the site form: “how do I renew my membership?”, “can I get a receipt for my donation?”, “does the association have a student discount?”. Athena, the organization’s operator, pulls from the Company Brain what’s already on record — bylaws, donation policy, assembly calendar, the answers the office repeats every week. She opens the chat and replies right away, outside business hours too. Each interaction updates that member or donor’s record in the CRM — channel, last contact, status — and nothing is lost when the person disappears for a month and comes back. If the question touches a donation amount, a financial condition, or a benefit that becomes a commitment, the agent searches the Brain; if it can’t find it, it doesn’t invent: it logs the question and escalates to coordination. Answering what’s already policy is routine work; promising a new condition is not.2. From the event plan to tasks and reminders
Trigger: the team decides to run an event — a volunteer drive, a campaign, an assembly, a charity sale — and describes the plan to the agent in a chat. The agent pulls from the Brain how similar events were run before and breaks the plan into tasks on a board: book the space, build the volunteer roster, post to the channels, buy the materials. Each task gets an owner — a person or another agent — and a due date. It schedules the milestones in Google Calendar via Composio, creates a routine that reminds each owner the day before, and keeps the event folder — brief, roster, checklist — always in one place.The agent organizes and reminds — it builds the event structure and
chases the progress, but who decides what gets spent, who signs with a
vendor, and who approves the piece that goes public is a person. It hands the
team a plan ready to execute.
3. The routine that watches grant and obligation deadlines
Trigger: a routine the agent schedules for itself — every morning, it sweeps the deadlines recorded in the Brain and on the boards: grant applications, accountability filings, certification renewals, reports due to a funder. On fire, the agent compares each deadline to today’s date and, for what’s approaching, raises the bell with a proactive notification and opens a task for the owner — with what needs doing and the documents that already live in the folder. For what isn’t even on the radar yet, Scout can research open grants and calls on the web via Tavily and bring back a list for the team to weigh.Why this matters: a missed grant deadline is the funding opportunity that
vanishes without anyone deciding to give it up — just because the email got
lost in the inbox of a three-person team. A routine has no crunch week: it
watches always, warns with room to spare, and turns “wait, that was
yesterday” into “nine days left, here’s what’s missing”.
4. Draft communications and reports for approval
Trigger: it’s time for the monthly member update, the impact report for a funder, or the thank-you to the donor base after a campaign. The agent pulls from the Brain and the boards what actually happened — volunteers mobilized, actions run, milestones met — and assembles a draft in a document: the update, the report, the email copy. The text comes out ready for review, never sent on its own. Once a person approves, the agent can send the communication via Outbound — email or WhatsApp — with per-send approval when the message goes out in the organization’s name.| Communication | What the agent does | What stays human |
|---|---|---|
| Member update | Builds the draft from what happened | Approving the text and authorizing the send |
| Funder report | Consolidates numbers and milestones met | Validating data and signing the report |
| Donor thank-you | Drafts the message with the real impact | Approving the piece that goes out officially |
| Receipt / proof | Gathers the data and prepares the document | Issuing and confirming amounts |
What stays human
Where to start
Teach the organization to the Brain
Upload to the Company Brain your bylaws, donation
policy, assembly calendar, grant and obligation deadlines, and the answers
the team repeats every week. That’s where the agent pulls what to answer,
what to watch, and what to draft.
Schedule the deadline watch
Create a routine that sweeps grants, filings, and
obligations and warns with room to spare. One agent, one cadence — and
autonomy grows like a ratchet, never a leap.
Next steps
Operations & support
The answer-organize-chase pattern applied to the team’s day-to-day.
Management & tracking
How to keep events, deadlines, and indicators visible without a manual
spreadsheet.
Routines
The daemon that watches grant deadlines, reminds the drive, and chases the
accountability filing.
Documents
Where the member update, the impact report, and the thank-you are born ready
for review.