Clarity
Fix firstDo they understand what you do?
15 could name what kind of product this is, unprompted.
https://ratedpower.com/15 AI-simulated buyers
Your message lands: they know what it is, who it's for, why it's worth their time, and why to pick you.
Do they understand what you do?
15 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
15 could quickly tell what problem it solves and who it is for.
Do they actually want it?
15 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
15 could name a reason to pick you over a similar option.
Your page describes: AI-powered PV design and engineering. They said:
12 couldn't name one; 3 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
One respondent praised the engineer-specific pain points over generic transformation language; another said the marketing layer obscures whether this is a single product or a bundle. 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: A reader cannot tell what 160x, 5% LCOE and 20% asset profit are measured against, or over how many projects. State the comparison base, sample size and who calculated them, right beside each figure.
4 of 15 raised this
“"5% less LCOE" and "20% more asset profits" have no baseline or methodology attached, so I'd push them to show the calculation, not just quote it, before I take this further internally.”
Why: "The round-trip is not lossless in every case" tells a civil team nothing about what breaks, so they assume the worst. Name which elements survive export and import, the cases where they do not, and the workaround.
6 of 15 raised this
“"the round-trip is not lossless in every case" on the DWG export is a real rule-out risk for me, since my whole workflow depends on handing edited layouts back to civil in CAD without corruption - if a rival tool doesn't have that caveat, or specifies exactly what breaks, they win on that line alone”
These landed. Keep the wording when you edit around it.
The first screen states the problem and who it is for without inference
“the hero line "AI-optimized pass takes your project site all the way to layout, yield, electrical design, CAPEX and 400+ editable pages of documentation... in up to 90% less design time" tells me the problem (slow one-scenario-at-a-time design in spreadsheets/CAD) and the fix in one breath”
The Black & Veatch audit against PVsyst is the only proof respondents believed
“The Black & Veatch audit number (+0.24% to +1.08% vs PVsyst) is the one bit of proof that would actually let me trust the yield output rather than just the marketing”
The offering reads clearly as one-pass PV/BESS design automation replacing the…
“PV/BESS design automation software, basically a faster replacement for the CAD/PVsyst/spreadsheet stack I'm using now.”
No specific edits needed here — this layer held up.
No specific edits needed here — this layer held up.
Why: The profit claim sits alone while the Black & Veatch audit carries its own evidence. Attach a named project, portfolio or customer to the profit and time savings figures the same way.
4 of 15 raised this
“"5% less LCOE" and "20% more asset profits" have no baseline or methodology attached, so I'd push them to show the calculation, not just quote it, before I take this further internally.”
Why: Buyers want to know the software holds up on messy real terrain, not a reference case. Say that you will run their site and reconcile the yield, and how to request it.
6 of 15 raised this
“"the round-trip is not lossless in every case" on the DWG export is a real rule-out risk for me, since my whole workflow depends on handing edited layouts back to civil in CAD without corruption - if a rival tool doesn't have that caveat, or specifies exactly what breaks, they win on that line alone”
A deliberately adversarial read of the same answers. Each claim was checked back against what the personas said and dropped if nothing supported it.
One disclosed caveat outweighs every benefit claim on the page.
Six respondents named the DWG round-trip data loss as the biggest risk and a reason a lossless competitor wins, more than the five who described the offering correctly. A single line of fine print is doing more work than the entire value argument.
The page's quantified claims are unverifiable and therefore load-bearing on nothing.
Four respondents said 160x speed, 5% LCOE and the profit and time savings carry no baseline, methodology or evidence, and one asked for a budget comparison against current CAD and Excel spend. Numbers without a denominator are decoration.
Credibility rests on a single borrowed proof point, leaving the page fragile.
Eight respondents named the Black & Veatch PVsyst reconciliation as the only believed proof and the one thing separating the page from competitor marketing. Everything else — headline metrics, customer quotes — sits below it, and only two cited the named…
Buyers do not accept that the demonstrated performance transfers to their own projects.
Two respondents said the speed and yield advantages only matter if the software holds up on messy real sites and asked for validation on a project of their own; two more wanted the audit extended to hybrid dispatch or their site. The proof is read as a demo…
The product architecture is unclear: buyers cannot tell what they would actually be purchasing.
One respondent said the marketing layer obscures whether this is a single product or a bundle, and one found the primary target ambiguous despite the hero naming personas. Scope ambiguity blocks procurement even when the pitch lands.
Audience clarity is the page's only uncontested strength, and it stops at the hero.
Nine respondents said the first screen names the problem, job titles and personas without inference — the highest agreement on the page. Below the fold, agreement collapses to six on the round-trip risk and four on missing methodology.
The offering reads clearly as one-pass PV/BESS design automation replacing the…
5 of 15 · what worked
“PV/BESS design automation software, basically a faster replacement for the CAD/PVsyst/spreadsheet stack I'm using now.”
“It's AI-driven design software for utility-scale solar (and storage/hybrid) projects — it takes a site through layout, yield simulation, electrical design and CAPEX/documentation in one automated pass”
“takes a site from GIS screening through layout, energy yield and CAPEX in one automated pass instead of doing it by hand in CAD and spreadsheets”
“The pitch was "160 layouts instead of one," which stuck because it's a concrete number, not because I trust it yet - I'd want to see that run on our own site data before buying in”
Named customers and specific workflow metrics made the tool feel real
2 of 15 · what worked
“The customer quotes (Engie, Akuo, Recurrent Energy, RES Group) naming actual workflow reductions like "50% of overall engineering workflow" and "30 to 40%" are what actually convinced me this is a real design tool and not just a buzzword wrapper.”
“The named customers - Engie, Akuo, RES Group, Recurrent Energy - and specific figures like "30 to 40% engineering time reduction" and DWG export into AutoCAD make it credible as a real design tool rather than vapourware”
The first screen states the problem and who it is for without inference
9 of 15 · what worked
“the hero line "AI-optimized pass takes your project site all the way to layout, yield, electrical design, CAPEX and 400+ editable pages of documentation... in up to 90% less design time" tells me the problem (slow one-scenario-at-a-time design in spreadsheets/CAD) and the fix in one breath”
“"A single site takes a day or two, so you run two options instead of twenty." That's my PVsyst/CAD reality.”
“It's obvious within the first line - "AI-powered design and engineering for utility-scale PV, storage and hybrid" tells you what it does, and the subhead "Screen with confidence. Engineer without delay" tells you the problem it's solving: slow, one-scenario-at-a-time manual design work”
“The "one scenario at a time" section spells the pain out explicitly: teams "build layouts in spreadsheets and CAD, one scenario at a time," a site "takes a day or two," so you "run two options instead of twenty." As for the audience, it's not left to guesswork either — the "Built for every team" section names developers, EPCs, banking/finance, consulting, IPPs, utilities, engineers and engineering leaders directly”
“they spell out the audience explicitly later with the "By industry / By role" tabs - developers, EPCs, banking and finance, IPPs, utilities, engineers - so I didn't have to infer who it's for”
“the "Built for every team" section lists developers, EPCs, banking/finance, consulting, IPPs, utilities, engineers and executives by name, and the testimonials come from exactly those job titles”
“there's a literal "By role" list - developers, EPCs, banking/finance, consulting, IPPs, utilities, engineers, engineering leaders - so I didn't have to guess who this is for”
“it's split between selling me on technical credibility and selling my boss on ROI.”
The headline numbers have no baseline or methodology behind them
4 of 15
“"5% less LCOE" and "20% more asset profits" have no baseline or methodology attached, so I'd push them to show the calculation, not just quote it, before I take this further internally.”
“phrases like "runs the whole design matrix," "searches the design space," and "applies the right CAPEX templates to each combination" describe outcomes but never the actual search method (is it exhaustive, gradient-based, some heuristic?)”
“the "5% LCOE" or "20% more asset profits" numbers, which have no baseline or source and I'd ignore until proven”
“A named budget line against a named alternative - what a consulting firm my size actually pays per year for this versus current CAD/Excel licenses and hours, not a generic ROI calculator I have to go build myself.”
The Black & Veatch audit against PVsyst is the only proof respondents believed
7 of 15 · what worked
“The Black & Veatch audit number (+0.24% to +1.08% vs PVsyst) is the one bit of proof that would actually let me trust the yield output rather than just the marketing”
“The Black & Veatch PVsyst reconciliation number (+0.24% to +1.08%) is the one bit of proof on the page that isn't just a customer quote, and that's what would get me to a meeting rather than a "thanks, pass." But I'd want that demo run on one of our actual sites with our BESS dispatch data before I take it further”
“The DWG round-trip export in the Layout Editor is the specific thing that would tip a shortlist decision my way — the page is honest that "the round-trip is not lossless in every case," which is actually a point in its favor because it's the kind of caveat you only write if you've tested it, and it directly answers my team's fear of being locked out of AutoCAD. Combined with the Black & Veatch audit figure ("+0.24% to +1.08%" against PVsyst), that's the one yield claim on the page with an actual named third party and a number I could go check”
“The Black & Veatch audit line - "+0.24% to +1.08%" against PVsyst - is the one thing that would actually pull me toward this over a competitor, because it's a named third party checking the yield number”
“The Black & Veatch audit line — "+0.24% to +1.08%" against PVsyst — is the one concrete thing that would push it onto my shortlist over a competitor with no third-party number”
“The Black & Veatch audit line - "+0.24% to +1.08%" against PVsyst - is the one thing here that would actually move it up my shortlist, because it's a named third party and a checkable number, not marketing fluff.”
“Getting a real project through the tool end to end - one of our own sites, our own terrain and grid constraints - and seeing the layout export cleanly into AutoCAD without my team having to redraw half of it by hand.”
Claimed advantages are conditional on performance with messy real sites
2 of 15
“Watching it take one of our own messy sites - not their demo site - through to a layout and yield number that's within a few percent of what my team already produced by hand, in minutes instead of days”
“Getting a real project through the tool end to end - one of our own sites, our own terrain and grid constraints - and seeing the layout export cleanly into AutoCAD without my team having to redraw half of it by hand.”
The DWG round-trip lossiness caveat is read as a deal-breaker
6 of 15
“"the round-trip is not lossless in every case" on the DWG export is a real rule-out risk for me, since my whole workflow depends on handing edited layouts back to civil in CAD without corruption - if a rival tool doesn't have that caveat, or specifies exactly what breaks, they win on that line alone”
“the CAD round-trip note ("The round-trip is not lossless in every case") almost rules it out on its own, since that's exactly where our real workflow would break”
“"The round-trip is not lossless in every case" for the CAD export is a genuine red flag they chose to disclose - it's honest, which I respect, but it also tells me there's friction in exactly the workflow step where our engineers would push back hardest”
“the DWG round-trip line — "not lossless in every case" — is exactly the kind of caveat that tells me adoption friction with our civil team is real, not hypothetical”
“the DWG export caveat "not lossless in every case" would rule it out if a competitor doesn't have that same asterisk on their CAD round-trip, since half my team's workflow lives in AutoCAD”
“The DWG round-trip export in the Layout Editor is the specific thing that would tip a shortlist decision my way — the page is honest that "the round-trip is not lossless in every case," which is actually a point in its favor because it's the kind of caveat you only write if you've tested it, and it directly answers my team's fear of being locked out of AutoCAD. Combined with the Black & Veatch audit figure ("+0.24% to +1.08%" against PVsyst), that's the one yield claim on the page with an actual named third party and a number I could go check”
The copy is written for engineers rather than generic digital-transformation buyers
2 of 15
“it doesn't oversell with generic "digital transformation" language, and quotes like "the turnaround time on everything is maybe 10% of what it was before" sound like something an actual engineer said, not marketing copy”
“If anything got in the way it's the marketing layer stacked on top of the description, phrases like "screen with confidence" and the four-part "GIS/Layout/Yield/AI" naming that make me re-read to confirm it's still one product and not a bundle of four.”
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.







