Member directory and event sign-ups for clubs
Member directory and event sign-ups for clubs is a SaaS idea for volunteer organisers of clubs, alumni groups and small associations, priced to test at $15 a month for up to 200 members. Member data lives in an old spreadsheet, a mailing tool and a chat group that never match. With it, alumni groups, hobby clubs and small associations keep one member list, a private directory and event sign-ups.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
Member data lives in an old spreadsheet, a mailing tool and a chat group that never match. Organisers can’t tell who is active, and every event needs a new sign-up form.
Why now: Many groups want a member list they control, instead of a chat group or a page on a social network.
What do they use today?
Organisers keep names in a spreadsheet or a notebook and announce events by email or in a group chat. Sign-ups come as replies in the thread, and renewals depend on a volunteer remembering to ask.
How does it work?
A volunteer organiser adds the members, and each member signs in to update their own details, so the list stays current without the organiser retyping anything. Members browse the private directory, which only members can see, and sign up for the next event from its page. The organiser checks the attendee list, emails an announcement to everyone or one group, and renewal reminders go out as memberships near their end.
What goes in the first version?
- A member list with profiles members update themselves
- A directory only members can see
- Event pages with sign-ups and attendee lists
- Email announcements to everyone or a group
- Renewal reminders
Who pays, and how much?
- Who pays
- Volunteer organisers of clubs, alumni groups and small associations
- Price to test
- $15 a month for up to 200 members
A flat price for a set number of members suits a volunteer group, because the committee agrees one fixed amount. It replaces the old spreadsheet and the sign-up forms organisers rebuild for each event.
How to test it in 7 days
- 1Ask five organisers you know how they keep their member list.
- 2Read r/nonprofit for posts about member management.
- 3Offer to move one club’s spreadsheet over for free.
Where to find the first customers
- r/nonprofit
- Alumni associations and hobby federations
- Local meetup organisers
What are the risks?
- Volunteer-run groups have small budgets.
- Collecting member dues needs Stripe Connect, which you would add yourself.
How to build it on shipanysaas
5 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.
- Already in the kit
- Sign-in
- Teams and roles
- Billing
- Emails
- In-app notifications
- You build
- Member profiles and a private directory
- Event sign-ups
- Renewal reminders
See the starting prompt
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Member directory and event sign-ups for clubs. Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it. ## The product - What it does: Alumni groups, hobby clubs and small associations keep one member list, a private directory and event sign-ups. - Who pays: Volunteer organisers of clubs, alumni groups and small associations - Their problem: Member data lives in an old spreadsheet, a mailing tool and a chat group that never match. Organisers can’t tell who is active, and every event needs a new sign-up form. - Price to test: $15 a month for up to 200 members (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. A member list with profiles members update themselves 2. A directory only members can see 3. Event pages with sign-ups and attendee lists 4. Email announcements to everyone or a group 5. Renewal reminders ## Already in the kit: reuse it, never rebuild it - Sign-in: email and password or Google, plus magic links and passkeys you can switch on - Teams and roles: team accounts with members, roles and invitations - Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments - Emails: transactional email through Resend or Nodemailer - In-app notifications: a notifications bell in the web app ## New code it needs - Member profiles and a private directory - Event sign-ups - Renewal reminders ## How to work 1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK. 2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files. 3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next. ## Rules - Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel. - Leave the parts of the kit this product doesn't use as they are. Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
Guides for the parts it uses
Want ideas for your own skills?
The free generator writes three while you watch, each with a plan and a starting prompt. Or paste this idea into it for two sharper versions.
More ideas: Creators
Listener questions inbox for podcasts
Podcasters collect listener questions and voice messages from one link, tag the best ones, and plan them into episodes.
Guest writer pitches and drafts for newsletters
Newsletters that publish guest writers collect pitches through one form, review them as a team, and track drafts to publication.
Attendance and certificates for live cohort courses
Course creators running live cohorts track who attended and handed in work, nudge students who fall behind, and issue completion certificates.