Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://www.ignite.no/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?
14 could name a reason to pick you over a similar option.
Your page describes: procurement software. They said:
11 couldn't name one; 4 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
One respondent noted the page omits founding date and headcount, information they treated as important for assessing vendor longevity. 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: Readers said a competitor that showed how savings are measured, or offered comparable named cases, would win on this point. One or two lines next to the savings figures — how savings are identified, what baseline they are measured from, whether the figure is identified versus captured, and whether implementation cost is netted out — turns "EUR 7.3M total savings captured" from a marketing number into an auditable one. "Savings captured" and "savings potential" also need to be visibly…
5 of 15 raised this
“everything else is aggregate and unsourced — "+€500B spend processed," "+5-10% savings potential" — no company names attached”
Why: Readers could restate the mechanism accurately — cleaning messy procurement data across fragmented ERPs, classifying spend, extracting contract terms, flagging savings and risk — but they got it from the mid-page sections and the interface labels, not the hero. The hero's "Reimagine procurement with AI. Better savings. Lower risk. Stronger supplier performance." is generic marketing phrasing that could sit on any competitor's site. Lead with the work: classify spend, deduplicate suppliers and…
3 of 15 raised this
“what slowed me down was the interface labels layered on top, things like "Ignite AI Normalizing, Cleaning, Enriching, Categorizing, Connecting..." strung together with no explanation of what each step actually does or how long it takes on real data”
These landed. Keep the wording when you edit around it.
Customer logos and role titles let respondents identify the target buyer without being…
“the customer names (Hurtigruten, Stena Metall, Veidekke, Aibel) and quotes from people with titles like "Head of Procurement" and "Strategic Purchasing Manager" made the target audience clear”
Named customer cases with hard numbers are the page's most believed proof
“the Hurtigruten quote about classifying "a couple million euros of spend and a couple thousand transactions" in minutes rather than a full day is the kind of concrete, checkable claim that would matter to my team”
The Nordic customer roster reads as specialist focus rather than generic enterprise vendor
“The tone does feel aimed at someone like me: it doesn't oversell with generic "digital transformation" fluff, it names concrete pain points — off-contract spend, duplicate suppliers, unclassified spend”
Why: The dashboard line "Total savings potential EUR 9-14.3M / Across all suppliers" floats with no baseline, no spend volume it is calculated against, and no customer behind it. Readers rejected it outright and said it made them trust the rest of the page less, citing bad experiences with vendor savings claims. Either tie the range to a named account with its annual spend ("identified EUR 9-14.3M in savings potential across Veidekke's EUR Xm annual spend") or drop the aggregate and let the…
5 of 15 raised this
“everything else is aggregate and unsourced — "+€500B spend processed," "+5-10% savings potential" — no company names attached”
Why: "Reimagine procurement with AI" and "turning what you already have into decisions you can act on" are claims any procurement vendor could make unchanged. The specific reason to choose Ignite — it runs across fragmented ERPs and does not require clean data first — is buried mid-page in "Ignite is built for messy inputs, so you don't need clean data to get started." Move that promise into the hero and name the situation: procurement teams running several ERPs across sites. Readers made a pilot…
5 of 15 raised this
“everything else is aggregate and unsourced — "+€500B spend processed," "+5-10% savings potential" — no company names attached”
No specific edits needed here — this layer held up.
No specific edits needed here — this layer held up.
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 page's headline economic promise is its weakest asset — the savings numbers subtract credibility rather than add it.
Five respondents rejected the platform-wide savings figures including the €9-14.3M claim for lack of baseline, methodology, implementation cost, or attribution; one said the unsupported figures triggered skepticism from past vendor experience, and two said a competitor showing methodology or named comparable cases would win the comparison outright. A number that provokes vendor distrust performs worse than no number.
All persuasive weight rests on two named customer stories, so the page has a single point of failure.
Ten respondents named Veidekke and Hurtigruten as the most credible evidence, and several said these beat the aggregate metrics — the same aggregate metrics five respondents actively rejected. Strip the two anecdotes and nothing quantitative survives scrutiny.
Clarity about what the product does is not converting into willingness to act, because the page never proves the hard case.
Five respondents restated the mechanism accurately, yet three made any pilot or budget move conditional on seeing 90%+ classification accuracy on their own data or confirmation that messy multi-ERP data is handled automatically — and one said positioning for multi-ERP manufacturers was missing outright. Comprehension without proof leaves the page short of the next step.
The page loses the buying committee by writing only to procurement insiders.
Three respondents said the messaging addressed operators and analysts simultaneously and diluted impact, and one noted the copy assumes procurement domain knowledge rather than addressing IT or finance. Multi-ERP data consolidation is bought with IT and finance in the room; neither is spoken to.
The customer roster does double duty as a positioning signal and a scale ceiling the page never controls.
Six respondents read the Nordic, Scandinavian-heavy roster as specialist focus, but one read the identical roster as evidence of mid-market rather than enterprise scale. The page hands over interpretation of its own market position to the reader.
Interface screenshots are shown as proof and read as filler.
Three respondents said generic marketing phrasing obscured concrete product understanding and that interface labels appeared without explanation of mechanism or processing time. Processing time is exactly the variable three other respondents gate a pilot on.
The aggregate savings figures are read as unsourced and actively damage credibility
5 of 15
“everything else is aggregate and unsourced — "+€500B spend processed," "+5-10% savings potential" — no company names attached”
“the "EUR 9-14.3M savings potential" figure with no methodology, and the vague "+5-10% savings potential on addressable spend" stat, would rule it out on their own if the competitor showed their working — unsupported ranges like that just make me want to see the calculation, not trust the number”
“"9-14.3M total savings potential" and "+5-10% savings potential on addressable spend" are exactly the kind of unanchored numbers that make me nervous — no baseline, no methodology, and I've been burned before by a vendor who quoted savings figures that never materialized once implementation costs and change management were factored in.”
“the €500B "spend processed" and "5-10% savings potential" claims are unsourced marketing fluff until someone shows me how they're calculated on data that looks like mine”
“the savings figures (EUR 9-14.3M "total savings potential," +€500B "spend processed") are shown as platform-wide mockup numbers with no attribution”
Parts of the page fall back on generic marketing language and a split audience
3 of 15
“what slowed me down was the interface labels layered on top, things like "Ignite AI Normalizing, Cleaning, Enriching, Categorizing, Connecting..." strung together with no explanation of what each step actually does or how long it takes on real data”
“If anything got in the way, it was generic phrases like "turning what you already have into decisions you can act on" — that's marketing filler that could describe almost any analytics tool, and I had to skip past it to the concrete bits (spend, contracts, suppliers, ERPs) to actually understand what it does.”
Respondents could state the product mechanism back in their own words
4 of 15 · what worked
“pulls together spend, contracts, and supplier data from your ERPs and spreadsheets, cleans and categorizes it, then surfaces savings opportunities and tracks initiatives”
“It's an AI-driven procurement intelligence platform — it pulls spend, contract, and supplier data out of ERPs and spreadsheets, cleans and categorizes it, and surfaces savings opportunities and risk flags in one dashboard.”
“pulls spend, contract, and supplier data out of your ERPs, accounting systems, and spreadsheets, cleans and categorizes it automatically, then surfaces savings opportunities and tracks initiatives against them”
“The mechanism is at least specific enough to name — dedup, spend classification, contract extraction — which is more concrete than most of these pages manage.”
Customer logos and role titles let respondents identify the target buyer without being…
6 of 15 · what worked
“the customer names (Hurtigruten, Stena Metall, Veidekke, Aibel) and quotes from people with titles like "Head of Procurement" and "Strategic Purchasing Manager" made the target audience clear”
“logos like SAP, Dynamics, the customer quotes from Heads of Procurement and Strategic Purchasing Managers at Hurtigruten, Stena, Veidekke, etc. make clear this is for procurement teams at mid-to-large companies with messy multi-system data”
“logos like SAP, Dynamics, Excel, and testimonials from "Head of Procurement," "Strategic Purchasing Manager," "Group Procurement" at industrial/shipping firms (Hurtigruten, Stena, Veidekke, Aibel) make clear this is for procurement leaders at larger, multi-entity companies drowning in spreadsheets — basically me. No one had to spell out "this is for you"”
“the customer logos and quotes (Hurtigruten, Stena, Veidekke) tell me it's mid-to-large procurement teams with multiple ERPs and decentralized purchasing, same profile as us. Didn't have to hunt — the hero line "turning what you already have into decisions you can act on" plus "Built for teams with multiple ERPs, decentralized purchasing, and large supplier bases" spells it out directly.”
“The logos row (Excel, SAP, Dynamics, Visma) signaled it's for teams like mine still stuck stitching together ERPs and spreadsheets”
Proof of handling messy multi-ERP data is the gating condition for a pilot
3 of 15
“I'd want a line naming my exact situation — something like "for procurement teams running SAP or Dynamics alongside Excel across multiple sites" — plus a case study from a manufacturer specifically”
“if it hits 90%+ correct categorization on our actual taxonomy with minimal cleanup, that's the threshold that justifies swapping tools”
Named customer cases with hard numbers are the page's most believed proof
6 of 15 · what worked
“the Hurtigruten quote about classifying "a couple million euros of spend and a couple thousand transactions" in minutes rather than a full day is the kind of concrete, checkable claim that would matter to my team”
“The thing that would actually move it up the shortlist is the named, specific customer proof — the Hurtigruten quote about classifying "a couple million euros of spend and a couple thousand transactions" in minutes, and the Hofseth numbers”
“Veidekke's numbers (90% spend classified, 95% visibility) are the kind of proof that would matter if I could actually talk to them about how messy their starting point was”
“that Hurtigruten quote about classifying "a couple million euros of spend... in minutes, not hours" is the kind of concrete detail that makes me believe it, because it's specific and testable rather than a generic efficiency claim.”
“The thing that would actually tip me toward Ignite over a competitor is the named-customer specificity — Nordic industrial/shipping companies like Hurtigruten, Stena Metall, Veidekke, Aibel giving quotes with hard numbers (97% spend classified, 95% contracts centralized, 10% savings realized at Hofseth)”
“The thing that would actually pull me toward this one over a competitor is the specific customer quote from Hurtigruten's Ivar Ording Andersen — "I was able to do what would normally take a full business day in less than an hour... I've classified a couple million euros of spend and a couple thousand transactions, and it took minutes, not hours." That's concrete, named, dated, and from a company in our own sector”
“that Hurtigruten quote about doing "a full business day in less than an hour" on classification is the kind of line that would actually change our workload”
Basic company facts respondents wanted for vendor longevity are absent
1 of 15
“What I can't tell from the page is how big the vendor itself is or how long they've been doing this — no headcount, no founding date, no "since 20XX" — and that matters to me because I want to know if they'll still be around and well-resourced in three years”
The Nordic customer roster reads as specialist focus rather than generic enterprise vendor
5 of 15 · what worked
“The tone does feel aimed at someone like me: it doesn't oversell with generic "digital transformation" fluff, it names concrete pain points — off-contract spend, duplicate suppliers, unclassified spend”
“the customer list (Hurtigruten, Stena, Veidekke, Aibel, AF Gruppen) is heavily Norwegian/Swedish shipping, construction, and industrial, so they're clearly selling into Scandinavian mid-to-large enterprises”
“it's written for someone like me: it assumes I already know what "off-contract spend" and "spend classification" mean, doesn't waste time explaining procurement basics, and leads with named customers in my exact sector”
“"Head of Procurement," "Strategic Purchasing Manager," "Group Procurement" titles in the quotes, references to ERPs and messy spreadsheets, and lines like "without relying on spreadsheets, analysts, or workarounds" — that's my exact daily complaint”
“Aibel, Hurtigruten, Stena, Veidekke, Havila, Norbit, all Nordic industrials and shipping firms, not global enterprise logos.”
“I picture a mid-sized, venture-backed B2B SaaS vendor, maybe 10-15 years old, probably Nordic-headquartered given the customer roster — Hurtigruten, Stena, Veidekke, Aibel, Havila, Nordlaks, AF Gruppen are all Scandinavian industrials and shipping/construction names, not global enterprise logos. That tells me they've grown up selling into Nordic procurement teams at asset-heavy, decentralized companies”
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.







