BIKE.co

By BIKE.coBusiness Technology Management

BIKE.co episodes

October 30The Work Order That Pays: Building a Bench Process That Bills Every Hour
There's a quiet revenue leak hiding in most independent bike shops, and it's not on the price list — it's in the space between what gets written on a work order at drop-off and what actually gets done at the bench. This episode of BIKE.co breaks down why that gap exists, how to measure it, and what a practical bench process looks like when it's built to capture every billable minute.
If you've ever wondered whether your shop's bike shop software cost breakdown reflects the true cost of lost labor, this episode gives the operational context to make sense of those numbers. Here's what the show covers:
The anatomy of unbilled labor — how small undocumented tasks (a bent hanger here, a quick cable end there) compound across a full week of jobs into hours of skilled work given away for free.

What a work order is actually for — the critical distinction between an intake note (a best guess before anyone looks at the bike) and a work order that evolves into a precise, billable record of what really happened.

Treat the assessment as a billable event — why shops should put an inspection or assessment line item on every ticket by default, and how doing so also speeds up quoting and builds customer confidence.

Log work at the bench, not from memory — the structural reason most shops lose detail at the end of a job, and how incremental documentation — enabled by tools like mechanic time tracking — changes the habit without adding friction.

The pre-invoice review — a practical quality-control step where a service manager checks the work order against the original intake before generating the invoice, protecting both revenue and customer trust.

A one-week audit to find your gap — a concrete first action: pull last month's closed bike shop work orders, compare invoiced totals to actual hours, and use the difference to start a process conversation with your team.
The episode frames the fix not as a technology problem or a staffing problem, but as a loop — intake, assessment, in-progress documentation, pre-invoice review — where each stage checks the one before it. Build the loop, and the hours that are already being worked start showing up on invoices where they belong.
For more on pricing and recovering labor value on the service side, check out the related episode The Labor Rate Conversation: How to Quote Repair Time Without Losing the Job.
BIKE.co
5 min
October 27The Labor Rate Conversation: How to Quote Repair Time Without Losing the Job
Every bike shop mechanic has lived this moment: a fair quote lands on the counter, the customer flinches, and suddenly you're defending your labor rate from scratch. This episode of BIKE.co digs into why that moment happens so often — and why the fix isn't lowering your prices, it's changing what surrounds them. From how you structure a quote to what your invoice says at pickup, small documentation habits make a measurable difference in how many jobs you actually close.
If you've ever wondered why customers accept the same rate at one shop and push back at another, the episode has a clear answer. Here's what's covered:
Why bare quotes fail: A number without context invites the customer to write their own story — and they almost always make you look expensive. For a closer look at how software pricing works the same way, the bike shop software cost breakdown on the BIKE.co blog is a useful parallel read.

Tiered, outcome-based quoting: Naming what each service tier delivers — not just what tasks it involves — gives customers a basis for comparison and makes your value legible before objections form. Repair quotes built around outcomes close more jobs than itemized task lists.

Checklists as live work tools: Service checklists earn their keep not as filed paperwork but as active parts of the work order — ensuring consistency, preventing comebacks, and creating a record that speaks for itself if a customer questions the invoice.

The partial-authorization problem: When a mechanic discovers additional work mid-job, shops most often handle it wrong — fixing it silently, halting with no process, or skipping it entirely. The answer is a defined escalation threshold agreed on by the whole team before any bike hits the bench.

Invoices that confirm, not reopen: Line items that mirror the language from the original quote feel honest. Cryptic codes or a single lump labor line create friction at exactly the moment you want to be building trust and collecting payment.

Mechanic retention as a side effect: Shops with clear quoting and authorization habits reduce the ambient ambiguity mechanics navigate every day — and that clarity is a meaningful factor in why good technicians stay.
More from the show: if you're thinking about the operational calendar behind all of this, The Spring Rush Is Not a Surprise: How to Schedule It Like One covers how to build a service schedule that absorbs seasonal volume without chaos. For more tools referenced in this episode, explore the labor rate guide and the repair pricing calculator in the BIKE.co resource library.
BIKE.co
5 min
October 23The Spring Rush Is Not a Surprise: How to Schedule It Like One
Spring arrives on the same schedule every year, yet most independent bike shops still greet the first warm weekend like it caught them off guard. This episode of BIKE.co tackles the real culprit behind spring chaos: accepting work based on available floor space instead of available labor hours — and what it actually looks like to schedule a rush instead of just surviving one.
If your shop has ever closed out a busy week with unhappy customers and overdue bikes despite the work getting done, this episode is for you. Here's what's covered:
The floor-space trap. Most shops greenlight a drop-off the moment there's a hook or a floor spot — without ever checking whether the labor to close that bike exists before the promised date.

