# Message test — https://d03997b8-229c-4fbf-aa45-3467eaa40d11.claudeusercontent.com/v1/design/projects/d03997b8-229c-4fbf-aa45-3467eaa40d11/serve/myKaarma%20Wireframe%20(standalone).html?t=bc5b4a09a66dd03c6e2b07c8e378b168ab928d9aa5ded3bdbb389bf05d6229d1.00ee5568-291a-43f2-a8cc-f34466838c1f.a2ddcbfb-4e8b-4d69-bf0f-7ceceaf4cda2.1791404666.fp&direct=1

After reading your page, only 1 of 15 personas could name what kind of product this is, unprompted.

- **Page tested:** https://d03997b8-229c-4fbf-aa45-3467eaa40d11.claudeusercontent.com/v1/design/projects/d03997b8-229c-4fbf-aa45-3467eaa40d11/serve/myKaarma%20Wireframe%20(standalone).html?t=bc5b4a09a66dd03c6e2b07c8e378b168ab928d9aa5ded3bdbb389bf05d6229d1.00ee5568-291a-43f2-a8cc-f34466838c1f.a2ddcbfb-4e8b-4d69-bf0f-7ceceaf4cda2.1791404666.fp&direct=1
- **Audience tested against:** Service directors, managers, and GMs at dealerships
- **Personas:** 15 simulated
- **Report:** https://grader.wynter.com/r/d03997b8-229c-4fbf-aa45-3467eaa40d11-claudeuse-1qzqbzc

> These answers are generated by AI, scored on Wynter's B2B Message
> Layers framework using behaviorally-diverse simulated personas. The
> methodology is real and the critique is directional. What a simulated
> persona cannot have is a live budget, a renewal coming up, or a boss
> asking about this quarter.

---

## 01 · The scores

Every persona answered all four questions. These are four independent
proportions of the same panel, not stages of a funnel.

| Layer | Question | Cleared the bar | Strength | Of those who passed |
| --- | --- | --- | --- | --- |
| 1. Clarity | Do they understand what you do? | 1/15 | 78% | all with reservations |
| 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 84% | 4 without hesitation, 11 with reservations |
| 3. Value | Do they actually want it? | 13/15 | 70% | all with reservations |
| 4. Differentiation | Is there a reason to pick you over the alternatives? | 5/15 | 41% | all with reservations |

**Brand alignment** (a side metric, not one of the four layers) — 14/15, 74% strength (all with reservations). Does the page read like the company you actually are?

**Fix first: Clarity.** Earliest failing layer, walking the sequence in order — not simply the lowest score.

### What they thought you sell

1 of the personas who named a category got it wrong:

- 1× “Fixed ops / service lane management software”

---

## 02 · What to change, layer by layer

Ordered worst-first. Specific edits, not a restatement of the score.

### Clarity

**Fill or delete the empty testimonial block and the unsourced logo statistic.**

A blank quote card and a statistic with no named dealer read as unfinished work and cast doubt on the rest of the page. Either name the dealer, store size and result, or remove the block entirely.

*effort medium · impact high · tested against Proof next to the claim*

**Replace every "CTA: TBD" label with the real link text for that section.**

Placeholder labels at the end of Capture, Convert and Consult make the site look half-built and hide where each section leads. Write the actual destination, such as a link to the campaigns or inspections page.

*effort low · impact high · tested against One clear next action*

**Rewrite the H1 to say what myKaarma does, not its category.**

"The Service Growth Platform for Fixed Ops" is a category label a reader cannot picture. Lead with the job, such as booking, inspections, approvals and payments running on top of your DMS.

*effort low · impact high · tested against Lead with the use case*

**Name service managers and fixed ops directors in the hero subhead.**

The page makes the reader infer the audience from workflow vocabulary instead of stating it. Say who this is for in the line under the headline, by role and dealership department.

*effort low · impact medium · tested against Name the audience*

### Differentiation

**Add a named dealer group result beside the "built around it" claim in the hero.**

