Buying-committee simulation · landing page
EXP AN-90670518 · 2026-08-12 · SeedCommittee - Technical Saas
Page under test · whyuser.com

The committee understands the core buying-committee simulation value and clicks forward, but missing proof and verifiable integration docs prevent confident internal justification.

Driver · Goal Approached 90% converted of 50 runs
50 agents — seeded runs Details
Committee
5 compiled buyers · 10 seeds each
Behaviour
3 declared profiles — Distracted, Skeptic, Ideal
Recorded
45 clicked · 0 submitted · 5 abandoned
Determinism
same fingerprints, same buyers — replayable, not re-generated
Where each finding landed 4 working · 5 broken
Nav
Hero
Logos
Body
CTA
Footer

Blocks are generic — only the labelled zones carry meaning, because they are the zones findings were tagged with. Cyan is working, magenta broken.

Read as one buyer

Working W1 · Body zone · medium reacted CH TD EB EU GR

Core value prop lands: deterministic, evidence-backed verdicts

Multiple roles latched onto “same page in, same verdict out” plus evidence/lineage framing as making outputs defensible and repeatable under launch pressure.

Roles that reacted: Champion, Economic Buyer, End User, Security Guardian, Technical Decision Maker

“the same page in produces the same verdict out.”

Champion · Staff Marketing Operations Manager — captured during the pass, not written afterwards.

If outputs aren’t deterministic and can’t show lineage with HIT/MISS across versions, I can’t defend this internally.

objection · fingerprint 6f744b870006001f · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · No ranked fix is tied to this finding.

Working W2 · Nav zone · medium reacted CH TD EB EU GR

Clear routing exists via nav/hero for evaluation paths (ROI, how it works, trust)

Committee members used nav/hero CTAs and router links (Request Access, ROI, How it works, What makes it trustworthy) to self-direct toward proof and next steps.

Roles that reacted: Champion, Economic Buyer, Technical Decision Maker

“Request Access”

Champion · Staff Marketing Operations Manager — captured during the pass, not written afterwards.

A guided demo that runs an ad-to-landing-page or email variant simulation end-to-end in under 30 minutes.

evidence need · fingerprint 6f744b870006001f · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · No ranked fix is tied to this finding.

Working W3 · Footer zone · medium reacted CH TD EB EU GR

Procurement trust path is discoverable via footer links (Security, DPA)

Senior evaluators noted Security and DPA links in the footer, reducing fear of hidden procurement traps and providing a verification route.

Roles that reacted: Economic Buyer, Security Guardian

“Footer contains 'Security' and 'DPA' links, which gives me a path to procurement controls.”

Economic Buyer · VP of Demand Gen — captured during the pass, not written afterwards.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · No ranked fix is tied to this finding.

Working W4 · Hero zone · low reacted CH TD EB EU GR

Product category clarity: buying-committee simulation for pre-launch checks

More than one role reported quickly understanding what the product is and when to use it (pre-launch buying committee simulation), anchoring the JTBD.

Roles that reacted: Security Guardian, Technical Decision Maker

“Headline / hero explains 'committee simulation'—I get the product claim.”

Security Guardian · Director of Security — captured during the pass, not written afterwards.

0 of 50 runs

low confidence at 20% · sample 50 · severity low · No ranked fix is tied to this finding.

Broken B1 · Hero zone · medium reacted CH TD EB EU GR

Proof is claims-first: weak immediate customer/logo/artifact validation

Across roles, “trusted by/accuracy/evidence” statements lacked fast, inspectable proof (logos, linked cases, example outputs, downloadable artifacts), creating caution even when interest remained.

Roles that reacted: Champion, Economic Buyer, End User, Security Guardian, Technical Decision Maker

“Trusted by demand gen teams at + NDA design partners”

Champion · Staff Marketing Operations Manager — captured during the pass, not written afterwards.

Buyers compare Wynter alternatives on value for money, feature depth, ideal use cases, and pricing transparency.

evidence need · fingerprint 6f744b870006001f · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · Repaired by fix 3

Broken B2 · Nav zone · medium reacted CH TD EB EU GR

Navigation is hard to scan (clutter/density slows wayfinding)

Multiple roles described the top nav as cluttered/concatenated and paragraph-like, increasing cognitive load and slowing visitors trying to find proof, trust, or technical routes.

Roles that reacted: Champion, Economic Buyer, End User, Security Guardian

“Multiple 'Request Access' CTAs and many competing nav links create mild choice paralysis.”

Champion · Staff Marketing Operations Manager — captured during the pass, not written afterwards.

Replace subjective internal debates with evidence-backed outputs that are easy to share across Demand Gen, PMM, and RevOps.

goal · fingerprint 6f744b870006001f · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · Repaired by fix 2 and 4 and 5

Broken B3 · Nav zone · high reacted CH TD EB EU GR

Technical validation path unclear: no explicit Docs/Architecture entry point

Despite API/headless signals, technical evaluators couldn’t quickly locate a clearly labeled Docs/Developers/Architecture route to assess integration scope and data flow.

Roles that reacted: Security Guardian, Technical Decision Maker

“I can't find a 'Developers' or 'Docs' link in the header nav to validate integrations or API docs.”

Technical Decision Maker · Head of Revenue Operations — captured during the pass, not written afterwards.

API documentation and an end-to-end integration walkthrough showing how GTM sources are ingested and how calibration quality is measured.

evidence need · fingerprint f4a6aff64619ac23 · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity high · Repaired by fix 2

Broken B4 · CTA zone · critical reacted CH TD EB EU GR

Sales-led gating dominates: “Request Access” repetition reduces self-serve validation

Evaluators saw repeated Request Access CTAs without a lightweight preview path, and for some this blocks quick hands-on validation and creates CTA noise/choice friction.

Roles that reacted: Champion, End User

“Sales-led gating blocks quick hands-on validation; 'Request Access' is the primary CTA.”

End User · Senior Demand Generation Manager — captured during the pass, not written afterwards.

0 of 50 runs

low confidence at 20% · sample 50 · severity critical · Repaired by fix 1

Broken B5 · Nav zone · medium reacted CH TD EB EU GR

Security and pricing are discoverable but not surfaced early enough

Security/DPA links exist (noted by EB/GR), but other roles still experienced above-fold trust/pricing uncertainty, indicating signposting/visibility gaps rather than true absence. EB located this path on-page — visibility gap, not absence.

Roles that reacted: Economic Buyer, Security Guardian

“Hero states what the product does... but says nothing about SOC 2, logs, or DPA up front.”

Security Guardian · Director of Security — captured during the pass, not written afterwards.

Security trust package covering encryption (TLS 1.2+; AES-256 at rest), tenant isolation, logging (CloudTrail/S3 access logging), vulnerability management, and incident response policy

evidence need · fingerprint ee9d5ad3faa9e3e8 · compiled 2026-08-12 — this existed before the page was opened.

0 of 50 runs

low confidence at 20% · sample 50 · severity medium · Repaired by fix 5

Pick a mark on the sheet — or a row below — to open that finding’s record: why it matters, the evidence from the page, and the compiled trait behind it.
Everything the run found
CH · EB · EU · GR · TD · Body
CH · EB · TD · Nav
EB · GR · Footer
GR · TD · Hero
CH · EB · EU · GR · TD · Hero
CH · EB · EU · GR · Nav
GR · TD · Nav
CH · EU · CTA
EB · GR · Nav

What to fix, in the order the committee blocks on

Ranked against the broken handoffs, not page order. Tick fixes and the graph on the right shows which handoffs reconnect.

1

Add a self-serve “Try a sample” path next to “Request Access” (interactive demo or prefilled sandbox) and reduce repeated Request Access CTAs to one primary + one secondary.

ui change CTA closes B4 · unblocks CH · EU
Why this rank

Addresses the critical gating/CTA noise by giving evaluators immediate hands-on validation without waiting for sales, while simplifying choices and lowering friction caused by repeated Request Access prompts.

Expected effect

Increases self-serve validation and reduces CTA friction for faster intent-to-proof.

Evidence behind it
Placement
above_fold
Component Type
dual_cta
Primary Cta
Request Access
Secondary Cta
Try sample
2

Add a top-nav “Developers” entry with direct links to Docs, API Reference, and Architecture/Data Flow, and mirror it as a persistent in-page anchor section.

signposting Nav closes B3 · B2 · unblocks CH · EB · EU · GR · TD
Why this rank

Directly fixes the missing technical validation route by making a clearly labeled Docs/Architecture path instantly discoverable; also reduces nav scanning burden by grouping technical items into one predictable entry point.

Expected effect

Unblocks GR/TD evaluation of integration scope and data flow in seconds.

Evidence behind it
Component Type
nav_item_with_dropdown
Nav Label
Developers
Links
['Docs', 'API Reference', 'Architecture']
3

Add an above-fold proof strip: 6–10 customer logos + 1 quantified metric, each linking to a short case study or downloadable example output.

content addition Hero closes B1 · unblocks CH · EB · EU · GR · TD
Why this rank

Resolves claims-first trust friction by adding fast, inspectable validation artifacts (logos, linked cases, example outputs) right where users decide whether to keep reading.

Expected effect

Raises trust and reduces skepticism across roles early in the scan.

Evidence behind it
Placement
above_fold
Component Type
logo_bar_with_links
4

Simplify the top navigation into 4–6 scannable buckets (Product, Solutions, Developers, Resources, Company) and move low-priority links into a “More” dropdown.

ui change Nav closes B2 · unblocks CH · EB · EU · GR
Why this rank

Directly addresses nav clutter/density that slows wayfinding; pairing consolidation with clear buckets helps users quickly locate proof, trust, and technical routes without paragraph-like scanning.

Expected effect

Faster wayfinding to proof/security/technical info; lower cognitive load.

Evidence behind it
Max Top Level Items
6
Component Type
grouped_nav_with_overflow
5

Surface “Security” and “Pricing” as first-class nav items and add an above-fold micro-row linking to Security (SOC2/DPA) and Pricing/Plans.

signposting Nav closes B5 · B2 · unblocks CH · EB · EU · GR
Why this rank

Fixes the visibility gap by making security and pricing discoverable immediately instead of buried; reduces early trust/pricing uncertainty while keeping existing content intact.

Expected effect

Improves trust and commercial clarity early for EB/GR and reduces drop-off.

Evidence behind it
Placement
nav_and_above_fold
Component Type
nav_links_plus_micro_row

How the committee moved — and where it stopped

2 of 7 handoffs snap. Everybody looked — 45 of 50 runs clicked, 5 abandoned — so the loss is not attention. It is that one buyer cannot hand the case to the next.

