What a Custom CRM Build Actually Costs a Bike Shop

Most owners sign a CRM statement of work the way they sign for a shop lease: they focus on the headline rent and skim the operating expenses. The monthly per-seat price gets all the attention. The one-time build line gets a glance. The maintenance clause gets a nod.

Then the first invoice arrives for scoping, and the second for data migration, and the third for a round of custom fields nobody discussed, and the budget starts to resemble something closer to a frame-up than a tune-up. CRM projects at firms under 100 employees average about $3,000 to implement, but that figure assumes a near-stock deployment. A bike shop that wants e-bike serials, battery warranty tracking, and a clean import out of Lightspeed is already past it.

So what does a customized build actually bill for before you countersign?

Scoping Is Not Free Discovery

The first invoice almost nobody budgets for is scoping. A vendor cannot quote a fixed price on a build they have not sized, and sizing takes hours of calls, a workshop walkthrough, a review of your current intake flow, and a written statement of work that spells out custom objects, user roles, integrations, and acceptance criteria.

Expect 10 to 25 hours at a US consulting rate. US developer rates typically run $100 to $250 per hour, with senior engineers in the $130 to $210 band. On the low end, a two-location shop scoping a stock deployment with light customization lands around $1,500. On the high end, a multi-brand e-bike specialist with a mobile van, a rental fleet, and three POS exports to reconcile will see $5,000 to $8,000 before anyone touches a database.

Two things keep scoping honest. First, insist on a written statement of work with a line-itemed list of custom fields and integrations, not a page of adjectives. Second, treat the scoping fee as insurance against a change-order avalanche later. Shops that skip discovery to save a few thousand dollars usually pay it back three times over in revisions.

Data Migration Is the Line That Hides the Real Bill

Migration out of Lightspeed Retail or Ascend is the single most variable item on any bike shop CRM quote. The vendor can hand you a CSV spec. What they cannot do is clean your data for you.

Count what you are moving before you ask for a number:

• Customer records, deduplicated by phone and email
• Bike records with serial, model year, and purchase source
• Service history linked to the right bike, not just the right customer
• Open work orders at cutover
• Parts catalog, with supplier SKUs and current cost
• Gift cards, store credit, and deposit balances

Rates for the actual migration work generally run $90 to $250 per hour for a specialist, with most small-shop jobs falling in a $2,500 to $6,000 band once custom fields and automations are in scope. The chart below shows how spend inside that band typically splits across the stages of a migration. The audit and dedupe step is the one shops underestimate most, and it is also the one that determines whether reporting works on day 31.

If you are moving off Lightspeed specifically, the mechanics of the export are well-trodden ground; the write-up on switching from Lightspeed walks through what the export file actually contains and where it falls short.

Custom Fields Are Where Bike Shops Diverge From Generic CRMs

A generic CRM assumes a customer and a product. A bike shop deals in a customer, a bike (sometimes several), a battery, a motor, and a stack of warranty clocks that all started ticking on different days. Every custom field is a small build item: schema change, form placement, report inclusion, sometimes an automation.

Budget for these as a group, not as a surprise:

• E-bike serial, motor serial, battery serial, and display firmware version
• Battery warranty start date and remaining cycle estimate
• Brand warranty contact and RMA process per supplier
• Suspension service intervals by fork and shock model
• Rental agreement and deposit status
• Fit record: saddle height, stem length, cleat position

A reasonable rule of thumb is one to three hours of configuration per custom object, plus more if the field has to appear on the intake form, the work order, the customer-facing status page, and a report. Ten custom fields do not cost ten times one; they cost closer to four or five, because the schema work compounds. Fifty custom fields across six objects is a different conversation, and it is where quotes start to double.

Training Is Billable, and It Should Be

Training is the line owners cut first and regret longest. Gartner has long reported that 50% to 70% of CRM projects fail to meet expectations, and the most common cause is not the software. It is a staff that was shown the new system once on a Tuesday afternoon and left to figure it out on Saturday morning.