Nothing on the page shows a real customer, so the claim that myKaarma is built around fixed ops rests on assertion. Add one dealership name, store count and an outcome figure next to that line.

*effort medium · impact high · tested against Proof next to the claim*

**State under the OEM logos whether each is a live, certified integration.**

Readers suspect the logos are partnerships or aspirations rather than working integrations. Label them with the certification status and how many dealers run each one today.

*effort low · impact high · tested against Proof next to the claim*

**Add a line to "Keep your DMS" naming what competing tools make you rip out.**

The DMS-layer positioning lands, but nothing says why myKaarma is the better layer than the alternatives a service manager is also evaluating. Name the specific trade-off buyers avoid by choosing it.

*effort medium · impact medium · tested against Give a reason to choose you*

### Value

**Add a declined-work recovery dollar figure under "Recover declined work".**

Declined-work follow-up is the one feature that sounds like new revenue, yet it carries no number. State recovered dollars per month at a store of a stated size.

*effort medium · impact high · tested against Specifics beat superlatives*

---

## 03 · What is working

### The "layer on top of your DMS, not a replacement" framing lands immediately

Eight respondents restated the core positioning unprompted: a fixed-ops software layer sitting on the DMS that handles service comms, scheduling, inspections, payments and video approvals without ripping out the DMS.

> It's a fixed-ops/service-lane software layer that sits on top of your DMS — handling customer communication, scheduling, inspections, approvals (the digital "service cart"), and payments
> 
> — Service Manager, Vehicle Service, 201-500

> It's a fixed-ops / service-lane software layer that sits on top of your DMS—handles customer comms, scheduling, inspections/video approvals, and payments for service departments, without replacing the DMS.
> 
> — General Manager, Automotive Repair, 501-1000

> It's a fixed-ops software layer that sits on top of your DMS and handles the whole service lane conversation - booking appointments, texting/calling customers, running the multi-point inspection and video approval process, and taking payment, all tied to one customer record.
> 
> — Service Director, Vehicle Service, 501-1000

> The "works with your DMS, doesn't replace it" line is the clearest thing on the page and the part I'd actually repeat to someone else.
> 
> — Service Manager, Automotive Repair, 51-200

> It's a fixed-ops software platform that sits on top of your DMS, handling the service lane workflow — booking appointments, texting/calling customers, running digital inspections with video, getting repair approvals, and taking payments, all tied back to the RO.
> 
> — Fixed Operations Manager, Vehicle Service, 51-200

> Your DMS stays the system of record... myKaarma gives your team deeper fixed-ops workflows.
> 
> — Service Director, Automotive Repair, 201-500

### The service department is recognised as the buyer within seconds of the header

Seven respondents named service managers or fixed ops as the audience and credited the hero line, the weak-DMS problem statement and the service-floor vocabulary for getting them there fast.

> The hero line "Dealership software may cover fixed ops. myKaarma is built around it" plus "Keep your DMS. Grow service in myKaarma" tells me within seconds this is for someone who already runs a DMS and is frustrated
> 
> — Service Manager, Vehicle Service, 201-500

> It was obvious within the first two lines - "Dealership software may cover fixed ops. myKaarma is built around it" tells you the problem (DMS fixed-ops modules are an afterthought) and the fix in one breath.
> 
> — Service Director, Vehicle Service, 501-1000

> it's obvious within the first screen from the language — "advisors," "technicians," "RO," "capacity, transportation, routing settings" — this is written for someone running a dealership service department, which is me.
> 
> — Service Manager, Automotive Repair, 51-200

> Dealership software may cover fixed ops. myKaarma is built around it
> 
> — Service Director, Automotive Repair, 201-500

### Declined-work recovery is the one feature respondents read as revenue

Four respondents singled out follow-up on declined work after the RO closes as the only item that sounds like new money, and paired it with faster approval workflows as a measurable operational gap competitors leave open.

