Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://consigns.co.uk/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?
14 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
12 could name a reason to pick you over a similar option.
Your page describes: digital waste tracking. They said:
6 couldn't name one; 9 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
14 of 15 recognized the kind of company behind the page, in a tone written for them. 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: "Listed on GOV.UK as a connected Digital Waste Tracking provider" is a status many suppliers share, so a buyer comparing options has nothing to pick on. State the specific scope no rival matches, such as one record covering England, Wales, Scotland and…
Why: A buyer cannot tell whether this is priced per site, per vehicle or per load, so the commercial question stays open. Show the model and an entry price next to that link.
2 of 15 raised this
“show me what happens when a driver's app data doesn't sync properly or a signature gets missed — because that's where I'd get burned, not in the happy-path demo”
Why: The countdown sits above a 1 October 2026 date, so the reader cannot tell what closes in ten days. Say what the ten days are for, or replace the countdown with the site-side date it actually tracks.
2 of 15 raised this
“the site-side stuff already applies now (October 2026), not our carrier/broker deadline of 2027, so the urgency on this page isn't quite our urgency yet”
These landed. Keep the wording when you edit around it.
The opening lines name the problem and the audience by role without requiring inference
“this was quick to read - the problem and audience are both spelled out fast. The strip up top - "permitted sites in England and Wales must report every load to DEFRA" from Oct 2026 - tells you the problem immediately, and the "Who it is for" section with Carriers/Receiving sites/Brokers named as separate tabs makes it obvious who's meant to be reading.”
Eliminating re-keying across paper notes, driver pads and spreadsheets is the value…
“If it genuinely does what it says - one entry at booking that carries through to the signed note and files itself with DEFRA - it would cut out the re-keying our office does at each handoff and stop the quarter-end scramble building the tonnage return from spreadsheets.”
The single-entry data flow and role-by-role walkthrough make the mechanism concrete
“I can tell what it does because the "one load, end to end" walkthrough actually names each step and who touches it, not just fluffy claims.”
Why: Readers assume their current supplier may handle the DEFRA integration already, and the page never answers that. Add a short line near the pricing link telling them how to check what their current system files and what switching involves.
Why: One named operator and a quote with no numbers give a comparison shopper nothing to weigh. Name the operator, their fleet or site count, and a figure such as admin hours saved per week and DEFRA filings rejected.
Why: "No signal? The app keeps going" only shows the happy path, and an operator wants to know what happens when sync fails or a device dies mid-round. State how long data is held on the device and what happens to a part-signed note.
2 of 15 raised this
“show me what happens when a driver's app data doesn't sync properly or a signature gets missed — because that's where I'd get burned, not in the happy-path demo”
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 wins attention and loses the sale — clarity is high, but every commercial question is unanswered.
Eight of 15 credited the opening for naming problem and audience, yet five demanded case studies and reference calls, two found no pricing, and two wanted reliability proof. Comprehension is not the bottleneck; evidence is.
A single named operator and a figure-free quote actively signal weakness rather than support the claims.
Five points flagged one named reference and a quote with no figures or competitor comparison, explicitly asking for hours saved and zero rejected DEFRA filings from comparable-size operators. Thin proof reads as absent proof.
The deadline is doing the persuasion the product should be doing, and the page mishandles it.
Two points said the October 2026 DEFRA deadline is what makes the page worth evaluating, while two others found the urgency argument breaks down on conflicting site-side and 2027 carrier deadlines. The one motivator is internally inconsistent.
The demonstrated mechanism only covers the happy path, so the walkthrough proves nothing about real operations.
Five points praised the step-by-step single-entry walkthrough, but three said happy-path demos are insufficient and asked for live offline sync, multi-nation handling and failure cases. The worked example stops exactly where risk begins.
The stated value — eliminating re-keying — is too small to justify a switch without a price.
Only three points restated the benefit, as removing duplication and spreadsheet errors, while two raised no pricing and asked whether their current supplier already handles the integration. An unquantified efficiency gain loses to inertia.
Terminology sloppiness undercuts credibility on the exact compliance detail the page sells against.
A point flagged that the consignment versus waste transfer note naming creates ambiguity, on a page whose core promise is correct DEFRA filings. Naming errors in a regulatory pitch invite doubt about the filing logic.
Reliability claims are unproven: respondents want offline sync, multi-nation handling…
2 of 15
“show me what happens when a driver's app data doesn't sync properly or a signature gets missed — because that's where I'd get burned, not in the happy-path demo”
No pricing is shown and switching cost is an open question
2 of 15
Eliminating re-keying across paper notes, driver pads and spreadsheets is the value…
3 of 15 · what worked
“If it genuinely does what it says - one entry at booking that carries through to the signed note and files itself with DEFRA - it would cut out the re-keying our office does at each handoff and stop the quarter-end scramble building the tonnage return from spreadsheets.”
“No more re-keying loads into DEFRA by hand, one signed record instead of paper chase.”
“office staff stop keying the same load into a paper note, a driver pad and then a spreadsheet, and the DEFRA receipt files itself the moment the receiving site signs”
The urgency argument breaks down because carrier and site deadlines differ
2 of 15
“the site-side stuff already applies now (October 2026), not our carrier/broker deadline of 2027, so the urgency on this page isn't quite our urgency yet”
“the wobble is in how it names the two note types almost interchangeably in places (consignment note vs waste transfer note) without always flagging which load type triggers which, so I had to hold two definitions in my head at once rather than one”
The opening lines name the problem and the audience by role without requiring inference
8 of 15 · what worked
“this was quick to read - the problem and audience are both spelled out fast. The strip up top - "permitted sites in England and Wales must report every load to DEFRA" from Oct 2026 - tells you the problem immediately, and the "Who it is for" section with Carriers/Receiving sites/Brokers named as separate tabs makes it obvious who's meant to be reading.”
“the strap "Digital waste tracking. One system. Filed with DEFRA" plus the countdown banner ("10 days to go... permitted sites in England and Wales must report every load to DEFRA") tells you the problem in the first two lines”
“the strap line "Book a load, collect the signatures and file the DEFRA receipt from one record" tells you the problem (duplicate paperwork, manual DEFRA filing) and the fix in one breath. The "Who it is for" section then spells the audience out explicitly with named tabs for Carriers, Receiving sites and Brokers”
“the top banner literally says "From 1 October 2026, permitted sites in England and Wales must report every load to DEFRA," which is exactly the deadline I'm staring down”
“"permitted sites in England and Wales must report every load to DEFRA" from 1 October 2026, plus "Check your site" - tells you the problem (upcoming mandatory digital reporting, currently done manually) in the first two lines. The "Who it is for" section then explicitly splits into Carriers, Receiving sites, and Brokers, each with its own "How the day runs"”
The single-entry data flow and role-by-role walkthrough make the mechanism concrete
2 of 15 · what worked
“I can tell what it does because the "one load, end to end" walkthrough actually names each step and who touches it, not just fluffy claims.”
“the concrete example carried through - "Producer Northgate Motors, EWC code 13 02 05, Quantity 200 kg... Entered by the office at 07:40. Never entered again" - is specific enough that I believe the mechanism”
“enter once, use everywhere, file automatically — which is exactly the kind of mechanism I'd need to believe the "no double entry" claim”
Customer evidence is too thin to trust: one named operator and a generic quote with no…
5 of 15
“Only one named reference though - Midland Oil Group - so I'd want a few more operators our size on record before I trust "listed on GOV.UK" and "files itself" claims fully.”
“the client quote is generic ("turns a manual paper process into something that mostly happens automatically") - no numbers, no named comparison to a competitor, so it doesn't differentiate this from another tool making the same claim”
“I'd want a named case study from a receiving site my size and headcount, not just Midland Oil Group in general terms - something that says 'this is what a 51-200 person waste site's gate process looked like before and after.'”
The mandatory compliance deadline itself is what makes the page worth evaluating
2 of 15 · what worked
“the top banner literally says "From 1 October 2026, permitted sites in England and Wales must report every load to DEFRA," which is exactly the deadline I'm staring down”
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.