Building a real capacity number. Factoring in interruptions, parts chasing, and part-time schedules, a two-full-timer, one-part-timer shop may have only 50–55 billable hours per week — a ceiling that doesn't move no matter how many bikes come in the door.

Booking by hours, not hooks. The front-counter question shifts from "is there floor space?" to "do we have the billable hours available before this customer's promise date?" — a discipline that makes realistic turnaround times possible and follow-up calls rare. Bike shop scheduling built around committed labor hours makes this check fast enough to do at intake.

Why an honest promise date beats an optimistic one. A shop that quotes ten days and delivers in nine builds more trust than one that quotes three and calls to push it back — twice.

Technician assignment and batching. Aggregate capacity isn't enough; knowing which mechanic is doing which job, and grouping similar work (cable sets, e-bike diagnostics) into dedicated blocks, prevents scope creep and protects focus time.

Connecting repair quotes to the week view. When work orders carry estimated labor from the quote, committed hours populate the schedule automatically — no whiteboard math, no guessing at the counter.
For a closer look at the financial side of running shop software efficiently, BIKE.co's bike shop software cost breakdown is worth a read alongside this episode. If you're weighing a platform switch before the season peaks, the related episode Price a Bike Shop Software Switch Before You Sign covers what that decision actually costs. More resources and tools are available at BIKE.co.
BIKE.co
5 min
October 20Price a Bike Shop Software Switch Before You Sign
A software proposal landing in your inbox looks like a number, but it rarely is one. This episode of BIKE.co breaks down the full cost of switching point-of-sale or shop management software — from the seats and modules you'll actually use to the migration surprises, payment processing gaps, and contract clauses that quietly reshape the total. The companion article on pricing a bike shop software switch goes deeper on the methodology if you want it in front of you while you listen.
Here's what the episode covers:
Rebuild the quote from scratch. Headline pricing reflects the cheapest seat on the cheapest plan. The real floor comes from counting every person who touches the system in a real week, multiplying by locations, and adding per-seat uplifts — before a single module is switched on.

Price every module, even the "free" ones. Rentals, SMS, loyalty, and advanced service reporting often show up as line items the month you actually turn them on — not before.

Treat migration as four separate budget lines. Customer and bike records, open work orders, inventory mapping, and historical data each carry different risks and different price tags. Industry data puts cost overruns on migration projects at around 30% on average — and that's the base rate, not a worst case.

Payment processing belongs in its own column. The quoted blended rate and the effective rate on a debit-heavy transaction mix can diverge enough to fund a full mechanic training budget — roughly $2,100 a year on a shop doing $600K in revenue.

Training is a line item, not a favor. Two onboarding webinars are not a training plan. Get the hourly rate for additional sessions in writing before you sign, because post-signature rates are always higher. For context, work order workflows alone warrant hands-on time with real shop data, not demo records.

Read four contract clauses before you negotiate price. Auto-renewal uplift caps, liability limits, data export rights, and termination-for-convenience terms can each cost more than a year of subscription fees if left unaddressed.
The episode closes by recommending a side-by-side 12-month and 36-month total — subscription, seats, modules, hardware, migration, training, and payment fees on actual volume. The NBDA's 2026 Cost of Doing Business Study puts average operating expenses at 40.4% of sales; if your three-year software total clears 2% of forecast revenue, something in the stack is overbuilt. For a detailed look at how BIKE.co stacks up against the platforms most independent shops are comparing right now, the BIKE.co vs Lightspeed comparison is a good starting point. If you're also weighing field-service tools, check out BIKE.co vs Jobber for a side-by-side on that angle. More from the show: What a Custom CRM Actually Costs a Bike Shop (Beyond the Per-Seat Price) covers the hidden overhead that follows even well-priced software into your workflow.
BIKE.co
6 min
October 16What a Custom CRM Actually Costs a Bike Shop (Beyond the Per-Seat Price)
The per-seat price on a CRM vendor's homepage is only a fraction of what a bike shop will actually spend. This episode of BIKE.co digs into the full cost stack of a custom CRM deployment — the fees that rarely appear in a sales call but reliably blow up budgets by year two. It's based on the BIKE.co deep-dive on custom CRM pricing for bike shops, and it's essential listening before you sign any statement of work.
The episode walks through every major cost layer that shop owners tend to underestimate or miss entirely:
Scoping isn't free discovery. Sizing a custom build takes 10–25 consulting hours at $100–$250/hr — a multi-location or e-bike shop with a rental fleet can spend $5,000–$8,000 before anyone touches a database.

