CRM KitsCabinet and millwork shops
Every ticket, through the shop.
A shop-floor traveler board for a custom cabinet and millwork shop. Every job is a row behind a drawing gate, every cabinet group or millwork item is a traveler ticket with a punched six-station strip, and nothing moves past cut until the drawings are recorded as approved.
One row per job, one ticket per item.
Each row opens with its drawing gate, its revision letter and the revision the approval on file belongs to, then the traveler tickets. A row whose current revision has no recorded approval is hatched and its tickets stay at cut.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Shop floor traveler board with per-row drawing gates
- Punched six-station strips on every traveler ticket
- Jobs ledger with revision letters and derived job state
- Drawings view by days waiting, with the approval log
- Stations, Hardware and finish, and Installs operating views
- Insights counts that open the jobs behind them
- Three native form drafts and three editable document templates
- Editable per-job checklists and preserved row history
four pipelines
- Cabinet and millwork jobs · 7 stages
- Commercial millwork · 7 stages
- Built-ins and casework · 6 stages
- Builder accounts · 6 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Field measure
- Drawings sent
- Approval follow-up
- Release to shop
- Hardware ordered
- Install scheduled
- Punch walk
- Finish complete
- Warranty check-in
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Project inquiry and field measure request
- Drawing approval response record
- Install feedback
- Shop traveler ticket
- Hardware and finish schedule
- Install punch list
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore nine fictional cabinet and millwork jobs carrying thirty-one traveler tickets across all six stations, three rows held by the drawing gate, one of them waiting on an approval for a newer revision letter, four tickets past their recorded due date, seven hardware or finish lines not received and five open punch items. Sample edits stay in memory and reset on navigation or reload.
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 business 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 backend helpers are required for connected record creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and enforce the drawing gate and every cross-field rule on the server. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked job holds the site label, the designer or builder, the drawing revision letter, the sent and approval dates, the revision letter the approval was recorded for, the install date and crew label, plus traveler tickets, hardware and finish lines, punch items and an editable checklist.
The drawing gate is enforced in the shared record model, so the included backend helper refuses a ticket past cut while the drawings are not approved. An approval belongs to the revision letter it was recorded for, so changing the letter closes the gate until an approval is recorded for the new one, and a job with tickets past cut cannot change its revision letter without either recording that approval or returning the tickets to cut. Approval is a fact a staff member records with a date and a revision letter; the kit collects no signature. It does not produce CAD, CNC output or cut lists, does not nest or optimize material, holds no inventory, places no supplier orders, and is not a scheduling engine, a payment system or a messaging tool.
Four optional pipeline templates and nine inactive workflow drafts. 9 fictional in-memory jobs with 31 traveler tickets.
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 Cabinet & Millwork Shop Kit
Checking access…
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?
Joinery keeps its application frame across the seven kit views and the native CRM tools in the same signed-in account. 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
