
CRM KitsFlooring contractors
Every measure ordered. Every order installed.
A flooring job is won and then it waits on a truck. Somebody measures the rooms, somebody orders the material, the material arrives, the crew installs it, and losing track of which of those four has happened costs a week, because the crew shows up to a house with nothing in it. Plank groups the board by the week the crew is supposed to be there and puts four marks on every card. The chrome is black, the page is white, and the only color anywhere is one blue dot showing where each job currently stands.
Grouped by the week the crew is there.
Jobs in the selected pipeline sit under install week headers in date order, with the ones that record no week in a group of their own. Each card carries the job name, the address label, a material pattern chip, the recorded crew label and install day, and a four step stepper: measured, ordered, received, installed.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Install week board with a four step measured, ordered, received, installed stepper on every job card
- Material pattern chips drawn purely in CSS from the recorded material type, with no image or icon file anywhere in the kit
- Quantity arithmetic enforced in the editor and again on the server, with an archived room excluded from both job totals
- Material orders with a late marking that only ever compares a recorded expected date with today
- Jobs by stage, a cross-job measurement record, install weeks read from recorded dates, and insights
- Archive-only rooms and material orders with stable IDs, so a measurement and a placed order are never erased
- Black and white Plank application frame with full permission-filtered CRM tools
four pipelines
- Residential flooring · 8 stages
- Commercial flooring · 7 stages
- Repairs and refinishing · 7 stages
- Builder accounts · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Measure appointment
- Quote follow-up
- Order placed note
- Expected delivery check
- Late order follow-up
- Install prep note
- Install day confirmation
- Final walkthrough
- Warranty check-in
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional flooring jobs across three install weeks, with 19 recorded rooms and 8 recorded material orders spanning hardwood, LVP, tile, carpet and laminate work. One order is past its recorded expected date and has not arrived, so the late marking is visible without editing anything. Example 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
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, 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 flooring helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks the whole quantity arithmetic along with the install week, crew and job stage 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.
A job is a native contact-linked opportunity with a namespaced job type, site address label, material type, product and supplier labels, crew label, recorded install week and day, the recorded job stage, job notes, an immutable supported currency, rooms with their measurements and material orders with their dates and received flag. The recorded quote reference stays separate from native opportunity value. Other custom fields are preserved.
Every number is something somebody measured or typed, or arithmetic on it. A room’s ordered quantity equals its recorded square footage plus the recorded waste percent of it, rounded up, and is nothing at all when either input is unrecorded. The job’s measured and ordered totals equal the sums across the rooms that are not archived. The editor computes all three and the server re-checks them, so a sheet that does not add up cannot be stored. An archived room keeps its measurements and stops counting. The quote reference is deliberately allowed to disagree with every measured figure, and the recorded order quantities are deliberately not forced to add up to the ordered total, because contractors order extra and reorder damaged boxes. The recorded job stage is evidence based: measured needs a measured room, ordered needs an order row, received needs a received order, installed needs a recorded install week. A recorded install week must start on a Monday, an install day must fall inside it, and a crew label needs a week. There is no supplier catalog, product database, SKU lookup, pricing feed or ordering integration, no inventory, cut list or remnant tracking, no takeoff from plans, and no delivery tracking or carrier feed. A late order is a comparison of a date the supplier gave with today. Nothing is invoiced, deposited, collected or ordered, nothing messages a client or a supplier, and crew labels reserve nobody and create no calendar entry. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: the kit adds no stage model and no stage mutation, so recording that material arrived never moves a card.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory flooring jobs with 19 rooms and 8 material orders across three install weeks.
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 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?
Plank keeps its flooring navigation across the original job 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 trades & construction kits
Browse all 220 kits









