CRM KitsShort-term rental operators
Mind the gap. Every single turn.
A booking calendar draws the stays and leaves the gaps as empty space. Turnover inverts that. On a white canvas with graphite chrome and a single indigo accent, every unit gets one strip across fourteen days: stays sit low and quiet, and every change-over day stands up as a block you cannot miss.
The work is in the gaps.
One horizontal strip per unit across a rolling fourteen days. Recorded stays are drawn as low bars with their guest label and night count. Every change-over day is a tall block carrying a cleaner label and one of three states. An indigo rule marks today, and a red flag marks the day a guest issue was logged.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Fourteen-day turnover strip calendar with a three-state turn block per change-over day
- Unit sheet with stays, turns, guest issues and a derived owner report block
- Turns view that sorts unassigned change-over days first
- Guest issues view with open rows first and the stay each one belongs to
- Owners view grouped by recorded owner label with a per-unit month summary
- White and graphite Turnover application frame with the full permission-filtered CRM tools menu
four pipelines
- New owner onboarding · 8 stages
- Unit turnovers · 7 stages
- Guest issues · 7 stages
- Owner renewals · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Owner onboarding checklist
- Listing details note
- Turn assignment
- Turn day reminder
- Turn complete note
- Issue triage
- Issue follow-up
- Month-end owner report
- Renewal conversation
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore eight fictional units across three owner labels and two cleaner labels, with thirteen recorded stays plus one archived stay, six recorded turns and three recorded guest issues. Example edits stay in the current page memory and reset on navigation or reload; sample units are never inserted into your CRM.
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, and default pipeline name. 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 short-term rental helper is required for connected creation, editing and starter setup. It checks the active account and native permissions, re-applies every domain rule, compares both the record timestamp and a server-managed revision, preserves unrelated custom fields and unknown child-row values, and then calls the native Seedly mutations in the same transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One unit under management is a native contact-linked opportunity. Its namespace records the address, bedrooms, bathrooms and sleeps, owner and cleaner labels, check-in and check-out times, channel labels, an optional monthly management fee, an optional owner report month, and three collections of child rows with stable IDs: stays, turns and guest issues. Other custom fields are preserved.
The domain rules are enforced on the server, not only in the editor. A stay occupies its check-in date through the night before check-out, and two recorded stays may not share a night on one unit. A turn is recorded on a change-over day and never in the middle of a stay, and two turns may not share a day. An assigned or completed turn needs a recorded cleaner label while an unassigned one records none. A guest issue falls inside a recorded stay, and a stay may only use a channel label its unit records. Night counts, change-over slots and the owner report are derived on every read rather than stored. There is no channel manager or booking platform sync, pricing engine, smart lock integration, guest messaging, payment processing, payouts, accounting, or cleaner scheduling engine. A channel label is a typed word, a recorded cleaner label assigns and notifies nobody, and a recorded payout reference is a number copied from a statement you already received.
Four optional pipeline templates and nine inactive workflow drafts. Eight fictional in-memory units with thirteen stays, six turns and three guest issues.
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 Short-Term Rental Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 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?
Turnover keeps its rental navigation across the original views and the native CRM modules. The full CRM stays available inside the same signed-in account and application theme. 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 real estate & property kits
Browse all 220 kits
