GoSeedly Appliance Repair Kit
Appliance repair is a two-visit trade with a wait in the middle. Reset draws every job as one row on one fourteen-day axis: the day somebody went out, the gap while the part is on its way, and the day somebody is going back. The rows with no day going back are the ones you can see at a glance.
YOUR RESET REPAIR TRACKER
01 — TWO-VISIT TRACKER
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 / Two-visit trackerEvery job in the selected pipeline sits on one shared fourteen-day axis, grouped by appliance type, with an emerald rule on today. Each bar carries the diagnostic visit day, the hatched parts wait, and the return visit day, or an open dotted segment when no return is booked.
02 / Job sheetSelecting a row opens the appliance record read off the rating plate, the recorded fault code and finding, the part lines with their ordered and expected dates, and the two visits with their technician labels and outcomes. A delivery can be recorded straight from the sheet.
03 / Repair jobsEvery job grouped by its native pipeline stage, with the recorded state read from the visits and part lines beside it. The two are deliberately separate: recording a delivery never moves a card, and moving a card never records a delivery.
04 / Parts waitingEvery part line that is waiting, ordered by the days since it was ordered, with the lines past their recorded expected date marked overdue. Received and archived lines are listed underneath, so the whole parts record reads across jobs rather than down one job.
05 / Return visitsRecorded return visits grouped by date with the technician label, the recorded outcome, and how many days after the diagnostic visit each one falls. The diagnosed jobs with no return booked are listed underneath in their own group.
06 / Repair insightsJob counts by recorded state and appliance type, the first-visit fix rate, the part receipt rate, the mean return gap, and recorded quoted totals grouped by currency. Every figure counts rows somebody entered and says nothing recorded rather than inventing a zero.
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 twelve fictional repair jobs across six appliance types, with 11 part lines and 16 recorded visits. Four are waiting on a part, one of those past its recorded expected date, five record a return visit and three record a repair. Example edits stay in the current page’s memory and reset on navigation or reload; sample jobs are never inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
A repair job is a native contact-linked opportunity with a namespaced appliance record (type, brand, model, serial reference, age reference and warranty flag), the recorded fault code and finding, a technician label, a quoted amount, job notes, up to 20 part lines with stable IDs, and at most one diagnostic visit and one return visit. Two jobs on the same machine stay independent; the kit keeps no appliance master record.
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, promise line, 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 appliance repair 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, and compares the current record timestamp and revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Visits and part lines are staff-entered records. A visit date reserves no technician, checks no availability and creates no native Calendar appointment. A part line records an order placed in the supplier’s own system: there is no parts catalog, supplier integration, delivery feed or inventory. A part line is marked overdue only when its recorded expected date has passed and it is not received, which is the only warning state in the kit. The warranty flag is a staff entry; nothing checks coverage or submits a claim. The recorded job state is derived from the visits and part lines on every read, and the helper exposes no stage mutation at all, so it can never disagree with the native pipeline stage.
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.
Reset keeps its index rail across the original repair 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.