GoSeedly Auto Repair Shop Kit
A repair shop does not run on a funnel or a calendar. It runs on the repair order. Gasket makes that ticket the work surface: a stack of printed-looking shop tickets that open their whole record inline, with the two things that actually stall a shop, approvals and parts, given their own views.
YOUR GASKET TICKET STACK
01 — TICKET STACK
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 / Ticket stackEach repair order reads like a printed shop ticket: a large monospace RO number, the vehicle, the plate or VIN reference, the recorded odometer, the lift label and a red status stamp. Beside it sit the promised date, the approved total, how many line items are still awaiting an answer and how many recorded parts have arrived.
02 / Repair order recordOpening a ticket expands it in place, pushing the stack down. The customer complaint and the recorded diagnosis sit side by side above every line item with its recorded approval state and every part with its vendor label and dates. There is no side panel and no second screen.
03 / Approvals queueEvery recorded line item across every repair order, split into awaiting, approved and declined, with the amount and the ticket it belongs to. Two controls record the answer a customer already gave. The kit sends no message and opens no approval link.
04 / Parts on orderRecorded parts with vendor labels, the date the office ordered them and the date they are expected. Past the expected date simply means a recorded date has gone by with no receipt flag. Marking a part received is something a person does when the box is on the shelf.
05 / Lift boardEvery lift label found on the loaded repair orders, with the tickets recorded against it and a separate card for the vehicles not on a lift. Two open repair orders on one label show as a recorded conflict for review. Lift labels reserve nothing and assign nobody.
06 / Vehicle recordsRepair orders grouped on the plate or VIN reference, or on the vehicle description when no plate was entered, with the highest recorded odometer and each visit’s status stamp and approved total. There is no separate vehicle master record and no VIN decoding.
07 / Shop insightsCounts by status stamp, recorded approval outcomes with the approved amount in USD records, recorded parts state and recorded lift use, for the selected pipeline only. Every number comes from something a person entered.
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 repair orders sitting at different status stamps, with twenty-four line items across awaiting, approved and declined, nine recorded parts, lift labels including one recorded conflict, and one vehicle that has been in twice. Example edits stay in the current page’s memory and reset on navigation or reload; sample repair orders 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 repair order is a native contact-linked opportunity with a repair order number, the vehicle, a plate or VIN reference, an odometer reference, the customer complaint, the recorded diagnosis, a lift label, a promised date and a status stamp. Line items and parts are stable-ID child records. Unrelated custom fields are preserved and stale record versions are rejected.
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 repair order helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps stable line item and part IDs, archives child rows instead of dropping them, and checks the current record state before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Status stamps, approvals, parts receipts and lift labels are all staff entered; nothing advances on its own. The kit reads no parts catalog, checks no availability, contacts no vendor and places no order. It has no labor guide and no flat rate times. It does no VIN decoding, registration lookup or vehicle history report. It sends no customer message, opens no approval link and collects no signature. It produces no invoice, takes no payment and calculates no tax. It books no appointment, reserves no lift and assigns no technician; a lift carrying two open repair orders is flagged for review, not prevented. Line item amounts are recorded references, separate from native opportunity value, estimates and payments.
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.
Gasket keeps its repair shop navigation across the original 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.
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 kitsUse the auto-shop demo to work through customer approvals, parts status, and the next handoff.
Read the auto repair CRM workflow guide →Customer 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.