# Message test — https://www.clari.com/?home_solutions=pipeline After reading your page, only 10 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.clari.com/?home_solutions=pipeline - **Audience tested against:** Clari’s primary ICP is mid-market to large enterprise companies with complex B2B revenue organizations, especially organizations running Salesforce and managing large sales teams, multi-layer forecasting, renewals, and revenue operations: job titles: Chief Revenue Officer, Chief Sales Officer/EVP Sales, VP/SVP Revenue Operations, VP/SVP Sales Operations, VP Sales, Head/Director of Revenue Operations, Head/Director of Sales Operations, GTM Operations leaders. seniority: primarily C-suite, EVP/SVP and VP as economic buyers, with Director-level RevOps/Sales Ops as key champions and administrators; company size: roughly 500–10,000+ employees, with the strongest fit at 1,000+ employee enterprises and a secondary mid-market segment around 200–999 employees, particularly for Groove/sales-engagement use cases; geography: primarily United States and Canada, followed by the UK and Western Europe, with global multinational enterprises also fitting well; industries: strongest in B2B technology/SaaS, cybersecurity, cloud/data infrastructure and other enterprise software, but Clari explicitly targets Technology, Financial Services, Healthcare & Life Sciences, Business Services, and Manufacturing - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/enterprise-revenue-orchestration-clari-3v-vYbk > 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 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 78% | all with reservations | | 3. Value | Do they actually want it? | 14/15 | 74% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 10/15 | 59% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 14/15, 74% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Differentiation.** 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. ### Differentiation **Say what Clari does that Salesforce forecasting does not.** Readers already running Salesforce forecasting and BI could not find a reason to add another layer. In the "Forecasting & Revenue Insights" tab, "See every revenue signal in one view — from CRM to ERP to email" hints at the answer but never lands it. Make it explicit: CRM holds what reps typed in, Clari adds the activity, ERP and email signals CRM never captures, and reconciles them without rep data entry. Name the difference in the heading, not the body. *effort medium · impact high · tested against Give a reason to choose you* **Answer the duplicate-data-entry and workflow-replacement objection directly.** Readers could not tell whether Clari replaces their existing forecasting workflow or adds a parallel one, and asked whether integration means reps key data twice. Add a short block near the platform section stating that Clari reads from Salesforce and writes back to it, that reps keep working in CRM, and which workflow it retires. This is the live blocker for a buyer with an incumbent stack. *effort low · impact high · tested against Answer the live objection* **Put the 3–4% accuracy figure in the hero.** The most persuasive proof on the page — forecasts landing within 3–4% every quarter for two years — is stranded in a rotating testimonial carousel below several abstract sections. Promote it beside the top-line claim, attributed to the named CRO, so the specific number carries the hero instead of "End-to-end pipeline coverage." It also gives the reader a concrete baseline to compare their current forecast variance against. *effort low · impact high · tested against Proof next to the claim* ### Value **Show the methodology behind the ROI figure.** The "roi-stats" block asks the reader to accept a headline ROI number and then sends them elsewhere with "Download the Forrester Study" to find its basis. Put the working next to the number: what was measured, over what period, at what company size, and the before/after baseline. Without that, the unsupported percentage undercuts the credibility the analyst mention and named-customer quotes earn. *effort medium · impact high · tested against Proof next to the claim* ### Clarity **Explain what the AI agents actually do, step by step.** "AI agents monitoring every deal at every stage across all sales motions" is a claim with no mechanism behind it. Readers wanted to know how a forecast is produced and what data feeds it. Replace or follow that hero line with a plain sequence: Clari pulls CRM opportunity records, calendar and email activity, and ERP billing data, scores each deal against how similar deals closed, and flags the ones that moved off track since last week. Name the inputs and the output, not the capability. *effort medium · impact high · tested against Concrete over abstract* **Rewrite "Revenue Context" section into a plain-language description.** "Turn Revenue Data into Action with Revenue Context" plus "Orchestrate revenue by powering AI with the context from every signal, cadence, and workflow so your execution matches how your business operates" is an undefined internal term wrapped in abstraction — a first-time reader has to decode it and gets nothing back. Either define Revenue Context in one sentence in the heading area (what data it holds, where it comes from) or drop the term and say what the platform does with CRM, email and… *effort medium · impact high · tested against Plain language* **Show the product interface near the top, not a stats graphic.** Above the fold the reader gets a tagline, a claim, two CTAs and a "roi-stats" block before any sight of the product; the "clari-platform" image sits far down the page. Move a labelled screenshot of the forecast view — with a caption naming what is on screen, e.g. the commit roll-up and the deals that changed this week — directly under the hero so the reader can see what they'd be using before reading further claims. *effort medium · impact high · tested against Show the product early* **State the problem before the solution in the hero.** The page opens with "The Predictive Revenue System" and "See and Act on Every Revenue Signal" — category label first, problem never named. Lead instead with the pain a revenue leader says out loud: forecasts that miss the number and a pipeline nobody can defend in the board meeting. Put that line above the product claim so the enterprise data trust framing does its work at the top rather than buried mid-page. *effort low · impact medium · tested against Problem before solution* ### Brand alignment (side metric) **Broaden "Global Enterprises Run Revenue with Clari" beyond large enterprise.** That heading, plus "Managing $5T in revenue for 1,500+ customers", tells mid-market and non-SaaS readers the page is not for them. If mid-market is in scope, name segment ranges or show a mid-market customer alongside the enterprise logos; if the fit is defined by sales motion rather than size, say so — for example complex, multi-stakeholder deals — so a manufacturer or infrastructure seller can place themselves. *effort low · impact medium · tested against Name the audience* --- ## 03 · What is working ### The forecasting and pipeline visibility headline lands before the fold Four respondents said the core message — AI-powered forecast accuracy and pipeline visibility for revenue leaders — was clear immediately, with two crediting the tab structure for mapping the offer to specific pain points. One additional respondent said the audience and use case were identifiable quickly through navigation. > It's revenue forecasting and pipeline visibility software that sits on top of Salesforce — basically an AI layer that watches deal signals across CRM/email/ERP to tell you what's real in the pipeline and how accurate your forecast is. > > — Senior VP Sales Operations, Technology/SaaS, 1001-5000 > The named reader is obvious once you hit the tab list: Pipeline Management, Sales Engagement, Forecasting & Revenue Insights, Customer Retention — that's clearly RevOps, sales leaders, and CROs, not individual reps. > > — Senior VP Sales Operations, Technology/SaaS, 1001-5000 ### The 3-4% forecast accuracy number and named customer quotes are what respondents believed Four respondents singled out the 3-4% forecast accuracy figure and the Okta and Checkout.com quotes as the most concrete and persuasive proof on the page, contrasting them favorably with generic ROI language. One described the accuracy claim as decisive if it holds up under scrutiny, and another treated it as the key point to verify. > Honestly, it's the forecast accuracy holding up under scrutiny - if a reference call with someone running multi-motion enterprise deals at our kind of volume confirms that 3-4% variance is real and not cherry-picked, that's the one thing that gets budget moving. > > — VP Sales, Cybersecurity, 5000+ > the BirchStreet quote about forecasts landing "within 3-4% every quarter" is the kind of number that matters to me, not the vague "398% ROI" or "67% don't trust their data" stats, which are just headline bait with no methodology shown > > — Chief Sales Officer, Business Services, 201-500 > The BirchStreet quote — "consistently landing within 3–4% every quarter for the last two years" — is the one specific, checkable claim on the page that would pull this ahead of a competitor > > — Chief Revenue Officer, Business Services, 5000+ --- ## 04 · What the personas said ### Respondents cannot tell what the AI actually does day to day Three respondents said the branding and AI agent claims are never explained mechanically, and two of them explicitly asked for a walkthrough of how a forecast is calculated and what data feeds it. The language reads as claim rather than function. > Phrases like "Predictive Revenue System," "revenue signal," and "Revenue Context" - they sound impressive but don't tell me what the software actually does day to day > > — VP Sales, Cybersecurity, 5000+ > they name an outcome without ever saying what the underlying model does, so "signal" and "agent" become placeholders instead of definitions I can evaluate. > > — VP Revenue Operations, Manufacturing, 501-1000 > The specifics of how the AI actually generates a forecast number or spots churn risk are still fuzzy to me — I'd need a mechanism walkthrough, not just "AI agents monitoring every deal." > > — Head of Sales Operations, Financial Services, 501-1000 ### The page does not answer why this beats the Salesforce forecasting they already run Four respondents raised existing Salesforce and BI tooling as the blocker: one saw no reason to add another layer, one asked how integration avoids duplicate data entry, one wanted documented accuracy improvement against a Salesforce baseline, and one said the page's own comparison to Salesforce native forecasting undermines its case. A fifth could not tell whether the platform replaces workflows or adds another… > I'd need to know what it actually replaces or removes, not just layers on top, because another tool for reps to feed and RevOps to babysit is a real adoption cost > > — Chief Sales Officer, Business Services, 201-500 > A documented forecast-accuracy improvement — actual variance percentage — versus our current Salesforce+BI baseline, from a customer our size, with the methodology shown so I can check it myself, not just quoted in a case study. > > — Director of Revenue Operations, Cloud and Data Infrastructure, 201-500 > I still don't know if the accuracy gain comes from better data aggregation (which we might get cheaper via Salesforce's own forecasting tools or a BI layer) or from genuinely predictive modeling, and that distinction determines whether this is a nice-to-have dashboard or a real step-change. > > — VP Revenue Operations, Manufacturing, 501-1000 ### The problem statement is buried under jargon and sits too low on the page Two respondents said the problem and audience are obscured by layers of branding language, with the enterprise data trust framing placed too far down to do work. ### The 398% ROI claim is not believed because no methodology is shown Five respondents rejected or discounted the ROI and metrics claims as unsubstantiated, calling for methodology, breakdown by company size, and before/after numbers. Two said the BirchStreet case study lacks a comparable company size or verifiable method, and one said the unsupported metrics actively damage the credibility the Gartner mention earns. One would only proceed after a pilot on their own data. > it's a single customer quote with no methodology, so on its own it doesn't rule anything in — I'd need that same kind of number from a business services company my size before it moves me > > — Chief Sales Officer, Business Services, 201-500 > The Forrester "398% ROI" and "landing within 3-4% every quarter" quotes from BirchStreet are the kind of proof that would matter, but I want the methodology behind that ROI number and a reference call with someone at our scale, not just a logo wall. > > — Senior VP Sales Operations, Technology/SaaS, 1001-5000 > that's a customer quote, not my number, so I'd want the Forrester study broken down by company size and industry before I believe it transfers to a 300-person manufacturer. > > — Chief Sales Officer, Manufacturing, 201-500 ### Enterprise positioning reads as excluding mid-market and non-SaaS buyers Three respondents said the brand is calibrated for large enterprise SaaS buyers and does not fit them — specifically a mid-market business services firm, a mid-market manufacturer, and a buyer with infrastructure rather than SaaS sales cycles. One of the three described this as active alienation. > it's clearly calibrated for bigger enterprise than mine — the customer quotes are all "field teams," "CEO and top executives," big bookings growth numbers, which reads more Fortune 500 than a 201-500 person business services firm > > — Chief Sales Officer, Business Services, 201-500 > The tone is written for a VP of RevOps or CRO at a big-logo enterprise, not a 300-person EU manufacturer — the case studies are fintech/SaaS names > > — Chief Sales Officer, Manufacturing, 201-500 > it's clearly calibrated for a SaaS/subscription-revenue buyer, not cloud/data infrastructure with long channel-partner sales cycles, so it feels adjacent to my world > > — VP Sales, Cloud and Data Infrastructure, 5000+ ### The audience is inferred from logos and job titles, never stated Four respondents said they worked out who the page is for from customer logos and quoted testimonial titles rather than any explicit positioning statement. None treated this as fatal, but all flagged it as inference on their part. > The audience is implied rather than stated outright — it's clearly sellers, sales managers, RevOps, and CROs, and that's backed up by the customer quotes being from a VP of Field Strategy, Head of Revenue Ops, and a CRO — so I inferred the reader from role titles in testimonials, not from an explicit "this is for you if..." statement. > > — Head of Sales Operations, Financial Services, 501-1000 > the customer logos (Okta, Checkout.com) and quoted titles (VP of Field Strategy, Head of Revenue Ops, CRO) make it obvious this is aimed at RevOps/sales leadership at large enterprises, not reps > > — Head of Sales Operations, Healthcare and Life Sciences, 501-1000 --- ## 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 loses the deal at the only question that matters — displacement of Salesforce — and no amount of headline clarity recovers it.** *(high)* Five of 15 respondents named existing Salesforce and BI tooling as the blocker: no reason to add a layer, unclear duplicate data entry, no documented accuracy lift against a Salesforce baseline, and one who said the page's own Salesforce comparison undermined its case. A fifth could not tell whether it replaces or adds workflow. Meanwhile only 3 of 15 credited the headline landing before the fold. The clearest thing on the page is the thing that does not decide the purchase. - **The two biggest numbers on the page work against each other: the 398% ROI actively drags down the 3-4% accuracy figure that was earning belief.** *(high)* Four respondents rejected the ROI claim as unsubstantiated and demanded methodology, size breakdowns and before/after data, with one saying the unsupported metrics damage the credibility the Gartner mention earns. Separately three respondents named the 3-4% accuracy figure and the Okta and Checkout.com quotes as the most persuasive proof precisely by contrast with generic ROI language. The page is spending its credible proof to subsidise an incredible one. - **Nothing on the page survives contact with diligence — every proof point respondents valued was treated as a hypothesis to be verified elsewhere.** *(high)* One respondent would only proceed after a pilot on their own data; two said the BirchStreet case study lacks comparable company size or verifiable method; and among those who praised the 3-4% accuracy number, one called it decisive only if it holds up under scrutiny and another treated it as the key thing to verify. Belief is conditional across the board. - **The page fails to qualify anyone in or out, so buyers self-disqualify on the wrong grounds.** *(high)* Four respondents had to reverse-engineer the audience from customer logos and testimonial job titles because no positioning statement exists, and two said the problem statement and audience are buried under branding language with the enterprise data trust framing sitting too low to work. The result: three respondents concluded the brand is calibrated for large enterprise SaaS and does not fit them, one calling it active alienation. Absent an explicit statement, the logos do the qualifying, and… - **The page markets an AI agent it never demonstrates, leaving the core differentiator unevaluable.** *(medium)* Three respondents said the branding and AI agent claims are never explained mechanically, and two asked outright for a walkthrough of how a forecast is calculated and what data feeds it. That same gap is why four could not judge integration, duplicate data entry, or accuracy lift against their Salesforce baseline — you cannot compare a mechanism that was never shown. - **Clarity was measured on the headline and nowhere else, and the page confuses being understood with being convincing.** *(medium)* Three respondents found the forecast-accuracy and pipeline-visibility headline immediately clear and credited the tab structure, yet three others could not tell what the AI does day to day and two found the problem statement obscured by branding layers. The top of the page reads cleanly; the substance underneath does not. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Sales Officer | Business Services | 201-500 | | 2 | VP Revenue Operations | Manufacturing | 501-1000 | | 3 | Senior VP Sales Operations | Technology/SaaS | 1001-5000 | | 4 | VP Sales | Cybersecurity | 5000+ | | 5 | Director of Revenue Operations | Cloud and Data Infrastructure | 201-500 | | 6 | Head of Sales Operations | Financial Services | 501-1000 | | 7 | GTM Operations Leader | Healthcare and Life Sciences | 1001-5000 | | 8 | Chief Revenue Officer | Business Services | 5000+ | | 9 | Chief Sales Officer | Manufacturing | 201-500 | | 10 | VP Revenue Operations | Technology/SaaS | 501-1000 | | 11 | Senior VP Sales Operations | Cybersecurity | 1001-5000 | | 12 | VP Sales | Cloud and Data Infrastructure | 5000+ | | 13 | Director of Revenue Operations | Financial Services | 201-500 | | 14 | Head of Sales Operations | Healthcare and Life Sciences | 501-1000 | | 15 | GTM Operations Leader | Business Services | 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-08-21, then deleted along with the personas and their answers.