For growing shops of 10 to 50 people

A shop with twenty people has solved the problems of a small one. There is a service manager, a head mechanic, a counter team, and maybe a mobile van or a second location. The problems now are the ones that come from being busy: keeping standards consistent across people you did not train yourself, knowing which part of the business actually makes money, and hiring before the spring rush instead of during it.

At this size, the owner is rarely at the bench. Decisions are made from numbers, and the numbers are scattered: the bench throughput in one place, labor in another, the books in a third. Nobody has a clear view of whether the van pays for itself or whether the second location is carrying its weight.

Hiring and training become a job of their own. A new mechanic in April has to learn your tune-up, your torque specs, your e-bike diagnostic process and your paperwork, fast, while the queue grows.

Growth is $99 a month with 10 users and five modules included; each user beyond ten is $20. Scale is $399 a month with 50 users, ten modules and white-label included; each user beyond fifty is $20. For a growing shop, the choice depends on headcount and on how many modules you run.

On headcount alone, the two cost the same at 25 users: Growth is $99 + 15 x $20 = $399, and Scale is $399. Below 25, Growth is cheaper. At 15 users, Growth is $99 + 5 x $20 = $199. Above 25, Scale is cheaper: at 30 users Growth is $99 + 20 x $20 = $499 against Scale's $399, and at 50 users Growth is $99 + 40 x $20 = $899 against $399.

Modules can decide it before headcount does. If you run more than five modules, for example Service, Phony, Accounting, CFO, ATS and Courses, you need Scale at any size, because Growth covers five. White-label is on Scale only. Phony adds $0.12 per minute of call time on every plan, and Enterprise is priced by quote for groups that need it.

Today, a growing shop gets the operational core of Service. Requests come in from web forms or the counter and are triaged to quotes. Approved quotes become numbered jobs with visits on a week schedule, gated on shared, versioned checklists. Mechanics clock time against the job, managers approve the week with overtime worked out, and finished jobs are billed in one click. The monthly reports show work closed and still booked, money invoiced, collected and overdue, and hours by person. The field app installs from the browser and keeps working with no signal, which helps the van crews.

Around it, the live erp.io modules cover hiring in ATS, training in Courses, the books in Accounting, the phone in Phony and team threads in Chat.

What a shop this size will miss is on the Service roadmap: job costing and margin, throughput and comeback reports, a bench board and capacity limits, van routing, parts by location, online payments, a payroll export and posting invoices into Accounting. Access follows erp.io roles, crew or admin, until per-person grants get a screen. If you need those this season, keep your current tools for them alongside BIKE.co.