Date holds and enquiry follow-ups for wedding venues
Date holds and enquiry follow-ups for wedding venues is a SaaS idea for owners and sales managers at wedding venues, barns and country-house hotels, priced to test at $79 a month per venue. Couples ask to hold a date while they decide, and holds sit in a diary, an inbox and someone’s head. With it, wedding venues keep every enquiry, viewing and date hold in one calendar, with a reminder before a hold expires.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
Couples ask to hold a date while they decide, and holds sit in a diary, an inbox and someone’s head. Dates get promised twice, or stay blocked long after the couple went quiet.
Why now: Couples enquire with many venues at once through listing sites and social media, so quick, clear follow-up wins bookings.
What do they use today?
Most venues keep a wall planner or a shared calendar for dates, a separate inbox for enquiries, and a notebook for who promised to decide by when. Quotes are adapted from an old email each time.
How does it work?
An enquiry arrives from the website form or by email and lands in one list, where the sales manager books a viewing and gets a follow-up task for afterwards. When the couple asks for time to decide, the manager holds the date with an expiry, and the venue and the couple both get a reminder before it lapses. The quote goes out from a template, priced for the season and weekday.
What goes in the first version?
- A calendar of held, booked and open dates
- Enquiries from the website form and email in one list
- Hold expiry dates, with reminders to the venue and the couple
- Viewing appointments with a follow-up task after each one
- Quote emails from templates, priced by season and weekday
Who pays, and how much?
- Who pays
- Owners and sales managers at wedding venues, barns and country-house hotels
- Price to test
- $79 a month per venue
A venue sells a limited set of dates from one calendar, so a flat monthly price per venue matches how the business is organised. It covers the owner and sales manager alike, with no seat count.
How to test it in 7 days
- 1Ask five venue managers how they record date holds and what happened the last time one went wrong.
- 2Read wedding venue owner groups on Facebook for posts about double bookings and lost enquiries.
- 3Offer three venues a free setup of next season’s holds in return for weekly feedback.
Where to find the first customers
- Wedding venue owner groups on Facebook
- Local wedding fairs where venues exhibit
- Wedding suppliers who work across many venues
What are the risks?
- Venue management suites already cover holds, so the angle is speed and a low price.
- Venue teams are stretched in season, so importing the existing diary must be painless.
How to build it on shipanysaas
5 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
- Sign-in
- Teams and roles
- Billing
- Emails
- In-app notifications
- You build
- Date calendar with holds and expiry rules
- Enquiry inbox from web forms and email
- Quote templates and follow-up reminders
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 Date holds and enquiry follow-ups for wedding venues. 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: Wedding venues keep every enquiry, viewing and date hold in one calendar, with a reminder before a hold expires. - Who pays: Owners and sales managers at wedding venues, barns and country-house hotels - Their problem: Couples ask to hold a date while they decide, and holds sit in a diary, an inbox and someone’s head. Dates get promised twice, or stay blocked long after the couple went quiet. - Price to test: $79 a month per venue (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. A calendar of held, booked and open dates 2. Enquiries from the website form and email in one list 3. Hold expiry dates, with reminders to the venue and the couple 4. Viewing appointments with a follow-up task after each one 5. Quote emails from templates, priced by season and weekday ## Already in the kit: reuse it, never rebuild it - Sign-in: email and password or Google, plus magic links and passkeys you can switch on - 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 - Date calendar with holds and expiry rules - Enquiry inbox from web forms and email - Quote templates and follow-up reminders ## 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
Shared run sheets for wedding and event planners
Planners share the day’s timeline with every supplier from one link, and see who has confirmed each change.
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.