CRM by industry

Generic CRMs model one deal moving through one pipeline. Most real businesses do not work that way. These pages cover where the standard model breaks per industry, the objects that actually fit, and whether to configure, buy or build.

Mortgage and commercial finance brokers: A generic CRM models one opportunity moving through one pipeline toward one close. A brokered deal is one file submitted to several lenders at once, each returning a different decision, different conditions, and a different offer — and then continuing to matter for two years after funding. That mismatch is why brokerages end up with a CRM that is accurate until approval and useless afterward.

Insurance brokers: An insurance brokerage does not run a sales pipeline. It runs a book that renews, and the calendar is the product. Sales CRMs are built to close a deal once; the whole value of a brokerage is that the deal comes back every twelve months and somebody has to be ready ninety days ahead.

Auto dealers: Dealer CRMs are built around the up: capture the lead, work the floor, log the test drive. On an independent or subprime lot the hard part starts after the customer says yes, when the deal has to survive a lender, three stipulations and a week of silence. That stretch is where the deals die and where most dealer software has nothing to say.

Equipment dealers: A machine sale runs for months, hinges on a monthly payment rather than a price, and involves a trade whose real value is not known until it is reconditioned. Standard CRMs assume a short cycle and a single number, so dealers end up quoting in spreadsheets and financing in email.

Staffing and recruiting agencies: Staffing has two sides and most software only sees one. An ATS tracks candidates, a CRM tracks clients, and the money is made in the middle: the placement, the hours it generates, the credential that has to be valid on the day, and the margin nobody calculates until month end.

Property management companies: Property management software is usually strong on accounting and weak on everything a manager actually does between the first of the month and the next. Maintenance arrives by text, vendors are coordinated by phone, and owner reporting is rebuilt by hand — none of which the ledger knows about.

Builders and construction companies: Construction has two decent software categories and a gap between them. Sales CRMs handle the lead and stop at contract. Project tools pick up at the schedule. The expensive part — selections drifting over allowance, verbal change orders never billed, draws slipping — falls between the two.

Field service companies: If you run ServiceTitan, Jobber or a similar platform, you probably do not need a CRM. You need the two things the platform does not do: answer the calls you are missing, and keep working the quotes nobody sold. Those two numbers decide the year and both are usually unmeasured.

Trucking and fleet operators: Carriers usually have a TMS for loads and an ELD for hours, and still have one person doing everything else by hand. Driver documents expire without warning, settlements get disputed every week, and proof of delivery arrives as a photo in a group chat.

Accounting and bookkeeping firms: An accounting firm does not have a sales problem, it has a collection problem. The same clients are chased for the same documents every cycle by qualified accountants, and the firms that fix it are not the ones with better CRMs — they are the ones that made the chase a system instead of a person.

Law firms: Two things consume a small firm's non-billable time: deciding which enquiries are worth taking, and telling clients what is happening. Practice management software handles neither well, because both sit outside the matter and before the bill.

Manufacturers and machine shops: In custom manufacturing the job usually goes to the first credible quote, not the lowest. Shops lose work they never knew they were competing for, because the RFQ sat behind whoever was estimating and the cost model lives in that person's head.

Powersports, RV and marine dealers: Dealership CRMs are built for car stores: a daily-driver purchase, a BDC working fresh leads on a five-day cadence, a customer who buys because their old vehicle died. A powersports, RV or marine dealership sells a discretionary unit into a season, takes deposits on units that have not arrived yet, and lives off a garage of owned machines that come back every year for service, storage and eventually trade. A CRM with no unit record, no deposit object and no memory of what the customer already owns is wrong for this business in a way no amount of configuration fixes.

Solar and energy retrofit companies: The solar CRM market is crowded, and almost all of it is sales software: lead capture, a proposal with a savings estimate, an e-signature, a commission report. The problem is that in solar the signature is the beginning of the hard part — site survey, design revision, permit, financing funding milestones, installation, inspection, permission to operate. Most installers run the sale in a vertical CRM and the project in spreadsheets, and the customer experiences the gap as three months of silence after the most enthusiastic sales process of their life.

Financed home improvement contractors: A financed home improvement company does not run a contact pipeline. It runs an appointment machine: a setter books the in-home visit, a confirmer keeps it alive, a closer sits at the kitchen table, and the economics of the whole company reduce to how many booked appointments actually issue and how many issued appointments close. Generic CRMs are built around contacts and deals, so the appointment — the unit everything is actually measured in — is a calendar entry with no states, and the numbers that run the business live in a whiteboard photo someone takes on Fridays.

