Shop software for the way your shop actually runs

Every bike shop that takes in repairs runs into the same three walls. The first is the queue: bikes arrive faster than they can be looked at, tickets get written on paper tags, and by Saturday afternoon nobody is sure which Trek belongs to which phone number. The second is the waiting: a job stalls on a derailleur hanger or a Bosch speed sensor, and the bike takes up floor space for days while the customer calls to ask where it is. The third is the money: labor gets undercharged, parts go on a job and never make it onto the invoice, and the books are a month behind.

How those walls show up depends on the kind of shop you run. A service-first shop feels the queue most. An e-bike specialist feels the waiting, because diagnostics take time and OEM parts take longer. A mobile mechanic feels the money at the curb, with a customer standing there and no card terminal. A rental or fleet operator feels the sheer repetition of forty identical bikes that all need the same inspection every month. A group with several locations feels all of it, multiplied, with parts that live in the wrong shop.

The pages below take each kind of shop in turn. Each one describes the day as it actually goes, names the specific pain, and then says plainly which part of BIKE.co handles it and whether that part exists today, is on the Service roadmap, or is done by another erp.io module that is already running.

BIKE.co is the erp.io Service module set up for bike shops, and the core of it is live. A request comes in from a web form or is typed in at the counter and lands in the Requests inbox. You write a numbered quote with line items, optional lines the customer can choose, a discount and tax, mark it approved, and convert it into a job with one or more visits. Each visit has a date and a person, and a required checklist stops it being closed until the checklist is submitted. The week schedule shows visits by day, with an unscheduled queue and a Today page. Mechanics clock their time against the visit, a manager approves the week, and when every visit is closed, one click bills the job as a numbered invoice. Monthly reports cover work closed, money invoiced and collected, and hours by person.

The checklists underneath all of that are live too: a builder with eight question types, photos and signatures, required answers, versioned templates, a PDF record and a CSV report. The field app installs from the browser and keeps working with no signal, which is new. Access follows the erp.io workspace role, so crew can close visits and fill checklists but cannot schedule, and recording payments stays with an admin.

Some of it is not built, and we say so on every page. Sending a quote or an invoice only changes its status for now; nothing is emailed or texted to the customer. Payments are recorded by hand, with no pay links, QR codes or card taking. There is no bench board by status, and jobs are recorded against a site, an address and a customer name, rather than a bike, because bike records with serials are on the roadmap. Parts inventory, purchase orders, job costing, routing, ready texts, the customer portal, online slot booking and accounting sync are planned. A shop owner who signs up expecting any of those would be misled, and we would rather lose the sale.

Around Service sits the rest of erp.io, and much of that is live. Phony answers your phone. CRM holds your customers and fleet accounts. Accounting keeps the books. Sign handles rental agreements and waivers. Chat keeps the counter and the bench talking. Courses trains new mechanics, and ATS helps you hire them. Those modules work today, on the same login, and the solution pages point to them where they help.

Pricing on erp.io turns on two numbers: how many people sign in, and how many modules they use. Nothing inside a module is held back by plan, so a solo mechanic gets the same checklist builder as a fifty-person group. Every workspace starts with a 30-day free trial with no card, and every module is switched on during the trial.

Starter is $20 per user per month and covers two modules, which suits one or two people running Service and one other module. Growth is $99 a month with 10 users and five modules included. Scale is $399 a month with 50 users, ten modules and white-label. Extra users on any plan are $20 each, and Enterprise is priced by quote. The three size pages work through the arithmetic for a solo mechanic, a small shop and a growing one, so you can see where the lines cross.