CRM KitsPest control
Every account treated, every re-treat on time.
A pest control company does not sell one job. It sells a perimeter it keeps coming back to, and it reads its work by area, not by stage. Perimeter makes the zone board the main screen: one column per service zone label recorded on the accounts, and the treatment history of the selected account directly underneath it, in deep green and white.
The perimeter, by area.
Columns are generated from the service zone labels on the accounts themselves, so there is no zone table to maintain. Each header carries the zone, how many accounts sit in it, how many are due and how many have a re-treat outstanding. Cards stay compact: account name, address, plan label, the recorded next service date behind a bright green marker, and pest flag chips with a single red chip when an infestation is flagged.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Zone board whose columns are generated from the service zone labels on the accounts
- Treatment history strip and account sheet for the selected account, newest visit first
- Re-treat queue that names the visit behind every recorded re-treat date
- Recorded service schedule by week and technician label, an account book, and a derived technician roll-up
- Archive-only treatments with stable IDs, preserved unknown fields, and immutable currency
- Deep green and white Perimeter application frame with the full permission-filtered CRM tools
four pipelines
- Recurring service accounts · 8 stages
- One-time treatments · 7 stages
- Termite and wood-destroying inspections · 7 stages
- Commercial accounts · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Inspection scheduling task
- Quote follow-up
- First treatment prep note
- Re-treat check task
- Quarterly service reminder task
- Renewal review task
- Termite inspection follow-up
- Commercial site review note
- Warranty check-in
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore twelve fictional service accounts across four recorded zone labels, from a quarterly residential perimeter to a restaurant on monthly service and a duplex with an open rodent program, with 26 treatment records between them and two re-treats due. Example edits stay in the current page’s memory and reset on navigation or reload; sample accounts 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 pest control helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every field rule and all four cross-field rules, and compares the current record state before saving. It exposes no stage mutation at all, so pipeline stages stay in your CRM’s own views under your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A service account is a native contact-linked opportunity with a namespaced property address and type, service zone label, plan label, recorded target pest labels, technician label, next service date, re-treat due date, an infestation flag, access notes, warranty label, an optional per-visit price reference, a next step note, and treatment child rows holding date, target pest, product label, method, technician label, outcome and notes. Other custom fields are preserved.
A zone is a label somebody typed, so the board has no map, no GPS, no route order and no drive-time estimate. A plan label records a cadence and creates no future visit or reminder. Product labels are free text and the kit stores no chemical registration data: no registration number, active ingredient, concentration, application rate or label document, and no inventory or regulatory report. Next service dates and technician labels reserve nobody and create no calendar entry. Nothing invoices, takes a deposit or collects a payment, and the price reference stays separate from native opportunity value. Nothing messages a customer or a technician. Four cross-field rules are enforced in the editor and again on the server: a re-treat date needs a treatment recorded as partial or re-treat scheduled, a re-treat date cannot precede the latest recorded treatment, the infestation flag needs a recorded target pest label, and a no access visit cannot record a product label. Pipeline stages stay your CRM’s own, through its own mutation and its own permissions.
Four optional pipeline templates and nine inactive workflow drafts. Twelve fictional in-memory service accounts with 26 treatment records across four zones.
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 Pest Control 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?
Perimeter keeps its pest control navigation across the original service account views and the native CRM modules. Full CRM tools remain available inside 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 home services kits
Browse all 220 kits