Medical and aesthetic equipment sellers: A generic CRM sees a medical equipment sale as an opportunity with an amount and a close date. The seller is actually managing three other things the CRM has no object for: a buying group where the clinician wants the machine, the office manager guards the budget and a DSO or hospital group holds the signature; a configured quote where the price moves with every option and trade-in; and an install base — every unit already in the field with a serial number, a warranty date and a service contract — which is where the next five years of revenue actually live. Model those three and the pipeline takes care of itself; model only the pipeline and the rep keeps the real business in a notebook.

Equipment rental companies: Rental software is counter software: reservations, dispatch, invoicing. What it does not manage is the commercial account — the contractor with credit terms, a negotiated rate sheet, a certificate of insurance that expires in March, and a rental pattern that quietly stopped six weeks ago. A generic CRM does not help either, because its core object is a deal that closes once, and a rental account is never closed; it is a relationship measured in on-rent days that either continues or silently moves to the competitor across town.

Wholesale distributors: A CRM built on deals assumes revenue arrives as opportunities that close. A distributor's revenue arrives as this week's orders from last year's accounts, and the sales question is never which deals will close — it is which of four hundred accounts a rep should touch this week, which lines each account buys elsewhere, and which price agreement expires next month. Put a distribution sales team in a pipeline CRM and they dutifully invent fake deals to have something to log, while the actual book — the accounts and their buying patterns — remains exactly as invisible as before.

Print and signage shops: A print or signage shop does not have a sales pipeline so much as an estimating queue: jobs arrive as specs, most quotes are won or lost inside a week, and the real money is in customers who come back — the restaurant that reorders menus, the franchise that opens another location and needs the same sign. A generic CRM models none of that, and a sign company carries an extra layer the CRM has never heard of: site surveys, municipal sign permits, landlord approvals and an installed product hanging on a building that will need service in three years.

Food producers and CPG: For a food brand selling into retail, the generic CRM fails on its central assumption: that winning means closing. Getting listed with a grocery banner is not a close — it is an admission ticket to a game measured in velocity, where the SKU must sell fast enough at each banner to survive the next category review, the distributor sits between you and your own customer, and trade spend quietly consumes a fifth of gross revenue with nobody able to say what any given deduction bought. A deal pipeline records the listing and goes blind exactly when the work starts.

Dental and orthodontic practices: A dental practice already has a system of record: the practice management software that holds the chart, the schedule and the claims. What it usually does not have is a front-of-house system — the thing that works new-patient inquiries, follows up presented treatment plans, and runs recall as a pipeline instead of a postcard. A generic sales CRM is the wrong answer to that gap, because it models a deal that closes once, and a patient is a relationship that renews every six months for twenty years.

Veterinary clinics: In a veterinary clinic the patient is the animal but the client is the human, and every generic CRM collapses that into one contact. The practice management system owns the medical record and it should keep it. What clinics are actually shopping for when they type veterinary CRM is the client side: new-client inquiries answered before the caller books elsewhere, reminders that go out without front desk labour, estimate approvals that do not stall on a voicemail, and lapsed clients noticed before the pet is overdue by a year.

Med spas and aesthetics clinics: A med spa usually owns two systems that both claim to be the CRM: booking software that is really a calendar, and maybe a sales CRM bought to chase consult leads. Neither can answer the questions the business runs on — how many sessions are left on this package, when is this client due back on her toxin cycle, which memberships billed wrong this month, and which consults from last quarter never converted. The clinical chart stays in the medical record system; the gap is everything commercial around it.

Clinics and rehab practices: A physio or chiro clinic shopping for a CRM is usually trying to solve three problems the EMR ignores: patients who drop off a twelve-visit plan of care at visit five, referral sources nobody thanks or measures, and discharged patients who are never heard from again. A generic sales CRM solves none of them, because its whole worldview is a deal that closes once. The clinical record — notes, outcomes, billing — stays in the EMR. The CRM question is what surrounds it.

Real estate teams: Almost every real estate CRM was designed for a single agent and then had seats bolted on. A team is a different machine: the team buys the leads, routes them to agents, and needs to know within minutes whether the agent actually called. When the CRM cannot answer who got the lead, how fast they responded and what happened next, the team is paying for lead flow it cannot audit — and when an agent leaves, the database walks out with them.

Self storage and flex space operators: Self storage management software is built around the unit: occupancy, billing, gate access. It is usually terrible at the part before the rental — the phone call about a ten-by-ten that ends with we're full, the web inquiry answered tomorrow, the caller who was never told a unit frees up Friday. That gap is the CRM problem in storage: inquiries, waitlists and win-backs are revenue objects, and in most facilities they live in a message pad by the phone.

