01 / Routes & planning weekGive 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.
GoSeedly Landscaping Kit
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.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR FIELDWORK PLANNING WEEK
01 — ROUTES & PLANNING WEEKActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
Plan the visit. Keep the property in view.
One connected workspace, with views built around the decisions your team makes each day.
01 / Routes & planning week
02 / Property portfolioA property has more than one visit.
Group independent visits by a stable property ID and review their history within the selected pipeline. Plan next visit creates a new service record and preserves the work already recorded.
03 / Seasonal workMake space for the larger jobs.
Review seasonal projects separately from the weekly route. Keep service scope, planned dates, recorded crew labels, and the next property action close to the work.
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.
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
- Recurring property care · 7 stages
- Irrigation service · 7 stages
- Seasonal cleanup · 7 stages
- Landscape installations · 8 stages
Give the next step a shape.
- 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
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore before adding records.
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 inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
Your workspace.
Your starting point.
Your code to edit.
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.
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 optional pipeline templates and nine inactive workflow drafts
Nine fictional properties and ten independent in-memory service visits
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide FROM KIT TO CONNECTED WORKSPACE
Check. Connect.
Make it yours.
Check your Seedly project.
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Set up your own team.
Edit company details, crew labels, capacity target, default pipeline, locale, and currency. 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 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.
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.
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.
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.
See DevLaunch All AccessAlready a member? Open your downloads.
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?+
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.
Find a workspace that fits the way you work.
Explore all CRM kits