CRM KitsLandscaping & property care
A week of work. Room to grow.
Give recurring property care a workspace with a weekly rhythm. Fieldwork brings horizontal navigation, an ordered visit manifest, a route schematic, and the selected property’s care details into one planning view.
Give each day an order.
Choose the planning day, review recorded stops, and open the matching care card. The schematic makes the sequence visible without claiming GPS, real geography, or automatic route optimization.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Weekly routes with ordered visit manifest, schematic, and property care inspector
- Property portfolio with grouped visit history and Plan next visit
- Seasonal work, crew capacity, and care agreement review views
- Horizontal Fieldwork navigation and permission-filtered All CRM tools in the shared theme
four pipelines
- Recurring property care · 7 stages
- Irrigation service · 7 stages
- Seasonal cleanup · 7 stages
- Landscape installations · 8 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Property site review
- Care estimate follow-up
- Visit preparation
- Property enquiry review
- Care agreement handoff
- Care renewal review
- Irrigation request review
- Seasonal visit handoff
- Installation agreement handoff
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore nine fictional properties across ten independent visits, including a previous-visit record. Examples stay in memory, separate from your CRM, and reset when you navigate or reload.
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 details, crew labels, capacity target, default pipeline, locale, and currency. 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 backend helper is required for connected visit edits. It checks the active location, permissions, and the expected record state before merging its namespace through the native Seedly update function. Deploy it from your authoritative backend source before testing saves. The pipeline and workflow presets remain optional; no schema migration is required.
Each opportunity is one service visit. A stable property ID groups related visits; address, access instructions, care cadence, scope, crew label, and service checks are recorded on each visit. Planning the next visit preserves the earlier record.
Property information is a per-visit snapshot rather than a separately synchronized property master record. Cadence records intent; it does not create repeat jobs or calendar appointments automatically. The route schematic is illustrative, not GPS or geographic routing. Capacity counts planned service minutes against your configured target, excluding travel, breaks, and weather. Crew labels and overlap checks do not reserve staff resources.
Four optional pipeline templates and nine inactive workflow drafts. Nine fictional properties and ten independent in-memory service visits.
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 Landscaping 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?
Fieldwork uses a horizontal application header across its original property-care views and native CRM pages. The permission-filtered All CRM tools menu keeps the full CRM within the same account and 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 home services kits
Browse all 220 kits
