Shared run sheets for wedding and event planners
Shared run sheets for wedding and event planners is a SaaS idea for independent wedding and event planners running 10 to 60 events a year, priced to test at $29 a month per planner, unlimited events. The run sheet is a document emailed to every supplier and changed again and again. With it, planners share the day’s timeline with every supplier from one link, and see who has confirmed each change.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
The run sheet is a document emailed to every supplier and changed again and again. On the day, the photographer and the band work from different versions, and the planner fixes it by phone.
Why now: Suppliers already run their bookings from their phones, so a live timeline beats a printout that’s out of date by lunchtime.
What do they use today?
Planners usually build the timeline in a document or spreadsheet and attach it to group chats and email threads. Updates go out as new files, and nobody is sure who opened which version.
How does it work?
The planner builds the wedding timeline with times, places and contacts, then sends each supplier a link that opens without an account and highlights their own tasks. When the ceremony moves, the planner edits the time, each supplier gets an email with a button to confirm they have seen it, and the planner sees who has. The planner also prints a day sheet for the venue and the couple.
What goes in the first version?
- A timeline per event, with times, places and contacts
- A supplier link that opens without an account
- Each supplier’s own tasks highlighted on their view
- Change emails, with a button to confirm they’ve seen it
- A printable day sheet for the venue and the couple
Who pays, and how much?
- Who pays
- Independent wedding and event planners running 10 to 60 events a year
- Price to test
- $29 a month per planner, unlimited events
Planners run busy and quiet months, so one monthly price per planner, with no limit on events, is easy to plan around. Suppliers open a plain link, so only the planner pays.
How to test it in 7 days
- 1Ask five planners how they share timelines and what went wrong at their last event.
- 2Ask three photographers and bands what they wish planners sent them before the day.
- 3Rebuild one planner’s next run sheet as a mock-up and send it to their suppliers.
Where to find the first customers
- Wedding planner groups on Facebook
- Courses and associations that train wedding planners
- Venues that keep a list of recommended planners
What are the risks?
- All-in-one planning apps exist, so stay focused on the day and its suppliers.
- Suppliers ignore new tools, so their side must be a plain link with no sign-up.
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
- Timeline builder with supplier roles
- Supplier links and change confirmations
- Printable day sheet
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 Shared run sheets for wedding and event planners. 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: Planners share the day’s timeline with every supplier from one link, and see who has confirmed each change. - Who pays: Independent wedding and event planners running 10 to 60 events a year - Their problem: The run sheet is a document emailed to every supplier and changed again and again. On the day, the photographer and the band work from different versions, and the planner fixes it by phone. - Price to test: $29 a month per planner, unlimited events (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. A timeline per event, with times, places and contacts 2. A supplier link that opens without an account 3. Each supplier’s own tasks highlighted on their view 4. Change emails, with a button to confirm they’ve seen it 5. A printable day sheet for the venue and the couple ## 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 - Timeline builder with supplier roles - Supplier links and change confirmations - Printable day sheet ## 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: Hospitality and events
Guest lists and check-in for small tour operators
Guides see today’s guests with dietary and medical notes on their phone, and tick people in at the meeting point.
Virtual office mail handling for coworking spaces
Coworking staff log each letter and parcel with a photo, and members choose what happens next: scan, forward, collect or shred.
Rooming lists for hotel group bookings
Hotels send group organisers a link where guests add names and dates, with unclaimed rooms flagged before the cut-off date.