A spreadsheet with a cycle time problem.
Most shop CRMs are generic sales tools pointed at an unrelated workflow. The Collision Bureau CRM is built around the stages a shop actually works: intake, estimate, supplement, parts, delivery, review. One board, one truth.
The Westside Collision Center dashboard, mid-morning.
42 active repair orders, 18 in supplement, 6 non-drivable, $184K WIP. The alert on the Ram 1500 is day 4 on supplement 2 with GEICO; the dashboard chases it.
Illustrative mockup · fictional shop
Everything in the package.
- Collision-specific kanban: Intake, Estimated, Supplement, Parts, In production, Delivered
- Vehicle, insurer, DRP, severity, drivable status, OEM/EV flag on every card
- Supplement timer: alerts at day 3 if supplement is sitting with the adjuster
- Parts tracker: PO numbers, ETA, backorder alerts, OEM/LKQ flag per line
- Delivery → review handoff: triggers the follow-up sequence
- Role views: estimator, parts, production manager, GM; each sees what they need
- Integration with CCC ONE, Mitchell, Audatex via CSV sync or API (add-on)
- Mobile-first for techs on the shop floor; desktop for the back office
The operational case.
Supplement cycle time is where margin lives or dies
Every day a supplement sits with an adjuster is a day the car sits in the bay. Shops that cycle supplements in 2-3 days keep bay turns at 7-10 days. Shops that let supplements sit a week push bay turns past 14 days, and margin collapses. The CRM alerts the supplement coordinator at day 3.
Spreadsheets lose non-drivable cars
A non-drivable repair that sits unassigned in a shared Google Sheet for 48 hours loses to a competitor who routed theirs to a dispatcher inside an hour. The CRM intake fork routes the moment the submission arrives.
The delivery-to-review handoff is the easiest 3-pack lift
Shops that trigger the review request 48 hours after pickup lift review count 3-5x in six months. The CRM fires that trigger automatically; the manual version almost always slips. The compounding effect on Local SEO ranking is why review generation is in every tier.
Related: how estimate leads land in the CRM, and the follow-up sequences the CRM triggers.
What shops ask before buying.
Does it replace CCC ONE or Mitchell?
No. CCC ONE and Mitchell are the estimating platforms your insurer DRPs require. The CRM sits alongside them and syncs via CSV or API. It is the shop's operational layer; the estimating platform is the insurer's.
How does supplement tracking work?
When an estimate is written, the file moves to Supplement if supplements are expected. The timer starts. At day 3 without a response, the supplement coordinator gets an alert. At day 5 the GM gets copied. Credit standard: if the file sits because of us, we fix it.
Can I use it on the shop floor?
Yes. Mobile view is designed for techs: tap a card to see current status, add a photo, flag a hidden damage finding. Does not require a laptop in the bay.
Who owns the data?
You do. Full export available at any time (CSV, JSON). If you cancel, we hand you the data and delete our copy within 30 days.
How is this different from a generic CRM like HubSpot?
HubSpot is a sales CRM optimized for a pipeline that ends in a signed contract. Shops do not have that pipeline. They have intake → estimate → supplement → parts → delivery → review. The CRM is built around those stages, not reskinned around them.
Is there a mobile app?
Progressive web app. Install on iOS and Android via "add to home screen"; works offline, syncs when back online. Dedicated native app on the roadmap, not shipped yet.
What usually ships alongside this.
The spreadsheet does not scale. This does.
$1,495 one-time setup + $195/month per shop, unlimited users. Bundled into every subscription tier.