Franchisors and franchise developers: A franchisor needs a CRM to do two jobs that share almost nothing: sell franchises to candidates, and manage the franchisees already open. Franchise sales is a long-cycle pipeline with a legal disclosure step whose timing has to be recorded and respected. Franchisee management is a portfolio of ongoing relationships with royalties, field visits and renewals. Generic CRMs are built for the first shape only, and even there they have no idea what a disclosure document is.

Roofing and exteriors companies: A generic CRM assumes a deal closes when the customer signs. On an insurance roof, the signature is the beginning: the job then has to survive an adjuster meeting, a scope argument, a supplement, and two separate cheques months apart. A roofing company running claims through a stage field ends up with a pipeline that says won while half the revenue is still inside the carrier's process, which is why the office keeps the real status in a spreadsheet next to the CRM.

Restoration and remediation contractors: A restoration company does not really sell to the homeowner standing in the flooded basement — that job was decided by whoever referred it: the plumber, the adjuster, the insurance agent, or the TPA program that assigned it. A generic CRM points all its machinery at the homeowner, who will hopefully never need you again, and has no model at all for the referrers who send losses every month. That is backwards, and it is why the marketing spend goes to ads while the referral relationships that produce most of the revenue are managed from memory.

Landscaping, snow and grounds companies: A landscaping company's revenue is not a stream of deals; it is a book of properties under annual contracts that renew, flip between growing season and snow, and sit on routes whose density decides the margin. A generic CRM models none of that: it treats a renewal as a new deal, a property as a note on a contact, and every lead as equally valuable — when a lawn two streets off an existing route is worth materially more than the same lawn across town. The result is a tool that can log calls but cannot answer the two questions that decide the year: what renews, and what fits the routes.

Pest control companies: Pest control is a subscription business, and a generic CRM measures it like a sales floor. The pipeline celebrates the new quarterly plan worth a few hundred dollars a year while a cancellation of equal value passes through unexamined — because a sales CRM has a stage for won and nothing at all for kept. In a business where the recurring book is the company's entire value, the objects that matter are the plan, the failed payment, the cancellation request and the save, and none of them exist off the shelf in a tool built to close strangers.

Pool and spa companies: A pool company is two businesses sharing a truck fleet: a construction business selling six-figure builds over months, and a subscription business servicing hundreds of properties weekly. A generic CRM forces both into one pipeline, so the build side loses its deposit schedule and design stages, the service side loses its route book, and the most valuable moment in the company — converting a finished build into a service customer for the life of the pool — belongs to neither side and usually just does not happen.

Excavation, septic and site services companies: An excavation contractor's pipeline is not a list of deals; it is a bid table and a backlog. Work arrives as invitations from builders and general contractors you already know, gets priced against equipment and crew you may or may not have available, and — if won — sits in a backlog for weeks before a machine ever mobilises. A generic CRM models a stranger being persuaded, which is almost never what is happening. The consequence is that the two numbers that actually run the company, win rate by client and weeks of backlog, cannot be produced by the tool that is supposedly tracking the sales.

Specialty subcontractors: A subcontractor's customer is not the building owner; it is the general contractor, and the relationship runs on a rhythm no sales CRM understands: get prequalified, get invited to bid, win some share of the invitations, then survive the project financially. The pipeline vocabulary of leads and closing describes almost none of it. What actually needs managing is a short roster of GC accounts, the prequalification documents that expire and quietly stop the invitations, and the awarded projects whose billing behaviour determines whether the GC deserves the next bid at all.

Cabinet and millwork shops: A cabinet shop's problem with CRM is that the sale is the shortest part of the job. A kitchen or a commercial millwork package lives for months after the contract — deposit, drawings, revisions, production, delivery, install, deficiencies, final payment — and a sales CRM closes the record at exactly the moment the real correspondence begins. Meanwhile the shop's actual sales engine, the designers, architects and contractors who specify it into their projects, has no model at all in a tool built to chase individual buyers.

Alternative business lenders: A sales CRM treats funding as the finish line. For a funder it is the starting gun: the moment money goes out, the file becomes a performing advance with a remittance schedule, a balance to track, and a renewal window that opens months later. Desks that run on a generic CRM know exactly who they funded and almost nothing about how those advances are performing, which is why the renewal call goes to whoever phones the merchant first.

Equipment leasing and finance companies: A lease is not a deal that closes. It is an asset, a schedule and a date two to five years out when something has to happen — buyout, return, renewal or upgrade — and the party who calls first usually decides which. A generic CRM has no object for the asset, no concept of a schedule under a master agreement, and no way to surface the end-of-term date as work, so lessors run their most predictable revenue event from memory.