> the declined-work-stays-alive-after-the-RO-closes piece is the one feature that actually sounds like new revenue, not just convenience
> 
> — Service Manager, Vehicle Service, 201-500

> declined recommendations stay in myKaarma after the RO closes" so they're automatically revisited instead of forgotten, and the "interactive service cart" where customers approve/decline from their phone with video and pricing attached should lift close rates on inspections
> 
> — Service Department Manager, Automotive Retail, 51-200

---

## 04 · What the personas said

### Placeholder copy and 'TBD' CTAs read as an unfinished site and bleed into doubt about…

Six respondents flagged the blank testimonial, unsourced logo stat and TBD call-to-action labels. They read these as execution and maturity problems, not just cosmetic gaps, and one said the labels obscured what the features actually do.

> leaving "CTA: TBD" and "Name, Title · Dealership" live on the page tells me either marketing is under-resourced or nobody proofed this before it went live, which is a weird mismatch for a company that's apparently landed OEM program approvals.
> 
> — Service Department Manager, Automotive Dealerships, 501-1000

> every CTA under the five-stage journey just says "CTA: TBD" — that's not marketing copy, that's an unfinished page, and if a vendor can't be bothered to finish their own site before I'm supposed to book a demo, I start wondering what else is half-built
> 
> — Service Department Manager, Automotive Retail, 51-200

> "CTA: TBD" placeholders scattered through each step and vague labels like "myKaarma keeps... together" made me double-check I wasn't missing an actual feature name versus just marketing glue words
> 
> — General Manager, Automotive Retail, 201-500

> half the CTAs just say "CTA: TBD," and that sloppiness makes me wonder if the company is bigger than its web presence or just hasn't finished this particular page refresh
> 
> — Service Director, Automotive Retail, 51-200

### No numbers means no meeting

Five respondents said they would need before-and-after close-rate lift or recovered declined-work dollars from a comparable-size store. The page offers feature description with zero metrics or case studies.

> A documented close-rate lift on declined/recommended work — show me a same-size shop going from X% to Y% recovered revenue per RO over a quarter, and I'll take the meeting; without that it's just a feature list.
> 
> — General Manager, Automotive Repair, 501-1000

> A measurable lift in closed declined-work dollars per RO within a quarter — if they can show me a before/after number like "X% of declined work got re-approved within 90 days" from a dealership our size, that's the proof point
> 
> — Service Department Manager, Automotive Retail, 51-200

> A real number — show me a comparable dealer's recovered-RO or declined-work close-rate lift after switching, not just the mechanic for how it could happen.
> 
> — Fixed Operations Manager, Automotive Dealerships, 201-500

> A measurable lift in closed declined-work dollars within the first two quarters - show me that recovered recommendations from closed ROs actually convert at even 15-20%, backed by a real store's numbers, and I'll put budget behind it. Without that number it's just a feature description, not a reason to act.
> 
> — Service Director, Vehicle Service, 501-1000

> everything on this page is a claim, not a result — no close-rate lift, no time-saved-per-RO, no case study with a dealership our size.
> 
> — Service Manager, Automotive Repair, 51-200

### The missing customer reference undercuts the OEM proof

Two respondents said the OEM integrations are concrete but the blank testimonial and unsourced statistic leave the credibility claim unsupported.

### The OEM logos are suspected of being aspirational rather than live

One respondent questioned whether the logos represent paying integrations or just partnerships, and the unfinished placeholder copy elsewhere on the page compounded that doubt about company maturity.

> the fact that they don't fill that in makes me wonder if the OEM logos are aspirational partnerships rather than live, paying integrations at scale
> 
> — Service Department Manager, Vehicle Service, 201-500

### The persona is inferred from vocabulary, never stated

Three respondents reached the right audience but noted the page implies it through workflow language rather than naming the role, and that the header states the problem without any supporting numbers.

