CRM KitsIndependent car dealers
Every unit priced to move.
A lot inventory aging strip with days on lot against your own age bands, the leads sitting on each unit, and every deal followed through to delivery. Frontline brings the two clocks a small lot runs on into one connected workspace.
Oldest unit first, every morning.
Each unit is one row: days on lot as a large number, an age bar drawn in your own recorded bands with a marker at today, the asking price and its last recorded change, photo and recon flags, and the open leads sitting on that unit.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Lot strip operating view
- Inventory operating view
- Leads operating view
- Appointments operating view
- Deals operating view
- Recon and sourcing operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable per-record checklists and preserved row history
four pipelines
- Lead to delivery · 7 stages
- Appointments and test drives · 7 stages
- Deal to delivery · 7 stages
- Sourcing and recon · 8 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New lead response
- Second follow-up
- Appointment confirmation
- No-show follow-up
- Deal paperwork
- Funding pending check
- Delivery prep
- Post-delivery review request
- Aged unit price review
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Vehicle enquiry
- Test drive request
- Trade-in details
- Lead follow-up call sheet
- Deal jacket checklist
- Delivery day checklist
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 22 fictional units and 27 fictional lead and deal records. 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 lot 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, the lot book and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and refuse free text that reads like a government identifier, a card or account number, a full VIN, a credit score or a licence number. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked record follows one customer from the first enquiry to delivery, holding the source, the unit of interest, the received and first response times, appointments, a deal step with recorded amounts and an editable checklist. Units live in the kit's own lot book with your age bands, aging threshold and response window.
Days on lot, age band, leads per unit and response time are derived from what you record. The kit is not a DMS, an inventory feed or a listing syndication, it does not decode a VIN or fetch vehicle history, and it takes no credit application and calculates no payment, rate or trade value.
Four optional pipeline templates and nine inactive workflow drafts. 22 fictional units and 27 fictional records.
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 Independent Car Dealer 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?
Frontline retains its application frame across the kit views and 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 automotive & fleet kits
Browse all 220 kits
