Events App Starter · Industry version
Nonprofit Event Template
Fundraising events without platform fees — sponsors, tables, and donations modeled in code your organization owns.
A fundraiser isn't ticket sales — it's a room full of relationships with a revenue goal. This starter models what galas actually run on: sponsorship tiers, table assignments, and donations attached to registrations, generated as code your organization owns instead of a platform taking points off the top.
- 6 core entities
- No per-ticket fees
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic Events falls short
The math is different at a fundraiser. A gala ticket might be $250 with an $80 fair-market-value dinner behind it, which makes $170 of it a tax-deductible gift that needs an acknowledgment letter. Generic ticketing sees one price and one line item — and your bookkeeper spends February reconstructing the split.
The room is also an object. Galas run on tables: a sponsor buys one, fills eight of ten seats, and the development director spends the final week seating the rest by relationship, not alphabetically. A platform without tables reduces the seating chart to a spreadsheet taped over the real system.
And the buyer often isn't the attendee. Sponsors register blocks under a company name with attendees arriving later, one by one, via an assistant. Ticketing flows built for individual buyers make block management a chain of forwarded emails — precisely where gala logistics go to die.
02 · Data model
The data model, adapted
Everything in the base Events starter —
eventsticket_typesregistrationsattendeescheck_inspromo_codes— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
donations | Gifts attached to registrations or standing alone — amount, deductible portion, and acknowledgment status. |
sponsorships | Sponsor commitments with tier, benefits owed, payment status, and the tables and seats included. |
seating_tables | Physical tables with capacity, sponsor ownership, and per-seat attendee assignments. |
03 · Screens
Modules through the industry lens
Event pages that ask for the gift
01Registration flows carry an add-a-donation step and honor sponsor-tier pricing, and the confirmation records the deductible split. Supporters who can't attend get a donate-instead path — often the quiet second revenue line of the night.
Registration with tables and blocks
02Sponsors register blocks of seats that fill over time, and the seating chart is a live view of tables and assignments rather than a separate document. When the board chair moves two guests the Friday before, it's a drag, not a re-print.
Check-in that knows the relationship
03The door screen shows each arrival's table, sponsor affiliation, and outstanding balance, so a major donor is greeted by name and walked to their seat. Arrival timestamps also tell you who to call before the paddle raise starts.
04 · In practice
Workflows it models
Gala season, one system
01Open sponsor commitments in spring, publish the event in summer, fill tables through fall. Sponsorships, registrations, donations, and seats accrue in the same database, so the revenue-to-goal number is live all season.
Sponsor block fulfillment
02A gold sponsor's two tables enter as twenty seats under their commitment. Their coordinator fills names over six weeks; unfilled seats surface in the final week for the development team to reassign — no forwarded-email archaeology.
Post-event acknowledgment run
03The morning after, the acknowledgment queue lists every deductible gift with the right split and attendance status. Letters go out in days while the memory is warm — which is when the follow-up gift conversations happen too.
Nonprofit Events template — frequently asked questions
Can it handle sponsorships and table seating?
Yes — sponsorships carry tiers, benefits, and blocks of seats, and tables are real entities with capacity and per-seat assignments. The seating chart is a screen over live data, not a document that forks from reality the week of the event.
Does it track the tax-deductible portion of tickets?
Each registration and donation records its deductible split based on fair market value, and the acknowledgment queue generates from those records. February reconciliation becomes a report, not a reconstruction.
We run a golf outing and a 5K too — does it stretch that far?
The base handles any registration-driven event, and because you own the code, format-specific fields — foursomes, race waves, pledge-per-mile — are additions to your schema rather than a different product.
How does this relate to donor management software?
This starter runs the events; a donor CRM runs the year-round relationship. They pair naturally — event donations and attendance export cleanly from tables you own — and there's a dedicated donor CRM starter built on the same conventions.
Related
Dual7 App Starters
Build your Nonprofit Events on your terms
Fundraising events without platform fees — sponsors, tables, and donations modeled in code your organization owns. Describe your version to start — the output is a project you own.