Add a layer
Behavioural profiles × seeds

3 declared profiles × 10 seeds per role. Filled marks are runs that clicked through.

10 seeds · CH 10 of 10 clicked through
10 seeds · TD 7 of 10 clicked through
10 seeds · EB 10 of 10 clicked through
10 seeds · EU 8 of 10 clicked through
10 seeds · GR 10 of 10 clicked through
clicked through abandoned colour marks the outcome, never the profile · solid bar = that role’s baseline profile · dashed = declared, not itemised
handoff holds handoff snaps click a role or an edge to open its record
Deal breaker
Deal Breaker: End User wants to proceed but cannot justify it to Technical Decision Maker without Docs evidence.

What the committee believed that the page did not answer

Each row pairs an assumption the page is written on against what the committee actually did with it. Open one to see both.

The page assumes
Repeating “Request Access” accelerates pipeline by pushing committees into a sales conversation early, before they overthink.
What the run recorded
The committee showed high click-through behavior but no submits; evaluators saw repeated Request Access CTAs without a lightweight preview path. For CH/EU, this created CTA noise and blocked quick hands-on validation.
Cost
You’re converting curiosity into deferral: people can’t confirm the product is real/fit before committing to contact, so they keep browsing and exit rather than taking the “ask.”
What closes it
Split the CTA into (1) “See an example run” (ungated interactive demo/sample report) and (2) “Request access.” Reduce repetition and place the preview CTA adjacent to proof so evaluators can validate value before they’re asked to talk.

High severity · 0 of 50 runs · reacted: CH · EU

The page assumes
API/headless signals and general product pages are enough for technical evaluators to infer feasibility; detailed docs can wait until after contact.
What the run recorded
The audit explicitly flags the technical validation path as unclear: TD/GR couldn’t quickly find a clearly labeled Docs/Developers/Architecture entry to assess integration scope and data flow, even while the committee overall kept clicking.
Cost
Even when CH/EB are sold, EU can’t justify the decision to TD without verifiable docs evidence—creating a cross-functional veto point that prevents submission and turns “Driver” interest into no-decision.
What closes it
Add a persistent top-nav “Docs” with subpages: Architecture, Integrations, Data flow, Security, and Output schema. Include one concrete integration walkthrough and a redacted example payload so TD can validate effort/risk in minutes.

High severity · 0 of 50 runs · reacted: TD · GR · EU

The page assumes
More options in the top nav helps each role find their path; the committee will explore and assemble the story themselves.
What the run recorded
Multiple roles described the nav as cluttered/concatenated and paragraph-like, increasing cognitive load and slowing wayfinding—especially for people trying to find proof, trust, or technical routes.
Cost
High-intent visitors spend their limited attention budget decoding the interface instead of verifying claims; that makes your strongest differentiators (proof, docs, security) effectively “not there.”
What closes it
Re-architect nav around committee jobs-to-be-done: Proof (Customers, Case studies, Example outputs), Product (How it works), Technical (Docs/Architecture/Integrations), Trust (Security/DPA), Pricing. Make these scannable labels, not prose.

High severity · 0 of 50 runs · reacted: CH · EB · EU · GR · TD

The page assumes
If the committee understands the concept (buying-committee simulation + stress test), they’ll trust the outputs enough to move to Request Access and let Sales handle proof.
What the run recorded
Momentum was high (CH 10/0, EB 10/0, GR 10/0, EU 8/2, TD 7/3), yet zero submits. The dominant friction was missing proof; claims like “trusted/accurate/evidence” weren’t backed by fast logos, linked cases, or example outputs people can forward internally.
Cost
High-intent evaluators can’t make the internal case, so interest stalls at “clicking forward” and leaks to tools that provide immediate, shareable validation assets (case studies, sample reports, technical docs).
What closes it
Make proof the primary above-fold payload: recognizable logos + 2–3 linked case studies + a downloadable “sample committee output” (lineage, HIT/MISS grading, example recommendations) that EU/EB can forward to TD/GR without a call.

Medium severity · 0 of 50 runs · reacted: CH · EB · EU · GR · TD

The page assumes
As long as Security/DPA and pricing details are present somewhere, serious evaluators (EB/GR) will find them during deeper evaluation.
What the run recorded
Security and pricing were discoverable (EB/GR noted links), yet other roles still experienced above-fold trust/pricing uncertainty—pointing to signposting/visibility gaps rather than missing content.
Cost
Committees can’t quickly de-risk vendor selection, so they hesitate to champion internally; this increases “no submit” outcomes even when interest is positive.
What closes it
Surface trust and commercial anchors earlier: a compact “Security & data handling” module near hero (DPA, retention, certifications) plus a pricing model explainer (how usage/consumption maps to value) with a link to full details.

Medium severity · 0 of 50 runs · reacted: EB · GR · EU · CH

What each buyer actually thought, pass by pass

Each entry is one simulated buyer reading the page once. Nothing here is a summary — it is the pass itself, in the order it happened, with the line they were looking at when they thought it.

Scan first sweep — what is this page even about Hunt evidence looking for the proof this role needs Hunt goal looking for the thing they came to do Safety scan one last check before leaving Convert took the action the page asked for Bounce left without it
CH Champion Staff Marketing Operations Manager 10 passes
Pass 1 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav is dense but full of promise — lots of topic links, and 'Request Access' is prominent.

    “Request Access Product Video RUN-2847 Committee flow · who carries the deal, who quietly stops it 300 agents · n=60/role · this run 52 of 60 champion cannot carry it”

  2. hero Scan First Impression

    Headline says it's a 'buying committee simulation' — clear claim, but not the technical proof I need.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    I look for proof and reliability links: I see 'Accuracy & track record' and 'What makes it trustworthy'. Good scent.

    “Accuracy & track record”

  4. body Hunt Evidence

    Page claims 'Every finding cites its evidence' and '473 sealed claims. 84% hit rate.' That's a concrete claim but light on lineage detail.

    “Every finding cites its evidence, so you can forward instead of defending it.”

  5. nav Hunt Evidence

    I need integration/docs signals (API, determinism, lineage). Nav lacks 'Developers' or 'Docs' labels — red flag for me.

    “Nav links include: How it works, Manifesto, FAQ, ROI, Compare, Accuracy & track record — no 'Developers' or 'Docs' label.”

  6. decision Convert

    I clicked Request Access because the CTA is visible and I'm still curious despite missing developer-facing proof.

Pass 2 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh — dense nav but I see clear anchors for proof and process.

    “How it works Proof Evidence, not opinion AI opinions vs. simulations One landing page, judged two ways. No login. Accuracy & track record 473 sealed claims. 84% hit rate.”

  2. hero Scan First Impression

    Okay — hero explains the product: 'WhyUser is a buying committee simulation...'.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign... Every finding cites its evidence, so you can forward instead of defending it.”

  3. body Hunt Evidence

    Wait — claims of '473 sealed claims' and '84% accurate' but no logos or case links visible.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team, against your own data. Claims graded 473”

  4. nav Hunt Evidence

    Scanning for integrations or API info — nav is my map when distracted.

    “Nav anchors: How it works, What makes it trustworthy, Accuracy & track record, Compare, ROI, FAQ”

  5. decision Hunt Evidence

    Red flag: nav has proof/process links but no explicit 'Integrations', 'Developers', or 'API' label.

    “No 'Integrations' or 'Developers' in top nav; anchors focus on 'How it works' and 'Accuracy & track record'.”

  6. decision Convert

    Okay — enough scent to act. Clicking Request Access to confirm next step.

Pass 3 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav shouts 'Request Access' repeatedly — clear path to try, good surface CTA.

    “ROI Request Access”

  2. hero Scan First Impression

    Headline: 'Marketing is the only team that opens without a rehearsal.' Evocative, not explicit — who exactly is this for?

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    They claim evidence-first: 'Every finding cites its evidence, so you can forward instead of defending it.' That's aligned with my need for lineage.

    “Every finding cites its evidence, so you can forward instead of defending it.”

  4. body Hunt Evidence

    Determinism callout is explicit: 'Same page in, same verdict out.' That answers my repeatability concern at a headline level.

    “Same page in, same verdict out.”

  5. body Hunt Evidence

    They promise a low-effort result: 'No new cycle, no new process... Run it in-app or via API.' Nice — headless API & 30min claim = quick test.

    “No new cycle, no new process. WhyUser fills the gap... Run it in-app or via API.”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate clarity, value proposition, and friction'? Yes — I found evidence lineage, determinism, and an API path, but third-party proof (logos/case depth) is light.

Pass 4 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Header shows 'Request Access' repeatedly — a clear path to try or demo.

    “Request Access”

  2. hero Scan First Impression

    Hero line is punchy but vague for a BoFu risk check.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    They claim determinism and lineage — exactly my demand: 'Lineage and the Evidence Tracker'.

    “Lineage and the Evidence Tracker, from one run. Each version re-tests only what you changed. The rest carries forward.”

  4. body Hunt Evidence

    They cite hit rates but show no clear customer logos or case-study thumbnails.

    “Trusted by demand gen teams at + NDA design partners Accuracy 84% Across live accounts.”

  5. body Hunt Evidence

    Integration signal present: 'Headless via API' text, but no public dev/docs link I can open fast.

    “30 min Headless via API Sourced Before spend”

  6. nav Hunt Evidence

    I need to confirm access/demo. Found 'Request Access' in header — validate link before committing.

    “Request Access”

  7. nav Convert

    Clicking 'Request Access' to confirm there's a concrete path forward — moving cautiously.

    “Request Access -> https://whyuser.com#access”

Pass 5 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Nav is dense but contains the forward path: 'Request Access' visible in header.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend. ... ROI Request Access”

  2. hero Scan First Impression

    Hero headline reads 'Marketing is the only team that opens without a rehearsal.' — evocative but vague on exact offer/audience.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Look for determinism proof: I see 'Same page in, same verdict out.' — promising language for repeatability.

    “Same page in, same verdict out.”

  4. body Hunt Evidence

    Found explicit lineage call: 'Lineage and the Evidence Tracker, from one run.' — matches my need to defend changes.

    “Lineage and the Evidence Tracker, from one run.”

  5. body Hunt Evidence

    Integration/low-lift scent present: '30 min Headless via API Sourced Before spend'.

    “30 min Headless via API Sourced Before spend”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? Partially: proof and integration claims present, clarity and social proof are thin.

  7. nav Convert

    I clicked the clear forward path in header to confirm engagement, but I move forward cautiously given thin visible social proof.

    “Request Access”

