# Message test — https://worven-identity-review.indigo-hq.com/site/ After reading your page, only 1 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://worven-identity-review.indigo-hq.com/site/ - **Audience tested against:** Mid-market ecom Brands and agencies; heads of marketing, CMOs, CEO's at 5-50-100 person co ($2-10M rev agencies; $25-75M+ brands) - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/worven-hq-installation-for-brands-and-agencies-tw8pUIM > 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? | 11/15 | 38% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 12/15 | 67% | all with reservations | | 3. Value | Do they actually want it? | 8/15 | 52% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 1/15 | 26% | with reservations | **Brand alignment** (a side metric, not one of the four layers) — 4/15, 37% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Value.** Earliest failing layer, walking the sequence in order — not simply the lowest score. ### What they thought you sell 3 of the personas who named a category got it wrong: - 1× “HQ implementation/onboarding consultancy” - 1× “Implementation/onboarding consulting service” - 1× “Software implementation / onboarding consultancy” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Raise the 30-day fix guarantee into the hero.** The guarantee is the only thing on the page readers could name as separating Worven from an alternative, yet it is buried as a single sentence after the "Larger installs" block. Put it in the hero next to "Starting at $5K" and the timeline, phrased as the risk the buyer is actually holding: if the install is wrong, it gets fixed at no cost for 30 days. *effort low · impact high · tested against Give a reason to choose you* **Rewrite section headings to carry their point unaided.** Scanning only the headings — "HQ Install", "Starting scope", "Larger installs", "After the install" — gives a process outline and no reason to choose Worven. Rewrite them so each states its conclusion: the install is done when your team can run it without us; fixed starting price, defined larger scope; the founders deliver it themselves. A reader who reads nothing but headings should finish with the argument. *effort medium · impact medium · tested against Headings stand alone* **Say why founder-delivered installs beat an agency team.** "The people you meet do the work" and the Matt and Mike bios build credibility but never draw the competitive conclusion. State it: no account manager handoff, no junior implementer, the person who scoped the install is the person who delivers and trains. That is a claim a larger competitor cannot copy, and right now the reader is left to infer it from two biographies. *effort low · impact medium · tested against Give a reason to choose you* ### Value **Add one named client outcome beside the $5K price.** "Starting at $5K" and "3 to 6 weeks" are the only hard facts on the page, and readers said price and timeline alone cannot justify a budget commitment. Put a short, attributed result next to the pricing block — a named brand or agency, the workflow installed, and what changed measurably after (review prep time, decisions with recorded owners, weeks to first live workflow). *effort high · impact high · tested against Proof next to the claim* **Attach a measured outcome to each of the three examples.** "Client operating brief", "Weekly operating review" and "Decision follow-through" describe capabilities and stop. Readers said these read as workflows already covered by CRM and shared drives. Each card should say what running it in HQ changed — the review now runs from one approved source instead of three exports, every decision now carries an owner and a date — so the feature carries a consequence rather than a label. *effort medium · impact high · tested against Tie the feature to the outcome* **Back the 30-day fix guarantee with completed-install evidence.** "If the agreed setup or handoff is wrong, Worven fixes it for 30 days" is the strongest line on the page but sits unsupported, and readers flagged that an unproven track record weakens it. Put the number of installs completed, or one line about a handoff that was corrected under the guarantee, immediately beside it rather than leaving the promise to stand alone. *effort medium · impact high · tested against Proof next to the claim* ### Clarity **Show HQ before describing the install process.** Everything above "After the install" is process: configure, launch, activate, scope. Nothing shows the product. Put a screenshot or a concrete before/after of one HQ company — the weekly operating review view, say — near the top so a reader can see what they are buying before reading five sections of methodology. Right now the service reads as onboarding consulting rather than a tool being installed. *effort medium · impact high · tested against Show the product early* **State what HQ is in the first two lines.** "We install HQ for brands and agencies" assumes the reader already knows what HQ is. Readers finished the page unable to say whether HQ is a database, a dashboard, an AI tool or a template. Add a plain-language clause directly under the H1 naming the category and what it holds — e.g. that HQ is the workspace where a company's people, sources and recurring workflows live, and that Worven configures it. The page currently describes only the install process, so the object being installed never… *effort low · impact high · tested against Concrete over abstract* **Define Builder, Inheritor and Lite User at first use.** The "Activate each role" block uses Builder, Inheritor and Lite User as if they were common terms, and the FAQ repeats them without ever defining them. Readers had to decode them. Gloss each one inline the first time it appears — the person who builds and changes the workflow, the person who runs and recovers it day to day, the person who only consumes the output — rather than leaving the definitions to be inferred from "learn to govern and change it". *effort low · impact medium · tested against Plain language* ### Relevance **Move the recurring-work problem above the install mechanics.** The line that names the reader's actual pain — "Start with work your team already runs" and the inconsistent-review examples — sits below the entire HQ Install process block. The opening does name the audience well, so keep it, but lift the problem statement directly under it: the same review run differently every week, decisions with no recorded owner, files scattered across drives. Then let the install steps answer it. *effort medium · impact high · tested against Problem before solution* ### Brand alignment (side metric) **Answer the two-person-shop objection with capacity facts.** Readers read the page as an early-stage shop that cannot scale, and nothing on the page contradicts them. Add a line to the FAQ stating installs completed to date, how many run concurrently, and what happens when a client needs support after handoff — "HQ Managed Success" is mentioned once in passing and never explained as continuity. Answer the durability question rather than leaving it open. *effort medium · impact high · tested against Answer the live objection* **Remove the mockup and no-launch-authorization banner.** The top line "Provisional website mockup · brand and copy evaluation only · no launch authorization", the "Plan your HQ Install · mockup" button and the "Built in HQ ×" fragment all read as internal draft artifacts left on a public page. They signal pre-launch status and were enough for readers to rule the vendor out for serious evaluation. Strip them and let the CTA read as a live offer. *effort low · impact high* **Rewrite the rebrand FAQ to lead with partner status.** "Worven is the agency rebrand of Enterprise Vibe Code" plus the aside about Mike Lady's media and publishing platform reads as an operation still sorting out its identity. Lead the answer with the fact that matters — Worven is an approved HQ partner, with the approval date or partner tier — and reduce the rebrand and the separate media property to a single trailing clause. *effort low · impact medium · tested against Answer the live objection* --- ## 03 · What is working ### The opening lines name the audience and the onboarding pain point, and respondents… Six respondents said the target audience and the recurring workflow or onboarding problem were immediately obvious from the first lines of the page. This was the most consistently positive reaction in the test. > The examples under "Start with work your team already runs" (agency delivery brief, weekly ops review, decision follow-through) made the target reader obvious too — it's brands/agencies with recurring, owner-less workflows, which is basically us. > > — Director of Marketing, Marketing and Advertising, 11-50 > the examples under "Start with work your team already runs" (client operating brief, weekly operating review, decision follow-through) made the target reader concrete: agency/brand ops leads with recurring, owned workflows > > — Vice President of Marketing, E-commerce, 51-200 > It's fairly quick to spot who this is for — "We install HQ for brands and agencies" is the second line on the page > > — Chief Marketing Officer, Marketing and Advertising, 11-50 > the "HQ Install" section spells it out: "HQ arrives blank. We configure one company around a recurring job" and the install is "complete when your team can govern it, run it, recover it, and use the result without us." > > — Head of Marketing, E-commerce, 51-200 ### The 30-day fix guarantee is the one differentiator respondents could name Four respondents identified the 30-day fix guarantee as concrete risk mitigation and the only thing separating this from competitors. Three of them explicitly called it the only differentiator on the page. One qualified it: an unproven track record undermines the guarantee. > The one thing that would tip it my way is the "if the agreed setup or handoff is wrong, Worven fixes it for 30 days" line — that's a concrete guarantee, not fluff, and it lowers the risk of the $5K bet. Against that, "Matt and Mike scope and deliver every HQ Install themselves" would actually rule it out for me at scale — two named people doing every install personally isn't a business I trust to still exist > > — Director of Marketing, Marketing and Advertising, 11-50 > "if the agreed setup or handoff is wrong, Worven fixes it for 30 days" — that's an actual accountability mechanism, not marketing fluff, and it's the kind of clause I'd compare line-by-line against any competitor's SLA. > > — CEO, Marketing and Advertising, 11-50 > The "30 days to fix it if the handoff is wrong" line is the one thing that would actually tip me toward this over a competitor — it's a concrete commitment, not marketing fluff, and it tells me who eats the risk if the install fails > > — Chief Marketing Officer, Digital Commerce, 201-500 > The "30 days" fix line — "If the agreed setup or handoff is wrong, Worven fixes it for 30 days" — is the only concrete risk-mitigation on the page, so it's a small point in their favor versus a competitor with zero guarantee. > > — Senior Marketing Manager, Retail, 501-1000 ### Naming the founders and their experience did credibility work, but respondents wanted… Two respondents said the named founders with verified ops and software experience create accountability and strengthen credibility against competitors. A third said the founder names build credibility but lack case-study proof of impact. > The one thing that would tilt me toward this over a faceless competitor is the "If the agreed setup or handoff is wrong, Worven fixes it for 30 days" line and the fact that it's two named people, Matt and Mike, with specific credentials > > — Senior Marketing Manager, E-commerce, 51-200 > The tone does feel like it's written for someone like me — direct, low-fluff, no fake urgency or "10x your ROI" hype, which I respect — but it reads more like two smart operators explaining their process carefully than a company that's sold this fifty times > > — Director of Marketing, Digital Commerce, 201-500 > Mike's "shipped production software at a Fortune 500 for twelve years" and Matt's "ten years across brands, agencies, and operations." That's concrete accountability, not a logo wall > > — Vice President of Marketing, E-commerce, 51-200 --- ## 04 · What the personas said ### Respondents finished the page unable to say what HQ actually is or does Seven respondents said the page explains the onboarding and implementation process but never the product itself — they could not tell whether HQ is a database, dashboard, AI tool, or template, and its category and technical foundation are never named. One noted the service reads as implementation and onboarding rather than the tool. Internal jargon such as Builder, Inheritor, and Lite User is used without… > So it's basically implementation/onboarding services for a tool called HQ, not the tool itself. I'd call it an "HQ implementation/setup service" or onboarding consultancy. > > — Senior Marketing Manager, Retail, 501-1000 > Honestly the "HQ" part is fuzzy to me — I couldn't tell you what HQ actually does day-to-day (is it a PM tool? a dashboard? an AI system?) > > — Head of Marketing, Retail, 501-1000 > every verb is about the install process, never a sentence like "HQ stores X" or "HQ automates Y," so I never get what the software actually is. > > — Director of Marketing, Marketing and Advertising, 11-50 > the page never actually says what HQ does functionally beyond vague words like "govern it, run it, recover it" > > — CEO, Marketing and Advertising, 11-50 > I still don't actually know what HQ does day-to-day (is it a CRM competitor? a project tracker? an AI ops layer?), since the page never explains the underlying mechanism, just the install process around it. > > — Senior Marketing Manager, E-commerce, 51-200 > they treat it as a proper noun everyone already understands, but never once define it as a category (software, database, framework) > > — Vice President of Marketing, E-commerce, 51-200 > "HQ" is never defined as software, platform, or system, it's just capitalized and treated as known, and then "Install," "Builder," "Inheritor," "Lite User," and "Configure/Launch/Activate" get stacked on top like internal jargon I'm supposed to already understand > > — Head of Marketing, Retail, 501-1000 > the copy never says whether it's a database, a dashboard, an AI layer, or just a fancy project template, so I'm left guessing at the noun > > — Director of Marketing, Digital Commerce, 201-500 ### The problem being solved is buried under process, and nothing shows it has been solved… Two respondents said the actual problem sits three sections deep beneath process description, and that no client names or case studies demonstrate the inconsistent-reviews problem has been fixed. This sits alongside the positive reaction to the opening lines: the audience is named, the evidence is not. > the actual problem being solved is buried under three sections of process description (Configure, Launch, Activate) before you hit concrete use cases > > — Head of Marketing, Retail, 501-1000 ### Every respondent who commented on value said the page has no proof — no metrics, no… Six respondents independently flagged the total absence of evidence: no case studies, no client references, no measured outcomes, no before/after numbers. One said the pricing and timeline alone cannot justify a budget commitment without proof. One added that the examples given describe workflows already covered by existing CRM and shared drives. > I'd want a concrete before/after example (e.g. "client review cycle went from 4 touchpoints across email/Slack to 1 tracked decision log") before I'd spend Matt and Mike's 3-6 weeks > > — CEO, Marketing and Advertising, 11-50 > I'd want them to name the actual mechanism (what does HQ replace or absorb — my CRM, Slack, a shared drive?) and show one before/after example with real time-saved numbers, not just "3 to 6 weeks" and a starting price. > > — Senior Marketing Manager, E-commerce, 51-200 > "3 to 6 weeks" and "$5K starting" for one workflow is a proof-of-concept price, not a transformation, and the page never tells me what HQ actually is day-to-day, so I can't judge if the underlying tool is worth building on > > — Chief Marketing Officer, Digital Commerce, 201-500 > no named customers, no logos, no case study saying "a 500-person retail team went from chaos to X in 6 weeks." > > — Head of Marketing, Retail, 501-1000 > the three examples they gave (client operating brief, weekly review, decision follow-through) are exactly the things I already patch together today > > — Director of Marketing, Digital Commerce, 201-500 > No named client, no before/after numbers, so I'm not moving budget on it yet. > > — Vice President of Marketing, Retail, 501-1000 > But "worth a meeting" hinges on proof I don't have yet — no case study, no before/after numbers, no sense of what "recovering" a workflow actually looks like when something breaks > > — Director of Marketing, Marketing and Advertising, 11-50 ### Visible internal draft and provisional mockup labels made respondents treat the vendor… Four respondents flagged the internal draft status note and provisional website mockup label as visible on the public page. They read these as signalling pre-launch status, undermining credibility, and one said it makes the vendor unsuitable for serious evaluation. > the flat "Provisional website mockup · brand and copy evaluation only · no launch authorization" line at the top is odd — that's an internal note, not copy meant for me > > — Vice President of Marketing, E-commerce, 51-200 > "Provisional website mockup" at the top is a red flag; if I'm shortlisting real vendors, one still marked as a mockup gets dropped for that reason alone > > — Chief Marketing Officer, Digital Commerce, 201-500 > the page itself is flagged "Provisional website mockup" at the top, which is honestly a strange thing to leave visible. > > — Chief Marketing Officer, Marketing and Advertising, 11-50 ### The brand reads as an early-stage two-person shop that cannot scale Three respondents described the operation as an early-stage, pre-team, two-person shop still building in public, lacking established firm credibility and not reading as a company that scales. One separately said the rebranding from Enterprise Vibe Code creates distrust. > Small, very early-stage outfit — two named guys, Matt and Mike, doing the scoping and delivery themselves, not a team behind a brand > > — Chief Marketing Officer, Digital Commerce, 201-500 > I picture two guys and a laptop, not a company — the page even confirms it: "Matt and Mike scope and deliver every HQ Install themselves." > > — Head of Marketing, Retail, 501-1000 > rebranded from something called "Enterprise Vibe Code" per that FAQ answer — which is a weird enough detail that it actually made me trust it less, not more > > — Head of Marketing, Retail, 501-1000 > the "mockup · brand and copy evaluation only · no launch authorization" line at the top actually tips me off that this isn't even fully live yet — it feels like an early-stage build-in-public thing > > — Head of Marketing, E-commerce, 51-200 --- ## 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 sells an implementation process for a product it never defines, so nothing else on the page can be evaluated.** *(high)* Seven of 15 could not say whether HQ is a database, dashboard, AI tool, or template, and said the copy describes onboarding rather than the tool (theme 0). The problem statement sits three sections deep beneath that process description (theme 1). A buyer cannot price, compare, or approve a purchase for an unnamed category. - **Zero evidence appears anywhere on the page, which converts the entire value argument into an assertion.** *(high)* Six respondents independently flagged no case studies, no client references, no measured outcomes, no before/after numbers, and one said pricing and timeline alone cannot justify budget (theme 2). Theme 1 confirms no client names demonstrate the inconsistent-reviews problem has been fixed. Seven of 15 total registered the absence — the largest negative signal in the test. - **The two things the page does well are both structurally cancelled by the missing proof, so the positives generate no net credibility.** *(high)* The 30-day guarantee was named the only differentiator by three of the four who cited it, and one said an unproven track record undermines it (theme 6). Founder names build credibility but a respondent said they lack case-study proof of impact (theme 7). Both assets depend on evidence that theme 2 shows does not exist on the page. - **Publishing internal draft and mockup labels cost the vendor consideration outright, not just polish points.** *(high)* Four respondents saw the internal draft status note and provisional website mockup label as public, read them as pre-launch, and one said the vendor is unsuitable for serious evaluation (theme 3). Three more read the operation as a pre-team two-person shop that does not scale, with the rebrand from Enterprise Vibe Code creating distrust (theme 4). Six respondents arrived at disqualification from surface artefacts before assessing the offer. - **The page fails to establish that anything is being sold beyond what buyers already own.** *(high)* A respondent noted the examples describe workflows already covered by existing CRM and shared drives (theme 2), and the only named differentiator is a guarantee, not a capability (theme 6). With the product category unnamed (theme 0), there is no answer to why a buyer would replace tools already in place. - **The strongest result on the page — audience recognition — reached only a third of respondents and delivers nothing downstream.** *(medium)* Theme 5 is described as the most consistently positive reaction in the test, yet it registered with five of 15 at 0.58 confidence. Theme 1 states the audience is named but the evidence is not. Recognition of a pain point that is then buried under process and unsupported by outcomes produces no reason to act. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Director of Marketing | Marketing and Advertising | 11-50 | | 2 | Senior Marketing Manager | E-commerce | 51-200 | | 3 | Chief Marketing Officer | Digital Commerce | 201-500 | | 4 | Head of Marketing | Retail | 501-1000 | | 5 | CEO | Marketing and Advertising | 11-50 | | 6 | Vice President of Marketing | E-commerce | 51-200 | | 7 | Director of Marketing | Digital Commerce | 201-500 | | 8 | Senior Marketing Manager | Retail | 501-1000 | | 9 | Chief Marketing Officer | Marketing and Advertising | 11-50 | | 10 | Head of Marketing | E-commerce | 51-200 | | 11 | CEO | Digital Commerce | 201-500 | | 12 | Vice President of Marketing | Retail | 501-1000 | | 13 | Director of Marketing | Marketing and Advertising | 11-50 | | 14 | Senior Marketing Manager | E-commerce | 51-200 | | 15 | Chief Marketing Officer | Digital Commerce | 201-500 | --- ## 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-24, then deleted along with the personas and their answers.