Skip to main content
W
Who's In
Built for university society committees

Run your society without losing weekends to admin

Free RSVPs for socials and trips. Member-only gating for paid events. Annual dues collection through Stripe. Committee handover that doesn't lose all your data each summer. WhatsApp + Discord share built in.

Freefor student society events
Annualcommittee handover built in
Discord + WhatsAppshare built in

Society admin is a job. It shouldn't take all your free time.

Running a university society means you're juggling dues collection, Wednesday socials, monthly trips, freshers' fair, end-of-year ball, AND a committee handover every summer. Most committees rebuild their RSVP process from scratch every year because the old data lived in someone's personal email.

Who's In is built for community organising — which student societies are. One platform for all your events. Annual dues through Stripe. Member-only gating for paid trips. Weekly socials with capacity caps. Trip deposits with cancellation policies. CSV export of your full member list at handover time so the next committee inherits a real database.

Free for free events. 2.7% on paid trips, dues, and ball tickets — significantly less than the Students' Union's standard event fees.

Sound familiar?

You're not alone. These are the challenges we hear every day.

Every committee starts from scratch

Last year's social secretary kept her events in her own Google Sheet. She graduated. The new committee can't access it. You're rebuilding the membership database from a Discord thread for the third year in a row.

~70% of student societies lose continuity at annual handover

Dues collection is a manual chase

£20 annual society membership. 60 members. You're chasing payment via Discord, splitting between two PayPal accounts (yours and the treasurer's), no clean record of who paid what when.

Avg society treasurer spends 8+ hours/term on dues collection

Member-only gating is a manual gate

Friday social is members-only. Members + their friends try to book. You're manually checking the membership list, messaging non-members to "please join the society first". Awkward.

~30% of "member-only" events get gatecrash attempts

Trip deposits + cancellation are a finance nightmare

Society trip in 2 months. £80 deposit. People drop. Refunds need approval from the treasurer. The cancellation policy lives in a Google Doc no one reads. Disputes happen.

Avg society trip: 15-20% drop-out rate, 50% with disputed refunds

Built for the society year, not just one event

Annual dues collection

Set the £20 annual fee. Stripe collects from each member at signup. Funds go to the society's account directly. CSV export for the treasurer. Renewal reminder emails the following year.

Member-only event gating

Mark an event as "members only". Only people on your active member list (paid dues this year) can book. Non-members see "join the society first" with a one-tap dues-payment flow.

Recurring weekly socials

Wednesday 7pm pub social, set up once for the academic year. Each week's instance is created automatically. Edit one specific week's location without breaking the recurring pattern.

Trip deposits + cancellation policies

Set the deposit (£80) and the cancellation deadline. Refunds run automatically through Stripe per your policy. No more refund disputes. Members see and accept the policy at booking.

Committee handover that survives

Add committee members as admins. When you graduate, the next committee inherits the full member database, event history, and Stripe account. Continuity. No annual rebuild.

Discord + WhatsApp + email reach

One link works everywhere your society lives — Discord, WhatsApp, Instagram bio, society website. Members find their event without you posting it 6 places.

Three societies, three setups

Society of 80 members, weekly socials + monthly trips

Free Events tier. £20 annual dues via Stripe. Member-only Wednesday socials. Public freshers' fair welcome event. Monthly trips with deposits + cancellation policy. CSV handover at end of year.

Sports / climbing / outdoor society

Studio plan ($15.83/mo annual). Annual £30 dues. Weekly trips with waiver acknowledgment. Equipment hire bookings. Insurance documentation collected at signup. Trip deposits + balance.

End-of-year ball, 200 attendees, £45/ticket

Free Events tier with paid bookings. Multiple ticket tiers (member £45, guest £55, table-of-10 £400). Apple Wallet ticket. Dietary + accessibility collection. 2.7% Stripe = ~£10 vs Eventbrite's £25+ per ticket.

Why student societies leave the SU's standard tools

vs Students' Union event system

Often takes 5-10% per ticket on paid events, doesn't handle dues collection, has clunky member-only gating, and the data doesn't survive the committee handover.

vs WhatsApp + PayPal

Fine for 8 friends. Breaks at 60+ active members. No dues record, no member-only gating, no cancellation policy, no handover survival.

vs Eventbrite + Google Sheet

Eventbrite charges 6%+ on tickets. The Google Sheet member database is in someone's personal Google Drive. Both fail at handover.

“Our society had been losing all its data every year because each committee used different tools. We standardised on Who's In two years ago. Annual dues, weekly socials, the end-of-year ball — all in one place. The new committee inherits a real database. Game-changer.”
DC
David Chen
Committee chair · Photography Society, University of Edinburgh

Frequently asked

Real questions from university society leaders.

Can we collect annual dues through the platform?
Yes. Set up "Annual Society Membership 2026" as a paid event. Members pay £20 via Stripe at signup. Funds go to the society's Stripe account directly. CSV export of paid members for the treasurer.
Can we restrict events to paid-up members only?
Yes. Mark an event as "members only". Only people on your active member list (paid this year's dues) can book. Non-members see "join the society first" with a one-tap dues-payment option.
What about committee handover at the end of the year?
When the new committee takes over, transfer admin access. They inherit the full member database, event history, Stripe account, and email templates. No more rebuilding from scratch every year.
Can we set cancellation policies for trips?
Yes. Each trip has its own cancellation policy — typically full refund 60+ days out, partial refund 30-60 days, no refund inside 30 days. Stripe runs refunds automatically per your policy. No disputes.
How does the cost compare to our SU's event system?
Most SU systems take 5-10% on paid events plus per-ticket fees. Who's In is 2.7% flat. On a £45 ball ticket: SU ~£3-£5 fee, Who's In ~£1.20. On 200 tickets, that's £400-£800 saved — significant for a society budget.

Run your society like the platform actually exists for you

Free for free socials. Annual dues + trip deposits via Stripe. Handover that survives.

Free for free society events
2.7% on dues, trips, and ball tickets
Member-only gating built in
Committee handover survives the academic year

We use essential cookies to keep you logged in and optional analytics to improve our service. See our Privacy Policy.