CRM KitsCampgrounds and RV parks
Every site. Night by night.
A site-by-night grid for campgrounds and RV parks: your own sites as rows in their loops and groups, nights as columns and every stay as a bar, with today's arrivals and departures above it and double-booked sites, late check-outs and missed arrivals called out in words. Sitepost keeps nightly stays, seasonal and monthly guests with their renewal dates, group and rally blocks and sites out of service for upkeep in one connected workspace. It takes no payment, holds no site by itself and never says a site, hookup or rig is safe or permitted.
See every site, night by night.
The season banner, the bookings that need attention with the reason in words, today's arrivals with their expected times and the departures, then the grid: each site with its amps, hookups, pull-through or back-in and recorded length, 28 nights across, and every stay as a bar. Checked-in, reserved, requested, seasonal, monthly, group and out-of-service bars each read differently and say what they are. The sample shows July 2 of a fictional season, with a rally block double-booked on A-4.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Site grid operating view
- Arrivals and departures operating view
- Reservations operating view
- Seasonal and monthly operating view
- Groups and rallies operating view
- Site upkeep operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable booking checklists and preserved row history
four pipelines
- Reservations · 8 stages
- Seasonal and monthly guests · 8 stages
- Groups and rallies · 7 stages
- Site upkeep · 6 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Deposit follow-up
- Prepare arrival notes
- Check-out review
- Agreement follow-up
- Record the renewal answer
- Group roster count
- Group wrap-up
- Schedule the work
- Back in service check
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Reservation request
- Seasonal and monthly site inquiry
- Group or rally request
- Arrival sheet
- Seasonal site agreement outline
- Group block summary
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore one fictional season, mid-April to mid-October, on 22 sites: 32 bookings in all, with 4 seasonal guests, 2 monthly guests, 3 groups and rallies, 5 upkeep jobs and 18 nightly bookings. Each booking shows from the date it was booked, so a summer date fills the grid and an off-season date shows next season's renewals and early reservations. Sample edits stay in memory and reset on navigation or reload.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, default pipeline name, the park's season and its own site list. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected booking creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep every figure in its own unit, refuse access codes, passes, Wi-Fi passwords, logins, card numbers, Social Security numbers and other ID numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked booking holds the kind (nightly, monthly, seasonal, group or rally, site upkeep), the guest or group, how they found the park, party counts and labels for pets and vehicles, the rig with its length, slide-outs and the power it needs, the recorded rate and its period, for seasonal and monthly guests the agreement dates and the renewal answer with its date, every stay with its site, arrival, departure, expected arrival time and status, every out-of-service window for upkeep, every payment line with its due and paid dates as recorded, and an editable checklist.
Sitepost records sites, stays, agreements, group blocks and upkeep as your office typed them. It takes no payment or deposit, runs no online booking, holds no site by itself, sends no confirmations or reminders, opens no gate and issues no codes or passes. It never says a site, hookup, road, rig or stay is safe, permitted, inspected or compliant with any health, fire, electrical or park rule, and an agreement here is your office's record, not a lease. The season follows the open and close dates your park records, with an honest off-season board. Gate, bathhouse, laundry and cabin codes, passes, Wi-Fi passwords, logins, card numbers and Social Security numbers are refused in recorded text and in the native form drafts, while site numbers, amps, rig lengths, plates, counts and prices are accepted.
Four optional pipeline templates and nine inactive workflow drafts. 32 fictional in-memory bookings across one season.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Campground & RV Park Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 190 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Sitepost keeps its light bar with the dusk violet rule, the current view set as a site post, and the campsite-post mark across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More hospitality, events & creative kits
Browse all 220 kits