Pass 6 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 8 steps
  1. nav Scan First Impression

    Nav is dense but shows 'Request Access' everywhere.

    “Request Access”

  2. hero Scan First Impression

    Hero voice is theatrical; audience not crisply named.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Finds determinism claim I care about.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    API/headless and 30-minute run called out — good qualifier.

    “No new cycle, no new process. WhyUser fills the gap between review and launch with one 30 minute test step. Run it in-app or via API.”

  5. body Hunt Evidence

    They show accuracy numbers but no visible customer logos.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team”

  6. nav Hunt Evidence

    Nav contains 'Accuracy & track record' and 'How it works' links I can follow.

    “Accuracy & track record”

  7. decision Hunt Evidence

    Does this meet my discovery needs for lineage and test speed? Partially; evidence claims present, proof artifacts thin.

    “Lineage and the Evidence Tracker, from one run. Each version re-tests only what you changed. The rest carries forward.”

  8. nav Convert

    Request Access is the clear path forward. I'll click to confirm interest.

    “Request Access”

Pass 7 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header calls the audience out: 'For demand gen and growth marketing leaders at B2B SaaS.' Good targeting.

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch.”

  2. body Scan First Impression

    Hero/body states the product plainly: 'WhyUser is a buying committee simulation...'. Clear core claim.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They call out the exact wins I care about: determinism, lineage, and repeatable runs.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    There are numbers ('84% hit rate', '473 claims') but no customer logos or case snapshots visible above the fold.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team... 473 claims graded”

  5. body Hunt Evidence

    They mention 'Headless via API' and 'Run it in-app or via API' — good signal but no obvious developer/docs link shown in top scan.

    “30 min Headless via API Sourced Before spend”

  6. nav Convert

    I need a clear next step; 'Request Access' is visible in the header — I'm clicking to confirm interest and collect the onboarding signal.

Pass 8 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav is dense but explicit: lots of product pages and 'Request Access'.

    “Request Access Product Video RUN-2847 Committee flow  who carries the deal, who quietly stops it 300 agents  n=60/role  this run 52 of 60 champion cannot carry it”

  2. hero Scan First Impression

    Hero copy explains the product: 'WhyUser is a buying committee simulation...' — clear promise, not succinct audience-targeted headline.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They loudly claim determinism and lineage: 'Lineage and the Evidence Tracker' is present.

    “Lineage and the Evidence Tracker, from one run.”

  4. body Hunt Evidence

    API path hinted: '30 min Headless via API' is explicit text, promising integration/automation.

    “30 min Headless via API Sourced Before spend”

  5. footer Hunt Evidence

    Proof claim exists but no logos: '473 claims graded, 84% accurate' — sounds like evidence but light on verifiable case studies.

    “473 claims graded, 84% accurate”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction'? No — missing explicit docs/links I can vet on this page.

Pass 9 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 8 steps
  1. nav Scan First Impression

    Nav calls out audience: 'For demand gen and growth marketing leaders at B2B SaaS' — promising alignment.

    “For demand gen and growth marketing leaders at B2B SaaS”

  2. body Scan First Impression

    Hero/body opens with a clear statement: 'buying committee simulation that runs before you launch a B2B campaign.'

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim determinism and lineage: 'same page in produces the same verdict out' — that matches my repeatability need.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    Proof feels thin: 'Trusted by demand gen teams at + NDA design partners' appears with no visible logos or case excerpts.

    “Trusted by demand gen teams at + NDA design partners”

  5. body Hunt Evidence

    Integration path is explicit: 'Headless via API' and 'Run it in-app or via API' — lowers lift risk if true.

    “30 min Headless via API Sourced Before spend”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? Partially — value and API fit clear; proof and forwardable case detail missing.

  7. nav Hunt Evidence

    Router check: nav/footer link to 'ROI', 'Accuracy & track record', and 'How it works' exist — paths to deeper proof are surfaced.

    “ROI”

  8. nav Convert

    I clicked 'Request Access' to confirm there is a real, low-friction path forward despite limited on-page proof.

    “Request Access”

Pass 10 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Nav is dense but useful — lots of labeled paths (Request Access, How it works, Accuracy).

    “Request Access Product Video RUN-2847 Committee flow · who carries the deal, who quietly stops it 300 agents · n=60/role · this run 52 of 60 champion cannot carry it”

  2. hero Scan First Impression

    Headline and title state audience: 'Buying Committee Simulation for B2B Campaigns' — relevant to my role.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Claims of measurable results: 'Accuracy 84%', '473 sealed claims' — that grabs my attention.

    “Trusted by demand gen teams at + NDA design partners Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team”

  4. body Hunt Evidence

    I need concrete proof (logos, case studies, lineage). I don't see logos or case studies here.

  5. nav Hunt Evidence

    There are explicit links: 'How it works' and 'Accuracy & track record' — decent signposting.

    “How it works”

  6. nav Hunt Evidence

    No 'Developers' or 'Docs' nav item — that's a miss for my need to confirm lineage / deterministic reruns.

  7. nav Convert

    I still need a forward path; Request Access is visible in the header so I'll use it to progress.

    “Request Access”

TD Technical Decision Maker Head of Revenue Operations 10 passes
Pass 1 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 8 steps
  1. nav Scan First Impression

    Header shows clear product links and a repeated 'Request Access' (good signpost).

    “Request Access Product Video RUN-2847 Committee flow · who carries the deal, who quietly stops it 300 agents · n=60/role · this run 52 of 60 champion cannot carry it”

  2. hero Scan First Impression

    Headline and opening paragraph state the product: 'WhyUser is a buying committee simulation...' — explicit about purpose but light on technical entry points.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim determinism and lineage on-page: 'Same page in, same verdict out' and 'Lineage and the Evidence Tracker'. Strong positioning for my priority.

    “Same page in, same verdict out.”

  4. body Hunt Evidence

    They mention 'Headless via API' and 'Run it in-app or via API' — signals of API-first execution but no obvious 'Docs' or 'Developers' link in top nav.

    “Headless via API”

  5. body Hunt Evidence

    Claims of accuracy: '473 sealed claims. 84% hit rate.' There's a nav link 'Accuracy & track record' so evidence is accessible but not surfaced in hero.

    “473 sealed claims · 84% accurate”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience.'? No — core technical depth (integration docs/API reference) is not visible in the header or hero.

  7. footer Hunt Evidence

    Footer contains 'Security', 'DPA', 'Accuracy & track record' links — rescue links exist for compliance and accuracy, but nothing labeled 'Docs' or 'Developer'.

    “Security · Contact · Privacy · Terms · DPA 473 claims graded, 84% accurate”

  8. decision Convert

    I've seen the essential signals I care about (determinism, lineage, API mention). I will click the visible business path to continue the decision flow: 'Request Access'.

Pass 2 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header nav is dense but explicit — lots of topic links including 'Request Access' and 'Accuracy & track record'.

    “Request Access ... Accuracy & track record ... What makes it trustworthy”

  2. hero Scan First Impression

    Headline/title names my audience: 'Buying Committee Simulation for B2B Campaigns' — I'm in the right category.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    I'm hunting for developer/docs or integrations links in the top nav (clear indicators of integration capability).

    “Top nav contains: How it works, Manifesto, FAQ, ROI, Accuracy & track record (no 'Developers' or 'Integrations' label)”

  4. body Hunt Evidence

    Proof language is present: 'Every finding cites its evidence' and numerical claims like '473 sealed claims' — decent methodological scent.

    “Every finding cites its evidence.”

  5. nav Hunt Evidence

    No explicit 'Docs', 'Developers', or 'Integrations' top-nav link — that's a gap for my evaluation needs.

  6. decision Convert

    I need a path forward; header 'Request Access' exists (lnk_1). I'm clicking it to confirm interest and force a sales conversation about integrations and lineage.

    “Request Access”

Pass 3 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav shows Request Access, How it works, Accuracy — a clear router to follow.

    “Request Access Product Video RUN-2847 Committee flow 7 who carries the deal”

  2. hero Scan First Impression

    Headline targets marketing: not callout for technical guarantees I care about.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    They claim API/headless and fast runs; that's relevant to my integration check.

    “Run it in-app or via API.”

  4. body Hunt Evidence

    They call out lineage and an Evidence Tracker — that addresses determinism.

    “Lineage and the Evidence Tracker, from one run.”

  5. body Hunt Evidence

    Claims: '473 sealed claims. 84% hit rate.' Good scent but no visible case-study artifacts.

    “473 claims graded, 84% accurate”

  6. decision Convert

    Did I satisfy the mission to evaluate clarity, value prop, friction? No — hero is marketing-first and docs are not obvious. I click Request Access because I need a concrete path forward.

Pass 4 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Header reads as product-first for demand-gen, lots of 'Request Access' CTAs.

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch. ... Request Access”

  2. hero Scan First Impression

    Headline frames the problem as rehearsal missing: clear but audience-skewed.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Content promises reproducibility and lineage — that hits my evidence need.

    “Lineage and the Evidence Tracker, from one run. Each version re-tests only what you changed. The rest carries forward.”

  4. body Hunt Evidence

    They call out determinism explicitly: "Same page in, same verdict out." Good scent.

    “Same page in, same verdict out.”

  5. body Hunt Evidence

    I need integration proof; page mentions API/headless but no dev docs visible yet.

    “30 min Headless via API Sourced Before spend”

  6. nav Hunt Evidence

    Looking for a clear docs/technical path — I see a header link 'How it works'.

    “How it works”

  7. decision Convert

    Did I satisfy the User Intent: 'Evaluate clarity, value proposition, and friction'? No — need specific technical detail, so I click 'How it works' to check lineage/integration.

Pass 5 ABANDON Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Bounce 8 steps
  1. nav Scan First Impression

    Scanning top nav: lots of marketing links and repeated 'Request Access' — no 'Developers' or 'Docs'. Ugh.

    “WhyUser Product ... Manifesto FAQ ROI Request Access ... Request Access”

  2. hero Scan First Impression

    Headline names the audience: 'WhyUser is a buying committee simulation... B2B campaign' — okay, that part's clear.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    Looking for proof paths: I see 'Accuracy & track record' in the nav — promising as a signpost to evidence.

    “Accuracy & track record”

  4. nav Hunt Evidence

    I see 'How it works' and 'What makes it trustworthy' — maybe they describe methodology, but not labeled as integrations or API.

    “How it works”

  5. body Hunt Evidence

    Claims: 'Every finding cites its evidence' and accuracy metrics ("84% hit rate"). Nice claim, but I need integration details to evaluate operational fit.

    “Every finding cites its evidence. ... Accuracy & track record 473 sealed claims. 84% hit rate.”

  6. nav Hunt Evidence

    Specifically searching for 'Docs', 'Developers', 'Integrations' — top nav has none of those explicit labels. This is a problem.

    “Nav links present: Request Access, How it works, Manifesto, FAQ, ROI, Accuracy & track record, Compare, What makes it trustworthy”

  7. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — integration/API proof is not surfaced in the top nav.

    “No 'Developers', 'Docs', or 'Integrations' link visible in top nav.”

  8. decision Bounce

    I give up: without a clear integration/docs path in the nav I can't proceed. Abandoning this visit.

    “Top-nav is the only map I trusted; it lacks any developer/integration signpost.”

