CRM KitsCourier and local delivery services
Every run, window by window.
A day board for courier and local delivery businesses: every run in its driver's lane on a clock, from the booked pickup window to the booked drop window, with the parcel count and the proof status the office recorded. Legwork keeps runs, proof, regular drop places, the driver week and accounts in one connected workspace.
See every driver's day on one clock.
A seven-day strip with runs and open runs counted in words, then one lane per driver on a 7 am to 7 pm axis. Each run spans its booked pickup and drop windows and shows its status, the drop place, the parcel count and the recorded proof status. Runs without a driver sit in their own lane, and a missing pickup, drop or proof status leads in the needs attention strip.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Day board operating view
- Runs operating view
- Proof operating view
- Places operating view
- Driver week operating view
- Accounts operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable account checklists and preserved row history
four pipelines
- Courier accounts · 8 stages
- Legal and title accounts · 7 stages
- Scheduled route accounts · 7 stages
- One-off and individual runs · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New inquiry follow-up
- Rate sheet review
- First run confirmation
- First drop check
- Proof status review
- Paused account check-in
- Regular drop place check
- Scheduled days review
- One-off follow-up
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Run request
- Regular drop place
- Delivery issue report
- Driver day sheet
- Drop record
- Account rate sheet
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 10 fictional courier accounts and three drivers: seven active, one paused, one lead and one closed, with 35 runs (six booked, nine with a driver assigned, three picked up, 14 dropped, one attempted, one returned and one cancelled), ten of them today, and 11 regular drop places. Sample edits stay in memory and reset on navigation or reload.
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 business 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 backend helpers are required for connected account creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep parcels, miles, minutes and money apart, refuse access codes, logins, card numbers and Social Security numbers, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked account holds the usual pickup address and hours, service mode, usual level, base and per-mile rates as quoted, how the pickup is handed over, start, pause, resume and closed dates, each run with its driver, pickup and drop windows, drop place or address, parcels, pickup time, time at the drop, proof status, received-by name, recorded miles, wait and charge, each regular drop place with its receiving hours and handoff, and an editable checklist.
Legwork records what the office booked and what drivers reported. Parcels are counts; miles, wait minutes and charges are recorded values, and none is added to another. It does not plan routes, track drivers, promise a delivery time, insure a parcel, price runs, bill or take payments, or send messages, and a proof status is never a legal proof of delivery or a chain-of-custody record. Door, gate, lobby, building, dock, keypad, lockbox and alarm codes, Wi-Fi and app logins, payment card numbers and Social Security numbers are refused in recorded text and in the native form drafts.
Four optional pipeline templates and nine inactive workflow drafts. 10 fictional in-memory courier accounts.
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 Courier & Local Delivery 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?
Legwork keeps its dark top bar, orchid tab underline and hour ruler across the kit views and native CRM tools in the same signed-in account. 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 home services kits
Browse all 220 kits
