Changeover-day cleaning board for holiday parks
Changeover-day cleaning board for holiday parks is a SaaS idea for managers of holiday parks and lodge sites with 20 to 300 units, priced to test at $89 a month per park. On changeover day, the office phones cleaning teams all afternoon to ask which units are ready. With it, cleaners mark each lodge or caravan clean and checked on their phones, and the office sees what’s ready for arrivals.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
On changeover day, the office phones cleaning teams all afternoon to ask which units are ready. Guests wait at reception, and damage found during cleaning gets mentioned days later, if at all.
Why now: Short breaks mean more changeovers each week, and every cleaner already carries a phone that can replace the paper list.
What do they use today?
Most parks print the day’s arrivals for the office and hand each team a paper list. The rest is calls, texts and walks across the site to find out which units are ready.
How does it work?
On changeover day the office imports the day’s departures and arrivals, then assigns units to teams with early arrivals first. Each cleaner marks a unit cleaned on their phone, it is then inspected, and any damage or missing item goes in with a photo. The office board shows every unit as ready, in progress or waiting, so reception knows what to tell arriving guests.
What goes in the first version?
- The day’s departures and arrivals, imported from the booking system
- Units assigned to teams, with early arrivals at the top
- Mark each unit cleaned, then inspected, from the phone
- Damage and missing items reported with photos
- A live office board of ready, in-progress and waiting units
Who pays, and how much?
- Who pays
- Managers of holiday parks and lodge sites with 20 to 300 units
- Price to test
- $89 a month per park
A park is a single site with its own office and routine, so a flat monthly price per park suits managers who budget by site. Cleaners are not counted, which matters when seasonal staff come and go.
How to test it in 7 days
- 1Ask five park managers how they track which units are ready on changeover day.
- 2Spend a changeover day with a friendly park’s office and count the calls to cleaning teams.
- 3Show a clickable mock-up to three head housekeepers and ask what would stop their teams using it.
Where to find the first customers
- Holiday park owner groups on Facebook and LinkedIn
- National and regional holiday park associations
- Lodge and caravan dealers who visit many parks
What are the risks?
- Park booking systems may add housekeeping screens, so stay simpler and quicker on the phone.
- Phone signal is patchy on many sites, so updates must save offline and sync later.
How to build it on shipanysaas
5 of the parts it needs are already in the kit, the phone app with the All-in plan. 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
- Phone app with All-in
- You build
- Arrivals import and team assignment
- Phone status flow with damage photos
- Live office board of unit status
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; with the All-in plan, the Expo phone app is in apps/native. Help me build the first version of Changeover-day cleaning board for holiday parks. 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: Cleaners mark each lodge or caravan clean and checked on their phones, and the office sees what’s ready for arrivals. - Who pays: Managers of holiday parks and lodge sites with 20 to 300 units - Their problem: On changeover day, the office phones cleaning teams all afternoon to ask which units are ready. Guests wait at reception, and damage found during cleaning gets mentioned days later, if at all. - Price to test: $89 a month per park (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. The day’s departures and arrivals, imported from the booking system 2. Units assigned to teams, with early arrivals at the top 3. Mark each unit cleaned, then inspected, from the phone 4. Damage and missing items reported with photos 5. A live office board of ready, in-progress and waiting units ## 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 - Phone app: an iPhone, iPad and Android app on the same backend (All-in plan) ## New code it needs - Arrivals import and team assignment - Phone status flow with damage photos - Live office board of unit status ## 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. - If apps/native is not in your copy (the Starter plan), build the web app only. 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
Date holds and enquiry follow-ups for wedding venues
Wedding venues keep every enquiry, viewing and date hold in one calendar, with a reminder before a hold expires.
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.