Pass 6 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav has 'Request Access' and 'How it works' — a clear start for demos.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof.”

  2. hero Scan First Impression

    Hero copy: 'Marketing is the only team that opens without a rehearsal.' Clear problem frame, lightly poetic.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    I see a determinism claim: 'WhyUser is deterministic at the element level.' Exactly my decision filter.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    API / headless callouts present: '30 min Headless via API' — integration signal but not proof.

    “30 min Headless via API Sourced Before spend”

  5. body Hunt Evidence

    Metrics appear ('473 claims graded, 84% accurate') but no logos or case links to verify provenance.

    “473 claims graded, 84% accurate”

  6. decision Convert

    Content claims lineage and API access — I need the demo/integration proof. I'm clicking Request Access to get the evidence I need.

Pass 7 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Ugh — header is dense but I spot 'Request Access' and 'How it works'.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation...”

  2. body Scan First Impression

    Okay — clear lead: 'WhyUser is a buying committee simulation that runs before you launch a B2B campaign.'

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. Your reviewers know the product, so they read the page as ideal users.”

  3. body Hunt Evidence

    Nice signal: deterministic claims and lineage are explicit — exactly what I care about.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    API/tech fit hinted: 'Run it in-app or via API' and 'Headless via API' appear — promising.

    “No new cycle, no new process. WhyUser fills the gap between review and launch with one 30 minute answer. Run it in-app or via API.”

  5. body Hunt Evidence

    There are performance claims: '473 sealed claims. 84% hit rate.' Feels thin without case studies or logos.

    “Trusted by demand gen teams at + NDA design partners Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team...”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate clarity, value prop, friction for target audience'? No — core claims and API hints are present but I need docs/examples to assess integration effort and proof.

  7. nav Convert

    Okay, I need to dig into 'How it works' to confirm tech fit — clicking it.

Pass 8 ABANDON Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Bounce 8 steps
  1. nav Scan First Impression

    Header nav shows 'Request Access', 'How it works', 'Accuracy & track record' — presence is clear.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend. Email Campaign Simulation The subject and CTA that win for each role. Audience Discovery The roles your content actually fits. How it works Proof Evidence, not opinion AI opinions vs. simulations One landing page, judged two ways.”

  2. hero Scan First Impression

    Headline names the audience and job: 'buying committee simulation ... before you launch.' Good clarity on what it is.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim determinism and lineage: 'deterministic at the element level' and 'Lineage and the Evidence Tracker'.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    They advertise API support: '30 min Headless via API' — promising for integration tests.

    “30 min Headless via API Sourced Before spend”

  5. nav Hunt Evidence

    I can't find a 'Developers' or 'Docs' link in the header nav to validate integrations or API docs.

    “Request Access Product Video RUN-2847 Committee flow  who carries the deal ... Accuracy 84% Across live accounts.”

  6. footer Hunt Evidence

    Footer includes 'Security' and 'DPA' links, but I'm blind to compliance; they don't answer my integration/docs need.

    “WhyUser Inc. ... Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  7. body Hunt Evidence

    There's a reference 'Why ngrok chose WhyUser' but no visible logos or linked case study to inspect evidence.

    “Why ngrok chose WhyUser”

  8. decision Bounce

    I cannot validate integrations or find developer docs; that triggers my veto for technical adoption.

Pass 9 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header nav is dense but explicit — lots of topic links, including 'How it works' and 'Accuracy & track record'.

    “How it works Proof Evidence, not opinion AI opinions vs. simulations Accuracy & track record Compare WhyUser next to panels...”

  2. hero Scan First Impression

    Okay — hero/body copy names the product: 'WhyUser is a buying committee simulation...' — clear baseline claim.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Good sign: determinism and lineage called out directly — that's exactly my priority.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    Integration scent present: 'Headless via API' and 'Run it in-app or via API' — promising but not a docs link.

    “30 min Headless via API Sourced Before spend”

  5. body Hunt Evidence

    Customer-proof is thin on the page (no logos or case excerpts visible above fold). Claims about '473 sealed claims, 84% hit rate' exist but lack visible artifacts.

    “82% hit rate · 41 graded calls”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — evidence for determinism and API exists, but integrations/docs and visible case proof are weak.

Pass 10 ABANDON Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Bounce 8 steps
  1. nav Scan First Impression

    Ugh — nav is dense but I see explicit links like 'Accuracy & track record' and 'What makes it trustworthy'.

    “Which buyer role killed it, and the missing proof.”

  2. hero Scan First Impression

    Okay, headline: 'WhyUser is a buying committee simulation...' — relevant audience named, that's on-point for MoFu.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    Good — 'Accuracy & track record' (lnk17) and 'What makes it trustworthy' (lnk19) are visible in top nav.

    “Accuracy & track record”

  4. body Hunt Evidence

    They claim 'Every finding cites its evidence' and '473 sealed claims. 84% hit rate.' That reads like metrics without attachments.

    “Every finding cites its evidence.”

  5. nav Hunt Evidence

    I need integration/API docs or a 'Developers' path to validate lineage and deterministic reruns — not seeing it in the top nav.

  6. decision Hunt Evidence

    Distracted state: I'm not going to dig into footer. With no clear 'Docs' or 'Developers' in the header, I can't confirm technical fit.

  7. decision Hunt Evidence

    This fails my core evaluation need: I can't validate integrations, lineage, or reproducibility from top-level links. High friction.

  8. decision Bounce

    Abandoning the page — useful hooks present but missing the clear docs/integrations path I require.

EB Economic Buyer VP of Demand Gen 10 passes
Pass 1 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh—top nav is a wall of concatenated labels; hard to parse quickly.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend.”

  2. hero Scan First Impression

    Okay headline reads like marketing copy, not a clear value metric.

    “Marketing is the only team that opens without a rehearsal.”

  3. nav Hunt Evidence

    Wait—there's an explicit audience callout for my role. Nice.

    “For demand gen and growth marketing leaders at B2B SaaS”

  4. body Hunt Evidence

    They surface accuracy metrics and claims of sourced evidence—promising but thin.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team, against your own data. Claims graded 473”

  5. nav Hunt Evidence

    I can’t find pricing, but there’s a 'Request Access' CTA and an 'ROI' link—there’s a sales path.

    “Request Access”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — hero is vague, proof is claimed but logo-level trust is missing; I clicked Request Access because I need the sales path to resolve pricing and security.

Pass 2 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header has a lot of links; looking for ROI, proof, pricing or an obvious path forward.

    “ROI Request Access The four engines Committee Simulation Which buyer role killed it, and the missing proof.”

  2. nav Scan First Impression

    I see an explicit 'ROI' link (lnk_8) and multiple 'Request Access' CTAs — good sign for a sales-led path.

    “ROI”

  3. hero Hunt Evidence

    Headline names audience: 'Buying Committee Simulation for B2B Campaigns' — clear on who it's for, not yet clear on ROI mechanics.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  4. body Hunt Evidence

    Claims about accuracy and evidence exist ("473 sealed claims", "84% hit rate") but no logos or case study links visible on this screen.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team, against your own data.”

  5. footer Hunt Evidence

    Footer lists 'DPA' and 'Security' — there's a signal for enterprise compliance, helpful for procurement checks.

    “Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  6. decision Convert

    I need a path forward; no public pricing or integration list in the top nav but there is a clear 'Request Access' CTA — I click to proceed and test the sales-led path.

    “Request Access”

Pass 3 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Top nav shows 'Request Access' and an 'ROI' entry; there's a clear path to action.

    “Manifesto FAQ ROI Request Access”

  2. hero Scan First Impression

    Hero states the core offer plainly: a 'buying committee simulation' before launch.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    I look for social proof — I see 'Why ngrok chose WhyUser' text but no visible logo set.

    “Why ngrok chose WhyUser”

  4. body Hunt Evidence

    They publish accuracy claims: '473 claims graded, 84% accurate' — numbers, but not linked enterprise case studies.

    “473 claims graded, 84% accurate”

  5. footer Hunt Evidence

    Footer contains 'Security' and 'DPA' links — procurement paths exist if I need controls.

    “Security · Contact · Privacy · Terms · DPA”

  6. decision Convert

    I need ROI detail to assess risk; I'll click 'ROI' to see the numbers and any calculator.

    “ROI”

Pass 4 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header nav shows an ROI link and repeated 'Request Access' CTAs — top map is present.

    “ROI”

  2. hero Scan First Impression

    Hero explains the product: a 'buying committee simulation' targeted at demand gen — audience named.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Page makes measurable claims: 'Accuracy 84%' and '473 sealed claims' — proof claim exists but I see no logos or case studies here.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team... Claims graded 473”

  4. nav Hunt Evidence

    Commercial path: only 'Request Access' CTAs in header — no explicit Pricing page in top nav.

    “Request Access”

  5. footer Hunt Evidence

    Quick legal/security check: footer text mentions 'Security' and 'DPA' but I see no SOC 2 badge or enterprise logos.

    “Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  6. decision Convert

    I need concrete ROI/methodology to unblock procurement; clicking the 'ROI' nav link to judge the numbers and methodology. Hero named audience but didn't give ROI detail.

    “ROI”

Pass 5 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header shows multiple 'Request Access' CTAs and an ROI link — obvious call path.

    “Request Access Manifesto FAQ ROI Request Access”

  2. hero Scan First Impression

    Headline names the audience: 'WhyUser is a buying committee simulation...' — clear audience, weak financial signal.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim accuracy: '473 claims graded, 84% accurate' — proof-style metric but no ROI case study visible here.

    “473 claims graded, 84% accurate”

  4. body Hunt Evidence

    Security badge missing above fold — they even call that out: procurement will notice.

    “Security badge missing above fold MISS”

  5. body Hunt Evidence

    Mentions 'Run it in-app or via API' but no integrations/connectors page in nav/footer — integration risk.

    “Run it in-app or via API.”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate clarity, value proposition, and friction for the target audience'? No — proof and integrations are thin, BUT there is a clear CTA path so I continue cautiously.

