Per-User vs Flat-Rate Automotive CRM Pricing

The pricing model changes how your team uses the software, which is a bigger deal than the number on the invoice.

Automotive CRM is sold two ways, and vendors rarely explain the consequences of either.

Per user, or per seat. You pay a monthly amount for each named login. Ten salespeople, four BDC agents, three managers and a receptionist is eighteen seats. Add a person, add a seat. Remove a person, and whether you stop paying depends on your contract and your notice terms, which is a detail worth pinning down before you sign.

Flat rate. You pay a monthly amount for the store, and users are not the meter. Hire six people for a spring push and the invoice does not move. This is how our plans work.

There are hybrids: a flat platform fee plus per seat above a threshold, or tiered bands where the price steps at twenty five and fifty users. Those are usually per seat pricing with extra steps, and they should be modeled as such.

The number on the first invoice is not the interesting part. What matters is how each model behaves eighteen months in, under staff turnover, and how it changes what your people actually do inside the software.

This is the argument almost nobody makes at the demo, and it is the one that costs stores the most.

When logins cost money individually, stores ration them. The decision is completely rational at the department level and quietly damaging at the store level. The part time BDC agent shares a login with somebody else. The lot porter who takes the first call on Saturday morning does not get one. The service advisor who spots a trade opportunity has nowhere to put it. The two green peas on a thirty day trial period wait until they are proven before they get an account.

Every one of those decisions puts activity outside the system. Shared logins destroy attribution, so you cannot tell who responded or who let a lead sit. Uncounted people take calls that never become records. A trade opportunity noticed in service evaporates because capturing it was somebody else's login. Six months later a manager pulls a report, sees numbers that do not match the showroom traffic, and concludes the CRM is inaccurate. The CRM is accurate. It only ever saw the part of the store that was allowed in.

The second behavior is worse: people work around the software. When a salesperson without full access texts customers from a personal phone, the store loses the conversation permanently. That cost never appears on a comparison spreadsheet.

It would be dishonest to pretend one model always wins, so here is when per seat is the right call.

A very small operation with a stable team. Two or three people, low turnover, no BDC and no plan to add one. Per seat pricing on a small headcount is often cheaper in absolute dollars than a flat platform fee, and there is no reason to pay for capacity you will not use.

An individual salesperson buying their own tools. If you are one person, you should pay for one person. That is why we also sell to individual salespeople rather than only to stores.

A store piloting a system in one department before a wider decision. Buying five seats to test something is a smaller commitment than a store wide fee, though month to month flat pricing achieves the same thing.

What all three have in common is a small, stable user count. The moment headcount is variable, per seat pricing starts charging you for the thing your business does naturally, which is churn.

Comparing the headline rates is where most evaluations stop and where most surprises come from. Get all of these in writing before you compare anything.

• Module fees. Is texting included, or an add on? Desking? Campaigns? Reporting? A low seat price with four required modules is not a low price.
• Telephony and messaging. Per minute, per message, per number. Ask for the rate card and model your real volume, not a sample.
• Implementation and data migration. One time, sometimes four figures, sometimes waived if you ask before signing rather than after.
• Integration fees. Charged by the CRM, and sometimes charged again by the other vendor for the same connection.
• Contract length and renewal uplift. A price that steps up in year two is a different product than the one you were quoted.
• Minimum seat counts. Per seat pricing with a floor of twenty five seats is a flat fee wearing a costume.
• Removal terms. Whether a seat you stop using stops billing this month or at renewal.

Our page on total cost of ownership works through the full list, and the CRM pricing guide covers how vendors package it.

The numbers below are illustrative only. They are not quotes, they are not any vendor's real pricing, and they exist to show the shape of the curve. Use your own quoted figures.

The crossover point in this illustration is around nine or ten users, and it arrives faster than most dealers expect once you count everyone who should be in the system. The bottom row is the one to sit with. Under per seat pricing, giving access to the whole store is a decision with a price tag, so it usually does not happen. Under flat pricing it is free, so it does, and your data gets better as a direct result.

