A tow operator does not work a board of tickets waiting for a bay. The work arrives by phone, in order, at any hour. Hook is a full dark console where the shift reads down the screen as a log and the selected call sheet stays open beside it.
A dense chronological table grouped by the recorded call date, newest day first, with monospace times and plate references so the time column reads straight down. A call still recorded as active is yellow, a cleared or cancelled call is gray, and the one red marker means a recorded priority flag. The sheet beside it holds the caller and account, the pickup and drop, the vehicle and plate, the truck and driver, the recorded requested, arrived and cleared times with the gap between the first two, the impound record and the recorded charges.
A tile per vehicle whose call records a lot-in date and a release status, ordered by days held so the vehicle that has been there longest is the first thing you read. Each tile carries the plate reference, the lot label, the recorded lot-in and released dates and the recorded charge total. Days held is the selected console date minus the recorded lot-in date. Nothing accrues and no storage fee is calculated.
The recorded account labels, derived by grouping the calls that are loaded, with the rate reference somebody wrote down, the calls recorded in the selected console month up to that date, the total in the loaded scope and the most recently recorded call. Calls with no account label are grouped last under "No account recorded". There is no account master record and no statement.
The recorded truck labels with the calls on the selected console date, the calls across the loaded scope, the calls still recorded as active and the driver labels that appear with each truck. A truck label is text somebody typed on a call: nothing here tracks a truck, knows where one is, or assigns work to it.
The impounded vehicles grouped by recorded release status, authorized releases first, then the vehicles still on the lot, then the released ones, ordered by recorded released date. Each row shows the lot, the lot-in date, the days held and the recorded charge total. Nothing issues paperwork, collects payment, or claims anything about lien or notice requirements in any jurisdiction.
Recorded call counts by status and by call type, a recorded clear rate that leaves cancelled calls out and reports "None recorded" rather than a zero, the spread of recorded arrival gaps with the count of calls recording no arrival, the lot counted by release status, and rate and charge reference totals grouped by currency and never added across them.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Roadside calls · 8 stages
Impound and release · 7 stages
Account customers · 7 stages
Heavy duty and transport · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
Call assignment task
Arrival check task
Cleared call note
Impound intake checklist note
Notice reminder task
Release paperwork task
Account month-end review task
Heavy duty scheduling task
Driver debrief note
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
Explore fourteen fictional calls across four fictional account customers, six of them recording a vehicle still on the lot with holds from the same night out to almost two weeks. Example edits stay in the current page’s memory and reset on navigation or reload; sample calls are never inserted into your CRM.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
A call is one dispatch request, stored as a native contact-linked opportunity with a namespaced call record name, call type, caller and account labels, pickup and drop locations, vehicle year, make, model and plate reference, truck and driver labels, the recorded call date and the recorded requested, arrived and cleared times, the recorded call status, a priority flag, an optional rate reference, an impound record and recorded charge rows. The rate reference and the charge rows stay separate from native opportunity value. Other custom fields are preserved, and charge rows are archived rather than dropped from a save.
Two-column call log: a dense chronological table beside a 380px call sheet, each scrolling inside one shared height
Yellow for an active call, the selected row and a primary action, and red for exactly one thing, a recorded priority flag
Impound lot tile grid ordered by days held, counted from the recorded lot-in date to the console date you choose
Accounts, trucks and releases derived from the loaded calls, each labelled as derived on screen
Insights over recorded statuses, call types, the clear rate, arrival gap spread and reference totals by currency
Installation-wide neutral black theme, so native CRM pages render as dark surfaces in the same frame, with full CRM tools
Four optional pipeline templates and nine inactive workflow drafts
Fourteen fictional in-memory calls, six of them recording a vehicle on the lot, across four account customers
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
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.
03
Set up your own team.
Edit company name, descriptor, and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
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 call helper is required for connected creation, editing and starter setup. It preserves native account permissions and unrelated custom fields, keeps stable charge IDs, preserves unknown fields inside the impound record, and checks the current record state before saving. Stage changes use the host’s own pipeline mutation, so they obey your existing roles. Deploy the helper from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
Every cross-field rule is checked in the browser and again on the server: a requested time needs a call date, an arrival needs a requested time it cannot precede, a cleared time needs an arrival it cannot precede, a cleared call needs a cleared time, an on-scene, in-tow or cleared call needs a truck label, a transport or impound call needs a drop location, and nothing is on the lot without a recorded lot-in date. Days held is a difference between two dates and the arrival gap is a difference between two typed times, so neither is a measured response time, a service level or a charge. There is no GPS and no truck tracking, no dispatch routing and no motor club, insurer or app integration, no invoicing, payments or storage-fee accrual, no lien processing, statutory notice, title work or auction handling, no driver or caller messaging, and no calendar booking. The impound lot, accounts and trucks views are all derived from the calls that are loaded, and each says so on screen. Empty values are reported in words, so a call with no truck says "No truck recorded" rather than showing a dash.
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.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
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.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
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.
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
Good questions. Clear answers.
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?+
Hook keeps its towing navigation across the original console 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.
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.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
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.
01 / Call log