Pass 6 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh — nav screams 'Request Access' and has an 'ROI' link; they expect me to talk to sales.

    “Request Access ... ROI calculator Request Access”

  2. hero Scan First Impression

    Okay: hero states purpose plainly: 'WhyUser is a buying committee simulation...'.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Wait — they cite accuracy and counts: '473 claims graded, 84% accurate' — some evidence is present.

    “473 claims graded, 84% accurate”

  4. body Hunt Evidence

    Ugh — no visible customer logos and a note reads 'Security badge missing above fold'.

    “Security badge missing above fold MISS”

  5. body Hunt Evidence

    Okay, pricing signal: 'No charge during the program. Post-program: only if it earns its place in your stack.' Not a clear pricing model.

    “No charge during the program. Post-program: only if it earns its place in your stack.”

  6. decision Convert

    I clicked the ROI link because I need a defensible ROI/TCO model; the homepage didn't provide the math I require.

Pass 7 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header gives me clear CTAs: multiple 'Request Access' links visible.

    “Request Access Product Video RUN-2847 Committee flow  who carries the deal”

  2. hero Scan First Impression

    Headline reads: 'Marketing is the only team that opens without a rehearsal.' Vague on ROI or buyer stake I care about.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Looking for concrete proof: I see '473 sealed claims. 84% hit rate' but no customer logos or case snapshots.

    “473 sealed claims  84% Across live accounts. Graded by you 100% Every call marked HIT or MISS”

  4. body Hunt Evidence

    Security signals: there's a 'Security' page and a 'DPA' link in the footer, but no security badge above the fold.

    “Security  DPA”

  5. nav Hunt Evidence

    Pricing path: I find an 'ROI calculator' link in header/footer, but no public pricing table.

    “ROI calculator”

  6. decision Convert

    I clicked 'Request Access' because the page raised procurement questions I need the sales path to resolve, BUT the hero failed clarity on ROI.

Pass 8 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is dense but shows 'Request Access' and an 'ROI' nav link — good sign.

    “Request Access ... ROI calculator Request Access”

  2. hero Scan First Impression

    Hero text names the product: 'WhyUser is a buying committee simulation' — clear audience/problem.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim determinism: 'Same page in, same verdict out.' That answers my repeatability need.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    There's a performance claim: '473 sealed claims. 84% hit rate.' No logos or method up front — suspicious.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS ...”

  5. footer Hunt Evidence

    Security and legal exist in footer: I see 'Security' and 'DPA' links — procurement rescues available.

    “Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  6. decision Convert

    Did I satisfy the User Intent: Evaluate clarity, value prop, friction? Partially — ROI path and security exist but proof/logos are thin.

Pass 9 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header shows 'Request Access' and an 'ROI' link — direct paths to more detail.

    “Request Access”

  2. hero Scan First Impression

    Headline: 'WhyUser is a buying committee simulation...' — audience aligned with demand gen.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They claim determinism: 'Same page in, same verdict out' and 'Lineage and the Evidence Tracker'.

    “Same page in, same verdict out.”

  4. body Hunt Evidence

    I want ROI proof and case studies. I see 'Why ngrok chose WhyUser' text but no clear case study or logos.

    “Why ngrok chose WhyUser”

  5. footer Hunt Evidence

    Security and DPA links exist in the footer — good. No security badge above the fold though.

    “Security ulinksunct DPA”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate clarity, value prop, and friction'? Partly — evidence paths exist but proof is light; I'm moving forward cautiously to confirm.

Pass 10 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header shows clear product paths and a 'Request Access' CTA — good signal.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend. ... ROI Request Access”

  2. hero Scan First Impression

    Headline: 'For demand gen and growth marketing leaders at B2B SaaS' — targeted to me.

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch.”

  3. body Hunt Evidence

    Core claim: repeatable, evidence-led simulations and '473 sealed claims, 84% accurate'. I want source material.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. ... Every finding cites its evidence, so you can forward instead of defending it.”

  4. body Hunt Evidence

    I look for proof: logos, case studies, or metrics backing the 84% claim — not obvious here.

    “82% hit rate · 41 graded calls”

  5. footer Hunt Evidence

    Security and DPA links exist in the footer — procurement path is present, but badge missing above fold.

    “WhyUser Inc. ... Security · Contact · Privacy · Terms · DPA 473 claims graded, 84% accurate”

  6. decision Convert

    I need a concrete next step to validate procurement/ROI — header 'Request Access' is the nearest path. I'm clicking it to pursue the evidence.

    “Request Access”

EU End User Senior Demand Generation Manager 10 passes
Pass 1 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Header nav is dense but explicit — many high-scent links present.

    “Request Access Product Video ... Accuracy & track record ... What makes it trustworthy”

  2. hero Scan First Impression

    Hero headline is cheeky, not a straight problem-statement for my role.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Claims I care about are present: 30-minute test and deterministic runs — that raises my interest.

    “No new cycle, no new process. WhyUser fills the gap between review and launch with one 30 minute answer.”

  4. body Hunt Evidence

    They explicitly claim repeatability and lineage — addresses my reproducibility veto.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  5. body Hunt Evidence

    I don't see customer logos or case-study excerpts on the fold — proof feels promised but not visible.

    “Full comparisons, no gate: vs. ChatGPT and Claude · vs. internal review · vs. building it yourself · vs. buyer panels”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — hero is vague, but proof-links exist in nav.

  7. nav Convert

    I need the evidence page. Clicking 'Accuracy & track record' to confirm their claims and satisfy my evaluation.

    “Accuracy & track record”

Pass 2 ABANDON Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Bounce 8 steps
  1. nav Scan First Impression

    Scanning the top nav for docs, integrations, or clear evidence links.

    “Request Access Product Video RUN-2847 Committee flow · who carries the deal, who quietly stops it 300 agents · n=60/role · this run 52 of 60 champion cannot carry it”

  2. hero Scan First Impression

    Okay. Headline and opening copy claim a committee simulation that finds silent vetoes.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. ... It finds the silent vetoes, the missing proof, and the bounce risk”

  3. nav Hunt Evidence

    Nice: a claimed quick run — 'In 30 minutes' checks my '30-minute stress test' trigger.

    “In 30 minutes: what works, what breaks, the fix.”

  4. hero Hunt Evidence

    They assert measurable hits: '84% hit rate' and 'Every call marked HIT or MISS by your team.' That aligns with proof-driven needs.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team”

  5. nav Hunt Evidence

    Looking for integrations, docs, or 'Developers' links in the top nav — nothing labeled as integrations or docs.

    “Top nav links: How it works (lnk5), Accuracy & track record (lnk17), Compare (lnk18), What makes it trustworthy (lnk19), ROI (lnk_8) — no 'Docs' or 'Integrations' anchor”

  6. nav Hunt Evidence

    Primary action is gated: multiple 'Request Access' CTAs in the header — that's a sales gate not a hands-on trial.

    “Request Access”

  7. decision Hunt Evidence

    Did I satisfy the mission to evaluate clarity, value prop, and friction? No — proof claims exist, but integration/docs links are missing and access is gated.

    “Summary: proof language present ('In 30 minutes', 'HIT or MISS'), but no developer/docs path and CTA is 'Request Access' (gate).”

  8. decision Bounce

    Abandoning: sales-led gate plus no clear integrations/docs in top nav blocks my evaluation flow.

    “Request Access”

Pass 3 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Header lists 'How it works' and 'Accuracy & track record' — promising places to prove claims.

    “How it works Proof Evidence, not opinion AI opinions vs. simulations Accuracy & track record”

  2. hero Scan First Impression

    Headline is direct: 'WhyUser is a buying committee simulation' — I know what they're pitching.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Nice — explicit promise: 'one 30 minute test' and 'Run it in-app or via API' — hits my '30-minute stress test' trigger.

    “No new cycle, no new process. WhyUser fills the gap between review and launch with one 30 minute answer. Run it in-app or via API.”

  4. body Hunt Evidence

    They claim determinism: 'Same page in, same verdict out.' That's my non-negotiable for iteration rigor.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  5. body Hunt Evidence

    Where are the developer docs or integrations? Text mentions API but no clear 'Developers' or 'Docs' link seen yet.

    “Headless via API”

  6. decision Hunt Evidence

    Did I satisfy the mission to evaluate clarity, value prop, and friction? Partially — claims are present but technical proof and integration details are unclear.

  7. nav Convert

    Footer/nav have 'Accuracy' and 'How it works' but no 'Developers' or 'Docs' label; I'll click 'How it works' to judge methodology.

    “How it works”

Pass 4 ABANDON Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Bounce 6 steps
  1. nav Scan First Impression

    Nav explicitly targets my role: 'For demand gen and growth marketing leaders at B2B SaaS.'

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch.”

  2. hero Scan First Impression

    Hero promises a 30-minute test: 'In 30 minutes: what works, what breaks, the fix.'

    “WhyUser adds one 30 minute test step. Catch what is broken before launch, not six weeks after the spend.”

  3. body Hunt Evidence

    They claim determinism: 'Same page in, same verdict out.' That's exactly my key evidence need.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    They mention API / headless: 'Run it in-app or via API' and '30 min Headless via API' — promising but not linked to docs.

    “No new cycle, no new process. WhyUser fills the gap between review and launch with one 30 minute answer. Run it in-app or via API.”

  5. body Hunt Evidence

    They cite accuracy numbers '473 sealed claims. 84% hit rate.' — claim present, but no customer logos or case artifacts visible here.

    “473 claims graded, 84% accurate”

  6. decision Bounce

    I cannot find a clear link to developer docs or an integrations list; for MoFu that absence fails my evaluation -> abandon.

Pass 5 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 8 steps
  1. nav Scan First Impression

    Header is dense but I see 'Request Access' repeated in the top nav.

    “Request Access”

  2. hero Scan First Impression

    Opening claim: 'WhyUser is a buying committee simulation...' — audience and problem are stated.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    They assert determinism: 'Same page in, same verdict out.' Good sign for my 'compare changes' need.

    “Same page in, same verdict out.”

  4. body Hunt Evidence

    They advertise a fast test: 'one 30 minute answer' and 'Run it in-app or via API' — this hits my quick demo trigger.

    “one 30 minute answer. Run it in-app or via API.”

  5. body Hunt Evidence

    Lineage claim exists: 'Lineage and the Evidence Tracker, from one run.' That aligns with my need for traceable changes.

    “Lineage and the Evidence Tracker, from one run.”

  6. footer Hunt Evidence

    Footer has Support links: 'Security', 'Request access', 'Accuracy & track record' — useful rescue links exist.

    “Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  7. decision Hunt Evidence

    I can't find a clear 'Docs' or 'Developers' link or an integrations list to validate implementation effort.

    “No explicit 'Docs' or 'Developers' top-nav link; only 'How it works', 'Compare', 'ROI' and API copy in body.”

  8. nav Convert

    I want hands-on access; I'll click Request Access to confirm the demo/trial path.

    “https://whyuser.com#access”