> the header says it straight out: "The Service Growth Platform for Fixed Ops" and "Dealership software may cover fixed ops. myKaarma is built around it." That tells me the problem (DMS fixed-ops functionality is thin, siloed comms/approvals/payments) and the buyer (dealership/fixed-ops leadership) within the first two lines, no hunting needed. What's still missing for me is proof — there's no number anywhere, just "turn more opportunities into appointments" with zero percentages or case data to back it.
> 
> — General Manager, Automotive Repair, 501-1000

> The reader isn't named with a job title, but it's clearly fixed-ops/service managers and advisors — "your team," "technicians," "advisors" all through the Capture/Convert/Consult/Complete/Optimize sections make that plain by inference rather than a stated "built for Service Managers" line
> 
> — Service Manager, Automotive Retail, 501-1000

---

## 05 · The hardest read

An adversarial pass over the findings. Every claim below was checked
against the panel's own answers; unsupported ones were dropped.

- **The page is being read as a company credibility test, and it is failing it.** *(high)*
  Six respondents read placeholder copy and TBD CTAs as execution and maturity problems rather than cosmetic gaps, and one questioned whether the OEM logos are paying integrations at all. Unfinished copy is being priced as business risk.
- **Comprehension is not the bottleneck — the page converts understanding into nothing.** *(high)*
  Eight respondents restated the positioning unprompted and seven named the service buyer within seconds, yet five said no numbers means no meeting. The message lands and then stalls for lack of proof.
- **The one concrete asset on the page is neutralised by what sits next to it.** *(high)*
  Two respondents called the OEM integrations concrete but said the blank testimonial and unsourced statistic leave the credibility claim unsupported, and one extended that doubt to the logos themselves. Proof placed beside placeholders reads as placeholder.
- **The only revenue story on the page is carried by a single feature with no evidence behind it.** *(high)*
  Four respondents named declined-work recovery as the sole item sounding like new money, while five asked specifically for recovered declined-work dollars from a comparable-size store. The strongest claim is the one most exposed by the missing metrics.
- **The page makes the buyer do the work of identifying themselves.** *(medium)*
  Three respondents reached the right audience only by inferring it from workflow vocabulary, noting the role is never named and the header states the problem without supporting numbers. Correct inference is not the same as stated qualification.
- **TBD labels are destroying feature comprehension, not just polish.** *(medium)*
  Among the six flagging placeholders, one said the labels obscured what the features actually do. The CTA gaps are eating into the product explanation that is otherwise the page's strongest asset.

---

## 06 · Who answered

| # | Role | Industry | Company size |
| --- | --- | --- | --- |
| 1 | Service Manager | Vehicle Service | 201-500 |
| 2 | General Manager | Automotive Repair | 501-1000 |
| 3 | Service Department Manager | Automotive Retail | 51-200 |
| 4 | Fixed Operations Manager | Automotive Dealerships | 201-500 |
| 5 | Service Director | Vehicle Service | 501-1000 |
| 6 | Service Manager | Automotive Repair | 51-200 |
| 7 | General Manager | Automotive Retail | 201-500 |
| 8 | Service Department Manager | Automotive Dealerships | 501-1000 |
| 9 | Fixed Operations Manager | Vehicle Service | 51-200 |
| 10 | Service Director | Automotive Repair | 201-500 |
| 11 | Service Manager | Automotive Retail | 501-1000 |
| 12 | General Manager | Automotive Dealerships | 51-200 |
| 13 | Service Department Manager | Vehicle Service | 201-500 |
| 14 | Fixed Operations Manager | Automotive Repair | 501-1000 |
| 15 | Service Director | Automotive Retail | 51-200 |

---

## 07 · Before you act on this

The methodology is real, and the critique is directional. What a
simulated persona cannot have is a live budget, a renewal coming up, or
a boss asking about this quarter. **Validate anything you're betting on
with real ICPs who are actually in-market.** Being wrong is more
expensive than you think. Finding out is cheaper than you'd guess.

Wynter runs message testing with verified B2B professionals — trusted
by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and
Miro. <https://wynter.com>

This report is kept for 60 days from 2026-10-07, then deleted along with the personas and their answers.