Data migration is where variability hides. Moving customer records, bike serials, linked service history, open work orders, and gift card balances out of platforms like Lightspeed or Ascend typically runs $2,500–$6,000 — and data auditing is the step most shops skip at their peril.

Bike shops have unusually complex data schemas. E-bike battery warranties, suspension service intervals, rental deposit status, and fit records are all custom objects — and 50 custom fields across 6 objects is where quotes start to double.

Training is the line owners cut first and regret longest. Gartner data consistently shows that CRM failures are a people problem, not a software problem; a realistic training budget for a two-location shop runs $2,000–$5,000 through the first 90 days, including a hypercare period after go-live.

Every integration is both an upfront cost and a recurring liability. Three integrations at $5,000 each means $15,000 up front plus up to ~$4,000/year in ongoing maintenance — a real argument for purpose-built software for repair-first shops that already includes what you need.

Year two isn't free. Custom software maintenance runs 15–20% of original development cost annually for bug fixes, security patches, and library updates — on a $25,000 build, that's $3,750–$5,000 before a single new feature is added.
The episode closes with a realistic year-one budget range for a single-location, repair-first shop: $8,000–$15,000 plus subscription — a figure that looks very different from the per-seat number on any vendor's pricing page. For more context on what a shop management system actually needs to do before you consider any CRM layer on top, listen to What a Bike Shop CRM Actually Needs to Do. Full pricing details are on the BIKE.co pricing page.
BIKE.co
5 min
October 13What a Bike Shop CRM Actually Needs to Do
Choosing a CRM for a bike shop sounds straightforward — until six months in, your service writers are still asking customers which bike they brought in last spring. This episode of BIKE.co digs into why most shop CRMs fail the service department, and what a purpose-built tool actually looks like when you open it on a real customer file. The discussion draws on the bike shop CRM checklist published on the BIKE.co blog.
Here's what the episode covers:
The bike as the primary record: Auto repair software centers the vehicle, not the owner — bike shops need the same logic. One customer, three bikes, three completely different specs; if the record is built around the person, every visit starts from scratch.

What bike-level fields actually matter: Serial number, frame size, brake standard, derailleur hanger part number, bottom bracket spec, tubeless setup — and for e-bikes, motor system, battery serial, firmware version, and key number. If a vendor demo can't show you these on a bike-level record, you're looking at a sales CRM in a service costume.

Repair history vs. invoice history: A list of past invoices tells you what a customer paid for. A real service record carries declined work, actual parts used by SKU, labor time per job, and searchable mechanic notes — the kind of detail that saves an hour on the next visit. Bike shop work orders built around this structure make the difference visible immediately.

Why texting has to live inside the ticket: SMS open rates sit around 98%; automated reminders reduce no-shows by 30–60%. But none of that holds if the thread lives in a separate app. The right pattern puts the text conversation inside the customer-and-bike record, firing status updates from the ticket and routing replies back to the same thread — alongside an AI receptionist for bike shops that can handle initial inbound contact without pulling a mechanic off the stand.

The retention math: The probability of selling to an existing customer is 60–70%; for a new prospect, 5–20%. A five percent lift in retention can raise profits by 25–95%. Clean bike-level records are the engine behind that number — enabling timely outreach based on last service date, flagged wear, and seasonal patterns.

