
CRM KitsFlooring showrooms and retailers
Every sample back. Every quote closed.
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.
One row per open visit.
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.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- 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 pipelines
- Showroom visits · 8 stages
- Builder and designer accounts · 7 stages
- Commercial bids · 7 stages
- Installer partner handoffs · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- 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
Inactive until you review and publish them. None send customer messages.
Sample workspace
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 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
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set company name, descriptor, promise line, 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 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.
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.
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.
Four optional pipeline templates and nine inactive workflow drafts. Twelve fictional in-memory visits with 29 sample rows, seven quotes and three installer handoffs.
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 Flooring Store Kit

DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
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?
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.
More retail & showrooms kits
Browse all 220 kits









