Clarity
Do they understand what you do?
13 could name what kind of product this is, unprompted.
https://www.refold.ai/15 AI-simulated buyers
Your message needs work: they know what it is, who it's for, and why it's worth their time, but not why to pick you.
Do they understand what you do?
13 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
11 could quickly tell what problem it solves and who it is for.
Do they actually want it?
12 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
7 could name a reason to pick you over a similar option.
Your page describes: AI integration delivery layer. They said:
2 named the wrong one; 13 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Six respondents said the mid-market logo wall and one-line CTO quotes are not case studies and show no SAP or Oracle-scale references. They also skimmed past hype like 'integrations that (literally) build themselves'. 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: Buyers could not tell what Refold does that their current iPaaS does not, beyond deployment. Show side by side who maps fields, who writes connector code, and what happens when a mapping breaks.
1 of 15 raised this
“'up to 90% faster' and '40% of engineering time recovered' have no baseline”
Why: Readers had to infer the audience from tabs and testimonials. Name SaaS product, PS and engineering leaders stuck hand-building SAP, Oracle and Salesforce integrations for each enterprise customer.
3 of 15 raised this
“the 'Who Refold Is For' section names Product, Professional Services and Engineering teams, so the audience is stated rather than fully inferred”
Why: 'AI integration delivery layer' did not tell readers what the product is, so they translated it themselves. Say it builds and maintains customer-facing integrations to enterprise systems.
4 of 15 raised this
“'AI integration delivery layer' and 'Integration Graph' are coined terms that tell me nothing about what the product actually is”
These landed. Keep the wording when you edit around it.
The pain of hand-built SAP, Oracle and Salesforce integrations came through for one…
“the hero line 'AI integration delivery layer that builds, runs, and maintains integrations up to 90% faster' plus the 'Who Refold Is For' tabs (Product, Professional Services, Engineering) tell me it's for ISVs stuck hand-building customer integrations to SAP, Oracle and Salesforce”
Why: 'Every integration gets smarter than the last' could describe any tool, so buyers saw no edge. Give a concrete case, such as a second SAP customer starting with mappings already filled in from the first.
1 of 15 raised this
“'up to 90% faster' and '40% of engineering time recovered' have no baseline”
Why: Buyers wanted to see the mapping work on real data before believing the speed claims. Show confidence scores on custom fields and what a reviewer approves.
4 of 15 raised this
“"up to 90% faster" has no source, so I wouldn't take a meeting on this page alone”
Why: Short quotes from mid-market logos read as early-stage, with no proof at SAP or Oracle scale. Name one customer, the systems connected, and cycle time or engineering hours before and after.
3 of 15 raised this
“'integrations that (literally) build themselves' and 'Never build from scratch again' is hype I'd skim past”
Why: Buyers did not believe the figures because nothing says whose results they are or what they were measured against. Put the customer name, the old timeline and the new one directly under each number.
3 of 15 raised this
“'integrations that (literally) build themselves' and 'Never build from scratch again' is hype I'd skim past”
Why: Enterprise buyers skimmed past the hype and read it as startup tone. Say plainly that agents map fields, generate code and assemble the workflow for your review.
3 of 15 raised this
“'integrations that (literally) build themselves' and 'Never build from scratch again' is hype I'd skim past”
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 makes buyers do the positioning work themselves, so the coined vocabulary is pure friction with no payoff.
Four respondents called the headline terms vague jargon, while three more had to restate the product as embedded iPaaS to describe it. The familiar category was the explanation the page should have led with.
Once translated into familiar terms, Refold lands in a crowded category with no stated reason to switch.
Respondents defaulted to 'embedded iPaaS' (3 of 15), and the page then left Refold level with existing setups. Nothing plainly shows where the AI layer differs.
The headline numbers backfire, because the page offers no proof that would make them credible to an enterprise buyer.
Four respondents rejected the 90% and 40% claims as unsourced. Three read the logos and one-line quotes as early-stage, with no SAP or Oracle-scale reference to back the figures.
The page withholds the exact asset that converts visitors into meetings.
Three respondents said engagement depends on a named customer with before-and-after hours or cycle times. Meanwhile the page offers only unsourced percentages and logo walls.
The page never tells the engineering buyer this is for them, so the strongest pain point reaches almost no one.
Three respondents had to infer the audience, and one said no problem is framed. Only one of 15 picked up the hand-built SAP/Oracle/Salesforce pain.
The hype tone actively undermines trust with technical evaluators.
Phrases like 'integrations that (literally) build themselves' were skimmed past. Separately, 'up to 90%' was read as startup confidence rather than proof, signalling marketing over engineering substance.
Beyond deployment, the page does not separate Refold from existing iPaaS
1 of 15
“'up to 90% faster' and '40% of engineering time recovered' have no baseline”
“I'd also want a plain comparison against what I use today, because right now I can't tell where the AI layer ends and a standard iPaaS begins.”
The audience and problem are never stated plainly
3 of 15
“the 'Who Refold Is For' section names Product, Professional Services and Engineering teams, so the audience is stated rather than fully inferred”
“The 40% engineering time recovered is closest to my backlog pain, but that's a stat, not a stated problem.”
“I inferred the reader from testimonials and tab labels rather than being told it in one plain sentence up top”
“The tone is pitched at product and PS leaders ('finally execute on roadmap, hit revenue goals sooner') more than at an engineering VP like me, who wants mechanism”
“I pieced the intended reader together from the testimonials ('productize integrations,' 'stop treating integrations like professional services') rather than finding one plain sentence”
The pain of hand-built SAP, Oracle and Salesforce integrations came through for one…
1 of 15 · what worked
“the hero line 'AI integration delivery layer that builds, runs, and maintains integrations up to 90% faster' plus the 'Who Refold Is For' tabs (Product, Professional Services, Engineering) tell me it's for ISVs stuck hand-building customer integrations to SAP, Oracle and Salesforce”
The '90% faster' and '40% engineering time' claims are not believed
4 of 15
“"up to 90% faster" has no source, so I wouldn't take a meeting on this page alone”
“What keeps it from feeling fully enterprise-grade is the 'up to 90%' with no baseline and no SAP-specific case study, which reads like startup confidence rather than a vendor with a decade of benchmarks.”
A meeting depends on a named customer with before-and-after numbers
3 of 15
“A first screen that says in one sentence who it's for, SaaS vendors shipping customer-facing integrations into SAP/Oracle/Salesforce, and what it replaces, plus one named customer with before-and-after numbers”
“I'd take a meeting only to demand a named customer's before-and-after cycle times and a live demo of the field mapping on a messy custom schema; without that, it's a no.”
“If they can't show a reference customer at my scale on SAP, I'd close it there.”
“Show me a named EU customer in production with the before-and-after engineering hours and I'd reconsider.”
The headline and coined terms do not say what the product is
4 of 15
“'AI integration delivery layer' and 'Integration Graph' are coined terms that tell me nothing about what the product actually is”
“'AI integration delivery layer' is a made-up label that told me nothing on first read”
“I'd need to see how the mapping confidence scoring works and what the 90% faster claim is measured against before I believed any of it”
“The phrase 'AI integration delivery layer' got in the way most, because 'delivery layer' isn't a category I recognize”
“'Context layer behind the most accurate field mapping agents' and 'Integration Graph' piled on more coined terms before the page said plainly what it ships.”
“The headline 'AI integration delivery layer' told me nothing on its own”
Respondents had to translate the page into familiar categories to describe the product
3 of 15
“In practice it's an embedded iPaaS with an AI layer on top that auto-maps fields, generates the code and workflows, and claims to self-heal broken integrations.”
“they're an AI-driven integration platform aimed at software vendors: you feed in call recordings and spec sheets, agents do the field mapping and generate the connector code and workflow for SAP, Oracle, Salesforce and so on”
“it's an AI-driven integration builder for SaaS vendors that auto-maps fields and generates connectors to things like SAP, Oracle and Salesforce”
Logos, quotes and hype phrasing read as an early-stage company without enterprise proof
3 of 15
“'integrations that (literally) build themselves' and 'Never build from scratch again' is hype I'd skim past”
“the logos and one-line CTO quotes aren't a case study”
“The logo wall (Coupa, HighRadius, Zycus, Incorta) plus one-line CTO quotes reads like a young company with a few design partners rather than a deep reference base.”
“these logos are mostly mid-market SaaS and I see nothing on SAP at scale”
“The logo wall (Incorta, Kantata, Coupa, Rillet, Scrut) is all mid-market ISVs and fintech, not a single Oracle-scale name, and the 'Introducing the Integration Graph' banner reads like a young team still shaping its story.”
“it leans on startup AI phrasing ('literally build themselves,' 'stop rebuilding, start compounding') and a lot of CTO quotes, which tells me they're strongest with smaller buyers”
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.







