A kitchen and bath remodel stalls for one of two reasons: a selection nobody made, or a trade that has not finished. Layout puts both on the same row. A pill per selection category above, eight trade chevrons below, and a countdown that names how many decisions are still open before the cabinet order.
Every project is one band on a white board. Above, a solid pill for each selection category somebody recorded a product for and a hollow pill for each one still open, with a countdown that reads "5 selections open before cabinets" or "Every selection made". Below, eight adjoining chevrons in trade order: filled black for a phase recorded as done, outlined in forest green for the current phase, light gray for what is still ahead. Each chevron carries its recorded window or the words "No window recorded".
Selecting a row opens the project sheet beside the board, and the board stays where it is. The project record sits at the top with the room, the address, the designer and lead labels, the target window, the derived current phase and the contract reference. Under it the selections read their recorded product, vendor and state, then the eight-row trade schedule carries each phase’s recorded window, its trade label and whether it is done, current or upcoming. The change notes with their amounts and the project notes follow in the same scrolling panel. A recorded selection can be marked as ordered from the sheet, and the pipeline stage never moves.
Every project as one ruled table banded by native pipeline stage, with the room type, the designer and lead labels, the target window, the derived current phase, the open selection count and the recorded contract reference. The stage control is the host CRM’s own: changing it here never records a phase, and recording a phase never moves a card.
Every recorded selection across the loaded projects, open ones first and then by the project’s target start. Each row reads its category, its project and room, the recorded product and vendor labels, and whether it is open, recorded, ordered or delivered. Ordered and delivered are flags somebody set after they did it themselves.
The phases whose recorded window touches the week containing the selected date, banded by recorded trade label. Each row carries the phase, the project, the planned start and end, the span in days, and whether that phase is done, current or upcoming. Windows are allowed to overlap, because plumbing rough and electrical rough share days on almost every job.
Where every project sits in the eight-phase sequence as ruled bars, the selection split across open, product recorded, ordered and delivered, the room mix, the number of phases recorded as done, and recorded contract and change note totals grouped by currency code and never summed across currencies.
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.
Kitchen remodels · 8 stages
Bath remodels · 7 stages
Design and selections consults · 7 stages
Builder and multifamily packages · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Design consult review
Selections deadline reminder
Selections complete record
Cabinet order check
Demo start reminder
Phase complete record
Punch list review
Final walkthrough review
Thirty day follow-up
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 nine fictional projects in the separate sample view: kitchens, baths and one whole-floor job, with one project sitting in each of the eight trade phases and one finished project whose whole strip is complete. Sixty-one selections, fourteen of them still open, and two change notes on two of the nine projects, so every chevron state and both pill states appear. Example edits stay in the current page’s memory and reset on navigation or reload; no sample project is ever written to 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 project is a native contact-linked opportunity with a namespaced project name, room type, address label, designer and lead labels, target start and finish, a derived current phase, notes, an optional contract reference, and three sets of child records with stable IDs: selections, trade schedule rows and change notes. Two projects at the same address stay independent opportunities, and other custom fields are preserved.
Trade sequence board with eight CSS chevrons and a selections pill row per project
Project sheet with the selections, the trade schedule, the change notes and the project record
Project records, selection records and trade schedule views
Project insights drawn from recorded workspace data only
Black and forest-green Layout application frame with the permission-filtered CRM tools drawer
Four optional pipeline templates and nine inactive workflow drafts
Nine fictional in-memory projects with sixty-one selections and a complete trade sequence
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 kitchen and bath helper is required for connected creation, editing and starter setup. It checks the active account, native permissions and the current record state, re-derives the current phase, preserves unrelated custom fields and unknown values, and invokes the native Seedly mutations inside one transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional, and no schema migration is required.
The current phase is the one value the kit computes: the first of the eight trades, in sequence order, that nobody recorded as done, and punch once all eight are. The server re-checks it against the project’s own trade rows, so the chevron strip can never disagree with the schedule table. Everything else is typed in. A planned window and a trade label reserve nobody, create no native Calendar appointment and resolve no conflict, which is why phase windows are allowed to overlap. Ordered and delivered are flags a person set: there is no vendor integration, purchase order, lead time feed or delivery tracking. The contract reference and change note amounts are recorded numbers, kept separate from native opportunity value, with no estimating, allowance engine or price book. A change note amount may be negative, because a change can be a credit. There is no design tool, room planner or rendering, no permit or inspection tracking, no invoicing or signatures, and no client portal or selection approval link. Selections, trade rows and change notes are archived in place, never deleted. Empty values read as words, never a dash.
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?+
Layout keeps one black chrome bar across the original kitchen and bath 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.
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.
01 / Sequence board
