Ground Truth Advisory — Helen Vernon | The retailer's-side read

Your plan is sound. I'll tell you what it feels like on the morning after it goes live.

Targets, systems and standards are designed by people who have never had to hit them, use them, or explain them to a technician on a wet Tuesday in March. Nobody's lying — there is simply no mechanism that tells you what your plan does when it lands. That's what I am.

Every seat, in order Marque

6 yrs Sales Executive Mercedes-Benz

4 yrs Used Car Controller → Used Car Manager Mercedes-Benz

1 yr Sales Manager Mercedes-Benz

18 mo Local Business Development Manager VW · Audi · Škoda

8 yrs E-Commerce & Implementation Manager Mercedes-Benz

4 yrs Group Agency Transition Manager — solo VW · Audi · Škoda · Mercedes-Benz · MINI

14 mo Head of Business — full P&L, all departments incl. Aftersales VW Passenger Cars & Commercial Vehicles

Now Founder, SMART · Advisory Independent

Thirty years. Every department in the book. Divisional accountability for enquiry management and KPI achievement. Then five marques, five different agency models — each designed in isolation, all landing on one network, one set of systems, one set of people. Over 40 sites. End to end, and through the regression. No team. Me.

What that seat actually held

The whole programme function

Change management. Process mapping. Training manuals. SharePoint build and delivery infrastructure. The single conduit between group and OEM — in both directions.

Five systems, learned from nothing

Each brand's architecture, structure and capability. Often taught to the network at go-live, because in several cases the system did not exist to be learned before it.

The agreement, read from the retail side

Reviewed the compliance provisions in each agency agreement and surfaced the operational gaps before they reached the network — the areas the process map and the what-ifs had not reached.

Every site, after go-live

Readiness, stakeholder alignment, DMS programme updates, and the resolution of the issues nobody had modelled. Because they only exist once it is live.

The plan was coherent. The damage happened at its edge.

Agency changed how a new car is retailed. It did not change how a used car is retailed. So at go-live the site runs two entirely different retail logics side by side — on dual systems, with the same executive, the same customer, and very often the same transaction. The part-exchange is the seam. And the seam is where it grinds.

Nobody designing the model was looking there, because the agency model is not about used cars. Meanwhile the customer excellence scoring stayed pointed at the site. The model changed; the accountability did not move. The retailer absorbed the difference — and absorbed the customer's confusion about why one half of the deal is negotiable and the other half is not.

That is the whole proposition. Not that the plan was wrong — it wasn't. That the plan had a boundary, and nobody was standing at the edge of it. I was. Four years, five marques, over 40 sites, on my own.

Readiness isn't a state you reach. It's a thing you declare so the date can hold.

Every plan I have ever received was written as though the unknowns could be eliminated before go-live. They cannot. So you go anyway — knowing you have done everything you can, not knowing what tomorrow looks like — and you learn in contact. Everyone downstream of that assumption is quietly absorbing the difference. It never appears in the report.

What the plan assumes

Readiness is verified before launch, and the gate means something.
The model is the only model. It lands in a clean building.
Process change is adopted once communicated and trained.
The system supports the process, because the process was specified to it.
Post-launch is a support phase.

What the morning after looks like

Readiness was signed off because the date could not move. Everyone knew.
Five marques, five agency models, one network, one DMS — and one person trying to remember which logic pays today.
Adoption dies at the first month-end when the old way is faster and the target is real.
The system holds one logic. You are running five. The gap is being closed manually, by people, at night.
Post-launch is where the actual design happens — and nobody budgeted for it.

I'll say the quiet part out loud.

Everything I have written on this page is a thing everybody already knew and nobody said. The readiness gate that got signed because the date couldn't move. The used car seam nobody was looking at. The customer score still pointed at the site after the model changed. The manager who left, and the cost that never got counted.

None of it is a secret. It is simply unsayable — because saying it is career-limiting for the person who knows, and unwelcome for the person who decided.

I have no career left to limit inside your business. That is precisely what you are buying.

Why it lands

Every plan I have watched fail, failed in the room — not in the model. The design was fine. The people had quietly decided in advance that it wasn't for them, and nobody had earned the right to be told.

I don't run culture workshops. I read the room as carefully as the P&L, I ask the question everyone is avoiding, and I tell you what I heard — including the parts you would rather I didn't.

