GoSeedly Short-Term Rental Kit
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.
YOUR TURNOVER CALENDAR
01 — TURN CALENDAR
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Turn calendarOne 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.
02 / Unit sheetThe unit record opens under the board: address, bedrooms, bathrooms, sleeps, owner and cleaner labels, check-in and check-out times and channel labels, then the stays, the turns, the guest issues and the owner report block. Night counts are derived from the two recorded dates rather than stored.
03 / UnitsOne table for the portfolio: recorded owner and cleaner labels, bedrooms, bathrooms and sleeps, the nights each unit has recorded inside the displayed window, its open guest issue count, and a stage control that calls the native CRM.
04 / TurnsEvery change-over day the recorded stays create, from the selected date forward, with days that carry no cleaner label sorted to the top. A day nobody recorded a turn for reads "No turn recorded" and stays in the list, so it can never quietly disappear.
05 / Guest issuesOpen rows before resolved ones, each with its date, category, note and the guest label of the stay the date falls inside. A guest issue is recorded against a stay, which is what lets it be pinned to that stay on the calendar.
06 / OwnersUnits grouped by recorded owner label, each with its own month summary: nights booked, turns, guest issues and the recorded payout reference for that month, alongside a count of how many of the month stays recorded one.
07 / InsightsOccupied nights against the window unit-nights, the three turn states across every recorded change-over day, the share of those days carrying a cleaner label, open against resolved guest issues by category, and recorded monthly management fees grouped by currency code.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit company name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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.
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.
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.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
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.
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.
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.
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.
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.
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.
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.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.