Questions to ask in a vendor demo: Pull up a demo customer with three visits. If you see three invoices and three dates, the product knows what a sale is — not what a repair is. Ask about texting numbers, photo support, and whether a customer reply creates a task or vanishes.
More from the show: if you're weighing what bike shop software actually costs across all its line items, the episode What a Bike Shop Actually Pays for Software, Line by Line pairs well with this one. For a deeper look at how BIKE.co approaches pricing, see BIKE.co pricing.
BIKE.co
6 min
October 09What a Bike Shop Actually Pays for Software, Line by Line
The pricing page is the starting point, not the whole story. This episode of BIKE.co breaks down the real cost of running bike shop software by walking through a quote the way a careful owner should — line by line, the way you'd audit a bank statement. If you've ever been surprised by month three of a new system, this one is for you. The full analysis is drawn from this detailed bike shop software cost breakdown published on the BIKE.co blog.
Here's what the episode covers:
Subscription sticker price vs. real price: Bike-specific platforms cluster at the higher end of the $50–$200/month range, and the tier you actually need — the one with the QuickBooks sync or multi-user access — is almost always one step above the plan you quoted.

Per-register and per-location fees: Each additional till is typically billed separately, turning a clean headline number into something considerably larger for a multi-station shop.

Payment processing as the dominant line item: At an average effective swipe rate around 2.4%, card processing routinely accounts for more than half of a shop's total software spend once real card volume runs through — and bundled processor lock-ins deserve extra scrutiny before you treat a discounted software price as a win.

One-time costs that quotes tend to bury: Hardware per station can reach $2,000 or more, migration fees vary widely depending on whether serial-numbered bikes and service history are included, and training downtime for a five-person team represents a four-figure soft cost before the vendor invoices anything. For shops managing complex intake workflows, purpose-built tools like bike shop work orders can reduce the training surface area significantly.

Integration sprawl: A shop running separate tools for scheduling, ecommerce, email, accounting, payroll, and text messaging can easily reach seven subscriptions — each with its own seat pricing and renewal date. New software that replaces only one or two of those tools adds cost, it doesn't consolidate it.

A sanity-check benchmark: Small businesses typically allocate 4–6% of annual revenue to technology. For a shop at the $1.2M industry average, that's $48,000–$72,000 across every piece of software, hardware, connectivity, and payment processing combined. If a single POS quote is consuming a third of that envelope before payments, the math doesn't work.
The episode closes with a practical exercise: take the vendor quote, open last month's bank statement, and write every line of the quote as a real monthly debit. Shops evaluating their labor economics alongside software costs may also find the labor rate guide a useful companion. If you missed the previous episode, The Comeback Problem: How to Stop Fixing the Same Bike Twice is worth a listen before you commit to any new system.
BIKE.co
6 min
October 06The Comeback Problem: How to Stop Fixing the Same Bike Twice
Every service shop has them: bikes that come back two days after pickup, customers who are frustrated, and mechanics who are pretty sure they did the work right. Comebacks are inevitable, but the way a shop handles them — the process, the documentation, the conversation — reveals a lot about the health of its entire service operation. This episode of BIKE.co digs into the comeback problem from the ground up, separating the avoidable from the ambiguous and laying out the habits that help shops stop fixing the same bike twice.
Here's what the episode covers:
Mistake vs. misunderstanding: The two root causes of comebacks look identical at the front counter but demand completely different responses — confusing them is where shops go wrong.

Why intake documentation changes the whole conversation: Recording the bike's condition at drop-off — including what was noticed and not addressed, and why — turns a tense comeback into a two-minute reference check. Bike shop work orders that capture those condition notes give everyone a shared record to point to.

Handling genuinely ambiguous comebacks: When neither the shop nor the customer is sure what happened, winning the argument is the wrong goal. Treating the visit as a diagnostic opportunity — looking at the bike together, narrating what you find — preserves the relationship without surrendering accountability.

The hidden cost of silent write-offs: Absorbing ambiguous comebacks without logging them makes the problem invisible. Without a record, you can't spot whether a specific repair type, service tier, or mechanic skill gap is quietly generating repeat visits.

Building a simple comeback log: Tagging any return visit within a two-week window on the original job — noting what was found, what was done, and whether it was a warranty — creates the data that surfaces patterns over time. Consistent service checklists at intake reduce ambiguity before a job even starts.

