Running your workshop on Excel: when to stop

Every workshop spreadsheet starts the same way. A mechanic tired of scribbling work orders on a notepad opens a blank sheet and lines up columns for customer, bike, job, price. It works fine, for a while. Then the file grows, splits into "inventory_2025_FINAL_v3.xlsx", someone saves it to the wrong desktop, and on the one evening you need to know whether there's still a 28" inner tube on the shelf, nobody can find the version that's actually current. The workshop software vs Excel question is never really about principle. It's about the moment the spreadsheet stops holding up under the shop's real workload.

What holds up, and for how long

In the early days, with a handful of customers and one mechanic, Excel (or Google Sheets) is an honest tool: free, flexible, familiar. A shop running twenty jobs a week can keep everything in one file without much drama. The catch is that a workshop that's doing well grows, and growth brings background noise: more rows, more columns, more people editing the same file, more crossovers between data that was never built to talk to itself. A spreadsheet has no real relationship between "this customer", "this bike" and "these three jobs done over the last two years" — every row sits in isolation, and reconstructing a bike's history means scrolling by hand, hoping nobody renamed a tab along the way.

Where the spreadsheet breaks down

The first failure point is inventory. A shop that draws 60-90% of its revenue from service work — a figure that keeps showing up across the industry — can't afford to discover mid-repair that the part marked "in stock" sold yesterday and nobody updated the cell. With component lead times that have stretched to 340-700 days in some categories, a stock error isn't a minor annoyance: it's a customer waiting on a part that turns out not to exist, because the spreadsheet was wrong.

The second is e-bike traceability. Electric bikes now account for a large share of workshop jobs, and motor and battery warranties have become, in 2026, the industry's single biggest management headache: you need to know when that battery was installed, under which serial number, under what warranty, and pull it up in twenty seconds while the customer is standing at the counter. In Excel that means one more hand-typed column that someone, eventually, forgets to fill in.

The third is customer history. A cyclist who brings their bike in three times a year generates valuable data — frequency, job type, average spend — that a proper system turns into a follow-up reminder, while a spreadsheet just lets it scatter across rows. In 2026 the industry talks openly about how much customer lifetime value and churn weigh on a shop's revenue, and that's hard to act on when the underlying data was never structured in the first place.

The signal that it's time to switch

There's no magic revenue or customer-count threshold. The most reliable signal is behavioral: when the owner or mechanic starts double-checking what the spreadsheet says — calling the supplier to make sure a part is really there, trying to recall a bike's last service from memory because the sheet can't be trusted anymore — the spreadsheet's hidden cost has overtaken its benefit. Other concrete tells: two people editing the same file at different times and one update quietly disappearing; work orders that stay open because nobody remembers to close them; a customer asking "when did I last replace this chain?" and the answer taking ten minutes instead of ten seconds.

What changes with software built for the workshop

Purpose-built workshop software — not a generic CRM bent into shape — automatically links customer, bike and service history, updates inventory with every job without anyone re-typing anything, and tracks e-bike warranties and components as structured data rather than a margin note. It isn't a complicated technological leap. It's the difference between chasing the spreadsheet and letting the system remember things for you.

If you're still wondering whether your Excel file is holding up, the fact that you're asking is usually the answer. CrankPal is built for workshops that want to stop chasing spreadsheets and put service back at the center of how they run the shop — if you want to see it in action, the workshop platform is one step away.