CMS stands for Content Management System. It’s the software people use to update their website without calling a developer every time they want to change a phone number.
If your marketing team can change the hours on your homepage, update a vehicle description, or post a sale without involving IT, you have a CMS that’s doing its job. If they have to file a ticket for every change, the CMS probably isn’t doing its job very well.
What a CMS actually is
A CMS is the layer between “the website is built” and “we need to change something on the website.” It separates content (what’s on the page) from presentation (how it looks) and gives non-technical users a way to manage the content.
When someone says “we have a CMS,” they could mean any of:
- WordPress — the most common CMS, used by dealers running their own sites.
- Dealer-specific platforms — Dealer.com, Dealer Inspire, DealerOn, etc. Each is a closed CMS that powers the site the vendor built.
- Headless CMS — Contentful, Sanity, Strapi, etc. The CMS holds the content, the website is built separately. Common at the enterprise level.
- Custom-built — the dealership’s own CMS, usually built by the original website vendor. Rare and fragile.
For most dealers, the CMS is the website vendor’s platform, or WordPress. The distinction is often invisible to the team that uses it.
Why a CMS matters for dealerships
The CMS is the part of the website the marketing team touches every day. New inventory arrives. Sale prices change. The service department’s hours update for a holiday. A salesperson wins an award and needs a bio added.
If each of these changes is a 24-hour ticket with a developer, the website becomes a bottleneck instead of an asset. The dealership that can’t update its own website fast enough ends up with:
- Stale content. Hours that are wrong. Prices that don’t match. Inventory that says “available” but sold last week.
- Slow marketing response. A competitor has a sale, but the dealer’s site can’t reflect it for two days.
- Marketing-team frustration. Good marketers leave dealerships that make them feel handcuffed.
The CMS is the test of whether your website is a tool or a constraint.
What to look for in a CMS (or what to ask about the one you have)
Five things:
- Who can use it? (Just admins, or any marketing person? Can the BDC update lead form copy? Can the service manager update service descriptions?)
- What can be changed without a developer? (Headlines, images, prices, hours, VDP content, blog posts, landing pages?)
- How long does a typical change take? (Minutes, hours, days?)
- Is there a preview/staging environment? (Can changes be reviewed before going live?)
- Is there a workflow? (Can someone draft, someone review, someone publish? Or is it all-or-nothing?)
The honest answer to “is our CMS working” is in the marketing team’s day, not the IT team’s.
What breaks when the CMS is wrong
- The content queue. Marketing accumulates a backlog of “things we need to change” because the CMS makes each one slow. The backlog becomes demoralizing. The most important changes don’t get made.
- The shadow CMS. Marketing starts using Google Docs, Notion, or spreadsheets to “manage the website” because the CMS doesn’t. The official CMS becomes a copy-paste destination, and the source of truth disappears.
- The accidental website owner. One developer, who originally set up the CMS, becomes the only person who can make changes. They’re overloaded, slow, and a single point of failure. When they leave, the website freezes.
- The Frankenstein site. Years of “we just need to add this one thing” accumulate. The site is full of plugins, workarounds, and inline HTML that no one understands. A small change breaks something else. The site becomes unmaintainable.
The fix isn’t picking the right CMS. It’s using the one you have well.
Most dealership CMSs can do more than the team is using them for. The questions to ask:
- Are we using the full feature set of the CMS we already pay for? (Often, no. The marketing team uses 30% of what’s available.)
- Are we paying for plugins or modules we don’t need? (Common.)
- Are we paying a developer to do things the CMS does natively? (More common than you’d think.)
- Is the team trained? (Often, no. The CMS has a learning curve that nobody has invested in.)
The dealership that gets the most from its CMS is the one that trains the marketing team, uses the CMS’s built-in features before adding new ones, and has a documented workflow for content changes.
The bottom line
A CMS isn’t a technology decision. It’s a people decision. The right CMS is the one your marketing team actually uses, the one that makes them faster instead of slower, and the one that doesn’t require a developer for every change.
You don’t need to be dangerous with CMS software. You need to be dangerous about asking why changes are slow, and who’s allowed to make them.
Next in the series: “What is an API, and why does it matter for your inventory and CRM?”
Part of the Just Enough to Be Dangerous infrastructure series from VCTRS. For the technical version to hand your IT team or vendor, read CMS for Car Dealerships: A Technical Reference.