Pass 6 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav is overloaded — long text blobs and many links; parsing cost is high.

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch. ... In 30 minutes: what works, what breaks, the fix.”

  2. hero Scan First Impression

    Headline says 'Buying Committee Simulation' — the product claim is clear about purpose.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. ... Every finding cites its evidence, so you can forward instead of defending it.”

  3. body Hunt Evidence

    They promise quick results: 'In 30 minutes' — that matches my speed-to-value need.

    “In 30 minutes: what works, what breaks, the fix. Before you spend on traffic.”

  4. body Hunt Evidence

    Claims include metrics ("84% accuracy", "473 sealed claims") and a trust path link 'Accuracy & track record'.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS by your team, against your own data. Claims graded 473”

  5. nav Hunt Evidence

    Clear path forward exists: 'Request Access' is in the top nav — a tangible next step.

    “Request Access”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — messaging is clear but the experience is noisy; still I will proceed to confirm interest.

Pass 7 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh — lots of nav links but it's a scatter: 'Request Access', 'How it works', 'Accuracy & track record'.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend.”

  2. hero Scan First Impression

    Okay: headline frames this as a 'buying committee simulation' — that's on-point for my role.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Nice — they call out a single 30 minute test step; that's exactly my 'time-to-value' trigger.

    “WhyUser adds one 30 minute test step. That gap is where silent vetoes slip through today. Run it in-app or via API.”

  4. body Hunt Evidence

    Finally: determinism and hit/miss language present — 'same page in, same verdict out' addresses my reproducibility veto.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  5. body Hunt Evidence

    Searching for a clear 'Docs' or 'Developers' path and an integrations list — can't spot a dedicated docs/dev hub link.

    “I scanned nav and footer for 'Developers', 'Docs', 'Integrations' and found no explicit match.”

  6. decision Convert

    I didn't find an explicit docs/developer hub, but the page names API/headless and shows determinism — I'll click Request Access to confirm integration details.

    “Request Access”

Pass 8 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 8 steps
  1. nav Scan First Impression

    Ugh — nav is dense, lots of claims jammed together.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend.”

  2. hero Scan First Impression

    Okay headline is evocative but not sharply prescriptive for my role.

    “Marketing is the only team that opens without a rehearsal.”

  3. body Hunt Evidence

    Finally a hard promise: a 30 minute test — that hits my "first-session win" trigger.

    “30 min Headless via API Sourced Before spend”

  4. body Hunt Evidence

    They claim determinism and lineage — exactly what I care about for reproducible runs.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  5. body Hunt Evidence

    They mention an Evidence Tracker and lineage — that addresses my reproducibility veto.

    “Lineage and the Evidence Tracker, from one run. Each version re-tests only what you changed.”

  6. body Hunt Evidence

    Scanning for concrete proof (logos, case studies) — I see numbers but no logos here.

    “473 claims graded, 84% accurate”

  7. nav Hunt Evidence

    I need a path forward to validate hands-on; there are multiple 'Request Access' links.

    “Request Access”

  8. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction'? No — hero is evocative, not role-specific, but core proofs I need (30-min run, determinism, lineage) are present; I'm clicking Request Access because I need to test it hands-on, BUT the page glosses over visible customer proof.

Pass 9 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Nav is dense but immediately shows 'Request Access' and 'ROI' — a clear action path.

    “Request Access”

  2. hero Scan First Impression

    Headline states product: 'WhyUser is a buying committee simulation...' — clear proposition, but I need proof.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Does this meet my task (evaluate clarity/value)? Not yet — they claim determinism and quick runs, need artifacts.

    “WhyUser is deterministic at the element level: the same page in produces the same verdict out.”

  4. body Hunt Evidence

    Found claims of measurable proof: '473 sealed claims. 84% hit rate.' That's a signal but no case artifacts or logos.

    “Accuracy 84% Across live accounts. Graded by you 100% Every call marked HIT or MISS”

  5. body Hunt Evidence

    They mention API and '30 min Headless via API' (promising) but I can't find API docs or an integrations list in nav/footer.

    “30 min Headless via API Sourced Before spend”

  6. decision Convert

    I need hands-on proof and a trial path; no visible docs but a clear 'Request Access' path exists — I'm clicking to get a demo.

    “Request Access”

Pass 10 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Header is loud and dense; I see 'Request Access' repeated — quick map.

    “Request Access”

  2. hero Scan First Impression

    Headline: 'Buying Committee Simulation' — speaks to my audience and problem.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    Claim: 'In 30 minutes: what works, what breaks, the fix.' That aligns with my 30-minute stress-test need.

    “In 30 minutes: what works, what breaks, the fix.”

  4. body Hunt Evidence

    They say 'Every finding cites its evidence' and '84% hit rate' — promising language, but no logos or case links visible.

    “Every finding cites its evidence.”

  5. footer Hunt Evidence

    Footer repeats '473 claims graded, 84% accurate' but still no customer logos or case-study links to inspect.

    “473 claims graded, 84% accurate”

  6. decision Hunt Evidence

    My goal: evaluate clarity/value — hero mostly passes but proof is thin. Do I click the path forward to confirm?

  7. nav Convert

    There's a clear CTA: 'Request Access' (header). That is the clear path forward; I'm tempted to proceed.

    “Request Access”

GR Security Guardian Director of Security 10 passes
Pass 1 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 7 steps
  1. nav Scan First Impression

    Quick scan of header: product scoped to B2B campaign reviewers, clear positioning.

    “Which buyer role killed it, and the missing proof.”

  2. hero Scan First Impression

    Headline / hero explains 'committee simulation'—I get the product claim, but no security signals above the fold.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Looking for explicit security claims (encryption, isolation, logging). I see a flagged note: 'Security badge missing above fold'. Ugh.

    “Security badge missing above fold MISS”

  4. footer Hunt Evidence

    Footer lists security assets and DPA — that's promising as a map to evidence.

    “Security  Contact  Privacy  Terms  DPA”

  5. body Hunt Evidence

    I need architecture/integration proof (data flows, tenant isolation). The body talks about 'Lineage and the Evidence Tracker' but no technical details here.

    “Lineage and the Evidence Tracker, from one run. Each version re-tests only what you changed.”

  6. decision Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience.'? No — security artifacts are referenced but not shown; check the Security page.

  7. footer Convert

    Clicking the footer 'Security' link to get the trust package I need. Finally, a direct path to evidence.

    “Security”

Pass 2 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is dense but I see explicit links for trust: 'What makes it trustworthy' and 'Request Access'.

    “What makes it trustworthy”

  2. hero Scan First Impression

    Hero/body copy explains methodology: 'Every finding cites its evidence' (elcontentp_1). Good claim, needs artifacts.

    “Every finding cites its evidence, so you can forward instead of defending it.”

  3. body Hunt Evidence

    Explicit self-note: look for DPA, Security page, and audit artifacts — this is my checklist.

    “Decision checklist: DPA, security trust package, audit trail”

  4. body Hunt Evidence

    I spot a content flag: 'Security badge missing above fold MISS' (elcontentdiv_104). Red flag for auditors.

    “Security badge missing above fold MISS”

  5. footer Hunt Evidence

    Footer has the exact links I want: 'Security' (lnk41) and 'DPA' (lnk44). Nice — Router proof.

    “Security  Contact  Privacy  Terms  DPA”

  6. decision Convert

    I found DPA and Security links, and a clear CTA 'Request Access' in header — I click to confirm interest.

    “Request Access”

Pass 3 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is dense — lots of product links but no visible security badge in header.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof.”

  2. hero Scan First Impression

    Hero states what the product does: 'WhyUser is a buying committee simulation...' but says nothing about SOC 2, logs, or DPA up front.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    There is an explicit flag: 'Security badge missing above fold' — red flag for me as a security reviewer.

    “Security badge missing above fold MISS”

  4. body Hunt Evidence

    Positive: page references 'Evidence Tracker' and 'EVIDENCE LEDGER' — language that maps to auditability artifacts.

    “EVIDENCE LEDGER Acme  /platform”

  5. footer Hunt Evidence

    Footer contains links I need: 'Security' and 'DPA' — a clear rescue path to control artifacts.

    “Security  Contact  Privacy  Terms  DPA”

  6. decision Convert

    I clicked the Security page to get the control pack and DPA details before advancing internal approval.

