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.
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.
The inspector opens as a panel beside the ledger. Job type, problem category, priority, address, access notes, technician label, arrival window, estimate status, parts and visits all edit in place, and the table stays readable behind it.
Filter the full ledger by problem category and priority, search across job name, address, customer and technician label, and change the native pipeline stage inline. Opportunities with no plumbing details yet are listed separately and excluded from the totals.
Water heater replacements, repipes and sewer work are grouped by category with a recorded phase rail, the next recorded day, the recorded estimate reference and the number of parts on the list.
Group the selected day by recorded technician label and see each recorded arrival window. When two recorded windows for one label collide, an advisory notice says so. Below it, every job expecting someone that day appears in the same ledger.
Records whose recorded follow-up date has been reached, plus anything with an estimate recorded as sent, with the note your team wrote and the recorded amount beside it.
Counts by job type, problem category, visit outcome and estimate status, drawn only from the records loaded in the selected pipeline, with the completion denominator stated on the card.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Service calls · 8 stages
Emergency response · 7 stages
Water heater replacement · 7 stages
Repipe and sewer projects · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Emergency intake checklist
Arrival window reminder
Estimate follow-up
Closeout review
Callback check
Parts pickup
Seasonal maintenance note
Permit reminder
Project phase handoff
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
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 inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
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.
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 optional pipeline templates and nine inactive workflow drafts
Ten fictional in-memory job records and 17 recorded visits
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit company name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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.
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.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.