NonprofitRun
- People and supporters
- Volunteers
- Events and tickets
- Newsletter and updates
- Board and records
TicketsVolunteersBoard guestsNewsletterOne record
For nonprofits and charities
Run your whole mission. From one platform.
People, volunteers, events, newsletters and your board, on one record per person instead of five spreadsheets.
- One login
- One record per person
- No spreadsheets
NewslettersEventsBoardVolunteers
Example data
AudienceMembers · Subscribers
3people
- AOAmara OkaforVolunteer
- PNPriya NatarajanSubscriber
- LBLeah BrennerVolunteer
The whole idea
One supporter. One record.
The volunteer who came to the gala and reads your update is one name, not three spreadsheet rows.
The five jobs
From the first name to the minutes
Five jobs a small team does every month. Each one is a room in the same building, so a change in one is already true in the rest.
- 01
People and supporters
One record per person, found by email. Search, filter and tag people (a supporter does not have to be a member), and import your spreadsheet with a consent step and an undo.
- 02
Volunteers
Roles and shifts that members and guests claim for themselves. A waiver signed once, a tracker for background checks, check-in that writes the hours, and a year-end hours statement.
- 03
Events and tickets
Free or paid tickets, guests who register without an account, QR check-in at the door, and sponsor packages for your gala. Paid tickets go to your own Stripe account.
- 04
Newsletter and updates
A block editor, a send sheet with a test send, audiences by tag, results per issue, and a public news page whose subscribe form needs a confirming click.
- 05
Board and records
Meetings, agendas, minutes that are circulated and approved, attendance, action items and a trail of what changed. Board-only people are supported.
The whole iceberg
One page above the line. Five jobs below it.
5 of 5 jobs covered
A supporter sees one friendly page. You carry five jobs underneath, from the list to the minutes. Then the turn: one record runs through every layer, so none of them has to be reconciled with the rest.
One record. A person is one record, found by email, so the volunteer, the ticket buyer and the newsletter reader are the same row.
Hover, focus or tap a layer to read it
Walk the hall
Now, where each job lives
The same five jobs, this time as rooms in a community hall. Walk the floor to see where each one sits and how one corridor reaches every door.
Five rooms, one corridor: that corridor is the supporter record. Hover, focus or tap a room to read its job.
How it starts
Start with your list
Three steps, and you do not have to move everything at once.
Tell us about your organization
The form at the bottom of this page. A few lines about who you are and what you run.
Import your list from a spreadsheet
A guided import with a consent step, tags, and an undo for the whole import if something looks wrong.
Post your first volunteer role or event
One shift or one event is enough to see the record start to fill.
Try it
Three small things you can touch
Gala week, before and after
Drag the torn edge, or focus it and use the arrow keys.
Ticket list
Paid? Which one?
Volunteer sheet
am I on for Sat?
check the sheet
Board guest list
Same people again?
Newsletter draft
Volunteers only?
built from memory
Right side: a real, cropped screenshot of the Volunteers overview, on demo data. Left side: an illustration of the patchwork, no real tools named.
One person, four hats
Pick a sample person to see the one record. Then choose tags to see who an email would reach.
Sample record, EXAMPLE DATA
Sample supporter A
One row. Four hats.
Email these people
Choose tags. People who carry every chosen tag are included.
Illustration with sample people. Nothing is sent anywhere.
Cleared before the day
This role needs a signed waiver and a current check. Try to apply, then fix what is blocking you.
Sample volunteer, signed in as a member
Kids’ corner, adult
This role requires: waiver, background check.
Waiver
Not signed
Background check
Expired in March
Blocked: sign the waiver, and the check needs renewing.
- Waiver. One active, versioned waiver, signed with a typed name. A new version invalidates earlier signatures. You can ask for an annual re-sign.
- Checks. You define the types and record each person’s status. Reminders go out 30, 7 and 1 days before expiry, and the status flips to expired the day after.
- Who is blocked. Signed-in members cannot apply until they have what the role requires. Guest applications skip the gate and staff review them.
Illustration with sample data. Nothing is sent anywhere.
Three more things to touch
Fill the roster. Check them in. Open the door.
Claim a shift the way a volunteer would. Then switch to staff mode and mark people in, or scan guests in at the gala door.
Roster
Tap Claim on a shift. Try the full one, then claim two shifts that overlap.
Sample volunteers and sample hours. Checking in writes the hours and runs the same side effects as an approval: points, badges and audit. Undo reverses it. Hour badges are seeded at 25, 100, 250 and 500 hours and can be edited.
Sample guests. A guest registers without an account and is checked in at the door, by QR badge or by staff. Capacity is decided as each person registers.
What it does for your week
One list that is right. Hours that write themselves.
The saving is not a speed trick. People are on one list instead of three, volunteers are cleared before the day, and hours are written the moment someone is checked in.
Comes off your desk
- Opening three files to answer “am I on for Saturday?”
- Keeping the same person in a ticket list, a volunteer sheet and a board list.
- Building the volunteers-only list from memory.
- Chasing people to sign the waiver before the day.
- Retyping sign-in sheets into hours.
Gets added
- One record per person, with tags for who they are.
- Shifts that members and guests claim for themselves.
- A newsletter narrowed by tag, with consent handled.
- Gala tickets and check-in, with the money going to your own Stripe account.
- Minutes, actions and attendance in one place for the board.
Who needs an account
Guests and volunteers by private link need none. Staff and members use a normal login. Turn a badge over to see what each person does.
Pricing, in plain words
No price list yet. Ask us.
There is no price list on this page yet. Tell us about your organization, roughly how many supporters and volunteers you have and what you run, and we will talk about pricing for it.
- NONPROFITRUN
- price on request
- YOUR PLAN
- FIVE JOBS
- BASED ON: supporters, volunteers a year, what you run
What is not here yet
We would rather tell you what is not built
Better you hear it from us now than find it out after you sign up.
Not here yet
- Donations. No giving page, no one-time or recurring gifts, no donor records.
- Tax receipts. Nothing here issues one. The volunteer year-end statement shows hours, and that is all it is.
- Grant management, case or client tracking, and accounting sync.
Here today
- Ticket sales and sponsor packages for your events, paid straight to your own Stripe account.
- The people side: one list, volunteers, events, newsletter and board.
- Whatever you use to take gifts today can keep doing that. Nothing here needs to replace it.
Questions
The honest answers
Not yet.
There is no giving page and no donor records. Ticket sales and sponsorship payments do work, and go straight to your own Stripe account.
Not yet.
Nothing here issues a tax receipt. The volunteer year-end statement is an hours statement, not a receipt.
Yes.
Guests give a name, email and phone. They need no account, and they see their hours from a private link. Members use their normal login.
Yes.
Free or paid tickets. Guests register without an account, capacity is decided as each person registers, and paid tickets go to your own Stripe account. You can add sponsor packages too.
Yes.
A guided import with a tags step, a consent step and a warning about addresses you have suppressed. If something looks wrong, undo the whole import.
Ask for pricing
Tell us what you run
Fill in the badge on the left as you go. We will write back about pricing for your organization.
Received.
We will read what you run and write back to about pricing for your organization.
Until then, nothing is public and nothing is charged.
Screens show example data. Photography: stock.