
CRM KitsInsulation and restoration contractors
Every reading. One board.
A restoration job is won twice: once when the building reads dry and once when the file survives the carrier. Dryline puts both on one white board. Every job is a card, every affected area is a row, and every row carries a strip of squares, one per recorded reading, shading from saturated to near white against that area’s own recorded dry standard, with the claim documentation checklist beside it.
The whole property, area by area.
Each job card lists its affected areas as rows. Each row prints the area, the material, the recorded dry standard, and the reading strip: one square per recorded reading in date order, with the last square widened to carry the latest percentage. Beside the strips, the five claim documentation checks show which items already carry a date.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Area reading board with a CSS moisture reading strip per area and the five-check claim documentation column
- Job sheet with the job record, every dated reading, the equipment log and the documentation dates
- Drying, Job records, Claim documentation and Equipment log views
- Drying insights drawn from recorded workspace data only
- Charcoal and cyan Dryline application frame with the permission-filtered CRM tools drawer
four pipelines
- Water mitigation · 8 stages
- Fire and smoke restoration · 7 stages
- Mold remediation · 7 stages
- Insulation upgrades · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Assessment scheduled task
- Initial readings note
- Equipment placed note
- Daily reading check task
- Dry standard reached note
- Documentation package task
- Estimate submitted follow-up
- Adjuster follow-up
- Equipment pull reminder
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore eight fictional job records in the separate sample view, across water, fire and smoke, mold and insulation upgrade work. Twenty-three areas each carry five days of readings, three are still above their dry standard, one of those was last read three days ago so the reading-overdue marker is visible, eleven equipment lines are recorded with four not yet pulled, and two claims record all five documentation items. Example edits stay in the current page’s memory and reset on navigation or reload; sample job records 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, promise line, 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 insulation and restoration helper is required for connected creation, editing and starter setup. It checks the active account, native permissions and the current record state, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. Existing area records and equipment lines are archived rather than dropped from a save. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
One job record is a native contact-linked opportunity with a namespaced loss type, property address label, loss date, carrier label, claim number reference, adjuster label, lead technician label, notes, an optional job amount, a fixed five-key documentation checklist of dates, the affected areas with their material label, dry standard percent and ordered readings, and the equipment lines with their quantity, placed date and pulled date. Two jobs at the same address stay independent, and other custom fields are preserved.
Every reading is a percentage and a date somebody typed in after reading their own instrument. There is no moisture meter, sensor, data logger or remote monitoring integration, and nothing in the kit measures a building. A dry standard is the number the assessor recorded; the kit supplies none, validates none and recommends none, and makes no IICRC, certification or compliance claim. The ramp is the ratio of two recorded numbers, not a drying calculation, psychrometrics, dehumidifier sizing or engineering advice. An area at exactly its standard is dry and an area with no readings is reported as not measured rather than counted as dry. Reading overdue means an area above its standard that has not been read for more than two days, and nothing else. The documentation checklist is five dates; the kit submits, transmits and files nothing, and there is no carrier, claim system, adjusting platform or estimating platform integration. Equipment lines are labels, quantities and dates, with no inventory, asset register or rental billing. Job amounts are recorded references, separate from native opportunity value, invoices, supplements and payments. Empty values read as words, never a dash.
Four optional pipeline templates and nine inactive workflow drafts. Eight fictional in-memory job records with twenty-three measured areas and eleven equipment lines.
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 Insulation & Restoration Kit

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?
Dryline keeps its grouped chrome-bar navigation across the original insulation and restoration views and the 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 trades & construction kits
Browse all 220 kits