Automotive sales has high turnover. That is not a criticism of anyone's store, it is the shape of the industry, and it interacts badly with per seat pricing in three ways.

First, administrative drag. Every hire and every departure becomes a billing event that somebody has to process, and stores routinely keep paying for seats belonging to people who left months ago because nobody owns the cleanup.

Second, the trial period problem. New hires who might not last sixty days still need to work leads on day one. Per seat pricing creates a real incentive to delay giving them access, which is exactly the period when their habits form.

Third, seasonality. Stores staff up for tax season and for spring, then contract. A cost that scales with headcount on the way up but is slow to scale on the way down is a ratchet.

Flat pricing removes all three. Onboarding a new hire is a user record, not a purchase order. Role based permissions decide what each person can see and do, so giving a new salesperson a login is not the same as giving them the keys to everything. The bill is the bill.

Our plans are flat and month to month, with no long term contract. Users are not the meter.

CRM Only is from $199 a month if you already have your own lead sources and just want the platform: lead management, SMS, MMS and RCS with SMS fallback, a VoIP dialer with call recording and transcription, voicemail drop, email with a real inbox and campaigns, automations and follow up processes, appointments, desking with a fifty state tax matrix, lead pages and three layers of reporting. Lead Data Only is from $599. Plans that include exclusive local leads start at $799 for Inbound buyer leads, $999 for Marketplace Acquisitions on the seller side, and $1,599 for the Buyers and Sellers Hybrid Plan. There is a Skip A Month option at $199 for stores that want to pause without losing their data and setup.

Two things follow from flat pricing that are worth naming. Put everyone in the system, including service advisors, the receptionist and the brand new hire, because it costs nothing extra and your reporting stops lying. And run your seasonal staffing however the market says, without a procurement conversation. Current figures are always on the pricing page.

Take these into every vendor conversation, ours included, and write down the answers.

What is the total monthly cost for every person who should be in the system, with every module we need, including messaging and telephony? What is the price at renewal, and is there a scheduled uplift? What is the contract length and the cancellation notice period? If we remove a user, when does billing stop? Is there a minimum seat count? What is the implementation fee and what does data migration cost? Which integrations carry a fee, from you or from the other vendor? What exactly can we export if we leave, in what format, and does it include communication history?

The last question is the one that reveals the most about a vendor's posture, and the answers separate them faster than any feature grid. If you want ours answered live rather than in a PDF, the demo is the place to start, and our vendor question list is written to be used with any vendor, not only with us.

Which pricing model is cheaper for a car dealership?

Per seat is usually cheaper below roughly nine or ten users, and flat rate wins above that, though the exact crossover depends on quoted rates. The bigger factor is that flat pricing lets you put everyone in the system, which makes your reporting real.

Does LeadLocate charge per user?

No. Plans are flat and month to month, and users are not the meter. CRM Only starts at $199 per month, and plans including exclusive local leads start at $799. Current figures are on the pricing page.

Should part-time BDC agents and service advisors have logins?

Yes, if the pricing model does not punish you for it. Activity that happens outside the system is invisible to your reporting, and shared logins destroy attribution entirely.

What hidden costs should we ask about?

Module fees, telephony and messaging rates, implementation and migration charges, integration fees from either vendor, minimum seat counts, renewal uplift, and exactly when billing stops after you remove a seat.

Is a flat rate risky if our store shrinks?

Only if you are locked into a term. Month to month pricing means a smaller store can move down or leave, and our Skip A Month option at $199 exists so a store can pause without losing its data and configuration.

How do we control what new users can see under flat pricing?

Role based permissions. Giving a new salesperson a login is not the same as giving them access to everything, so you can onboard on day one without exposing gross, company settings or other people's customers.

Tell us your headcount and what you need running, and we will give you one monthly figure with nothing hidden behind it. Month to month, no long term contract.