Budget training in three tranches:

• Admin training. Four to eight hours for the owner or service manager who will configure users, menus, and reports. This is the person who will field every "how do I" question for the first month.
• Role training. Two to four hours per role: service writer, mechanic, sales. Each role sees a different slice of the system and needs its own walk-through.
• Hypercare. A standing weekly call for the first four to six weeks after go-live, usually billed as a block of hours.

At typical consulting rates, a two-location shop should expect $2,000 to $5,000 in training through the first ninety days. The alternative is a system that technically works and that nobody uses, which is the most expensive outcome on this page.

Integrations Are the Quiet Multiplier

Every integration is a build and a long-term liability. Accounting sync, payment processor, SMS gateway, label printer, supplier EDI feeds, your email platform. Each one has an API that will change, credentials that will rotate, and a schema that will drift.

The upfront build for a clean integration runs $2,000 to $8,000 depending on complexity. The ongoing cost is the part most quotes bury: integration maintenance typically runs 15% to 25% of the original build cost per year to handle those changes. Three integrations at $5,000 each is $15,000 up front and roughly $2,250 to $3,750 per year, every year, forever.

This is a real reason to prefer a platform that already includes the pieces you need over one that bolts them on. The comparison of POS, field service, and ERP options for bike shops is a reasonable starting point if you have not mapped the integration surface area of each candidate yet.

Year Two Is Not Free Either

The yearly maintenance line is the one that quietly compounds. Software maintenance for custom builds typically runs 15% to 20% of the original development cost per year, covering bug fixes, library updates, security patches, and small enhancements. On a $25,000 custom build, that is $3,750 to $5,000 annually before anyone adds a feature.

Then there is the per-seat subscription, which does not go down. A five-seat shop at $75 per seat is $4,500 per year on top of maintenance, and most shops add a seat or two in year two as they realize who else needs access.

The diverging chart below shows the shape of a typical year-two budget relative to year one for a mid-complexity bike shop deployment. The build line goes away. Everything else gets heavier.

A Realistic Budget Worksheet Before You Sign

Pull these numbers together and the picture clarifies. A single-location repair-first shop with modest customization and one POS migration should budget $8,000 to $15,000 in year one, plus subscription. A two-location shop with e-bike custom fields, a rental module, and three integrations is realistically $18,000 to $35,000 in year one. A regional operator with a mobile van and multi-location inventory can clear $50,000 before anyone argues it is wrong.

Those are build and services numbers. Subscription sits on top, and the line-by-line software cost breakdown walks through what per-seat pricing looks like once the implementation dust settles.

Three questions to ask before you countersign the statement of work:

1. Is every custom field listed by name, with the object it attaches to and the forms it appears on?
2. Does the data migration line specify records in scope, dedupe rules, and a reconciliation report after cutover?
3. Is the maintenance percentage stated, and does it include integration drift as well as the core app?

Why the Per-Seat Number Matters Less Than You Think

Owners obsess over the per-seat line because it is the one number quoted on every vendor's homepage. It is also the smallest number in the stack for a customized deployment. A shop paying $75 per seat for five seats spends $4,500 per year. The same shop may spend $25,000 in year one on scoping, migration, custom fields, training, and integrations, and $7,000 to $10,000 every year after on maintenance and subscription combined.

The right lens is total cost over three years, not month one. A vendor charging $120 per seat with a $5,000 implementation often costs less over three years than a $45 vendor who bills $30,000 to make it do what a bike shop actually needs. The specifics are what matter, and the specifics belong in writing before the first invoice. If you want a second set of eyes on a statement of work, the shop owner resources page collects the templates and checklists worth reading first.

The NBDA's Cost of Doing Business study has long noted that high-profit shops pull 11.4% of revenue from repair parts and labor, nearly double the 6.5% average. The software that runs the service department is not where to cut, but it is also not where to overspend. A clear budget worksheet is how you tell the difference.