01 / Rack and buildsOpen 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.
GoSeedly Bike Shop Kit
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.
Checking access…See the interface
One-time purchase · USD · Your Seedly backend · Editable kit sourceYOUR SPOKE BIKE SHOP
01 — RACK AND BUILDSActual interface captures with fictional sample data. Open a screenshot for a closer look.
TAKE A CLOSER LOOK
From the counter to the stand to the call.
One connected workspace, with views built around the decisions your team makes each day.
01 / Rack and builds
02 / Service tagsThe whole rack as one ledger.
Every tag with its step, days at step, promised date and the approved and unapproved totals kept apart. Picked-up tags sort to the end.
03 / Waiting on partsKnow what the shop is still waiting for.
Every special-order part by tag with its supplier label, ordered date and expected arrival, and a flag on anything past it.
04 / Ready for pickupFinished bikes should not wait.
Days waiting, whether the rider was called and a plain-words storage note after the days the shop recorded. No fee is calculated.
05 / BuildsNothing leaves the floor unbuilt.
Box arrival, build state, the fit appointment and the accessories to install, with a label on any build recorded ready with no fit booked.
06 / RidersRemember the rider, not just the bike.
The shop's own rider book: bikes owned, last service date, a service reminder month and a club or team label.
07 / InsightsRecorded counts, nothing predicted.
Counts you can filter the rack from, and recorded amounts totalled inside one currency.
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.
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
- Service tags · 7 stages
- New bike builds · 8 stages
- Fit appointments · 7 stages
- Seasonal service reminders · 7 stages
Give the next step a shape.
- 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
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
Explore before adding records.
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 inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
MORE OF THE WORKING DAY
From the first inquiry
to the final handoff.
Editable native forms and document templates give your team a practical starting point.
Three ready-to-edit forms.
- Service booking request
- New bike enquiry
- Pickup feedback
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Three reusable templates.
- Service tag and estimate
- Build and fit checklist
- Ready for pickup call sheet
Open each template in Documents and complete it for the actual job or visit.
Checklists alongside the work.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
THE KIT, UNPACKED
Your workspace.
Your starting point.
Your code to edit.
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.
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 optional pipeline templates and nine inactive workflow drafts
36 fictional in-memory records and a 14 rider sample book
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Read the installation guide FROM KIT TO CONNECTED WORKSPACE
Check. Connect.
Make it yours.
Check your Seedly project.
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
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.
Set up your own team.
Edit shop 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 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.
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.
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
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.
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
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?+
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.
Find a workspace that fits the way you work.
Explore all CRM kits