# Message test — https://spd.tech/zero-to-one/ After reading your page, only 1 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://spd.tech/zero-to-one/ - **Audience tested against:** Non-tech Founders/CEOs of scaleups or startups who've built an AI-based prototype to validate their product idea and want to evolve it into a scalable, investor-ready V1 fast. Not technical decision makers. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/ai-mvp-development-for-non-technical-founders-zNqmm64 > 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? | 13/15 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 97% | 13 without hesitation, 2 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) — 7/15, 48% 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 1 of the personas who named a category got it wrong: - 1× “Fractional CTO / dev agency (CTO-as-a-service)” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Add a line under "Verified Velocity" naming what competitors do differently.** "AI does the heavy lifting, and a rigorous engineering process makes the result trustworthy" is a sentence any dev shop could publish. Name the concrete thing you do that a freelancer or agency does not, such as the written commitments and the handover… *effort medium · impact high · tested against Give a reason to choose you* **Add a founder-stage client example beside the PitchBook testimonial.** A ten-year enterprise relationship says nothing about getting one founder's V1 live. Add a short reference from a non-technical founder naming what shipped and how long it took. *effort medium · impact high · tested against Proof next to the claim* **Replace "The factory stays with you" with a plain description of what you hand over.** "The factory stays with you" is undefined, and buyers want to know what a future CTO inherits. List the artifacts handed over: specs, architecture decision records, test suites, repos and access. *effort low · impact medium · tested against Plain language* ### Value **Replace the PitchBook quote with a before/after case study showing timeline, scope and cost.** The page asks for trust in speed claims with no example of a project delivered. Show one build with start date, launch date, what shipped, and what it cost. *effort high · impact high · tested against Proof next to the claim* **Add a pricing line under "How to start with us" stating fee model and typical V1 range.** A founder cannot tell whether this is a $20k engagement or $500k, so the call to action is a blind step. State whether work is fixed-fee or monthly, and the typical cost of a first version. *effort medium · impact high · tested against Answer the live objection* **Add units and definitions beside each of the three numbers: 3 days, 80%, 24 hrs.** "3 days", "80%" and "24 hrs" sit alone with no units, baseline or definition, so a reader cannot tell what is measured. Write each as a full sentence naming what is delivered, measured against what, and by when. *effort low · impact high · tested against Specifics beat superlatives* ### Clarity **State in the first two lines that you are an outsourced product development team.** A reader has to scroll past pillars and pipelines before learning this is an agency that builds software for you. Name the service plainly right under the opening line. *effort low · impact high · tested against Show the product early* ### Brand alignment (side metric) **Add a line under the hero naming who you work with, including funded teams with engineers.** The copy speaks only to founders who have never shipped code, so a technical leader reads themselves out. Say which situations you take on, including teams with an existing engineer who need architecture and delivery capacity. *effort low · impact high · tested against Name the audience* **Rewrite the FAQ heading "Won't I need to hire a CTO anyway?" to address teams with engineers.** Every FAQ assumes the reader has no technical staff at all. Add one entry answering what happens when a founder already has one or two engineers in place. *effort medium · impact medium · tested against Answer the live objection* **Reframe the PitchBook quote with a caption tying enterprise rigor to founder V1 work.** A Chief Product Officer testimonial about a ten-year partnership makes the page look like it serves enterprises, not first-time founders. Caption it with the point you want made: the same engineering discipline is applied to first builds. *effort low · impact medium · tested against Proof next to the claim* --- ## 03 · What is working ### The opening line names the problem and the reader, and it lands Seven respondents independently praised the opening sentence for immediately identifying the non-technical founder pain point and the target audience. It was the most consistently positive element on the page. > "Every non-technical founder knows the feeling — the market timing is right, but the build keeps slipping" tells you exactly who this is for and what pain it addresses. > > — Co-Founder and CEO, Software, 1-10 > the opening line "Every non-technical founder knows the feeling — the market timing is right, but the build keeps slipping" told me both the problem and the reader in a single sentence > > — CEO, AI/Machine Learning, 51-200 > the very first line, "Every non-technical founder knows the feeling — the market timing is right, but the build keeps slipping," names both the problem (stalled builds) and the reader (non-technical founder) in one sentence > > — Founder and CEO, Software, 1-10 > the opening line "Every non-technical founder knows the feeling — the market timing is right, but the build keeps slipping" names both the problem and the reader in one sentence, right at the top > > — Co-Founder and CEO, SaaS, 11-50 > the opening line "Every non-technical founder knows the feeling — the market timing is right, but the build keeps slipping" names both the problem and the reader in one sentence, no hunting needed > > — CEO, SaaS, 11-50 ### The V1-to-investor-ready problem is one respondents recognise as real One respondent said the page solves a genuine V1-to-investor-ready problem, conditional on execution matching the claims. > If it worked exactly as promised, I'd get a real V1 shipped without me having to become the de facto CTO, and I'd get it with less risk of the "guesses compound" problem they describe — that's a real pain I recognize. > > — Founder, SaaS, 11-50 --- ## 04 · What the personas said ### The three headline metrics are unusable without units, baselines, or sources Eleven points attack the same numbers: no units, no baselines, no definitions, no measurement criteria, no sourcing. Multiple respondents called them unfalsifiable or impossible to benchmark. > the three headline numbers — 3 days, 80%, 24 hrs — are never defined anywhere on the page; if a competitor showed me the same pipeline with those metrics actually explained (80% of what, measured how), I'd pick them over this one on specificity alone. > > — Co-Founder and CEO, Software, 1-10 > The three headline stats themselves — "3 days," "80%," and "24 hrs" — sit as standalone labels with no unit, baseline, or noun attached. > > — CEO, AI/Machine Learning, 51-200 > The "80%" and "3 days" numbers on the Verified Velocity pillars have zero sourcing, and "Autonomy is earned" / "Change is never judged by its author" sound nice but tell me nothing about actual turnaround or cost — I'd need a real case study with before/after timelines and a fixed-fee structure > > — Founder and CEO, Software, 1-10 > the promise is "3 days," "80%," "24 hrs" of accountability, but none of those numbers are defined or sourced, so I don't actually know what improves > > — Founder, AI/Machine Learning, 51-200 > The "3 days / 80% / 24 hrs" numbers next to Velocity/Verification/Accountability are the kind of thing that would make me lean in, but as written they're just floating stats with no definition — 3 days to what, 80% of what test coverage or what, 24 hrs response on what > > — Founder and CEO, SaaS, 11-50 ### What the company actually sells only becomes clear after scrolling Three points note the service type is not immediately legible: one had to scroll to work out it is outsourced product development with AI in the workflow, and abstract phrasing like 'factory stays with you' went unexplained. > I'd flag the word "pipeline" and terms like "the factory stays with you," which sound polished but are a bit abstract until you actually click into a stage to see what's produced. > > — Co-Founder and CEO, Software, 1-10 > AI baked into the workflow, wrapped in their "Verified Velocity" and "Spec-First Delivery" framework. Stripped of the jargon, it's: they take your spec, use AI to build faster, and run it through a six-stage pipeline > > — Founder and CEO, Software, 1-10 ### The single PitchBook testimonial carries sentiment but no scope, timeline, or budget Four respondents said the lone enterprise reference proves nothing: no scope, timeline, or cost. One noted it also fails to demonstrate viability for the stated founder audience. > The PitchBook CPO quote is the one thing that could tip it over a competitor with zero named references — it's a real company I recognize, not a made-up "Sarah K." testimonial. But it's a single quote with no specifics on what was built or timeline, so it's not enough to actually differentiate > > — Founder, SaaS, 11-50 > the numbers backing it up — 3 days, 80%, 24 hrs — have zero source or context, and one Pitchbook quote from a CPO doesn't tell me if this works for a scrappy 5-person shop like mine > > — Founder, Software, 1-10 > the quote is pure sentiment ("there is nothing they can't do") with no scope, timeline, or budget attached, so it doesn't actually differentiate them from another shop with a similar quote > > — Founder, AI/Machine Learning, 51-200 ### The enterprise case study contradicts the small-founder positioning One respondent said the enterprise reference raises doubt about whether the agency actually serves the small founder segment the copy addresses. > the one proof point they lead with — PitchBook's CPO — is a company way bigger than mine, which makes me wonder if I'm actually their target customer or just their case study while they chase bigger fish > > — Founder, Software, 1-10 ### The page reads as built for first-time founders and excludes teams with existing… Five points flag the same mismatch: the copy targets first-time founder anxiety and people who have never shipped code, which several said pushes away experienced engineering teams and leaders. > The tone is written squarely for a non-technical, first-time founder — "the decisions a non-technical founder can't be expected to get right alone" — not for me > > — CEO, AI/Machine Learning, 51-200 > the copy is squarely aimed at the earlier-stage, technically blind buyer, not an exec who already has a team > > — Founder, AI/Machine Learning, 51-200 > there's no mention of integrating with an existing eng team or handling scale, which is the gap for me > > — Co-Founder and CEO, AI/Machine Learning, 51-200 > The tone is clearly written for a non-technical solo founder, not someone like me > > — Founder and CEO, AI/Machine Learning, 51-200 ### Respondents said they would only buy after seeing a before/after case study with… Four points name the missing artifact explicitly: a case study with before/after timeline and cost, fixed fees, and documented architecture decisions handed to a future CTO. > The "80%" and "3 days" numbers on the Verified Velocity pillars have zero sourcing, and "Autonomy is earned" / "Change is never judged by its author" sound nice but tell me nothing about actual turnaround or cost — I'd need a real case study with before/after timelines and a fixed-fee structure > > — Founder and CEO, Software, 1-10 > I wouldn't take a meeting off this page alone — I'd want one concrete case study with before/after timeline and cost before I'd give up 30 minutes > > — Co-Founder and CEO, SaaS, 11-50 > a shipped V1 on a fixed timeline with the architecture decisions documented and defensible enough that I could hand it to a real CTO later without a rebuild > > — CEO, Software, 1-10 --- ## 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 proof points are unverifiable, so the hook converts into doubt rather than interest** *(high)* Eight of 15 respondents attacked the three headline metrics as having no units, baselines, or sources, with multiple calling them unfalsifiable. The single testimonial drew four more objections for lacking scope, timeline, and cost. - **The strongest asset on the page is a sentence, and nothing behind it holds** *(high)* Seven respondents praised the opening line as the most consistently positive element, yet 8 rejected the metrics and 3 could not tell what is sold without scrolling. Attention earned at the top is spent immediately. - **The page names a buying condition it does not meet, so the purchase decision is deferred by design** *(high)* Four points explicitly name the missing artifact: a before/after case study with timeline and cost, fixed fees, documented architecture decisions. Only one respondent affirmed the underlying problem, and conditionally on execution. - **The audience framing shrinks the addressable market instead of focusing it** *(medium)* Five points flag copy pitched at first-time founders who have never shipped code, which several said actively pushes away experienced engineering teams and leaders. Narrowing is only worth it if the named segment is convinced. - **The proof and the positioning point at different buyers, so neither audience is served** *(medium)* The lone enterprise PitchBook reference sits against copy addressing first-time founder anxiety; one respondent said it raises doubt the agency serves small founders at all, and another said it fails to demonstrate viability for the stated audience. - **Abstract phrasing costs the page its category, forcing the reader to do the positioning work** *(medium)* Three points note the service type is not immediately legible — one had to scroll to work out it is outsourced product development with AI in the workflow, and 'factory stays with you' went unexplained. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Co-Founder and CEO | Software | 1-10 | | 2 | Founder | SaaS | 11-50 | | 3 | CEO | AI/Machine Learning | 51-200 | | 4 | Founder and CEO | Software | 1-10 | | 5 | Co-Founder and CEO | SaaS | 11-50 | | 6 | Founder | AI/Machine Learning | 51-200 | | 7 | CEO | Software | 1-10 | | 8 | Founder and CEO | SaaS | 11-50 | | 9 | Co-Founder and CEO | AI/Machine Learning | 51-200 | | 10 | Founder | Software | 1-10 | | 11 | CEO | SaaS | 11-50 | | 12 | Founder and CEO | AI/Machine Learning | 51-200 | | 13 | Co-Founder and CEO | Software | 1-10 | | 14 | Founder | SaaS | 11-50 | | 15 | CEO | AI/Machine Learning | 51-200 | --- ## 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-22, then deleted along with the personas and their answers.