GoSeedly Air Duct & Dryer Vent Kit
A recall board for air duct and dryer vent cleaning companies. Each home sits under Air duct or Dryer vent by when its next visit is due, computed from the last done visit and the interval the customer agreed, with overdue recalls that have no visit booked leading the page. Route days, estimates with vent counts, photo marks, partners and memberships sit in the same Ductwise workspace.
YOUR DUCTWISE RECALL OFFICE
01 — RECALLS
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 / RecallsAir duct and dryer vent columns crossed with due bands. Each card shows the interval, the last visit, the due date and the due state in words, and says when the next visit is already booked. Overdue recalls with nothing booked lead the needs-attention strip.
02 / Route daySeven day buttons from today. The chosen day lists its booked visits in recorded route order with the service, crew, system and vent counts or the dryer vent exit, the access note label and the photo marks. Visits booked earlier and never closed come first.
03 / EstimatesInquiries and sent estimates by follow-up date with systems, supply vents, return vents and the dryer vent exit as recorded, then one ledger for the counts and another for the recorded estimate amounts.
04 / PhotosVisits marked done in the last 90 days with before and after photo marks and where the crew keeps the photos. A recent visit with a mark missing is flagged. The photos themselves stay outside the CRM.
05 / PartnersEach partner label with its homes, homes on recall, visits done in the last year, the next recall due and open estimates, then the homes under each partner.
06 / MembershipsPlan label, status, start and renewal dates, recorded price per year, the recalls each plan covers and the last visits, with the yearly total as plain arithmetic.
07 / InsightsRecalls by service and band, visits done and recorded visit prices in the last 90 days, and system and vent counts on homes on recall, each in its own ledger, plus the homes behind them with the same alerts.
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 16 fictional homes: 9 on recall, 2 with a visit booked, an inquiry, 2 sent estimates, one marked do not recall and one not proceeding, with 20 recall intervals and 30 visits. Sample edits stay in memory and reset on navigation or reload.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
One contact-linked home holds its property and client type, partner label, access note label, system, supply vent and return vent counts, dryer vent exit, estimate, membership, visits with photo marks, recall intervals by service and a ten-step checklist.
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 business name, descriptor 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 backend helpers are required for connected home creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, card numbers and SSNs, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
Everything shown is what the office recorded. Recall dates are computed from the last done visit and the interval the office recorded; the kit does not recommend intervals. It does not test air quality or report air quality results, make fire safety or health claims, store photos, plan routes, dispatch crews, bill, take payments or send messages. Access codes, card numbers and SSNs are refused on the server and in the browser; access notes stay labels such as "attic hatch in the hall closet".
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.
Ductwise keeps its cool grey top bar and recall canvas across the kit views and the native CRM tools in the same signed-in account. 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.