CRM KitsMobile mechanics
Every appointment. On the driveway, on time.
A mobile mechanic drives to the car, so the day is a sequence of stops rather than a board of tickets. Curbside puts that sequence on a crimson and white timeline in recorded arrival-window order, marks where the recorded travel zone changes between legs, and keeps the selected vehicle, complaint, diagnosis and parts list in a sheet beside it.
The day, in order.
Choose a date and read the stops down one rail in recorded arrival-window order, with the customer, vehicle, service type, zone label and status on each block. A gray chip marks where the recorded zone label changes between two consecutive stops.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Day route timeline with recorded travel-zone chips and an appointment sheet
- Appointment book grouped by recorded date
- Vehicle and travel-zone records derived from the loaded appointments
- Follow-up repair queue grouped by recorded priority
- Insights drawn from recorded workspace data, grouped by currency
- Crimson and white Curbside application frame with full CRM tools
four pipelines
- On-site appointments · 8 stages
- Diagnostics and quotes · 7 stages
- Fleet on-site service · 7 stages
- Follow-up repairs · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Appointment confirmation task
- Parts check task
- Arrival window reminder task
- Diagnosis write-up note
- Quote follow-up
- Follow-up repair scheduling task
- Fleet visit prep note
- Post-service check-in
- Seasonal service note
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore ten fictional appointments on one day across three recorded travel zones, with their parts lists, recorded diagnoses and follow-up repair items. Example edits stay in the current page’s memory and reset on navigation or reload; sample appointments 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 appointment helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, re-checks every cross-field rule on the server, and compares the current record timestamp and revision before saving. It deliberately exposes no stage mutation, so a stage change runs through the host’s own function. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
One on-site appointment is a native contact-linked opportunity. Its namespace holds the customer address, travel zone label, appointment date and arrival window, vehicle year, make, model, plate reference and mileage reference, service type, complaint, recorded diagnosis, quote reference, status, a follow-up recommendation with its due label, a recorded parts list, and follow-up repair items with stable IDs. Unrelated custom fields are preserved.
The timeline is the order somebody wrote down. There is no routing, no GPS and no travel-time calculation: the zone chip says the recorded zone label changed, nothing more. Arrival windows reserve nothing and create no native Calendar appointment. Vehicle details are typed by staff; no VIN is decoded. A part row is a label, a quantity and an on-van flag, with no catalog, pricing, stock level or ordering. The quote reference is a recorded number, separate from native opportunity value, and requires a recorded diagnosis behind it. Nothing in the kit texts, calls or emails a customer. Stage changes stay with the native CRM, under its own permission.
Four optional pipeline templates and nine inactive workflow drafts. Ten fictional in-memory appointments on one day across three travel zones.
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 Mobile Mechanic 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?
Curbside keeps its driveway navigation across the original mobile mechanic views and the 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 automotive & fleet kits
Browse all 220 kits
