Clarity
Fix firstDo they understand what you do?
0 could name what kind of product this is, unprompted.
https://codibly.com/15 AI-simulated buyers
Your message needs work: they could not tell what it is, who it's for, why it's worth their time, or why to pick you.
Do they understand what you do?
0 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
2 could quickly tell what problem it solves and who it is for.
Do they actually want it?
8 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
3 could name a reason to pick you over a similar option.
Your page describes: consent management. They said:
14 couldn't name one; 1 named the wrong one.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Four respondents said protocol terminology crowds out business outcome narrative, with no cost, headcount, or reporting language for ops and sustainability buyers. Not one of the four layers, and it does not affect the scores above or the order to fix them in.
These are 15 simulated buyers. Want 15 real ones?
Test with humansThe first is on your weakest layer, the second on the next, the third on the layer the most buyers had a problem with. Each says what to change on the page and why, with one simulated answer behind it.
Why: The list of capability labels reads like an agency directory rather than a defined offering. Lead with a single line saying whether you deliver projects, embed specialists, or both.
6 of 15 raised this
“Nobody ever states "this is for Operations Managers at clean energy companies" — I inferred the reader from the client logos (Siemens Energy, SolarEdge, Nordex) and the service list, not from any direct statement”
Why: The page presents capabilities before naming any situation the reader recognises. Open with the problem: EV charging projects stall because protocol engineers cannot be hired fast enough.
Why: Case study titles name clients but no outcome, so credibility rests on brand recognition alone. Under each, add what was delivered, in what timeframe, and the measured result.
8 of 15 raised this
“no named client outcome, no scope, no pricing. Not worth a meeting yet.”
These landed. Keep the wording when you edit around it.
Spyrosoft Group backing reads as a concrete, verifiable differentiator
“The "over a decade" of experience claim, the Spyrosoft acquisition in 2024 (a publicly traded group with 1700+ experts and 20+ offices)”
Client logos do most of the qualifying work the copy fails to do
“the one thing that would move the needle is the client list — Siemens Energy, SolarEdge, Wallbox, Nordex — because named enterprise logos in exactly this sector is real proof of relevant delivery experience”
The niche protocol staffing gap is a value proposition respondents could name
“Software dev consultancy for e-mobility and renewable energy — EV charging, BESS, OCPP stuff. Not a product, a services shop.”
Why: Readers cannot tell from the top of the page what is actually being sold, and fall back on guessing from the expertise grid. Write one opening sentence: engineering teams for EV charging and renewable energy projects.
6 of 15 raised this
“Nobody ever states "this is for Operations Managers at clean energy companies" — I inferred the reader from the client logos (Siemens Energy, SolarEdge, Nordex) and the service list, not from any direct statement”
Why: Nothing on the page tells a visitor whether it is meant for a CPO, a utility, or an OEM. Name the buyer directly, for example heads of engineering at charge point operators and renewables developers.
6 of 15 raised this
“Nobody ever states "this is for Operations Managers at clean energy companies" — I inferred the reader from the client logos (Siemens Energy, SolarEdge, Nordex) and the service list, not from any direct statement”
Why: A reader scrolls through claims before seeing any evidence of real work. Lead with one named project, its scope, and its result.
Why: Logos currently do the qualifying work the copy should do, and readers who do not recognise them learn nothing. Caption them with the sectors and project types those clients represent.
Why: The page shows breadth but never says why to choose it over any other engineering consultancy. Write that OCPP, OCPI and BESS engineers take months to recruit and you supply them immediately.
Why: Headings read as categories any software firm could claim. Make each heading name the concrete thing, such as OCPP 2.0.1 backend integration or battery storage control software.
Why: The acquisition is mentioned as a fact and left to speak for itself, and one reader took it as a delivery risk. Say what it buys the client: bench depth, continuity of team, and financial stability.
Why: Buyers cannot judge fit without knowing team size, engagement length, or how you charge. State typical team composition, minimum engagement, and whether work is time-and-materials or fixed price.
8 of 15 raised this
“no named client outcome, no scope, no pricing. Not worth a meeting yet.”
Why: Operations and sustainability buyers find only engineering vocabulary and no reason to keep reading. Add outcomes they answer for: charger uptime, rollout schedule, and hiring avoided.
5 of 15 raised this
“it uses category terms I recognize (OCPP, CSMS/CPMS, V2G, IEEE 2030.5, demand response) without over-explaining them”
Why: Non-engineering decision-makers hit undefined acronyms and stop. Add a short gloss after each, for example OCPP, the protocol connecting chargers to your management platform.
5 of 15 raised this
“it uses category terms I recognize (OCPP, CSMS/CPMS, V2G, IEEE 2030.5, demand response) without over-explaining them”
A deliberately adversarial read of the same answers. Each claim was checked back against what the personas said and dropped if nothing supported it.
The copy is doing none of the qualifying work — the logo wall is carrying the page
Six respondents inferred the buyer and problem only from the expertise grid and logos, and four said recognized logos established credibility within seconds, outperforming the copy. Remove the logos and the page communicates nothing.
The one asset carrying the page is also the least substantiated element on it
Eight respondents said the logo wall and case study titles carry no metrics, timelines, scope, or pricing, while four relied on those same logos to identify the buyer. Credibility rests on name-dropping that respondents explicitly called a hit to credibility.
Only two respondents in fifteen could articulate the value proposition, so the offer effectively did not register
Two respondents named the OCPP/OCPI/BESS staffing gap correctly, against four who read the page as an undifferentiated services listing and six who could not find a stated problem. The correct read is the exception.
The page disqualifies the economic buyer by writing exclusively for the technical evaluator
Five respondents said protocol terminology crowds out business outcome narrative, with no cost, headcount, or reporting language, and eight noted the absence of metrics and pricing. Nothing on the page supports a budget decision.
Breadth is being shown at the direct expense of a purchasable offer
Four respondents read stacked service labels as an agency listing with no single statement of what is sold, and six found no named problem. Listing capabilities is substituting for defining the product.
The strongest differentiator is inherited from a parent company, not earned by the work
Four respondents cited Spyrosoft Group backing as the concrete proof point — and one read it as a delivery-consistency risk — while eight found no substantiated outcomes anywhere. Ownership is standing in for evidence of capability.
The target buyer and the problem are never stated, only inferred
6 of 15
“Nobody ever states "this is for Operations Managers at clean energy companies" — I inferred the reader from the client logos (Siemens Energy, SolarEdge, Nordex) and the service list, not from any direct statement”
“the page never says who buys this in plain English — it lists deliverables like "OCPP Implementation Services" and "EMS & BESS Integration" without ever naming a job title or a problem statement”
“I had to piece it together from the "Our Expertise" list (CSMS/CPMS Development, OCPP Implementation, EV Fleet Management, V2G, Smart Charging & Load Management, BESS integrations) and the client logos”
“the actual problem and buyer only get concrete once you hit the expertise grid: CSMS/CPMS, OCPP, EV fleet management, BESS integration, demand response”
“The phrase "digital transformation" itself is the culprit — it's a catch-all consultancy word that could describe literally any service engagement”
“had to scroll past cookie banner and logos to "Who We Are" to get e-mobility/energy consultancy angle”
Service category labels stack up without one clear offering statement
4 of 15
“there's zero pricing, case study depth, or team sizing info on the page itself”
“this reads like an agency site, not "comparable tooling" I'd evaluate as a category”
“It's the sheer density of service-category labels stacked one after another — CSMS/CPMS, OCPI & OICP Interoperability, V2X, Dynamic Load Management, EMS & BESS Integration — with an arrow carousel and no plain sentence tying them into a single offering”
“Not a product, a services vendor.”
Client logos do most of the qualifying work the copy fails to do
3 of 15 · what worked
“the one thing that would move the needle is the client list — Siemens Energy, SolarEdge, Wallbox, Nordex — because named enterprise logos in exactly this sector is real proof of relevant delivery experience”
“The "Our Expertise in e-Mobility" and "Our Expertise in Renewable Energy" section headers with items like "CSMS/CPMS Development," "OCPP Implementation Services," "EV Fleet Management Software Services," and "Battery Management Systems (BMS)" told me within seconds this is a custom software dev shop”
“The client logos (Wallbox, SolarEdge, Siemens Energy, etc.) and the long list of named protocols support that this is real technical work, not vague consulting fluff.”
“the client logos (SolarEdge, Siemens Energy, Wallbox) told me who they're for more than the copy did”
Spyrosoft Group backing reads as a concrete, verifiable differentiator
4 of 15 · what worked
“The "over a decade" of experience claim, the Spyrosoft acquisition in 2024 (a publicly traded group with 1700+ experts and 20+ offices)”
“a named parent company, "publicly traded on the Warsaw Stock Exchange," 1700+ experts, 20+ offices — that's a verifiable stability signal”
“The Spyrosoft Group backing is the one specific thing that actually moves the needle for me — "publicly traded technology leader on the Warsaw Stock Exchange," "1700+ experts, 20+ offices in 9 countries," and named in the FT's fastest-growing companies list three years running. That's a concrete, checkable claim”
“raises "will I actually get senior e-mobility engineers or get routed into a generic Spyrosoft delivery pool" — so I'd need that answered before it beats a smaller, more specialized shop”
Case studies and logos are asserted but never substantiated with outcomes
8 of 15
“no named client outcome, no scope, no pricing. Not worth a meeting yet.”
“there's zero pricing, case study depth, or team sizing info on the page itself”
“no "we built X for Siemens Energy," no case study link that actually names the client, just a logo wall and a case-study teaser ("Developing a Scalable OCPP Server for Seamless EV Charging & V2G Integration") with no company attached”
“it's a services engagement, so worth a meeting only if procurement can get me two direct references from those logos confirming scope and timeline, not just a logo wall”
“no case study numbers, no timeline, no "we cut integration time from X to Y for client Z," just a client logo wall and a list of service names”
“the page gives me zero proof of delivery quality: no case study detail, no client outcome numbers, just a logo wall and a list of service names”
“the case studies section just says "Read more" with no numbers attached, so I can't tell if this changes timelines by weeks or months”
“Client logos - Siemens Energy, SolarEdge, Nordex - are the only real signal here. Rest is generic service list, no case metrics.”
The niche protocol staffing gap is a value proposition respondents could name
2 of 15 · what worked
“Software dev consultancy for e-mobility and renewable energy — EV charging, BESS, OCPP stuff. Not a product, a services shop.”
“I'd get a technical partner who could pick up OCPP/OCPI protocol work, CSMS integration, or a dedicated team for V2X/smart charging without me having to hire”
The page speaks to engineers, not to operations or business decision-makers
5 of 15
“it uses category terms I recognize (OCPP, CSMS/CPMS, V2G, IEEE 2030.5, demand response) without over-explaining them”
“The tone is written for a technical buyer or a founder evaluating "who can build this," heavy on capability lists and "years of experience and expertise" boilerplate; it never once addresses what happens to my team's workload or timeline if I hire them”
“it's heavy on protocol names and service categories (CSMS/CPMS, V2X, dynamic load management) and light on the plain-English "here's what changes for your team" story I actually need”
“There's no promise here to test against my current workflow because there's no product or measurable outcome pitched at a sustainability manager; it's "OCPP Implementation," "BMS," "Fleet Management Software" — all engineering deliverables for a CTO or product lead”
“The tone is not written for someone like me — it's written for an engineer or technical evaluator who already knows what OCPP and OCPI/OICP mean”
15 AI-simulated personas matched to your target market. Each answered independently, without seeing your goal, the scoring criteria, or each other’s answers. Attribution is role, industry and company size only.
Every answer on this page was written by an AI model role-playing a buyer profile, scored on Wynter’s B2B Message Layers framework. The personas were sampled in code across role, industry, company size and behavioral traits; the model wrote only the answers. Scores arrive through fixed verdict categories and the counts are computed in our own code, so no number here was written by a model.
The count is how many personas cleared the bar on each question. A yes can be unhesitating or come with reservations; the scorecard counts both as a yes, and this is the only place the difference is shown. Per layer:
These answers are AI-simulated and directional. Validate anything you’re betting on with real buyers, your ICPs.
A detailed, section-by-section message test report from verified B2B professionals who are actually in-market for what you sell.







