# Message test — https://encore.dev/ After reading your page, 11 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://encore.dev/ - **Audience tested against:** Software engineering managers - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/automated-infrastructure-for-humans-and-agents-mVAMcp8 > 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 | 81% | 2 without hesitation, 13 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 88% | 7 without hesitation, 8 with reservations | | 3. Value | Do they actually want it? | 13/15 | 70% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 11/15 | 63% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 15/15, 78% 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 **Add a section showing how an existing Terraform codebase and multi-account AWS setup adopt Encore.** Every screen shows a brand-new app, leaving teams with years of Terraform state unable to tell whether adoption means a rewrite. Show the import or coexistence path with the same detail as the IAM provisioning log. *effort high · impact high · tested against Answer the live objection* **Rewrite the OPERATE heading to name what Encore does that Terraform plus a platform team cannot.** "Let developers self-serve without losing control" is a claim every internal developer platform makes. Lead with the specific difference, such as infrastructure declared in application code with no separate IaC repo to maintain. *effort low · impact high · tested against Give a reason to choose you* **Define "approved policies" under the OPERATE section: who sets them and what they cover.** "Developers and agents move independently within approved policies" uses an undefined term, so a reader cannot tell what is enforced or who writes the rules. Name the control, for example instance sizes, regions and IAM scopes set by the platform team. *effort low · impact medium · tested against Plain language* ### Value **Replace the 2–3x and 90% stat block with the baseline, team size and timeframe behind them.** "2–3x faster development speed" and "90% shorter time to market" float above the Groupon quote with no measurement period, team or starting point, so readers dismissed them. State what was measured, over how long, and at what scale. *effort medium · impact high · tested against Proof next to the claim* **Add a named outcome under the Groupon quote: what was provisioned, by how many engineers.** "days or weeks of back-and-forth ... is now automated and completed in minutes" is a feeling, not an outcome a buyer can check. Add the service count, environment count or engineer count behind it. *effort medium · impact high · tested against Specifics beat superlatives* **Add a line under the DEPLOY section naming what happens when provisioning fails.** The deploy panel shows every step succeeding, so a buyer cannot tell what happens when a provision step breaks in production. Say whether deploys roll back, how drift is detected, and who gets paged. *effort medium · impact medium · tested against Answer the live objection* ### Clarity **Cut "and agents" from the H1 and keep the agent story in the BUILD section.** "for humans and agents" makes the headline read as two products, and readers could not tell which audience the page serves. Lead with the developer and Terraform pain the rest of the page actually delivers on. *effort low · impact medium · tested against Name the audience* --- ## 03 · What is working ### The hero line and subheading name the Terraform/DevOps-ticket pain clearly enough that… Seven respondents said the headline, subheading and section structure stated the problem and the intended reader immediately, naming the Terraform handoff and infra-ticket bottleneck. Logos and CTO/Eng Director quotes reinforced the developer/engineering… > the hero line "Encore automates infrastructure from development to production, so developers and agents can build, validate, and ship without waiting on Terraform PRs or platform tickets" names both the pain (platform ticket queues) and the fix in one breath > > — Engineering Manager, Software Development, 5000+ > the hero line "Encore automates infrastructure from development to production, so developers and agents can build, validate, and ship without waiting on Terraform PRs or platform tickets" gives you the problem (slow infra handoffs) in one sentence > > — Director of Engineering, E-commerce, 501-1000 > the subhead says it "automates infrastructure from development to production, so developers and agents can build, validate, and ship without waiting on Terraform PRs or platform tickets," which tells me the problem (slow infra provisioning via Terraform/platform teams) and the mechanism in one line. > > — Engineering Manager, Software Development, 1001-5000 > the hero line "so developers and agents can build, validate, and ship without waiting on Terraform PRs or platform tickets" tells you the problem (slow infra provisioning via tickets/PRs) in the first ten seconds, and the BUILD/VALIDATE/DEPLOY/OPERATE section headers walk through exactly who touches it at each stage. > > — Software Engineering Manager, SaaS, 5000+ > the headline and subhead do the job: "Encore automates infrastructure from development to production, so developers and agents can build, validate, and ship without waiting on Terraform PRs or platform tickets." That tells me the problem (slow Terraform/DevOps handoffs) and the reader (dev teams/platform engineers, now apparently also AI agents) in one line, no hunting required. > > — Senior Software Engineering Manager, Financial Technology, 51-200 > The reader is clearly developers/eng teams, inferred from "so developers and agents can build, validate, and ship" and the BUILD/VALIDATE/DEPLOY/OPERATE flow — it's not explicitly "this page is for engineering managers," but given the logos (Groupon, Coinbase, Pave Bank) and quotes from CTOs/Eng Directors, I could tell within seconds this is aimed at people like me > > — Senior Software Engineering Manager, Financial Technology, 501-1000 ### Respondents accepted that automated provisioning removes a real bottleneck, conditional… Three respondents said provisioning infrastructure directly from code removes the DevOps ticket queue for large engineering orgs. Two explicitly hedged the value on the mechanism functioning as depicted. > the main change is removing the DevOps ticket queue — developers go from "write code, file a Terraform PR, wait on platform team" to "declare the infra need in code, get a real database/queue/bucket provisioned automatically" > > — Engineering Manager, Software Development, 51-200 > no more waiting on platform tickets for a new queue or bucket, which today is a real bottleneck with 1000+ engineers > > — Director of Engineering, E-commerce, 1001-5000 > If it actually works the way the DEPLOY and OPERATE sections show — database and S3 bucket and IAM policy getting provisioned automatically on merge, scoped to least privilege, in my own AWS account, with no Terraform PR sitting in a platform team's queue — that changes a real bottleneck for us. > > — Engineering Manager, Software Development, 5000+ --- ## 04 · What the personas said ### The page does not resolve whether the buyer is a developer or an AI agent Two respondents read the AI-agent framing as hype bolted onto the core infrastructure value proposition and were unsure which audience the product serves. > the word "agents" sitting next to "developers" throughout — it's never quite clear if this is infra tooling for humans that happens to also work with AI coding agents, or a product built primarily for agent workflows > > — Director of Engineering, E-commerce, 501-1000 > But it's also got one eye on hype-chasing managers with the "2-3x faster" quotes and agent/Claude Code screenshots, which feels like it's trying to ride the AI-agent wave as much as sell solid infra tooling. > > — Engineering Manager, Software Development, 501-1000 ### "Validate" and "approved policies" are used without explaining the mechanism Two respondents could not tell what the product validates or how policy validation works from the hero line and surrounding copy. > phrases like "validate complete workflows" and "move independently within approved policies" are the soft spots — "validate" and "approved policies" never say what's actually being checked or who sets the policy > > — Engineering Manager, Software Development, 5000+ > "Validate" is also doing a lot of unexplained work in the hero line — validate against what, a schema, a policy, a test suite? — and that ambiguity is what made the category clear but the value murky. > > — Software Engineering Manager, SaaS, 5000+ ### The page shows only greenfield provisioning and says nothing about migrating existing… Four respondents flagged the absence of a brownfield adoption path — years of existing Terraform state and multi-account setups — and said it needs the same screenshot-level specificity as the IAM demo. One said a competitor would win on that basis. > I'd need a line that names my situation directly — something like "already running services in AWS with existing Terraform? here's how Encore sits alongside it" — plus a screenshot of that brownfield path with the same specificity as the IAM provisioning log > > — Engineering Manager, Software Development, 5000+ > If a competitor on my shortlist showed me their brownfield adoption path as clearly as Encore showed me its IAM provisioning log, that would tip it their way regardless of the 2-3x speed numbers. > > — Engineering Manager, Software Development, 5000+ > What I'd still need before recommending a pilot: how it handles our existing non-trivial Terraform state and multi-account setup, since "adopt without a platform rewrite" is asserted but not shown the way the provisioning flow was. > > — Engineering Manager, Software Development, 5000+ ### Performance claims are unsourced pull quotes and were not believed Four respondents rejected the Groupon 2-3x claim and other metrics as lacking methodology, baselines or real numbers, and said they would require reference calls on production failure modes before piloting. > I'd go in wanting the Groupon or Pave Bank case fleshed out with real numbers, not just a pull quote, before I put budget behind it. > > — Software Engineering Manager, SaaS, 201-500 > I'd walk in wanting Groupon or Pave Bank's actual infra lead on the phone talking about what broke in production and how long the migration off their old setup took — not another quote about "2-3x faster," which still has no methodology behind it. > > — Senior Software Engineering Manager, Financial Technology, 201-500 ### The copy speaks to engineers and ignores procurement and budget approval Four respondents said the engineer-focused voice and unsourced stats do not survive a security review, SOC2 question or budget meeting, and the value proposition is never translated into numbers a committee would use. > Nothing on the page talks to procurement concerns like security review timelines, SOC2, or what happens in a vendor dispute — that's the gap that tells me this was written by and for developers, not for the person who has to defend the decision later. > > — Engineering Manager, Software Development, 1001-5000 > it's pitched slightly below my level — it's selling to the dev doing the waiting, not the director who has to defend the spend, so I'd still need to translate "2-3x faster" into numbers I can take to a budget meeting myself. > > — Software Engineering Manager, SaaS, 201-500 > The tone is aimed at the engineer doing the work and the CTO/Eng Director approving it, not at a budget committee — it assumes I already feel the pain of "waiting on Terraform PRs or platform tickets" rather than selling me on why I should care. > > — Software Engineering Manager, SaaS, 5000+ ### The core mechanism was understood: provisioning AWS/GCP directly from code in place of… One respondent played the positioning back accurately as replacing Terraform and infra tickets with code-driven cloud provisioning. > It's an infrastructure automation platform that sits between app code and cloud deployment — you declare databases, queues, buckets in your code (Go or TypeScript) and it provisions the actual AWS/GCP resources on merge, replacing Terraform configs and the usual infra-ticket back-and-forth. > > — Senior Software Engineering Manager, Financial Technology, 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's only reliable achievement is naming a pain it then fails to prove it solves.** *(high)* Seven respondents recognised the Terraform/infra-ticket problem, but just three granted value and two of those hedged it on the mechanism working as depicted, while two could not tell what "validate" or "approved policies" actually do. - **Every proof point the page offers was rejected, leaving the argument resting on assertion alone.** *(high)* Four respondents dismissed the Groupon 2-3x claim and other metrics as lacking methodology or baselines, and four said the unsourced stats collapse in a security review or budget meeting. No respondent cited evidence as persuasive. - **The page is unsellable past the engineer who likes it.** *(high)* Four respondents said the copy never translates value into numbers a committee would use and ignores procurement, SOC2 and budget approval; four more demanded reference calls on production failure modes before piloting. - **The page disqualifies itself from every account that already runs Terraform — which is the audience it just told it understands.** *(high)* The hero names the Terraform handoff pain for seven respondents, yet four flagged no brownfield path for years of existing state and multi-account setups, with one saying a competitor wins on that alone. - **The AI-agent framing actively costs credibility rather than adding it.** *(medium)* Two respondents read it as hype bolted onto the infrastructure value proposition and could not tell who the buyer is, compounding the two who could not decode "validate" and "approved policies." - **Comprehension is being mistaken for conviction.** *(medium)* Seven respondents restated the problem and one played the mechanism back accurately, yet the believability, procurement and brownfield objections each drew four respondents. Understanding the pitch is what enabled the rejection. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Engineering Manager | Software Development | 51-200 | | 2 | Software Engineering Manager | SaaS | 201-500 | | 3 | Senior Software Engineering Manager | Financial Technology | 501-1000 | | 4 | Director of Engineering | E-commerce | 1001-5000 | | 5 | Engineering Manager | Software Development | 5000+ | | 6 | Software Engineering Manager | SaaS | 51-200 | | 7 | Senior Software Engineering Manager | Financial Technology | 201-500 | | 8 | Director of Engineering | E-commerce | 501-1000 | | 9 | Engineering Manager | Software Development | 1001-5000 | | 10 | Software Engineering Manager | SaaS | 5000+ | | 11 | Senior Software Engineering Manager | Financial Technology | 51-200 | | 12 | Director of Engineering | E-commerce | 201-500 | | 13 | Engineering Manager | Software Development | 501-1000 | | 14 | Software Engineering Manager | SaaS | 1001-5000 | | 15 | Senior Software Engineering Manager | Financial Technology | 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-10-05, then deleted along with the personas and their answers.