The $0 stack: what a nonprofit taught me about rebuilding operations

The most useful budget I've worked with this year is $0. Not small. Zero. Casa de Venezuela Orlando, the nonprofit where I volunteer as IT Director, runs on donations and volunteer hours, so when I took the tech seat, the software budget was whatever I could get for free. That constraint turned out to be the best architecture decision nobody made.

Here is what zero budget usually looks like in a volunteer organization, because we had all of it. Spreadsheets living in personal accounts. Passwords traveling through chat threads. A website on a paid site builder that only one person knew how to edit. NDAs printed, signed by hand, scanned, and filed wherever. Every handoff was a person remembering to do something, and volunteers rotate, so the memory kept walking out the door.

The fix was not a donation drive for software. It was five moves, in an order the constraint forced on me.

1. Inventory reality first. One afternoon: what do we pay for, what does each thing actually do, who holds each login. You cannot rebuild a stack you have not listed. Half the problems surface right here.

2. Claim the nonprofit tiers. Software companies give real product away to 501(c)(3)s, and almost nobody finishes the paperwork. Canva for Nonprofits. monday.com's nonprofit plan. Google for Nonprofits, which includes Ad Grants: up to $10,000 a month of in-kind search advertising. Zeffy for fundraising, with no platform fees. The application forms are the moat. An afternoon of paperwork is worth thousands a year, every year.

3. Fix identity before features. Every shared credential went into a Bitwarden vault, with access mapped to roles instead of people. Boring, and the single highest-return move on this list. Volunteers rotate. The vault stays.

4. Migrate what costs money onto free rails that are also better. The site came off the paid builder and onto Vercel behind Cloudflare, with both domains consolidated so casadevenezuelaorlando.com redirects to cdvorlando.org. Hosting bill: $0. A content edit went from "wait for the one person with builder access" to a file change and a deploy. The old builder subscription, $39 a month, became the only line item we deleted instead of replaced.

5. Automate the paper last. The NDA and member ID flow is now a Google Apps Script: form comes in, document generates, ID gets assigned, everything files itself. Claude wrote most of the script; I wrote the rules it follows. What used to be print, sign, scan, and chase is now a link.

Notice what is not on that list until the very end: AI. That is the point. The order matters more than the tools. Structure first, tools second, automation last, and only then point a model at what remains. Our next build is a WhatsApp assistant for member questions, and I expect it to work precisely because the unglamorous 70% underneath it is already done: identity is named, data has a home, and someone owns each exception.

Most companies run this backwards, with money. They buy the twelfth tool, demo the agent, and skip the plumbing, because budget lets you skip the thinking. The zero-dollar constraint would not let me. Which suggests a copyable trick even if you have budget: pretend you do not, for one quarter, and watch what order you do things in.

A volunteer nonprofit taught me more about stack discipline this year than any funded project did. If that is the kind of unglamorous work you want more of, that is exactly what the newsletter is for: The 70%.