On using AI agents to run more of a life than one person's spare time should hold.
I have a full-time job, a family, a two-acre hilltop, a homelab, and a seat on the board of a small nonprofit. For most of my adult life, the limiting factor on what I could take on wasn't ability or interest. It was hours. Things I cared about sat unfinished for months because the twenty minutes they needed never lined up with the twenty minutes I had.
This year that changed, and I want to write down how, honestly, without the hype that usually smothers this topic.
The nonprofit problem
A couple of years ago I joined the board of a small all-volunteer nonprofit that supports pastor training in West Africa. I serve as secretary, and because I'm the technical one, everything with a login became mine: the website, the records, the state filings, the donor communications, the grant research nobody had time to do.
Here's what that job actually looks like at a tiny nonprofit. There is no staff. There is no budget for staff. Every task is small, none of them are optional, and they arrive continuously: a board email that needs filing, a compliance deadline nobody remembers until it's urgent, a partner organization posting updates that should reach our supporters, a funder whose eligibility rules need reading before anyone wastes a weekend on an application. Any one of these is twenty minutes. Together they're a part-time job that nobody has.
The standard outcome is that volunteer boards run on heroics and guilt. Things slip. The person who cares most burns out first.
What I actually built
Over the past year I stood up an AI agent that functions as the org's administrative assistant. It runs on a small server, talks to me over chat, and drives our ordinary office tools: email, calendar, the shared drive, a spreadsheet that acts as the operations hub. Around two dozen scheduled jobs handle the recurring work.
A normal day looks like this. At 9 AM I get a short message: here's what's outstanding, here are the top three things, here's the link if you want the whole picture. Board emails that arrived overnight have been triaged: routine ones handled and filed, anything needing my judgment flagged. Documents dropped in a shared folder have been renamed, filed, and logged. If our partner ministry posted an update, a draft is waiting on the website for approval. Once in a while there's a note that a funding opportunity surfaced overnight, with deadlines and fit notes attached.
I read it in the time it takes to drink coffee, make the two or three decisions that actually need a human, and go to work.
Some of what came out of this, concretely:
- Compliance filings that had been hanging over the board since incorporation got done. The agent assembled the filing packages; I reviewed and signed; the state approved them. That was the single biggest weight off the board's shoulders, and it was mostly review time on my end.
- Grant prospecting went from nonexistent to nightly. No volunteer was ever going to spend evenings scanning funder sites. An automated job does, and it reads eligibility rules against our actual documents before anything reaches the board. It caught, for example, that a foundation we liked requires organizations to be older than we are, by pulling our real incorporation date from our IRS paperwork. That's a wasted application avoided and an honest reminder scheduled for when we qualify.
- Board records became records. Every decision and email is logged and retrievable. When someone asks "what was that concept note from last year?", the answer takes seconds instead of inbox archaeology.
- The website updates itself, mostly. Partner updates become drafts I approve. Promo materials that would have been a multi-day design favor get generated from source material in the org's own style in an afternoon.
What I refuse to pretend
This is the part most writing about AI leaves out, so let me be specific.
The failures are real and constant. The token for the primary model expired once and the system quietly degraded to cheaper models for days before anyone noticed; the fix was another automated check, watching the watchers. A reminder got scheduled for the wrong year; I caught it. A briefing once referenced a project that had a tracker row but no documentation; the fix was auditing everything and making cross-referencing a standing rule. A funding deadline surfaced too late to act on. Two emails failed to send and were done by hand. The first architecture for the recurring jobs was wasteful and had to be redesigned. A monitoring job I thought was running had been off for months.
Human oversight is load-bearing. Nothing goes to the board, a funder, or the public without my review. The system's job is to make my twenty minutes count, not to replace my judgment. Every one of the failures above was caught either by an automated check I added after a previous failure, or by me reading something before it went out. Both layers earn their keep monthly.
The outcomes are modest and I'll state them plainly. We have not won a grant. We haven't even submitted an application yet; the pipeline's honest output so far is one fully researched, board-ready opportunity and a list of funders we now know we don't qualify for, with dated reasons. What changed is that the org went from no systematic effort to a running process that costs almost nothing and never gets tired. For an all-volunteer organization, the difference between "nobody has time" and "it happens every night" is the whole game.
The general lesson
The same year, the same pattern ran through everything else I do: the inference server in my basement that this blog documents, the agent tooling at my day job that turns client call recordings into project proposals, the monitoring that tells me about problems before I go looking. None of it is one big AI doing something impressive. All of it is small, boring automation with careful boundaries, checked by a human, compounding.
What AI actually bought me this year is not intelligence. I still make every decision that matters. It bought me parallelism. Things now make progress during hours I'm not present: overnight, during the workday, while I'm mowing the hill. My attention became the scarce resource the whole system is designed to spend well, twenty minutes at a time.
A year ago, the honest description of my volunteer role was "important things slip, and I feel bad about it." Today it's "the routine runs itself, and I spend my time on judgment." Same hours. Same person. That's the difference, and for a small mission-driven organization that difference isn't a productivity statistic. It's whether the work of keeping the lights on leaves any energy for the mission itself.
Top comments (0)