One organisation for every event you run. One roster every night adds to.
Twelve nights and a summit a year. One organisation, one team, one list of people.
Attendees follow the organisation once and see every event it runs.
Give the team roles, not a shared password. Approve who joins from the same panel.
Team
A Players Club
- Nadia FerreiraOwner · since 2025Admin
- Tomas LindqvistRuns the Stockholm nightsAdmin
- Jonas BergJoined 12 MarMember
- Priya RamanJoined 22 AprMember
Requests
One club, one year
Every night adds to the same organisation, and the year adds up to a record.
The regular night, the roster between nights, the summit on the same account, and what you hold in December.
Step 1 of 4
Put the regular night up under the club, not under a new list.
New event · acting as
A Players Club
Filed under the organisation, beside the last one.
- Founders’ Night, MayThu 14 May · 19:00
- EntryRSVP, 80 places
- The doorQR check-in
Every event is created acting as the organisation that runs it. Take RSVPs or sell tickets, scan people in at the door, and the night is filed where the last one was.
One account, every organisation you run, switched from the sidebar.
Acting as
A Players Club
Scopes the events list, and stamps the next event you create.
- PersonalEvents under your own name
- A Players ClubAdmin · 13 events
- Stockholm Product CircleAdmin · 4 events
Public, unlisted or invite only. Requests wait for your approval.
Who may join
Invite only
Listed, and a tap on the page becomes a request you decide on.
- PublicListed, one tap to join
- UnlistedLink only, one tap to join
- Invite onlyRequest, then your approval
1 request waiting · an invite code skips the queue
Every email the organisation ever sent, across every event, in one history.
History
Every event, one log
- 13 MayFounders’ Night, MayReminder · 74 sent · 61 opened
- 22 AprAmsterdam Founders SummitYour ticket · 146 sent · 144 opened
- 2 MarFounders’ Night, MarchDoors open at 19:00 · 68 sent
- 1 FebAmsterdam Founders SummitEarly bird is open · 191 sent
Sent from each event’s Comms tab. Read from the organisation, in one place.
What changes when twelve nights run under one organisation instead of twelve lists.
The left column is a club’s own experience of a group chat, a ticketing link and a spreadsheet. Nobody else’s product is named, on purpose.
Who came, who came back, and which nights they chose, across the whole year.
The ones who came back.
Two nights or more, counted against each name by the door.
61
of 228 people came to two nights or more
Counted by the door, not by a survey
Who runs it.
Roles on the organisation, and the parts an event hands out on the day.
2
roles on the web. Admin runs it, Member sees it.
- Admins2
- Members226
- Per event, on topHost, co-host, door code
The roster, growing.
People on the organisation, month by month.
Nobody was imported. Every name walked through a door.
Thirteen nights, one record.
Checked in per event, the summit in blue.
Twelve nights and the summit in April, under one name.
A club is the room and the nights in it. Not a record of who paid.
Dues, subscriptions, the phone, and what it does not do yet.
It is the record membership software misses: the people who came to your events and what they came to, in one roster across every event you run.