Pass 4 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is busy but I don't see an explicit 'Security' link in top nav.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof.”

  2. hero Scan First Impression

    Hero declares the product: 'WhyUser is a buying committee simulation...' — clear what they sell, not security details.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Ugh — page flags the problem: 'Security badge missing above fold MISS' (they've acknowledged a gap).

    “Security badge missing above fold MISS”

  4. nav Hunt Evidence

    I see 'What makes it trustworthy' in the header (lnk_19) — scent for trust but vague.

    “What makes it trustworthy”

  5. footer Hunt Evidence

    Good — footer contains 'Security' and 'DPA' links; the trust artifacts are buried, not visible up front.

    “Security · Contact · Privacy · Terms · DPA 473 claims graded, 84% accurate”

  6. decision Convert

    I need the DPA and security details to unblock procurement — clicking the DPA link now.

Pass 5 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header nav is dense; I see repeated 'Request Access' and product links.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation ...”

  2. hero Scan First Impression

    Hero claim: 'WhyUser is a buying committee simulation...' — clear claim, but no visible security artifact above the fold.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. ... Every finding cites its evidence, so you can forward instead of defending it.”

  3. nav Hunt Evidence

    Looking for trust/compliance links in nav; I see anchors like 'How it works' and 'What makes it trustworthy' but not 'Docs' or 'Architecture'.

    “How it works”

  4. footer Hunt Evidence

    Footer contains 'Security' and 'DPA' links — good scent for compliance evidence.

    “Security”

  5. footer Hunt Evidence

    Footer also lists 'DPA' and 'Contact' — paths for contractual and security artifacts are present.

    “DPA”

  6. footer Convert

    I need the security page; clicking Security to confirm there's an evidence path.

    “Security”

Pass 6 CLICK Skeptic (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Top nav is marketing-heavy; no security or legal in the header. Ugh.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend. ... Request Access”

  2. hero Scan First Impression

    Headline says 'buying committee simulation' but zero compliance language above the fold.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign. Your reviewers know the product, so they read the page as ideal users.”

  3. body Hunt Evidence

    Wait — page explicitly calls out 'Security badge missing above fold' — that reads like a self-check. Hmm.

    “Security badge missing above fold MISS”

  4. nav Hunt Evidence

    No top-nav link for Security or DPA; not great for quick trust scanning.

    “Header links: Request Access, How it works, Manifesto, FAQ, Compare… (no 'Security' in header)”

  5. footer Hunt Evidence

    Finally: footer includes 'Security', 'Privacy', and 'DPA' links. Okay, rescue path exists.

    “WhyUser Inc. ... Security · Contact · Privacy · Terms · DPA 473 claims graded, 84% accurate”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? Partial — trust links exist but proof isn't visible above the fold.

    “Clicking footer 'Security' to confirm there's a public trust path (lnk_41).”

Pass 7 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is dense and repeats many items; hard to parse at a glance.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation”

  2. hero Scan First Impression

    Content claims every finding is sourced; that's the exact control evidence language I look for.

    “Every finding cites its evidence, so you can forward instead of defending it.”

  3. body Hunt Evidence

    No explicit SOC 2, ISO, or trust badges visible in the body text I scanned.

    “No 'SOC 2' or 'ISO' literal in the visible content blocks I scanned.”

  4. nav Hunt Evidence

    Found a semantic trust path: nav link 'What makes it trustworthy' — that matches my 'Trust Center' scent.

    “What makes it trustworthy”

  5. decision Hunt Evidence

    I need the trust artifacts to decide; the nav link is my best rescue path before I abandon.

    “Scanning nav for 'DPA', 'Security', 'Trust' links per checklist.”

  6. nav Convert

    Clicking 'What makes it trustworthy' to get the control evidence pack and DPA link.

    “What makes it trustworthy”

Pass 8 CLICK Ideal (High Motivation, High Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh — header is dense but I see audience text for demand gen leaders.

    “For demand gen and growth marketing leaders at B2B SaaS See your campaigns and pages the way your buyers will. Before you launch.”

  2. hero Scan First Impression

    Okay — product claim is explicit: 'buying committee simulation'. Good topical fit for evaluation.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. body Hunt Evidence

    Wait — there's a clear callout: 'Security badge missing above fold MISS' — flagged absence of visible security signal.

    “Security badge missing above fold MISS”

  4. body Hunt Evidence

    Finally: evidence-oriented language — 'EVIDENCE LEDGER' and 'Each finding cites its evidence.' That resonates with my audit needs.

    “EVIDENCE LEDGER Acme  /platform”

  5. footer Hunt Evidence

    Good — footer has explicit links for Security and DPA (rescue links for my checklist).

    “Security”

  6. decision Convert

    I clicked the Security link because I need the trust pack to proceed with evaluation.

Pass 9 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Ugh — header is dense and copy-smashed together, hard to parse quickly.

    “WhyUser Product The four engines Committee Simulation Which buyer role killed it, and the missing proof. Ad Campaign Simulation The ad to page gap, caught before you spend.”

  2. hero Scan First Impression

    Okay, hero states product succinctly: a 'buying committee simulation' — that names the product and audience.

    “WhyUser is a buying committee simulation that runs before you launch a B2B campaign.”

  3. nav Hunt Evidence

    Wait — there's a risk path link: 'What makes it trustworthy' in the top nav. Good scent for security.

    “What makes it trustworthy”

  4. body Hunt Evidence

    Scanning body for explicit controls: no SOC 2 or retention-policy text visible in the first screen.

    “Which buyer role killed it, and the missing proof.”

  5. nav Hunt Evidence

    There are multiple 'Request Access' CTAs in header — a clear engagement path is present.

    “Request Access”

  6. decision Convert

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — clarity is mixed, but nav contains trust path; I'll follow it.

Pass 10 CLICK Distracted (Low Motivation, Low Ability) Scan First Impression → Hunt Evidence → Convert 6 steps
  1. nav Scan First Impression

    Header is dense but I spot a trust path: 'What makes it trustworthy' in the nav.

    “What makes it trustworthy”

  2. body Scan First Impression

    Page copy claims: 'Every finding cites its evidence.' Good—that speaks to auditability.

    “Every finding cites its evidence, so you can forward instead of defending it.”

  3. body Hunt Evidence

    I'm looking specifically for DPA, SOC2, subprocessor list, retention policy — not seeing those artifacts here on the first screen.

  4. footer Hunt Evidence

    Footer lists 'Security · Contact · Privacy · Terms · DPA' — DPA text is present in footer copy.

    “Security  Contact  Privacy  Terms  DPA 473 claims graded, 84% accurate”

  5. nav Hunt Evidence

    Did I satisfy the User Intent: 'Evaluate overall clarity, value proposition, and friction for the target audience'? No — the page signals evidence exists but the specific artifacts I need are not explicit above the fold.

  6. decision Convert

    There is a clear action: 'Request Access' in the header. I clicked it to reach the access path and request the security pack.

What went in, before the artifact was seen

50 seeds · 3 behavioural profiles · 5 compiled buyers
Input 1 · the artifact
URL https://whyuser.com
Page intent Evaluate overall clarity, value proposition, and friction for the target audience.
Committee bc-dd71cb81
Intent stage dark funnel
Seats CH Champion · TD Technical Decision Maker · EB Economic Buyer · EU End User · GR Security Guardian
Analysis LANDING_PAGE · COMMITTEE · GENERAL strategy
Run 2b9d0a03 · AN-90670518
Input 2 · the seed plan
CH Champion baseline profile · Ideal 10 clicked · 0 submitted · 0 abandoned of 10
across profiles Distracted ≈3 Skeptic ≈3 Ideal ≈4
TD Technical Decision Maker baseline profile · Skeptic 7 clicked · 0 submitted · 3 abandoned of 10
across profiles Distracted ≈3 Skeptic ≈4 Ideal ≈3
EB Economic Buyer baseline profile · Skeptic 10 clicked · 0 submitted · 0 abandoned of 10
across profiles Distracted ≈3 Skeptic ≈4 Ideal ≈3
EU End User baseline profile · Skeptic 8 clicked · 0 submitted · 2 abandoned of 10
across profiles Distracted ≈3 Skeptic ≈4 Ideal ≈3
GR Security Guardian baseline profile · Skeptic 10 clicked · 0 submitted · 0 abandoned of 10
across profiles Distracted ≈3 Skeptic ≈4 Ideal ≈3
Each bar is one seeded run clicked through abandoned the page

Each mark is one independent pass of one compiled buyer over the page. Roles are never averaged — the committee graph is assembled from per-role outcomes afterwards. The across-profiles row is the declared allocation, not a recorded tally: the run file states which profiles were covered and each role's baseline, but does not itemise which profile each individual seed ran in, so those bars are shown approximate.

Recorded outcomes
90%
of runs clicked through
10%
abandoned the page
0%
submitted a form
Behavioural profile weighting
Distracted — low motivation · low ability 30%
Skeptic — high motivation · high scrutiny 40%
Ideal — high motivation · high ability 30%

Every seeded buyer is drawn into one of these states before the page is served. A finding that only survives the ideal state is not the same evidence as one that survives all three.

Input 3 · the committee, as compiled

Frozen by fingerprint. Re-run the same fingerprints and you get the same buyers — this is a replay, not a re-generation.

CH Champion

Staff Marketing Operations Manager · B2B Saas · Technical Saas

Motivated internal champion who optimizes for visible wins and cross-functional alignment, adopting tools that produce defensible proof fast while avoiding credibility-damaging rollout risks.

Baseline state
Ideal
Fingerprint
6f744b870006001f · compiled 2026-08-12 · 1.1.0-pins
State vector, as compiled
budget sensitivity 35–60
urgency 70–90
domain sophistication 65–85
skepticism 35–55
Decision heuristics
Loss Aversion 45%
Social Proof 55%
Anchored against
Gong/Chorus as the evidence source of truthOur current campaign QA checklist and launch process
Dominant biases
Authority BiasOutcome BiasAvailability HeuristicCommitment and Consistency
Will veto if
  • Results can’t be explained or traced to evidence (no lineage, no HIT/MISS, no version carry-forward).
  • Implementation requires heavy integration work upfront with unclear ROI or timeline, creating risk to my credibility.
Will adopt if
  • Must produce repeatable, comparable outputs (same inputs yield the same verdict) with clear lineage so I can defend changes across versions.
  • Must fit into existing campaign workflows with a low-lift path (in-app run or API) and a concrete way to package results for stakeholders.
TD Technical Decision Maker

Head of Revenue Operations · B2B Saas · Technical Saas

A skeptical, systems-integrity-first evaluator who adopts only when scalability, auditability, and deterministic repeatability are proven end-to-end.

Baseline state
Skeptic
Fingerprint
f4a6aff64619ac23 · compiled 2026-08-12 · 1.1.0-pins
State vector, as compiled
budget sensitivity 35–65
urgency 40–70
domain sophistication 75–95
skepticism 80–95
Decision heuristics
Loss Aversion 65%
Authority Bias 35%
Anchored against
Gong/Chorus-style evidence workflowsVanta-style compliance automation
Dominant biases
Loss AversionAmbiguity AversionConfirmation BiasStatus Quo Bias
Will veto if
  • Non-deterministic results or inability to trace verdicts back to evidence and versioned inputs
  • Integration or security gaps that create operational fragility (manual exports, unclear data handling, or no DPA support)
Will adopt if
  • Must provide deterministic, repeatable outputs with versioned lineage so campaign changes can be compared across iterations
  • Must support secure, API-based integration into existing GTM workflows with tenant isolation and auditable access logging
EB Economic Buyer

VP of Demand Gen · B2B Saas · Technical Saas

Defaults to skeptical, ROI-first validation—will only fund tools that prove measurable pipeline lift or spend reduction with defensible attribution and low operational drag.

Baseline state
Skeptic
Fingerprint
b15b305314651986 · compiled 2026-08-12 · 1.1.0-pins
State vector, as compiled
budget sensitivity 75–95
urgency 45–70
domain sophistication 65–85
skepticism 80–95
Decision heuristics
Loss Aversion 65%
Authority Bias 35%
Anchored against
Board-level scrutiny of CAC and paybackFinance gatekeeping on tools with uncertain utilization
Dominant biases
Loss AversionAmbiguity AversionConfirmation BiasSunk Cost Fallacy
Will veto if
  • Usage-based pricing that cannot be capped/forecasted or that creates surprise overages for normal experimentation volume.
  • Cannot demonstrate enterprise-ready security posture for handling GTM inputs (DPA support, data controls) in a way Finance and Security will accept.
Will adopt if
  • Must quantify expected spend waste reduction or pipeline lift with a defensible methodology (e.g., ROI/TCO model tied to campaign throughput).
  • Must provide repeatable, deterministic results with change tracking so revisions can be compared version-over-version.
EU End User

Senior Demand Generation Manager · B2B Saas · Technical Saas

A skeptical, time-boxed operator who will adopt only if the product proves immediate, low-friction time-to-value and improves campaign outcomes without adding workflow overhead.

Baseline state
Skeptic
Fingerprint
c0789681a4373404 · compiled 2026-08-12 · 1.1.0-pins
State vector, as compiled
budget sensitivity 35–60
urgency 65–85
domain sophistication 55–75
skepticism 80–95
Decision heuristics
Loss Aversion 65%
Effort Minimization 35%
Anchored against
A/B testing in ad platformsLanding page experiment tools
Dominant biases
Negativity BiasConfirmation BiasStatus Quo BiasEffort Heuristic
Will veto if
  • Outputs are not reproducible or can’t be traced (no lineage/evidence trail), making it impossible to trust for launch decisions.
  • Time-to-value is slow due to heavy integrations or unclear required inputs before anything actionable appears.
Will adopt if
  • Must produce campaign-ready, role-specific objections and missing-proof guidance within the first session (no multi-week setup).
  • Must let me compare changes deterministically across versions so iteration is measurable and not subjective.
GR Security Guardian

Director of Security · B2B Saas · Technical Saas

A checklist-driven Security Guardian who advances only when evidence artifacts match control requirements and implementation claims are verifiable.

Baseline state
Skeptic
Fingerprint
ee9d5ad3faa9e3e8 · compiled 2026-08-12 · 1.1.0-pins
State vector, as compiled
budget sensitivity 35–60
urgency 40–65
domain sophistication 75–90
skepticism 85–98
Decision heuristics
Loss Aversion 70%
Authority Bias 30%
Anchored against
SOC 2 Type II control evidence expectationsISO 27001-aligned vendor due diligence
Dominant biases
Loss AversionNegativity BiasAuthority BiasAmbiguity Aversion
Will veto if
  • Cannot substantiate security and privacy claims with verifiable evidence (e.g., logs, configs, policies, IR plan) during evaluation
  • Unacceptable data handling posture (e.g., unclear PII processing, retention, or third-party subprocessor risk) or refusal to sign DPA/security terms
Will adopt if
  • Must provide a complete security trust package (policies + technical controls + audit logs) aligned to our questionnaire and procurement requirements
  • Must demonstrate strong data protection (PII handling, encryption in transit/at rest, clear retention/deletion) with a signed DPA

Walk any finding back to what produced it

W1

Core value prop lands: deterministic, evidence-backed verdicts

Working · Body zone · medium severity · traced through Champion

1 · Compiled before the page

If outputs aren’t deterministic and can’t show lineage with HIT/MISS across versions, I can’t defend this internally.

objection · fingerprint 6f744b870006001f · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“the same page in produces the same verdict out.”

Champion · Staff Marketing Operations Manager — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Multiple roles latched onto “same page in, same verdict out” plus evidence/lineage framing as making outputs defensible and repeatable under launch pressure.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

No ranked fix is tied to this finding.

W2

Clear routing exists via nav/hero for evaluation paths (ROI, how it works, trust)

Working · Nav zone · medium severity · traced through Champion

1 · Compiled before the page

A guided demo that runs an ad-to-landing-page or email variant simulation end-to-end in under 30 minutes.

evidence need · fingerprint 6f744b870006001f · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Request Access”

Champion · Staff Marketing Operations Manager — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Committee members used nav/hero CTAs and router links (Request Access, ROI, How it works, What makes it trustworthy) to self-direct toward proof and next steps.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

No ranked fix is tied to this finding.

W3

Procurement trust path is discoverable via footer links (Security, DPA)

Working · Footer zone · medium severity · traced through Economic Buyer

1 · Compiled before the page

No compiled trait was traced for this finding.

fingerprint b15b305314651986 · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Footer contains 'Security' and 'DPA' links, which gives me a path to procurement controls.”

Economic Buyer · VP of Demand Gen — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Senior evaluators noted Security and DPA links in the footer, reducing fear of hidden procurement traps and providing a verification route.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

No ranked fix is tied to this finding.

W4

Product category clarity: buying-committee simulation for pre-launch checks

Working · Hero zone · low severity · traced through Security Guardian

1 · Compiled before the page

No compiled trait was traced for this finding.

fingerprint ee9d5ad3faa9e3e8 · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Headline / hero explains 'committee simulation'—I get the product claim.”

Security Guardian · Director of Security — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

More than one role reported quickly understanding what the product is and when to use it (pre-launch buying committee simulation), anchoring the JTBD.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity low

Ranked fix

No ranked fix is tied to this finding.

B1

Proof is claims-first: weak immediate customer/logo/artifact validation

Broken · Hero zone · medium severity · traced through Champion

1 · Compiled before the page

Buyers compare Wynter alternatives on value for money, feature depth, ideal use cases, and pricing transparency.

evidence need · fingerprint 6f744b870006001f · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Trusted by demand gen teams at + NDA design partners”

Champion · Staff Marketing Operations Manager — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Across roles, “trusted by/accuracy/evidence” statements lacked fast, inspectable proof (logos, linked cases, example outputs, downloadable artifacts), creating caution even when interest remained.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

Repaired by fix 3

B2

Navigation is hard to scan (clutter/density slows wayfinding)

Broken · Nav zone · medium severity · traced through Champion

1 · Compiled before the page

Replace subjective internal debates with evidence-backed outputs that are easy to share across Demand Gen, PMM, and RevOps.

goal · fingerprint 6f744b870006001f · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Multiple 'Request Access' CTAs and many competing nav links create mild choice paralysis.”

Champion · Staff Marketing Operations Manager — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Multiple roles described the top nav as cluttered/concatenated and paragraph-like, increasing cognitive load and slowing visitors trying to find proof, trust, or technical routes.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

Repaired by fix 2 and 4 and 5

B3

Technical validation path unclear: no explicit Docs/Architecture entry point

Broken · Nav zone · high severity · traced through Technical Decision Maker

1 · Compiled before the page

API documentation and an end-to-end integration walkthrough showing how GTM sources are ingested and how calibration quality is measured.

evidence need · fingerprint f4a6aff64619ac23 · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“I can't find a 'Developers' or 'Docs' link in the header nav to validate integrations or API docs.”

Technical Decision Maker · Head of Revenue Operations — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Despite API/headless signals, technical evaluators couldn’t quickly locate a clearly labeled Docs/Developers/Architecture route to assess integration scope and data flow.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity high

Ranked fix

Repaired by fix 2

B4

Sales-led gating dominates: “Request Access” repetition reduces self-serve validation

Broken · CTA zone · critical severity · traced through End User

1 · Compiled before the page

No compiled trait was traced for this finding.

fingerprint c0789681a4373404 · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Sales-led gating blocks quick hands-on validation; 'Request Access' is the primary CTA.”

End User · Senior Demand Generation Manager — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Evaluators saw repeated Request Access CTAs without a lightweight preview path, and for some this blocks quick hands-on validation and creates CTA noise/choice friction.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity critical

Ranked fix

Repaired by fix 1

B5

Security and pricing are discoverable but not surfaced early enough

Broken · Nav zone · medium severity · traced through Security Guardian

1 · Compiled before the page

Security trust package covering encryption (TLS 1.2+; AES-256 at rest), tenant isolation, logging (CloudTrail/S3 access logging), vulnerability management, and incident response policy

evidence need · fingerprint ee9d5ad3faa9e3e8 · compiled 2026-08-12

2 · Read in every declared state
Distracted low motivation · low ability
Skeptic high motivation · high scrutiny
Ideal high motivation · high ability
3 · Evidence from the page

“Hero states what the product does... but says nothing about SOC 2, logs, or DPA up front.”

Security Guardian · Director of Security — verbatim from the run file, not rewritten.

4 · What it cost the committee

0 of 50 runs

Security/DPA links exist (noted by EB/GR), but other roles still experienced above-fold trust/pricing uncertainty, indicating signposting/visibility gaps rather than true absence. EB located this path on-page — visibility gap, not absence.

CH TD EB EU GR
Evidence weight

0 of 50 runs

Confidence

low confidence at 20% · sample 50 · severity medium

Ranked fix

Repaired by fix 5

Reproducibility record

Everything needed to re-execute this run and diff the result against it.

Run id
2b9d0a03
Experiment
AN-90670518
Lineage
LN-AN-90670518 · root AN-90670518 · this is the root
Created
2026-08-12T00:40:53.588271+00:00
Schema
v3 · kind LANDING_PAGE_COMMITTEE
Integrity
50 simulations from 50 seeds · 1 stage per seed · roles ch, eb, eu, gr, td
Profiles covered
Distracted (Low Motivation, Low Ability) · Ideal (High Motivation, High Ability) · Skeptic (High Motivation, High Ability)
Persona fingerprints
ch-434a1103 → 6f744b870006001f eb-45e01278 → b15b305314651986 eu-5a5ccb59 → c0789681a4373404 gr-a44d08ba → ee9d5ad3faa9e3e8 td-0b38d7b3 → f4a6aff64619ac23
Compiler
1.1.0-pins

Running a prompt vs running this simulation

Same question · different machinery 50 passes. 5 compiled buyers. 3 behavioural profiles.
A prompt
This simulation
Reader
Invented at answer time, shaped by the phrasing of the question.
5 buyers compiled from market evidence, frozen by fingerprint before the page was opened.
State
One implied state: attentive, reading every word.
3 declared profiles — Distracted, Skeptic, Ideal — every role read under each.
Passes
One. Ask again, get a different critique.
50 independent passes recorded, 10 per role.
Sees
The page. No second person to hand the case to.
The handoffs — 2 of 7 snap, which is where this deal stalls.
Under a finding
An assertion. Nothing to point at.
Compiled trait, role, verbatim line, counted denominator.
Re-run
A new answer, not comparable to the last.
Same fingerprints, same buyers — replayable and diffable.