Back office & operations
A back office that runs itself
Board portal, meeting intel, and donor plumbing for a team with no technical staff.
The system
A lean institution running on volunteer hours, where the back office was email threads and a donor database nobody enjoyed opening. The work lands piece by piece rather than as one platform — a board portal, meeting capture that turns into notes and follow-ups, and the donor plumbing between them.
One constraint shapes every decision: each piece has to be simple enough that a non-technical team keeps using it after we step back. Anything that needs us in order to keep working is a failure, not a retainer.
The hard parts
It has to stick without us
The test isn't whether it works on handoff day. It's whether it's still in use a quarter later, run by people who have no interest in the tooling underneath.
No new headcount
There is no ops hire waiting on the other side of this. Every piece has to remove work rather than relocate it into someone's evening.
Shipping in pieces
A single platform launch would ask a volunteer team to change everything at once. Landing one useful thing at a time keeps adoption ahead of the build.
In numbers
Connected workspace · meeting capture · donor-system integration
Happy to walk through this one properly — what it does, how it's put together, and what it would take to build something like it for you.