What the data eventually tells you: A comeback log reveals underpriced repairs that rarely hold on the first pass, training gaps in specific skill areas, and service tiers that aren't setting the right customer expectations.
If you're thinking about the broader systems that support repeat-free service work, the BIKE.co blog has a practical look at switching your bike shop away from Lightspeed — worth a read if your current software is making documentation harder than it should be. For more on pricing the service side of your shop, don't miss the earlier episode Why Your Tune-Up Menu Is Costing You Money (And How to Fix It).
BIKE.co
5 min
October 02Why Your Tune-Up Menu Is Costing You Money (And How to Fix It)
A tune-up menu is often the very first thing a potential customer hears from your shop — and most of them are an accidental collection of task lists inherited from years past. This episode of BIKE.co digs into the operational and pricing logic behind building a service menu that's genuinely easy to sell, easy to deliver, and easy to defend when something goes sideways. If you're rethinking how your shop prices labor more broadly, the labor rate guide is a strong place to start before rebuilding your tiers.
Here's what the episode covers:
Task-based vs. outcome-based tiers: Defining each service level by the condition the bike leaves in — not just the motions a mechanic goes through — eliminates the comeback arguments that task lists invite.

Pricing the gaps correctly: Tiers priced too close together collapse into one option in practice; tiers too far apart kill your mid-range. The episode walks through a worked example showing how interval spacing drives which tier becomes your volume seller.

What to explicitly exclude: Stating what's not included in a tier removes bench-side judgment calls, turns add-ons into clean customer conversations, and eliminates invoice surprises — a small structural choice with an outsized effect on trust.

Making your work orders do more work: When your service checklists map to outcomes rather than motions, every completed step becomes an accountability checkpoint — useful for comeback protection and for training newer mechanics.

Naming your tiers so your team actually uses them: Forgettable tier names ("Basic / Standard / Premium") get replaced with vague, hesitant pitches at the counter. Names your staff can say with confidence shape how your whole shop talks about its services.

The menu as a management tool: A well-designed tune-up structure sets expectations, defines what "done" means, and gives every person in the shop something consistent to stand behind — not just a pricing sheet.
Use a three-tier tune-up checklist to put these ideas into practice right away. More from the show: listen to How to Switch from Lightspeed to BIKE.co Without Losing the Winter for a related look at the operational decisions that happen behind the counter.
BIKE.co
5 min
September 30How to Switch from Lightspeed to BIKE.co Without Losing the Winter
For most independent bike shops, Lightspeed earns its keep at the retail counter — but service is where the real margin lives, and a bolt-on service module rarely cuts it when repairs are your profit center. This episode of BIKE.co lays out a practical, low-risk path for shop owners who have already decided to move their workshop off Lightspeed and just need to know how to do it cleanly. The full step-by-step plan behind the episode is in the detailed switching guide on the BIKE.co blog.
The episode covers a six-week parallel-run migration strategy designed to fit inside the winter slow season — the one window where training doesn't eat into billable time and a dropped ticket won't cost you a peak-season customer. Here's what gets unpacked:
Why winter is the only realistic window: Nearly 80% of service volume is compressed into seven months, making a mid-season cutover mathematically brutal — and a slow Tuesday in November genuinely manageable.

The parallel-run principle: Rather than a hard flag-day switch, the method keeps both systems live for a defined overlap period, with a single rule — every new ticket into BIKE.co, every existing open ticket finishes in Lightspeed — to prevent the same bike from living in two systems at once.

What moves and what stays: Workshop tickets, bike shop work orders, bench scheduling, mechanic time tracking, repair invoicing, and service checklists migrate to BIKE.co; retail POS, parts inventory, and card processing stay in Lightspeed for now.

Week-by-week scope: Six distinct phases — scope definition, system configuration, ticket cutover, full bench migration, reconciliation, and archiving — each with a clear goal and a defined endpoint.

Honest roadmap awareness: The episode names exactly which BIKE.co features are live today and which are still planned, so shops can build a migration that doesn't depend on functionality that doesn't exist yet. See what is live and what is planned.

Four metrics to track post-switch: Turnaround time, billable hours per mechanic per day, missed calls, and average ticket value — concrete numbers to evaluate the move come spring, not just a gut feeling.
Whether you're running a repair-first operation or a full retail-and-service shop, the core argument here is simple: if service is where your margin is, the software running that side of the business should be purpose-built for it. Winter is the window to make that change without losing revenue, momentum, or your mechanics' sanity.
BIKE.co
5 min

About BIKE.co

From the publisher's feed

The service department is where an independent bike shop makes or loses its margin. Labor rates and tune-up menus, quoting a repair the customer will approve, keeping the bench moving through the spring rush, e-bike diagnostics and warranty paperwork, comebacks, and the software a shop actually needs to run all of it.

Share BIKE.co

Sign up to save your podcasts

BIKE.co

BIKE.co episodes

About BIKE.co