The Normandy Park Police Foundation is a community-based 501(c)(3) in Washington State. It supports the Normandy Park Police Department and the people it serves: Blockwatch and crime prevention education, Shop with a Cop, Paws on Patrol, and officer appreciation. It is run by a board and volunteers, not a paid staff.
The Foundation engaged me to build its online presence. The obvious answer would have been a website: a few pages, a donate button that goes to a third-party form, a newsletter signup that goes to a mailing service, a shared drive for documents, and a spreadsheet for everything else.
We didn't build that. We built one platform that runs the organization.
The problem with the "website plus subscriptions" model
Most small nonprofits end up with the same stack by accident. The website is on one vendor. Donations go through a second. Email lives with a third. Member or volunteer records sit in a fourth, or in a spreadsheet nobody fully trusts. The board's documents are in a shared folder, and the filing deadlines are in someone's head.
None of these tools know about each other. A donor who gives online, signs up for the newsletter, and volunteers for a program is three different records in three different systems. Every tool has its own login, its own monthly fee, and its own idea of how a nonprofit should operate. The organization spends its time adapting to the software instead of the other way around.
For a volunteer-run foundation, that overhead is the difference between a program that happens and one that doesn't.
What one platform looks like
The NPPF platform is a single custom application. One login, one data model, one place for everything the Foundation does online. Here is what it covers.
Giving. Donors can give once without creating an account, by card, PayPal, or Venmo. They choose which fund their gift supports: the General Fund, or a program fund such as Shop with a Cop or officer appreciation, training, and equipment. Program funds pay only for their program. Donors can optionally cover processing fees. Receipts go out by email after every gift. With a free account, donors can set up monthly or yearly gifts, change or stop them on their own, and pull year-end statements from their account page.
Blockwatch. Normandy Park has twelve numbered Blockwatch provinces. The platform includes a Province Finder that locates a resident's province by address or map, a membership request flow, and a private desk where province volunteers confirm new members. Confirmation happens the way neighbors actually do it: in person, by door card, or through a vouching neighbor. Member contact details stay among neighbors. If someone leaves, their personal details are cleared.
Emergency preparedness. The Foundation's printed preparedness guide is published on the site. Anyone can read it and tick through the checklists on their own device. Account holders can save a personal preparedness plan with household planning and contacts, print it, and download the guide as a PDF. The plan is visible only to the account holder.
News, documents, and the newsletter. Editors write and schedule news with photos, galleries, and tags. Everything starts as a draft and is approved before it publishes. The documents library holds annual reports, Form 990s, minutes, flyers, and bylaws. The newsletter uses double opt-in, every email has an unsubscribe link, and account holders choose which types of email they receive. Site search covers all of it.
The back office. Behind the public site, the platform includes a board room for board records and minutes, a tracker for IRS, state, insurance, and other filing deadlines with automated reminders, and a grant desk for scouting and scoring funder programs, logging expenses with receipts, checking budgets, and tracking reimbursements.
Accounts and roles. Sign-in is by emailed link, with an optional password. Access is limited by role: administrators, editors, Blockwatch volunteers, grant volunteers, and board members. Gift records are visible only to administrators and the Treasurer. Changes are logged.
The basics done properly. The site is mobile-first, targets WCAG 2.1 AA, supports keyboard use, respects reduced-motion settings, and follows the device's dark mode preference. Analytics are cookieless and collect no personal data.
Why custom, not configured
Every item above could be approximated with an off-the-shelf product. None of them could be done the way the Foundation actually operates.
A donation vendor doesn't know that the Treasurer is the only person who should see gift records, or that Shop with a Cop money has to stay with Shop with a Cop. A membership product doesn't know that Blockwatch confirmation happens at the front door, not by phone, or that Normandy Park has twelve provinces with their own volunteers. A document tool doesn't know which files are public and which require a free account. A generic admin panel doesn't know that the Foundation's real administrative load is filing deadlines and grant paperwork.
When the software is built for the organization, those rules are the design. They aren't workarounds layered on top of someone else's product, and they don't break the next time a vendor changes its pricing or its feature set.
The result is a platform the Foundation's board and volunteers can run themselves. Editors publish. The Treasurer reconciles. Province volunteers confirm their neighbors. The board tracks its deadlines. Nobody needs to know how it was built to use it.
What comes next in this series
Over the next several weeks I'll walk through each part of the platform and the decisions behind it:
- Donations that match the chart of accounts, not the vendor's template
- Blockwatch: a membership system no off-the-shelf product could have shipped
- Content, newsletter, and documents in one editorial workflow
- The back office: board room, filing deadlines, and grant tracking
- One account, every role: members, volunteers, editors, and board
- What a custom platform costs to run
If this sounds like your organization
We work with nonprofits and mission-driven organizations that have outgrown the website-plus-subscriptions model but don't have the budget or staff for enterprise software. The engagement starts with a free assessment: We look at how your organization actually runs, what it's paying for, and where the manual work is, and tell you plainly what a purpose-built platform would and wouldn't change.