A flooring store sells out of a room. Somebody walks in, talks about two rooms and a stair run, walks out with four sample boards under one arm, and either comes back or does not. The exposure is never which stage a deal sits in. It is the boards that left the building, the quote nobody answered, and the accepted job nobody handed to an installer partner. Sample is built around those three leaks: a checkout ledger of open visits, one row each, ordered by the board that has been out longest, with a chip for every sample, a pill for the quote, and a flag that stays hollow until a partner actually has the work.
The customer label with the recorded visit name beneath it, the visit date, a rounded chip for every sample board with its due back date, a quote state pill and an installer handoff flag. Rows sort by the earliest due back date among the boards still out, so the board that has been gone longest sits at the top. A chip is outlined in ink while a board is out, red once its due back date has passed on the selected date, and hollow with a struck label once a return is recorded.
The sheet is a full-width disclosure row directly under the selected visit, so the ledger keeps one set of column widths and the customer never scrolls away. Four ruled blocks: the customer record with the rooms, the square footage reference, the budget band and the salesperson; every sample with its category and three dates; the quote with its amount, quoted date and decision; and the installer handoff with its partner, handoff date and install target.
The whole book ordered by recorded visit date, filtered to open, closed or all. Rooms, square footage, budget band, salesperson, boards still out against boards recorded, the quote state and its amount, the recorded partner, and the native stage select beside each row as the keyboard and assistive equivalent of moving the card in your CRM. A closed visit is one whose boards are back, whose quote has a decision, and whose accepted quote records a handoff.
Every non-archived sample row that records no returned date, across every loaded visit, overdue first and then by due back date. The product label, the category, the customer, the visit, the day it left and how many days it has been gone, with a control to record the return from the list. Underneath, the boards already back, most recent return first, because the list of what is missing should never be confused with the list of what exists.
Only the visits whose recorded quote state is Quoted, so an amount and a quoted date exist and no decision has been written, oldest quoted date first with a day count beside each one. Beneath it, the quotes that did get an answer, with the decision, the days between the recorded quoted date and the recorded decision date, and whether the accepted ones have reached a partner.
Accepted quotes split into those still awaiting a handoff and those with one recorded, plus a summary of the recorded partners: visits handed over, recorded amount, and how many carry an install target date. A handoff needs both a partner label and a handoff date and requires an accepted quote, because a store does not hand work to a partner the customer never agreed to.
Sample boards by category, recorded returns with their rate, the four quote states with a recorded acceptance rate, recorded quote totals grouped by currency with the accepted total beside them, the recorded square footage with how many visits actually recorded one, and the handoff and salesperson counts. Every card reports None recorded rather than an invented zero.
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.
Showroom visits · 8 stages
Builder and designer accounts · 7 stages
Commercial bids · 7 stages
Installer partner handoffs · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Visit follow-up task
Sample due-back reminder
Overdue sample task
Quote sent note
Quote accepted note
Quote follow-up
Installer handoff task
Install target check task
Thirty-day review request task
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 twelve fictional showroom visits with 29 recorded sample rows: 22 still out, four of those overdue, and seven recorded as returned. Seven visits carry a recorded quote, three of them accepted and one declined, and three record an installer handoff across two salespeople and two installer partners. Every sample date is computed from the day you open the page, so the red overdue tags, the outstanding chips and the struck returned chips are all visible without editing anything. Example edits stay in the current page’s memory and reset on navigation or reload; sample visits 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 showroom visit is a native contact-linked opportunity with a namespaced visit name, recorded visit date, room labels, a whole square footage reference, a budget band, a salesperson label, visit notes, an immutable supported currency, a quote group of amount in minor units, quoted date, decision and decision date, an installer handoff group of partner label, handoff date and install target date, and archive-only sample rows with stable IDs carrying a product label, a category and its checked out, due back and returned dates. The recorded quote amount stays separate from native opportunity value. Other custom fields are preserved.
Sample checkout ledger of open visits, ordered by the board that has been out longest
A rounded chip per sample board that turns red when overdue and hollow once it is back
A quote state pill where only an accepted quote is filled, and a handoff flag that stays hollow until a partner and a date both exist
A visit sheet that opens as a full-width disclosure row, so the ledger never loses its column widths
Record a board returned in one control from the sheet or the sample list, without touching the pipeline stage
Visit book with the native stage select, outstanding and returned sample lists, open and answered quotes, and a recorded partner summary
Archive-only sample rows with stable IDs, so nothing somebody recorded is ever erased
One black chrome bar over a white ledger canvas, a single magenta accent, red only on an overdue tag, and no image, SVG or icon file anywhere in the pack
Four optional pipeline templates and nine inactive workflow drafts
Twelve fictional in-memory visits with 29 sample rows, seven quotes and three installer handoffs
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, promise line, 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 showroom visit helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks all eleven cross-field rules, and compares the current record state before saving. It exposes no stage mutation at all, so pipeline stages stay in your CRM’s own views under your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Eleven cross-field rules are validated by one shared implementation used by the editor, every view and the server, identically on create and on save: a board cannot be checked out before the recorded visit date, a due back or returned date cannot precede the checked out date, a recorded quote needs both an amount and a quoted date, an unquoted visit cannot hide a draft amount or date, a recorded decision needs a decision date while a quote still waiting must leave it blank, a decision date cannot precede the quoted date, a quoted date cannot precede the visit date, a handoff needs both a partner label and a handoff date, a handoff requires an accepted quote, and an install target date requires a recorded handoff it cannot precede. Four non-rules are deliberate: a returned date is never constrained against a due back date because a board that came back late is still back, two boards of one product may sit on one visit, an install target never waits for a board to come home, and a quote amount is never constrained against the square footage or the budget band. Nothing prices anything: there is no product catalog, price book, square-foot rate, markup, margin or pricing advice, and the recorded square footage is never multiplied by anything. A recorded due back date reminds nobody, because the kit sends no message, email or text of any kind and a workflow draft writes an internal task or note only. A recorded handoff reserves no installer, checks no availability, builds no install schedule and creates no calendar appointment. A sample row is a record of a board somebody took home, not a stock level: the kit holds no inventory, reads no supplier catalog and orders nothing. There is no point of sale, no invoicing and no payments. Day counts are calendar arithmetic at UTC noon, so they never shift across a daylight saving boundary. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the helper exposes no stage mutation at all, so recording a returned board never moves a card and moving a card never rewrites a recorded sample, quote or handoff.
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?+
Sample keeps its showroom navigation in one chrome bar across the original ledger views and 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 / Checkout ledger
