GoSeedly Mobile Mechanic Kit
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.
YOUR CURBSIDE DAY ROUTE
01 — DAY ROUTE
Actual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
One connected workspace, with views built around the decisions your team makes each day.
01 / Day routeChoose 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.
02 / Appointment sheetSelect a stop to read its vehicle record and mileage reference, the customer complaint, the recorded diagnosis, the quote reference, the parts brought with their on-van flags, and the follow-up repairs recorded for that visit.
03 / Appointment bookThe whole book grouped by recorded appointment date, newest day first, with the window, vehicle, service type, zone label, status, quote reference and follow-up count. Appointments with no recorded date are grouped last.
04 / VehiclesVehicle records grouped out of the appointments already loaded, by recorded year, make, model and plate reference. Each card carries the most recently recorded mileage reference and the recorded diagnosis from every visit, so a vehicle that came back to have the part fitted shows both.
05 / Travel zonesRecorded zone labels with how many appointments used each one, the window most often recorded for that zone, and the days that zone has recorded work. Appointments with no zone label are listed separately, because they never produce a zone change on the day route.
06 / Follow-up repairsRecorded follow-up items grouped by priority, with the ones still only recommended first, each showing the vehicle, the recommendation, its recommended date and its status.
07 / InsightsCounts by appointment status, service type and zone label, the recorded follow-up scheduling rate, and recorded quote reference totals grouped by currency. Nothing is summed across currencies.
YOUR PROCESS, YOUR STARTING POINT
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
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.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
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.
FROM KIT TO CONNECTED WORKSPACE
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
Edit company name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
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.
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.
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.
DEVLAUNCH ALL ACCESS
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
See DevLaunch All AccessAlready a member? Open your downloads.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
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.
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.
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.
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.
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.
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.
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.
Find a workspace that fits the way you work.
Explore all CRM kitsCustomer experiences / Trustpilot
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.