Every home checked on schedule. Every owner's return ready.
A check-in route for home watch companies: every watched home with its visit frequency, last and next check, the owner's departure and return dates and its open issues, followed by a visit log with a checklist per visit, issues and vendors, an owner calendar and agreements. Keyholder keeps homes, visits and owner travel in one connected workspace, and never stores access codes.
Every home under watch is a stop with its zone and route position, frequency, last and next check, the owner's travel dates and open issues, grouped into overdue or due today, the next 7 days, later, and owner home. Homes with an overdue check, an issue past follow-up, arrival prep not done or an agreement past its end lead.
Zone and stop, frequency, key tag label, alarm company name, water shutoff location, the thermostat setting agreed with the owner and the insurer visit note, as recorded. Door, gate, lockbox and alarm codes and Wi-Fi passwords are refused.
Each visit shows doors and locks, windows, water and leaks, HVAC setting and pests as recorded, with the thermostat reading in the home's own unit, extra checks and the report-sent date.
Homes by watch state, next check position, checks in the last 30 days by item and result, open issues by category and recorded monthly fees, never added across units.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Home watch agreements · 8 stages
Owner departures and returns · 7 stages
Issues and vendors · 7 stages
Renewals · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Walkthrough preparation
Agreement follow-up
Key tag and home details intake
Departure close-up visit
Arrival prep
Next trip check-in
Issue owner update
Vendor follow-up
Renewal reminder
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore 12 fictional homes: nine under watch, two with the owner home and one ended agreement, with 14 owner absences, 37 visits, 185 visit checks and 6 issues. Sample edits stay in memory and reset on navigation or reload.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry to the final handoff.
Editable native forms and document templates give your team a practical starting point.
01 / INTAKE & FOLLOW-UP
Three ready-to-edit forms.
Home watch inquiry
Owner travel dates
Vendor access request
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
02 / WORKING DOCUMENTS
Three reusable templates.
Home watch visit report
Home details sheet
Vendor dispatch record
Open each template in Documents and complete it for the actual job or visit.
03 / THE NEXT STEP
Checklists alongside the work.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
One contact-linked home holds its zone and route position, visit frequency, key tag label, alarm company name, shutoff location, agreed thermostat setting, agreement dates and fee, owner absences, visits with an editable checklist per visit, issues with vendors and a setup checklist.
Check-in route operating view
Watched homes operating view
Visit log operating view
Issues & vendors operating view
Owner calendar operating view
Agreements & renewals operating view
Insights operating view
Three native form drafts and three editable document templates
Editable checklists per visit and per home, with preserved row history
Four optional pipeline templates and nine inactive workflow drafts
12 fictional in-memory homes
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit business name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 home creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, Wi-Fi passwords, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Keyholder records what the office saw and agreed. It does not monitor a home or read sensors, cameras, thermostats or alarms, secure or insure a property, hold or track keys, dispatch or pay vendors, plan routes on a map, send reports or messages, or bill. Door, garage, gate, lockbox and alarm codes, Wi-Fi passwords, payment card numbers and Social Security numbers are refused in recorded text.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
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?+
Keyholder keeps its deep ocean top bar and key-tag tabs 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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.