# Rooming lists for hotel group bookings

Rooming lists for hotel group bookings is a SaaS idea for reservations managers at independent hotels with wedding, sports and conference groups, priced to test at $59 a month per hotel. Group organisers send rooming lists as spreadsheets, late and full of gaps, then keep changing them. With it, hotels send group organisers a link where guests add names and dates, with unclaimed rooms flagged before the cut-off date.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

Group organisers send rooming lists as spreadsheets, late and full of gaps, then keep changing them. Reservations staff retype every name, and unused rooms are released too late to resell.

**Why now:** Guests already manage their own bookings online, and stretched hotel teams have no time to retype lists by hand.

## What do they use today?

Most hotels ask the organiser for names by email and phone, take whatever list comes back, and key it in by hand. Gaps are often noticed only when the cut-off date is close.

## How does it work?

The reservations manager sets up a group block with room types, rates and a cut-off date, then sends the organiser a link to share with guests. Guests add names, dates and requests without an account, and as the cut-off date nears the organiser gets reminders while unclaimed rooms are flagged. The reservations team then takes a clean export for the hotel’s booking system.

## What goes in the first version?

- A group block with room types, rates and a cut-off date
- A link for the organiser to share with guests
- Guests add names, dates and requests without an account
- Reminders to the organiser as the cut-off date nears
- A clean export for the hotel’s booking system

## Who pays, and how much?

- **Who pays:** Reservations managers at independent hotels with wedding, sports and conference groups
- **Price to test:** $59 a month per hotel

An independent hotel has one reservations desk and takes groups through the year, so a flat monthly price per hotel is easy to budget. Organisers and guests only use a link, so only the hotel pays.

## How to test it in 7 days

1. Ask five hotel reservations managers how they collect rooming lists and what goes wrong.
2. Ask two people who organised a wedding or team trip how they gathered names for the hotel.
3. Offer to run one upcoming group through a mock-up and time it against the spreadsheet.

## Where to find the first customers

- Hotel reservations and revenue groups on LinkedIn
- Independent hotel associations
- Hotel sales consultants who work with independents

## What are the risks?

- Hotel booking systems may add group tools, so integrate cleanly rather than compete.
- Organisers may still send spreadsheets, so importing one must be easy.

## How to build it on shipanysaas

4 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:** Teams and roles, Billing, Emails, In-app notifications

**You build:**

- Group blocks with cut-off dates
- Guest sign-up page without an account
- Export for the hotel’s booking system

[Get the kit](https://shipanysaas-demo.vercel.app/pricing)

### The starting prompt

```text
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 Rooming lists for hotel group bookings.

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: Hotels send group organisers a link where guests add names and dates, with unclaimed rooms flagged before the cut-off date.
- Who pays: Reservations managers at independent hotels with wedding, sports and conference groups
- Their problem: Group organisers send rooming lists as spreadsheets, late and full of gaps, then keep changing them. Reservations staff retype every name, and unused rooms are released too late to resell.
- Price to test: $59 a month per hotel (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. A group block with room types, rates and a cut-off date
2. A link for the organiser to share with guests
3. Guests add names, dates and requests without an account
4. Reminders to the organiser as the cut-off date nears
5. A clean export for the hotel’s booking system

## Already in the kit: reuse it, never rebuild it
- 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
- Group blocks with cut-off dates
- Guest sign-up page without an account
- Export for the hotel’s booking system

## 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

- [How to add Stripe embedded checkout to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-stripe-embedded-checkout)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://shipanysaas-demo.vercel.app/blog/multi-tenant-saas-teams-roles-invitations)
- [How to add in-app notifications to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-in-app-notifications)

## More ideas: Hospitality and events

- [Gift vouchers for B&Bs and small hotels](https://shipanysaas-demo.vercel.app/saas-ideas/guesthouse-gift-vouchers): B&Bs sell gift vouchers on their own site, email a printable gift, and check each code when the guest books.
- [Changeover-day cleaning board for holiday parks](https://shipanysaas-demo.vercel.app/saas-ideas/holiday-park-changeover-board): Cleaners mark each lodge or caravan clean and checked on their phones, and the office sees what’s ready for arrivals.
- [Date holds and enquiry follow-ups for wedding venues](https://shipanysaas-demo.vercel.app/saas-ideas/wedding-venue-date-holds): Wedding venues keep every enquiry, viewing and date hold in one calendar, with a reminder before a hold expires.

- [All SaaS ideas](https://shipanysaas-demo.vercel.app/saas-ideas)
- [Try the free generator](https://shipanysaas-demo.vercel.app/saas-ideas#generator)