Skip to content
View packages

CRM KitsPlumbing & drain service

Every call. Answered in order.

A plumbing company runs on triage. Mainline puts emergencies, same-day calls, scheduled work and multi-day projects into one dense slate-and-yellow ledger, with the job inspector opening beside the table instead of on top of it.

Call board in the GoSeedly Plumbing Kit with fictional sample records

One list, four lanes.

Switch between emergency, same-day, scheduled and project work over a single ledger sorted by recorded priority and arrival window. Counters above the table show recorded emergency and same-day volume, jobs with no technician label yet, and recorded visit completion.

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

What’s in the kit

Screens

  • Keyboard-navigable dispatch ledger with sticky header, lane control and tabular numerals
  • Job inspector panel that opens beside the table, not over it
  • Projects with recorded phases, technician day view with advisory overlap notices, follow-ups and insights
  • Slate and safety-yellow Mainline application frame with permission-filtered All CRM tools

four pipelines

  • Service calls · 8 stages
  • Emergency response · 7 stages
  • Water heater replacement · 7 stages
  • Repipe and sewer projects · 7 stages

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

nine workflow drafts

  • Emergency intake checklist
  • Arrival window reminder
  • Estimate follow-up
  • Closeout review
  • Callback check
  • Parts pickup
  • Seasonal maintenance note
  • Permit reminder
  • Project phase handoff

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

Sample workspace

Explore ten fictional jobs and 17 recorded visits across emergency, same-day, scheduled and project work. Sample edits stay in the current page’s memory and reset on navigation or reload; sample jobs 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, 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 plumbing helper is required for connected creation, editing and starter setup. It checks the active account and native permissions, compares the current record timestamp and job revision, preserves unrelated custom fields and unknown values, and calls the native Seedly mutations. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional and need no schema migration.

One job is a native contact-linked opportunity with namespaced job type, problem category, priority, property address, access notes, technician label, arrival date, time and window, a recorded parts list, estimate status and reference amount, project phase, follow-up date and note, and individually recorded visits. Other custom fields are preserved.

Technician labels and arrival windows are recorded metadata. They do not dispatch anyone, reserve a vehicle, create native Calendar appointments or prevent two windows from overlapping; the overlap notice is advisory. The parts list is a note for the crew, with no ordering, inventory or pricing. Estimate status is a recorded label and the estimate reference is a planning number, separate from opportunity value, invoices and payments. Nothing here files a permit, books an inspection or routes a truck. Visit completion is completed divided by completed plus no access plus parts needed, so scheduled and cancelled visits are excluded and no qualifying records gives an unavailable ratio.

Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory job records and 17 recorded visits.

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 Plumbing 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?

Mainline keeps its icon rail and slate header across the original plumbing views and native CRM modules, inside 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.