What it is
Most organizations run on six disconnected things: a spreadsheet of guests, a form for RSVPs, a ticketing site, a chat group with the caterer, a folder of photos and, at the end, someone counting by hand for the board. Roshym replaces the six with one record — and the night runs on the same data you planned with.
One-off events
Seating, ticket types, invitations, vendors and the door — with a public page of their own from the minute they are created.
Recurring programming
A weekly class, a daily service, a Friday dinner with tables: capacity, waitlists, memberships and attendance per session.
Money
Ticket sales, donations added at checkout, crowdfunding pages, sponsorships and numbered receipts for donors.
Everything you can do
For your organization
Not features — consequences. These are the things that stop happening the week your calendar moves in.
| What used to happen | What happens now |
|---|---|
| Two lists that never match — the spreadsheet says one thing and the door says another. | One record. Move a guest to another table and the check-in screen already knows; cancel a seat and the waitlist moves by itself. |
| A hall over capacity, and an inspector asking how you controlled it. | Every space carries its legal capacity. Registration stops there, the waitlist takes over, and check-in produces a timed attendance list you can hand over. |
| Chasing families one by one to find out who is coming and what they eat. | One account per household: an adult registers, pays and follows everyone under their roof, and allergies travel with each person into the kitchen's list. |
| The caterer called at midnight because the headcount changed again. | The order is built from who is actually registered, with meal choices counted and the allergen list attached — and it flags when the number drifts. |
| Donations in a notebook and receipts written by hand in January. | Giving history per family, sequential receipts with your details and footer, recurring gifts marked as such, campaigns with a live total. |
| Everyone seeing everything — the caterer holding the full guest list. | Roles: the office sees the roster, each vendor sees only their own service in the event that hired them, and the public sees only what you publish. |
| The board asking for numbers and someone losing a weekend to them. | Attendance, no-show rate, income by source and participation trends on one printable page, for any period. |
| Photos scattered across ten phones and never seen again. | Guests upload straight into the event album from their own portal, tagged with the challenge, voted by the room and published on a page you can share. |
It keeps working
Check-in holds when the venue's connection drops and syncs when it returns. The queue at the entrance does not care about the WiFi.
It says what happened
If something does not save, does not send or does not charge, the screen says so. Nothing is ever marked done that was not done.
It travels
The office computer, the phone at the door and the member portal read the same workspace, with the sync status always in view.
Getting started
Step 1
The console asks for it the first time you walk in. That name becomes your member portal address and the header on every receipt.
Step 2
Create the first event or the first recurring class. Each one is born with its own public page and a link to share.
Step 3
Share the portal link once. Families register themselves, pick their meal, add a donation and keep their own QR pass.
Step 4
Scan at the door, watch the room fill, send the reminder, and read the report the next morning.
Before you ask
Card payments run in test mode until the keys are configured. The whole checkout is built — tickets, donations, recurring gifts, sponsorships — and while it is in test mode it records the amounts for reporting and charges nothing, saying so on screen. It never pretends a payment happened.
Formal compliance instruments are not in place yet. No public-sector purchasing vehicle, VPAT, StateRAMP or FedRAMP authorization, no DoD impact level, and a FERPA/COPPA agreement on request rather than as a standard document. Ask before you build a solicitation on any of them.
Roshym is the software, not the host. Each event belongs to its organizer, who is responsible for its content, permits, safety and everything promised to its guests.
The AI drafts, you decide. Budgets, schedules, texts and images come out as drafts. Read them before they reach a guest or before money is committed to them.
