Skip to content
View packages

CRM KitsChimney and fireplace services

Every system. In season order.

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.

System ledger in the GoSeedly Chimney & Fireplace Kit with fictional sample records

Two columns decide the season.

Rows 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.

Actual interface captures with fictional sample data. Open a screenshot to see it full size.

What’s in the kit

Screens

  • Seasonal system ledger with a CSS three-bar level marker and a tinted season countdown column
  • System sheet carrying the system record, inspection log, sweep log and repair recommendations side by side
  • Systems register, banded inspection call list and open-recommendation views
  • Season insights drawn from recorded workspace data only
  • Soot-black and maroon Flue application chrome with the permission-filtered CRM tools drawer

four pipelines

  • Annual inspections and sweeps · 8 stages
  • Repairs and relining · 7 stages
  • Real estate transaction inspections · 7 stages
  • Gas fireplace service · 7 stages

Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.

nine workflow drafts

  • Booking confirmation task
  • Day-before reminder
  • Inspection recorded note
  • Repair estimate task
  • Estimate follow-up
  • Repair scheduled note
  • Repair complete task
  • Next season reminder
  • Off-season outreach task

Inactive until you review and publish them. None send customer messages.

Sample workspace

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.

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
Read the installation guide
  1. Check your Seedly

    Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.

  2. Connect the helper

    Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.

  3. Make it yours

    Set company name, descriptor, the promise printed in the chrome bar, 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 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.

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.

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.

Four optional pipeline templates and nine inactive workflow drafts. Thirteen fictional in-memory systems with recorded inspections, sweeps and repair recommendations.

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 Chimney & Fireplace Kit

Checking access…

DevLaunch All Access

Every kit and every template.

See DevLaunch All Access

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?

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.

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.

Browse all 220 kits

Customer experiences / Trustpilot

What customers say
about DevLaunch.

Read all reviews on Trustpilot ↗

Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.