
CRM KitsHome inspectors
Every booking placed. Every report delivered.
An inspection is only half the job. The booking sits inside somebody else’s transaction, the report has a deadline measured in hours, and an agent usually sent the work. Walkthrough puts the next two working days side by side, prints the report delivery step on the face of every card, and gives the referring agent its own ledger.
Read tomorrow before it arrives.
The working date you choose and the next calendar day, side by side, as two columns of time-ticked cards. Each card carries the recorded arrival window, the property and its type, the inspector and referring agent labels, the recorded add-on chips, the four-step report delivery stepper and the date that report is due.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Two-day booking board with hour ticks and a report delivery stepper on every card
- Reports-due bands measured against a working date you choose
- Referring agent ledger with side split, booking counts and last referral date
- Booking register, follow-up rows by type, and insights with stated denominators and per-currency totals
- White Walkthrough application frame on a light slate canvas with full CRM tools
four pipelines
- Buyer inspections · 8 stages
- Seller pre-listing inspections · 7 stages
- Add-on services · 7 stages
- Agent referral partners · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Booking confirmation task
- Pre-inspection access note
- Day-before reminder task
- Report drafting task
- Report due check task
- Report delivered follow-up
- Agent thank-you task
- Annual maintenance inspection outreach
- Referral partner review note
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional bookings: nine across the two board days and one earlier walkthrough whose report is already past due. All four delivery steps appear, four referring agents are recorded plus one direct booking with none, and exactly two reports are due. Sample edits stay in the current page’s memory and reset on navigation or reload; sample bookings 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 booking helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record timestamp and revision before saving. It deliberately exposes no stage mutation, so a stage change goes through your own Seedly move function under its own permission. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional and no schema migration is required.
One booking is a native contact-linked opportunity with namespaced property address, property type, year built and floor area references, booking date, an HH:mm arrival window, inspector, referring agent and brokerage labels, client side, up to eight recorded add-on labels, a fee reference in integer minor units, the recorded report delivery step, report due and delivered dates, notes and follow-up rows with stable IDs. Other custom fields are preserved, and archived follow-up rows are kept rather than dropped.
This kit never contains the report. There is no report writing, no report template, no narrative library, no defect rating, no photo storage, no image annotation and no lab result; it records only that a report is drafted and delivered. There is no scheduling engine, availability model, double-booking prevention or travel-time calculation: booking dates and arrival windows are recorded plans that reserve nothing and create no Calendar appointment, and two cards may overlap on the same day without comment. Recording radon, a sewer scope, termite, pool and spa, mold sampling, well water, thermal imaging or crawlspace work orders nothing, schedules no subcontractor, prices nothing and records no result. There is no agent or client portal, no shared link and no messaging: the referrals ledger is an internal view of labels somebody typed, and nothing texts, calls or emails a client, an agent or an inspector. It makes no claim about any jurisdiction’s inspector licensing, standards of practice, report content requirements, retention rules or insurance. The recorded delivery step is a staff entry independent of the native pipeline stage, and saving booking details never moves a deal. A booking counts as due only when it has been inspected or drafted and records a due date, and the recorded on-time delivery rate excludes any delivered booking missing either date rather than counting it late. The fee reference is a recorded planning number, separate from opportunity value, estimates, invoices and payments.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory bookings across two board days and one past-due report.
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 Home Inspection Kit

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?
Walkthrough keeps its inspection navigation across the original booking views and native CRM modules. Full CRM tools remain available within 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








