GoSeedly Chimney & Fireplace Kit
A chimney company does not run a day, it runs a book of systems that come back every year. Flue puts one row per system on a white ledger, grouped by the month that customer wants serviced, with the last inspection level and the days until their window opens in a column each.
YOUR FLUE SYSTEM LEDGER
01 — SYSTEM LEDGER
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 / System ledgerRows group under September, October, November and off-season, each header carrying its own count. Every row shows the recorded address, the system type, a three-bar level marker for the last inspection, the last sweep date, the condition somebody wrote down, and the days until that window opens, tinted when the selected date is already inside it. Inside a group the system nobody has looked at in longest reads first.
02 / System sheetSelecting a row opens the sheet beside the ledger: the system record with construction, liner label and cap flag, then the inspection log, the sweep log and the repair recommendations. The native pipeline stage sits in the same panel, so a recorded inspection never moves a card and a stage change never rewrites a recorded value.
03 / Inspection call listOne row per system in three bands: no inspection recorded, overdue, then recorded. Overdue means the last recorded inspection is more than 365 days before the selected date, and a system nobody has ever inspected sits in its own band instead, because those are different facts. Each row carries the days since, the technician label and the recorded condition.
04 / The registerEvery system in the pipeline as one ruled table: type, masonry or prefab, liner label, cap flag, service window, technician label and recorded service price. A house with a fireplace and a furnace flue is two independent records, so the register is a list of flues rather than a list of addresses.
05 / Open recommendationsOpen recommendations grouped urgent, soon and planned, one row per recommendation rather than per system, so a system carrying two reads as two rows. Scheduled, completed and declined rows are counted in Insights and deliberately left out of this list.
06 / Season insightsSystem mix, the masonry and prefab split, the distribution of last inspection levels, the service-window spread including off-season, sweep recency, recommendation outcomes by status, and recorded service price totals grouped by currency code and never summed across them, with the number of systems that recorded a price stated alongside.
07 / Starter setupThe starter picker opens with every box unchecked. Four pipelines are listed with their stages written out, from the eight-stage annual visit to gas fireplace service, alongside nine workflow drafts that install inactive and name the pipeline and trigger stage each one watches. A pipeline already present on the account is marked as added rather than offered again, because applying a choice twice creates no duplicate.
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 thirteen fictional systems in the separate sample view: five wood fireplaces, four gas fireplaces, two stove inserts and two furnace flues, split four, four, three and two across September, October, November and off-season. They carry 18 recorded inspections at all three levels, 14 recorded sweeps and 10 repair recommendations. Two systems read overdue, one records no sweep at all, and four recommendations are still open. Example edits stay in the current page’s memory and reset on navigation or reload; sample systems 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 system is a native contact-linked opportunity with a namespaced service address label, system type, construction, liner label, cap flag, preferred fall service month, technician label, an optional recorded service price, notes, and three child collections: inspections with a date, level 1, 2 or 3, technician label, condition label and findings note; sweeps with a date, technician label and creosote level label; and repair recommendations with a label, priority and status. Two systems 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, the promise printed in the chrome bar, 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 chimney and fireplace 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. It exposes no stage mutation of its own, so a stage change stays the host’s own control. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
Nothing in this kit certifies a system. Inspection levels, condition labels and creosote level labels are what a person typed; there is no code text, standard, certification register, inspection form, certificate or compliance status anywhere. The preferred service month is a recorded customer preference and the season countdown is calendar arithmetic on it, run at UTC noon so a window never shifts across a daylight saving boundary: nothing books a visit, reserves a technician, creates a native Calendar appointment or optimizes a route. A repair recommendation is a label, a priority and a status with no date at all, so nothing holds stock, orders a liner or cap, prices a part or tracks a delivery. Recorded service prices are references, separate from native opportunity value, invoices and payments. Three rules are enforced on both the client and the server: a level 2 or level 3 inspection requires a recorded findings note, a recorded liner label requires a recorded construction, and a gas fireplace may record no creosote level, because gas appliances produce none. The cap flag is a strict boolean with two drawn states, and "No cap recorded" means nobody recorded a cap rather than that a cap was confirmed absent. Empty values read as words, never a dash, and counts are pluralized against their own value.
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.
Flue keeps its two-band chrome across the original chimney 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.