# Message test — https://www.silobreaker.com/ After reading your page, only 0 of 15 personas could quickly tell what problem it solves and who it is for. - **Page tested:** https://www.silobreaker.com/ - **Audience tested against:** Chief Risk Offers, Chief Intelligence Officers, Chief Security Officers, and to an extent CISOs - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/silobreaker-decision-intelligence-for-security-njQsZ24 > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 15/15 | 79% | 1 without hesitation, 14 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 0/15 | 22% | — | | 3. Value | Do they actually want it? | 12/15 | 67% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 4/15 | 39% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 3/15, 33% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Relevance.** Earliest failing layer, walking the sequence in order — not simply the lowest score. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Relevance **Rewrite the hero headline to name the job: producing intelligence reports on cyber, geopolitical and physical risk.** "Intelligence for people who think" and the "posturing. noise. panic." lines say nothing about what a reader does all day. Put the actual task in the headline so a threat intelligence lead recognises their own work. *effort medium · impact high · tested against Lead with the use case* **Replace the hero strapline with one sentence naming the problem: fragmented feeds and manual report writing.** The page presents an answer before naming any pain a reader already feels. Open with the reporting burden and scattered sources analysts deal with today, then say what the product does about it. *effort medium · impact high · tested against Problem before solution* **Add a subhead under the hero naming the buyer: threat intelligence teams, analysts and CISOs.** The audience only becomes clear from logos and case studies far down the page. Say who this is for in the first screen instead of making readers infer it. *effort low · impact high · tested against Name the audience* ### Differentiation **Add a line under the hero stating what Silobreaker covers that single-domain threat feeds do not.** Nothing here would stop a reader assuming Recorded Future or Dataminr says the same thing. Name the specific scope, cyber plus geopolitical plus physical risk in one workflow, as the reason to pick you. *effort medium · impact high · tested against Give a reason to choose you* **Replace "Decision-grade, defensible outputs" with a concrete description of the report a user produces.** "Decision-grade" and "finished intelligence" are undefined terms that any competitor could print. Describe the output itself, a sourced briefing traceable to requirements, so readers can judge it. *effort medium · impact high · tested against Plain language* **Add a product screenshot or short walkthrough above the customer logos.** A reader scrolls through three claim lines and a logo wall before seeing anything the product actually does. Show the interface producing a report early so the difference is visible, not asserted. *effort medium · impact high · tested against Show the product early* ### Value **Add baseline and timeframe beside the 90% reporting-time claim in the case study card.** "Reduces reporting time by 90%" gives no starting point or measurement period, so readers discount it. State hours before and after and over what period. *effort low · impact high · tested against Proof next to the claim* ### Clarity **Add two lines under the hero describing how sources are ingested and turned into reports.** The page never says what happens between raw feeds and a finished report. Describe the steps a user takes, from setting requirements to publishing, in plain words. *effort medium · impact high · tested against Tie the feature to the outcome* ### Brand alignment (side metric) **Cut "posturing. noise. panic." and the "people who think" line from the hero.** The atmospheric opening reads as agency copy to analysts and CISOs and delays comprehension. Replace it with a flat statement of what the product does for intelligence teams. *effort low · impact high · tested against Concrete over abstract* **Break the run-on strapline into two short claims written in analyst language.** "Decision-grade intelligence, cross-domain by design, built for the analyst, trusted by the executive, defensible at the board" stacks five abstractions with no content. Say what the analyst gets and what the board sees, in separate plain sentences. *effort medium · impact medium · tested against Headings stand alone* **Remove the placeholder "I am a button" elements from the hero.** Unfinished placeholder text next to serious claims undercuts credibility with risk buyers. Leave one demo request button. *effort low · impact medium · tested against One clear next action* --- ## 03 · What is working ### The two hard numbers were the only things respondents could repeat back Respondents named the 90% reporting-time reduction and 70,000 suppliers covered as the sole memorable, credibility-anchoring takeaways from the page. > that 90% reporting-time reduction stat and the "70,000 suppliers" line stuck with me as the actual proof points, everything else was just "decision-grade intelligence" fluff. > > — VP of Intelligence, Financial Services, 1001-5000 > The "90% reduction in reporting time" and "70,000 suppliers" numbers are the only concrete things that stuck, everything else was mood copy > > — Senior Chief Risk Officer, Technology, 5000+ ### The customer outcomes map directly onto respondents' own third-party risk work Four points say the case study metrics and feed consolidation would materially change procurement and reporting time, with two calling them sufficient to warrant a first call. > If it actually did what the "70,000 suppliers" case study implies — consolidating cyber, geopolitical and physical signals into one workflow so my team isn't stitching together three tools and a spreadsheet > > — Director of Risk, Technology, 501-1000 > If the 90% reporting-time reduction and the 70,000-supplier figure are real and repeatable, that's genuinely a change > > — Senior Chief Risk Officer, Technology, 5000+ --- ## 04 · What the personas said ### The page never explains how the product turns risk signals into outputs Eleven points say the top-of-page copy stacks abstract nouns and adjectives with no mechanism, no product description, and no explanation of data processing or cross-domain integration. Terms like 'decision-grade' and 'finished intelligence' were called… > I can't tell you how it ingests sources, what the analyst UI looks like, or how it differs from Recorded Future or Flashpoint > > — Director of Risk, Technology, 501-1000 > the homepage itself is thin on mechanism — lots of "decision-grade," "defensible outputs" language without explaining how it ingests, correlates, or scores data > > — Chief Risk Officer, Government, 5000+ > the top-of-page copy ("posturing. noise. panic.") is just fluffy positioning and doesn't tell me what it actually does > > — Chief Intelligence Officer, Energy, 501-1000 > It was the run of abstract nouns strung together with no verb or subject doing anything to anyone - "posturing. noise. panic." and then "Decision-grade intelligence, cross-domain by design, built for the analyst, trusted by the executive, defensible at the board" - that's five clauses stacked with commas and no single sentence telling me what the tool does or who it's for. > > — Chief Information Security Officer, Critical Infrastructure, 1001-5000 > I'd still want to know what "one structure across domains" actually means technically before I'd take this further > > — Senior Chief Risk Officer, Technology, 5000+ > "decision-grade," "finished intelligence," "cross-domain by design" are all defined-sounding terms that are never actually defined > > — Director of Risk, Financial Services, 501-1000 ### Audience and problem are inferred from logos and case studies, never stated in the hero Nine points say the buyer persona and pain point only become clear from the social proof and customer-proof sections. The opening tagline actively blocked immediate problem comprehension. > Not obvious at all — the hero copy is just fragments ("posturing. noise. panic. Intelligence for people who think") and then a dense line about "decision-grade intelligence, cross-domain by design" that reads like a tagline, not a problem statement. > > — Senior Chief Risk Officer, Critical Infrastructure, 5000+ > The reader is never explicitly named ("you are a threat intel analyst at a bank" or similar); I inferred it from the logos and case-study labels, not from a direct statement. > > — VP of Intelligence, Financial Services, 1001-5000 > the hero copy ("posturing. noise. panic. Intelligence for people who think") is just tone-setting fluff, no problem statement, no named audience > > — Chief Intelligence Officer, Energy, 501-1000 > It wasn't until I hit the customer proof section - "Global financial services firm scales third-party intelligence analysis across 70,000 suppliers" and "UK government department reduces reporting time by 90%" - that the actual use case and audience (intelligence/security teams at large enterprises and government) became clear. > > — Chief Information Security Officer, Critical Infrastructure, 1001-5000 > Not obvious at all up top — the opening is just "posturing. noise. panic. Intelligence for people who think," which is atmosphere, not a problem statement > > — Senior Chief Risk Officer, Technology, 5000+ > The closest thing to a problem statement is buried in the customer snippets — "UK government department reduces reporting time by 90%" and "scales third-party intelligence analysis across 70,000 suppliers" > > — Director of Risk, Financial Services, 501-1000 > So the reader (security/intel analysts and their executives) is inferred from social proof, not stated outright, and the problem — turning fragmented threat data into fast, board-ready reporting — only becomes clear once you scroll past the slogans. > > — VP of Intelligence, Government, 1001-5000 ### The 90% claim is not believed without a baseline or methodology Four points withhold belief in the time-savings figure pending measurement detail, baseline, or sector-specific validation. One asked for a live supplier-scoring walkthrough before committing. > the page gives me the headline stat and customer quotes but nothing on methodology, and I've been burned before by vendor-supplied case studies that don't hold up under questioning > > — Chief Risk Officer, Government, 5000+ > The "reduces reporting time by 90%" line is the one number that would make me pick up the phone, but it's attributed to a UK government department, not an energy peer > > — Chief Intelligence Officer, Energy, 501-1000 > I'd walk in wanting to see the actual workflow for scoring and prioritising 70,000 suppliers, not just the headline stat, because "decision-grade" and "90% faster" are exactly the kind of claims that need a live demo with my own use case before I believe them. > > — Chief Information Security Officer, Critical Infrastructure, 1001-5000 > I still don't know the mechanism behind "UK government department reduces reporting time by 90%" — 90% of what baseline, measured how, over what volume of reports? > > — Director of Risk, Financial Services, 501-1000 ### Only the unverified numbers separate the page from Recorded Future and Dataminr Eight points say the marketing language mimics competitors and that differentiation rests entirely on the stats. Anonymised case studies with no published methodology were named as the gap a competitor could exploit immediately. > they're unsourced one-liners with no named customer, no methodology, and no baseline ("90% of what, measured how?") > > — Senior Chief Risk Officer, Critical Infrastructure, 5000+ > Everything else — "decision-grade intelligence," "defensible at the board" — is category language every vendor in this space uses, so it wouldn't differentiate this one from the alternatives > > — VP of Intelligence, Financial Services, 1001-5000 > there's no detail behind that case study, no metric, nothing to compare against what I already run > > — Chief Intelligence Officer, Energy, 501-1000 > both are anonymised case studies with no methodology - I can't tell if "scales across 70,000 suppliers" means automated scoring or just a bigger database, and none of the testimonials mention third-party/supply-chain risk specifically, they're mostly generic cyber threat intel comments. > > — Chief Information Security Officer, Critical Infrastructure, 1001-5000 > what would tip it my way is a named reference customer of comparable scale I could actually call, not just a quoted case study snippet > > — Senior Chief Risk Officer, Technology, 5000+ > If a competing vendor's page showed me the same case study but with a paragraph on what "90%" actually measures — reports per week before/after, headcount, what counts as "finished intelligence" — that would win the shortlist on the spot > > — Director of Risk, Financial Services, 501-1000 > But as it stands it wouldn't decide anything on its own — there's no mechanism behind the 90% (what was their baseline, manual process before?) and no detail on whether "one structure" means a real integrated data model or just a shared dashboard on top of three tools. > > — VP of Intelligence, Government, 1001-5000 ### The tone reads as general-audience agency copy, not writing for analysts and CISOs Four points call the opening tone poetic or atmospheric and misaligned with risk buyers, with one noting it addresses executive sign-off rather than budget-holder accountability. > the opening "posturing. noise. panic. Intelligence for people who think" feels like it's aimed at a CMO or a brand consultant, not an analyst or CISO deciding whether to trust this with supplier risk scoring > > — Chief Information Security Officer, Critical Infrastructure, 1001-5000 > the tone up top — "posturing. noise. panic. Intelligence for people who think" — reads like it was written by a brand agency trying to sound sharp for a general audience, not for an analyst or a VP > > — VP of Intelligence, Energy, 1001-5000 > I get "Intelligence for people who think" and "decision-grade... defensible at the board" — that's aspirational branding aimed at whoever signs off on vision, not the person who has to justify the line item > > — Senior Chief Risk Officer, Technology, 5000+ > Tone's too poetic ("noise, panic") for a risk buyer like me. > > — Chief Risk Officer, Energy, 5000+ --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page's entire memorability rests on two numbers that a separate theme shows are disbelieved.** *(high)* Only the 90% and 70,000 figures were repeatable (2 respondents), while 4 withhold belief in the 90% claim absent baseline or methodology. The single recall hook and the single credibility failure are the same asset. - **Differentiation collapses the moment a competitor publishes methodology.** *(high)* Eight points say the language mimics Recorded Future and Dataminr and that only the stats separate the page, and four points already refuse those stats without a baseline. Anonymised case studies were named as the exploitable gap. - **The hero section is a net liability that the rest of the page has to repair.** *(high)* Eight points say audience and problem only emerge from logos and case studies, with the tagline actively blocking problem comprehension; eleven points find no mechanism in top-of-page copy. Work happens downstream of where buyers quit. - **The page sells outcomes it never proves it can produce.** *(high)* Four points say the case study metrics would materially change their procurement and reporting work, yet eleven points report no explanation of how risk signals become outputs or how data is processed across domains. Desire without a credible path to delivery. - **Vocabulary choices signal the wrong buyer entirely.** *(medium)* Four points call the opening poetic and misaligned with analysts and CISOs, while eleven flag abstract nouns like 'decision-grade' and 'finished intelligence' as empty. The register and the substance fail together, compounding rather than offsetting. - **The strongest asset on the page is buried where it cannot do commercial work.** *(medium)* Four points found case study metrics compelling enough that two would take a first call, but eight points say those same sections are where audience and pain point are first inferred. The page's only persuasive content is doing orientation work instead. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Senior Chief Risk Officer | Critical Infrastructure | 5000+ | | 2 | Director of Risk | Technology | 501-1000 | | 3 | VP of Intelligence | Financial Services | 1001-5000 | | 4 | Chief Risk Officer | Government | 5000+ | | 5 | Chief Intelligence Officer | Energy | 501-1000 | | 6 | Chief Information Security Officer | Critical Infrastructure | 1001-5000 | | 7 | Senior Chief Risk Officer | Technology | 5000+ | | 8 | Director of Risk | Financial Services | 501-1000 | | 9 | VP of Intelligence | Government | 1001-5000 | | 10 | Chief Risk Officer | Energy | 5000+ | | 11 | Chief Intelligence Officer | Critical Infrastructure | 501-1000 | | 12 | Chief Information Security Officer | Technology | 1001-5000 | | 13 | Senior Chief Risk Officer | Financial Services | 5000+ | | 14 | Director of Risk | Government | 501-1000 | | 15 | VP of Intelligence | Energy | 1001-5000 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-09-17, then deleted along with the personas and their answers.