GoSeedly Insulation & Restoration Kit
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.
YOUR DRYLINE READING BOARD
01 — READING BOARD
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Reading boardEach 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.
02 / A stalled areaSearch narrows the board to one property. This job records five days of readings that stopped three days ago with the basement wall still at 31 percent against a 16 percent standard, so the row is marked Reading overdue in the one red the kit uses. The job sheet beside it holds the job record, every dated reading, the equipment log and the documentation dates.
03 / Still above standardEvery area whose latest recorded reading is above its own recorded dry standard, ordered by the ratio of that reading to the standard rather than the raw percentage, so 27 percent on a 10 percent carpet pad sorts above 17 percent on a 12 percent hardwood floor. Each row carries the standard, the latest reading and its date, the ratio, the days since it was read, and the strip.
04 / Job recordsAll job records in the selected pipeline, most recent recorded loss date first, with the loss type, carrier and claim number reference, adjuster label, lead technician label, area counts, areas above standard, equipment units on site, documentation count, recorded job amount and a native pipeline stage control on each row.
05 / Claim documentationOne row per job record with the same five checks drawn the same way and every recorded date printed underneath, jobs missing a document first and complete ones marked Documented. The carrier label, claim number reference and adjuster label sit on the row, because a claim with no carrier recorded is the first thing to fix.
06 / Equipment logEquipment lines placed and not yet pulled, longest on site first, then the pulled lines with their recorded pull date. Each row carries the label, the recorded quantity, both dates and the days on site. A line is a label, a quantity and two dates somebody recorded; there is no inventory and no rental billing.
07 / Drying insightsRecorded loss types as ruled bars, the drying state split with unmeasured areas reported separately from dry ones, every measured area counted by its latest reading’s ramp step, the five documentation items counted across the pipeline, the equipment lines on site against pulled, and recorded job amounts grouped by currency and never summed across them.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Edit company name, descriptor, promise line, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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.
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.
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
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.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
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
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.
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.
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.
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.
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.
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.
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 kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.