That is the method. It's also the reason the rest of it works — because a rollout, a target or a transition only lands in a business where someone was willing to hear the truth before it was too late to act on it.

Design is the easy half. Landing it is the job.

Every engagement produces something written that you can act on without me. I'd rather be re-hired than retained out of habit.

AI, Designed and Landed

Not a strategy deck. A rollout. Nobody in this industry has a person whose job is to take AI from decision to adopted across a group — so it stalls at the pilot, or it lands and nobody uses it.

I have done this shape of work before: five brands, over 40 sites, systems that didn't exist until go-live, solo. Process maps, training, the SharePoint, the person on the phone at 4pm when a site can't make it work — and the regression afterwards, which is where the real design happens.

Design is the easy half. Landing it is the job.

Dealer groups · OEMs · Suppliers · Multi-site networks

Design — 4Ds diagnostic, use cases ranked by return, governance and risk framework
Build — working tools, not slideware. Proven at pilot before the network sees them
Land — process maps, training materials, site-by-site rollout, readiness that means something
Hold — adoption tracked, the post-live regression owned, and the fix delivered
Eleven AI certifications. Production systems built, not described

Interim / retained day rate on application
3–12 months

The Ground Truth Read

Before you set the target, launch the model, or roll the standard — I take your plan into real retailers and tell you what it will actually collide with. Written from the receiving end, in the language of the people who have to make it work.

OEM national & regional · Network development

Plan read against operating reality
Collision points, ranked by cost
What your network won't tell you, and why
Board-ready written finding

£12k–£25k scope-dependent

Product & Roadmap Reality

Your product assumes the Head of Business has time to look at the dashboard. He doesn't. I'll show you his actual Tuesday — where your tool sits in it, what it's competing with, and why the feature you're proudest of is the one nobody opens.

DMS & SaaS · Suppliers to the network

Voice-of-the-retailer, unfiltered
Workflow reality mapping
Roadmap challenged before it's built
Sales narrative that survives the room

from £10,000 4–6 weeks

Agency & Structural Change

Five marques. Five agency models. Over 40 sites. I delivered every one of them — solo, end to end — and was accountable through the regression, when the launch architecture met the showroom floor and something had to give. Advice from the only side of the table that saw all five arrive at once.

OEM · Retail groups · Transition programmes

Model design stress-tested against multi-brand reality
Post-live regression planned, not discovered
System and process reconciliation
Change plan the network will actually adopt

day rate on application

Retention: Women in the Network

Not a values workshop. A retention audit. Where women enter, where they stall, where they leave — and what each departure costs you in recruitment, lost margin and rebuilt relationships. Then we fix the mechanism. I have been the only one in the room for thirty years; I know precisely where it breaks.

OEM · Groups · Anyone tired of the photograph

Pipeline leakage mapped by grade and function
Attrition costed in pounds, not sentiment
Stay and exit interviews, run externally
Intervention plan with review gates

from £9,000 6 weeks

Standing reality check

Send me the plan before it goes to the network. I'll mark it up. Two days a month, an open line, and someone outside the building who has no reason to tell you it's fine.

Retained · Six-month minimum

Plans reviewed pre-issue
Standing monthly session
Direct access between sessions

£2,500–£4,000 per month

A finding nobody adopts is a cost, not a deliverable.

Change delivery

Every engagement carries a change plan — stakeholder and impact mapping, a readiness gate that means something, and the objection handling for the three people who will quietly kill it. Kotter and the Change Curve, applied to a business that still has to sell cars while it changes.

What the numbers don't show

The reason your best manager is leaving. The reason the workshop and the showroom don't speak. The reason the last consultant's report is in a drawer. I read the room as carefully as the P&L, because in this industry the room is where the plan dies.

Read these before you enquire. They are not negotiable.

I will not validate a plan I think is wrong. If you want a consultant who confirms the decision you've already made, there are excellent ones and I'll recommend three.

I speak to your network directly, or not at all. A finding filtered through the people it implicates is not a finding.

Nothing is named without permission. Former employers, current clients, and the people who talk to me in confidence stay protected. Always.

The report says what happened. Including the parts that are already working — those get protected in writing, because the second-worst outcome of a review is breaking the thing that wasn't broken.

Your plan is sound. I'll tell you what it feels like on the morning after it goes live.