CRM KitsBike shops
Every bike tagged in. Every build on the stand.
A service tag rack beside a new bike build queue. Spoke keeps the tag number, the rider, the bike as they described it, the service package, the special-order parts and the promised date in one connected workspace.
Open work leads the rack.
Service tags hang in promised-date order with a four-step line, the package and add-on lines and both estimate totals. The build queue sits beside them.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Rack and builds operating view
- Service tags operating view
- Waiting on parts operating view
- Ready for pickup operating view
- Builds operating view
- Riders operating view
- Insights operating view
- Three native form drafts and three editable document templates
- A revision-guarded rider book with service reminder months
- Editable per-record checklists and preserved row history
four pipelines
- Service tags · 7 stages
- New bike builds · 8 stages
- Fit appointments · 7 stages
- Seasonal service reminders · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- New booking task
- Tag checked in note
- Estimate approval task
- Parts arrival check task
- Ready for pickup task
- Pickup reminder after a wait
- Build scheduled task
- Thirty-day new bike check-in task
- Seasonal service reminder task
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Service booking request
- New bike enquiry
- Pickup feedback
- Service tag and estimate
- Build and fit checklist
- Ready for pickup call sheet
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 36 fictional records: 22 open service tags across the four steps, 8 new bike builds, 6 picked-up tags in the ledger and a rider book of 14 riders. 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 shop 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 record creation, edits, rider book saves and resource setup. They preserve native account permissions, unrelated custom fields and row history, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked record is one service tag or one new bike build. It holds the tag number, rider label, bike label as typed, an optional serial number in its own field, the service package and its price, add-on lines with approval flags, the stand or mechanic label, the step and its date, the promised date, special-order parts, the build fields and an editable checklist. Riders live in a separate revision-guarded rider book.
The approved total counts the package only once the estimate is approved, plus every add-on line marked approved; the unapproved total counts the same lines the other way round. Past promised, parts past expected arrival, days at step, days waiting and reminders due this month are derived at read time. The kit is not a point of sale, inventory, supplier catalog, parts lookup, serial registry, theft check, bike fit, safety certification, scheduling or messaging product, and it takes no payments. The storage note is plain words after a recorded number of days, never a fee.
Four optional pipeline templates and nine inactive workflow drafts. 36 fictional in-memory records and a 14 rider sample book.
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 Bike Shop 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?
Spoke keeps its slim white rail 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 retail & showrooms kits
Browse all 220 kits
