Skip to content
Brian Kudera

§ THE WORK

The Nonprofit Back-Office

One platform to run a small charity — website, shared inbox, photos, and donations — without a team of staff or a stack of subscriptions.

The problem

Most small nonprofits are run by volunteers in their spare time: mission-rich and operations-poor. The 'official' inbox is one person's personal Gmail, and when that person is away, messages from families and donors go unanswered. Hundreds of event photos pile up untitled and never reach the site. The website is a brochure nobody can edit, so it goes stale. Donations, volunteer sign-ups, and event listings each live in a different tool with a different login and a separate bill. The board spends its limited hours fighting tooling instead of serving the people they exist to help.

The idea

A back-office built for the organization that doesn't have one. Not another website builder — a single, opinionated platform that handles the unglamorous operational work a small nonprofit actually does every week: answering mail, publishing events, sharing photos, and collecting donations. The public website is the front door; the value is everything behind it. It grew out of a real, in-production system for a 501(c)(3) serving seniors and veterans.

What's inside

A real shared inbox — on the org's own domain

Mail to the organization's address lands in a shared, threaded inbox the whole board can read, reply to, and manage together. Replies go out from the org's address; attachments are handled automatically. No more 'I thought you answered them.'

A photo library that organizes itself

Upload the photos from the event and the system does the tedious part: it writes captions, tags content, recognizes recurring faces, flags duplicates, and crops each image for every screen. Pictures actually make it onto the site, looking good.

Events & galleries anyone on the board can publish

Create an event, mark it published, attach a gallery, and it's live. Drafts, cancellations, and write-ups are built in. No developer, no ticket, no waiting.

Donations and volunteer sign-ups, built in

A donate button and volunteer intake form are part of the platform, not a bolted-on third-party widget with its own login and its own monthly fee.

Multi-user admin with real security

Invite board members, each with their own login. Sessions are secure, passwords are hashed, sign-in supports Google, and access is revocable the moment someone leaves — the standard you'd expect from software handling a donor's information.

Swap the look without touching code

Photos and key settings are editable from the admin panel — the organization controls its own imagery and configuration without calling a developer for every change.

Why it matters

Without itWith the back-office
Official email lives in one volunteer's personal GmailA shared inbox on the org's own domain the whole board manages
Photos pile up unsorted and never reach the siteA self-organizing library that captions, tags, and publishes
The website goes stale because nobody can edit itBoard members publish events and swap photos themselves
4–5 separate tools, 4–5 logins, 4–5 billsOne platform, one login, one bill
Continuity breaks every time a volunteer leavesThe org owns its identity, history, and data

Who it's for

  • Small 501(c)(3)s and community charities run by volunteers
  • Faith groups, service clubs, booster organizations, and mutual-aid groups
  • Any mission-driven group with more heart than headcount, tired of duct-taping free tools together

Built on a production foundation

  • A working, deployed system — Next.js and React with a Postgres database — running live for a real nonprofit.
  • Battle-tested, with an extensive automated test suite guarding every release.
  • Cloud-native: infrastructure-as-code, separate staging and production, zero-downtime releases, AI-assisted where it saves real time.