Private lenders and MICs: A private lending fund runs two pipelines at once: mortgages to place and capital to place them with. A generic CRM can hold one of them badly and the other not at all. The questions the desk actually needs answered every morning — what matures in the next ninety days, how much committed capital is undeployed, which broker sent the last five deals that closed — are all joins across loans, investors and referral sources, three objects a sales CRM does not have.

Factoring and PO finance companies: Factoring breaks a sales CRM in a way most industries do not: every relationship has two counterparties. The client sells you the invoices; the account debtor is the one who actually pays. The credit risk sits with the debtor, the CRM has no object for the debtor, and the facility itself never closes — it funds again every week for years. A pipeline built to move a deal to won has nothing to say about any of that.

Debt restructuring and insolvency practices: Debt practices usually buy a CRM for the front of the business — consultations, follow-up, conversion — and it works until the moment it matters most: the day the file becomes a regulated engagement. A filed proposal is not a won deal. It is years of scheduled payments, counselling obligations and creditor correspondence, and the sales CRM that got the client in the door has no object for any of it, so the handoff from marketing to administration happens by re-typing.

Collection agencies: A sales CRM and a collections operation want opposite things. The CRM is engineered to maximize touches; a collection agency operates under rules that limit when, how often and through which channel a person may be contacted, and it has to be able to prove compliance afterward. On top of that, an agency serves two masters a sales tool cannot see at once: the debtor accounts being worked and the creditor clients who placed them and expect remittance and reporting. A generic CRM models neither side correctly.

Business brokers and M&A advisors: A generic CRM assumes one deal has one counterparty. A business sale has one seller and, at its peak, eighty buyers under NDA, each at a different stage with the same listing. That many-to-many is the whole job, and a sales pipeline cannot represent it: either the listing is the deal and the buyers blur together, or every buyer is a deal and the listing shatters into eighty copies. Brokers resolve the contradiction with spreadsheets, which is why nobody can say on a Tuesday which buyers on which mandates owe a response.

Grant and tax credit consultants: A grant or tax credit practice does not run a sales pipeline, it runs a book of claims against filing deadlines. Each claim is an evidence package that must be complete by a fixed date, and the client who has to produce that evidence is the slowest party in the chain. A sales CRM models none of this: it has no deadline that generates work, no checklist that measures completeness, and no memory that this same client files the same claim again next year.

Immigration consultants: An immigration consultancy is a caseload, not a pipeline. Each file is an application to a specific program with its own document requirements, its own filing window, and a government processing queue on the far side that the consultant does not control. A sales CRM can record that a client signed a retainer; it cannot say whether a file is ready to submit, which documents expire before the window closes, or which of forty open files needs attention today. Those are the three questions the practice runs on.

Notaries, title and escrow offices: A closing office does not sell; it coordinates. Every file has a fixed closing date and four parties — lender, agent, buyer, seller — each of whom must deliver something before that date, and any one of whom can stall the file. A CRM built around contacts and deals has no object for the file, no checklist attributed to parties the office does not employ, and no calendar that ranks twenty simultaneous closings by which one is quietly going off the rails.

Customs brokers and freight forwarders: A forwarder's customer relationship is not a deal, it is a lane: the same importer shipping the same goods month after month, judged on the last shipment that went wrong. A sales CRM can log that an importer was won; it cannot see that their last three shipments cleared late, that a quote for a new lane has been sitting unanswered for a week, or that the account's volume has been sliding for a quarter. The operational systems know the shipments; nothing watches the relationship.

Engineering and architecture firms: A design firm does not close deals, it wins pursuits: proposals against a submission deadline, often with teaming partners, judged partly on which projects and people the firm can cite. The relationships that generate those pursuits run through individuals — a project manager at a developer, a director at a municipality — who change employers and take the relationship with them. A sales CRM models neither the pursuit nor the person-centred relationship, which is why most firms' CRM is a graveyard of stale opportunities beside a proposal folder that holds the truth.

Collision and auto repair shops: A repair shop's customer record is a vehicle with a history, and its pipeline is a row of cars in bays, each waiting on a part, an insurer's approval or a technician. A sales CRM has no object for any of that. What a shop calls CRM is really three jobs: knowing each vehicle's history when it arrives, keeping the owner informed without answering the phone all day, and bringing the customer back when service is actually due. None of those is a pipeline, and forcing them into one is why shop CRM attempts stall.

Moving and courier companies: Moving and courier companies run two different businesses on one fleet, and a generic CRM fits neither. Moving is a quote race: the lead books whoever answers first with a credible estimate, and the deal is won or lost in hours against a calendar of trucks and crews. Courier work is the opposite — accounts won once, served daily, and lost silently when volume drifts to a competitor. One needs speed-to-quote against capacity; the other needs account watching. A sales pipeline gives you a slow version of the first and nothing of the second.