CRM KitsProperty management
Every unit. Every request.
A property manager thinks in buildings and units. Stackview puts a graphite building tree beside a floor-ordered unit stack, then keeps the maintenance queue and lease renewal dates one click away.
Start with the building, not a list.
The tree groups recorded building labels from your unit records. Choose one and its units lay out by recorded floor label with a status color, alongside an aging summary of that building’s open requests.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Portfolio tree with a floor-ordered unit stack grid
- Dense unit table with status filter and native stage control
- Maintenance queue with four aging buckets from recorded request dates
- Lease renewal timeline at 30, 60 and 90 days
- Owner reporting groups and portfolio insights
- Graphite and cobalt Stackview frame with full CRM tools
four pipelines
- Leasing and move-in · 8 stages
- Maintenance request · 7 stages
- Lease renewal · 7 stages
- Turnover and make-ready · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Application review
- Move-in checklist
- Request triage
- Vendor follow-up
- 90-day renewal outreach
- 60-day renewal reminder
- Notice to vacate checklist
- Make-ready inspection
- Owner report review
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore twelve fictional unit records across two fictional buildings, with fifteen maintenance requests, recorded lease dates and owner labels. Example edits stay in the current page’s 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 property management 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. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One unit record is a native contact-linked opportunity holding namespaced building, unit and floor labels, bedrooms, recorded status, tenant label, lease start and end dates, an optional monthly rent reference, an owner label, unit notes, an owner reporting note and individually recorded maintenance requests.
Occupancy status, tenant labels, owner labels and maintenance requests are staff-entered records. The kit does not collect rent, produce statements, run accounting or make owner disbursements; the recorded monthly rent is a reference figure separate from opportunity value and payments. It does not sign leases, run a tenant portal, dispatch vendors or schedule inspections. Vendor labels are recorded text, and marking a request done records that status only. Aging buckets and renewal bands recompute from the date you choose in the workspace; they are not predictions or automatic outreach.
Four optional pipeline templates and nine inactive workflow drafts. Twelve fictional in-memory unit records and fifteen maintenance requests.
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 Property Management 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?
Stackview keeps its portfolio navigation across the original property management 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
