CRM KitsResidential real estate
Every home. Every step.
An agent runs two businesses at once. Lantern gives each one its own desk, with a buyers and sellers toggle, property cards drawn in code, a showings week, and the closing checklist beside the transaction it belongs to.
Two books of business, one toggle.
Switch the whole desk between buyer side and seller side. Record-level metrics, property cards, and a next-touch column keep the people who are waiting to hear from you in view.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Dual-pipeline transaction desk with a buyers and sellers toggle
- Buyer and seller lists with recorded price, lender, and MLS labels
- Seven-day showings strip with feedback notes and outcomes
- Per-transaction closing checklist with recorded milestone dates
- Referral source grouping and record-level insights
- White and forest-green Lantern application frame with full CRM tools
four pipelines
- Buyer journey · 8 stages
- Seller listing · 7 stages
- Under contract to close · 7 stages
- Referral and sphere · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New buyer consult prep
- Showing feedback follow-up
- Offer review task
- Listing launch checklist
- Seller market update
- Inspection deadline reminder task
- Financing check-in
- Closing gift note
- Referral thank-you task
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore nine fictional transactions, five buyer side and four seller side, with recorded showings and closing checklists. Example edits stay in the current page’s memory and reset on navigation or reload; sample transactions 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 real estate helper is required for connected creation, editing, and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One transaction is a native contact-linked opportunity on one side of the deal, with namespaced property details, price, beds, baths, square feet, an MLS reference label, key dates, agent and lender labels, a referral source, next-touch notes, a five-item closing checklist, and individually recorded showings. A client who is selling and buying holds two independent records.
There is no MLS integration, listing feed, or automatic property data; the MLS reference is a label your team types. Showings and milestone dates are recorded metadata. They do not reserve time, create native Calendar appointments, notify a buyer agent, or confirm a visit happened. The closing checklist is a set of staff-entered milestones, not a transaction management system of record, an e-signature flow, or proof of completion. Recorded prices are planning references, separate from opportunity value, commissions, escrow, and payments. Next-touch dates are recorded intent, not automatic outreach or lead routing.
Four optional pipeline templates and nine inactive workflow drafts. Nine fictional in-memory transactions with recorded showings and checklists.
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 Real Estate Agent 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?
Lantern keeps its horizontal transaction navigation across the original real estate 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
