# Message test — https://aligned.net/ After reading your page, only 3 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://aligned.net/ - **Audience tested against:** CEO, CFO, CTO at post product market fit SaaS company, $3,000,000 to $20,000,000 ARR. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/software-platform-margin-recovery-exit-readine-VAwAfpI > 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? | 6/15 | 79% | 1 without hesitation, 14 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? | 11/15 | 63% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 3/15 | 33% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 13/15, 70% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Clarity.** 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× “Technical/platform cost remediation consulting” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Attach numbers to the OCA Aspire testimonial.** The lone client quote carries no figures, so it cannot evidence low-disruption execution. Add the infrastructure cost reduction, uptime change or diligence outcome, with the timeframe. *effort medium · impact high · tested against Proof next to the claim* **Promote "We Build to Leave" into the hero.** The lines that actually separate the firm — self-exclusion from staff augmentation and the no-permanent-dependency promise — are absent from the top of the page, which instead offers margin language any consultancy could write. Put them beside the H1. *effort low · impact high · tested against Give a reason to choose you* **Say why an embedded firm beats a staff-aug vendor.** The eight service cards read as a capability list any consultancy could publish. Name the contrast directly: one accountable party that owns the fix and exits, versus contractors you keep paying. *effort medium · impact medium · tested against Give a reason to choose you* ### Clarity **Label every percentage in the header graphic.** The header dumps "+15%", "68%", "72%", "55%" with no label, unit or timeframe, so readers cannot tell what recovered or for whom. Either caption each figure with the metric and engagement it came from, or remove them. *effort low · impact high · tested against Proof next to the claim* **Replace "specialized, temporary capacity" with what you actually do.** "We are the specialized, temporary capacity that lets your technology leader finally get the structural work done" makes the reader decode an abstraction before they learn the job. Say engineers embed with your team for a fixed period to cut platform cost… *effort low · impact high · tested against Plain language* **Front-load "What We Do" with the engagement shape.** The section buries the concrete detail — codebase, architecture, exit — under two abstract sentences. Open with the sequence: diagnose, remediate, transfer, leave, in a stated number of weeks. *effort medium · impact medium · tested against Conclusion first* ### Value **Add one named before/after cost breakdown.** Every claim about recovered margin is unsourced, so a CFO has nothing to price the work against. Publish one engagement with starting run-rate, post-remediation run-rate, duration and fee. *effort high · impact high · tested against Proof next to the claim* **State engagement length and pricing model near the CTA.** "Let's Talk" asks for a call with no sense of what an engagement costs or how long it runs, the exact objection an executive holds. Give a typical duration and how fees are structured. *effort medium · impact high · tested against Answer the live objection* ### Brand alignment (side metric) **Add partner bios beside the client logos.** Logos alone read as a small boutique, undercutting the C-suite tone. Name the people doing the work and the platforms they have run, so portfolio weight is visible rather than inferred. *effort medium · impact medium · tested against Proof next to the claim* --- ## 03 · What is working ### The problem and the buyer are named on the first screen without inference Nine respondents said the landing page states the problem and target audience explicitly in the subheading or first two lines, with no interpretation required. > the header "Fight the Hidden Margin Erosion Inside Your Software Platform" plus the "CEOs, CFOs, CTOs, and founder-led technology teams turn to Aligned when..." line tells you the problem and the reader in the first screen. No hunting required > > — Chief Technology Officer, Software, 1001-5000 > "Fight the Hidden Margin Erosion Inside Your Software Platform" - and the "Post-PMF SaaS companies hit a point where the platform... starts working against them" line under it > > — Chief Executive Officer, Technology, 201-500 > Pretty obvious fast — headline "Fight the Hidden Margin Erosion Inside Your Software Platform" plus "Post-PMF SaaS companies hit a point where the platform... starts working against them" told me the problem in the first two lines. > > — Chief Financial Officer, SaaS, 501-1000 > claims like "MARGIN+15%" and "68%/72%/55%" floating in that graphic have no source or case study attached, so the problem/audience framing is clear immediately, but I'd still want a number I can trace before I believed the outcomes. > > — Chief Technology Officer, Software, 1001-5000 > the subhead "Fight the Hidden Margin Erosion Inside Your Software Platform" plus the line "CEOs, CFOs, CTOs, and founder-led technology teams turn to Aligned when..." tells me both the problem (margin leaking from infrastructure/architecture as you scale, platform breaking, buried risk before a sale) and the reader within the first screen > > — Chief Financial Officer, SaaS, 501-1000 > the subhead "Fight the Hidden Margin Erosion Inside Your Software Platform" plus the line right under "The Problem" — "CEOs, CFOs, CTOs, and founder-led technology teams turn to Aligned when..." — tells me both the problem (shrinking margins, fragile platforms, buried risk, GTM blocked by architecture) and the reader (post-PMF SaaS leadership, explicitly named by title) without me having to dig > > — Chief Technology Officer, Software, 1001-5000 > the subhead "Fight the Hidden Margin Erosion Inside Your Software Platform" plus the line "Post-PMF SaaS companies hit a point where the platform that got them to product-market fit starts working against them" told me the problem in the first ten seconds > > — Chief Executive Officer, Technology, 201-500 ### "Don't Call Us for Staff Augmentation" and "We Build to Leave" are the lines respondents… Four respondents named these two lines as what separates the firm from competitors, citing self-exclusion from staff aug and the removal of permanent team dependency. > The one line that would tip me toward taking the meeting over a competitor is "Don't Call Us for Staff Augmentation" — most turnaround/consulting shops blur the line on scope, and them naming what they're NOT doing, plus the explicit "We Build to Leave... no long-term dependency, no lock-in," is a concrete positioning claim I can hold them to > > — Chief Technology Officer, Software, 1001-5000 > The line "Don't Call Us for Staff Augmentation... Call us when the problem is hiding or systemic" is the thing that would actually differentiate them on a shortlist — most turnaround/consulting firms don't self-select out of engagements like that > > — Chief Executive Officer, Technology, 201-500 > The line "We Build to Leave" plus "no long-term dependency, no lock-in" is the one thing that would tip me toward this one over a competitor — it directly answers the fear I'd have with any embedded team, which is that they become a permanent tax on my org chart > > — Chief Technology Officer, Software, 1001-5000 ### The tone reads as C-suite-facing and technically credible Three respondents said the language signals deep platform execution expertise and business-impact framing aimed at executives, matching the stated buyer. > "CEOs, CFOs, CTOs, and founder-led technology teams turn to Aligned when..." names the buyer directly, and "your CFO sees exactly where, in P&L terms" shows they know I don't want engineering jargon, I want margin impact > > — Chief Executive Officer, Technology, 201-500 > lines like "the CTO already knows what's broken, what they don't have is bandwidth" show they've sat in that exact executive conversation before — that's what makes it land rather than read as generic vendor copy. > > — Chief Executive Officer, Technology, 201-500 --- ## 04 · What the personas said ### The header percentage metrics are unlabeled and unsourced Two respondents said the percentage figures in the header lack context, labels, and any supporting data source or case study. > the graphic with '68%, 72%, 55%' and 'MARGIN RECOVERED' floating with no labels or context is what threw me first > > — Chief Executive Officer, Technology, 201-500 > the "68%/72%/55%" graphic and "+15% margin" in the header art are never explained, so I'd want a real case study with before/after cost figures before I took the pitch seriously > > — Chief Technology Officer, Software, 1001-5000 ### No quantified case study exists, and respondents say before-and-after numbers are what… Ten respondents flagged the absence of named-customer before/after cost figures, methodology, or engagement cost. One called a client cost breakdown the deciding artifact for picking up the phone. > no case study with actual numbers (they cite "68%/72%/55%" and "+15% margin recovered" in a graphic with zero context on what those numbers even mean), no timeline, no sense of engagement cost > > — Chief Technology Officer, Software, 1001-5000 > there's no number attached, just a chart graphic showing "68% / 72% / 55%" and "MARGIN +15%" with no methodology behind it. Without a case study showing actual dollars recovered or margin points regained > > — Chief Financial Officer, SaaS, 501-1000 > A sourced before/after cost breakdown from an actual client — e.g. 'infra spend went from $X to $Y over Z months, here's the architecture change that caused it' — that's the one artifact that would make me pick up the phone. > > — Chief Technology Officer, Software, 1001-5000 > I'd want to see one concrete case study with before/after numbers (margin %, infra cost delta, timeline) beyond the one Jim Wright quote, because right now the proof is a single testimonial and a lot of confident language about "structural risk" with no specifics on how they diagnose it or what it actually costs. > > — Chief Executive Officer, Technology, 201-500 > I'd need named references from companies our size with real before/after figures, not just 'delivered on time.' > > — Chief Financial Officer, SaaS, 501-1000 > right now I've got one client quote (Jim Wright, OCA Aspire) with no hard numbers, and a decorative "15% margin recovered" graphic that isn't tied to any named, comparable company > > — Chief Financial Officer, SaaS, 501-1000 > the page is all claims, no proof: no case study with numbers, no "we cut X% of spend in Y weeks," and the one testimonial talks about innovation and scalability, not margin recovery specifically > > — Chief Financial Officer, SaaS, 501-1000 ### The single OCA Aspire testimonial carries no numbers and is not enough proof Three respondents identified the lone client testimonial as unquantified and insufficient to evidence low-disruption execution or impact. > the one testimonial from OCA Aspire's COO says "delivered in under six months and within budget" with zero numbers on the actual margin or cost outcome > > — Chief Executive Officer, Technology, 201-500 > it's a single testimonial with no numbers behind it, and the "MARGIN +15%" chart graphic is unsubstantiated — no case study with actual dollar or margin-point recovery. Without a second reference client or a real before/after figure, it's not enough > > — Chief Financial Officer, SaaS, 501-1000 > there's exactly one testimonial, from OCA Aspire's COO, and it's qualitative — "delivered in under six months and within budget" with no numbers on margin recovered > > — Chief Executive Officer, Technology, 201-500 ### Client logos and the absence of bios make the firm read as an early-stage boutique Four respondents read the logos as mid-market or smaller post-PMF SaaS rather than enterprise, and noted no founder story or partner bios to establish portfolio weight. > the client logo wall (Credit Key, SmartMoving, PayNearMe, RXO — mid-market SaaS/fintech, not enterprise giants) suggests they sell to post-PMF, venture-backed software companies in the growth-to-exit stage, not massive incumbents like us > > — Chief Technology Officer, Software, 1001-5000 > What would firm this up is an actual founding story or named partner bios - right now it reads like a well-positioned pitch deck with no faces behind it > > — Chief Executive Officer, Technology, 201-500 ### The service model reads correctly as embedded, temporary remediation consulting rather… Six respondents described the offering back accurately: a services firm that embeds with engineering to fix technical debt, platform cost and reliability before an exit, then leaves. > They're a consulting outfit that parachutes in to fix technical debt and cost bloat in your platform before a sale or fundraise > > — Chief Technology Officer, Software, 1001-5000 > we embed, not advise... we are not arms-length consultants who hand over a slide deck and disappear > > — Chief Executive Officer, Technology, 201-500 > They're a consulting outfit that parachutes into SaaS companies to fix technical debt and cost bloat in the platform — basically a temporary engineering SWAT team > > — Chief Financial Officer, SaaS, 501-1000 > They're a consulting outfit that embeds temporarily with your engineering team to fix platform cost and reliability issues — basically technical due diligence plus remediation, not staff aug. > > — Chief Technology Officer, Software, 1001-5000 > They're a consultancy that parachutes in for a fixed engagement to fix technical debt and cost bloat in your platform before a sale — basically exit-readiness and infrastructure remediation, not a software product at all. > > — Chief Financial Officer, SaaS, 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 asks for a high-trust remediation engagement while offering zero verifiable evidence, so the entire proof burden falls on the buyer.** *(high)* Ten respondents flagged missing named-customer before/after figures and methodology, two called the header percentages unlabeled and unsourced, and three found the lone testimonial unquantified. Every proof element on the page was rejected. - **The page's clarity advantage is wasted because comprehension does not convert into a reason to call.** *(high)* Nine respondents got the problem and buyer with no inference and six described the service model back accurately, yet ten still said before-and-after numbers are what would trigger contact. Understanding the offer is not the bottleneck. - **The differentiation is rhetorical, not evidenced, and collapses the moment a buyer asks for substantiation.** *(high)* Only four respondents named "We Build to Leave" and the staff-aug line as separators, while three said the single testimonial fails to evidence low-disruption execution. The claim to leave cleanly is asserted, never demonstrated. - **The page contradicts its own positioning: executive-grade tone paired with signals of an unproven boutique.** *(high)* Three respondents read the language as C-suite-facing and technically credible, but four read the client logos as mid-market or smaller and noted the absence of founder story or partner bios. The credibility gap is visible on the same screen. - **Unsourced header percentages actively damage credibility rather than merely underdelivering.** *(medium)* Two respondents said the figures lack labels, context, and any case study behind them, while ten separately demanded methodology and before/after numbers. Numbers presented without provenance to a buyer already hunting for them read as invented. - **Omitting bios and engagement cost is a fatal gap for a service sold on embedded senior expertise.** *(medium)* Four respondents noted no founder story or partner bios to establish portfolio weight, and ten flagged missing engagement cost alongside outcome figures. Buyers cannot price or staff-check an offer built entirely on who shows up. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Technology Officer | Software | 1001-5000 | | 2 | Chief Executive Officer | Technology | 201-500 | | 3 | Chief Financial Officer | SaaS | 501-1000 | | 4 | Chief Technology Officer | Software | 1001-5000 | | 5 | Chief Executive Officer | Technology | 201-500 | | 6 | Chief Financial Officer | SaaS | 501-1000 | | 7 | Chief Technology Officer | Software | 1001-5000 | | 8 | Chief Executive Officer | Technology | 201-500 | | 9 | Chief Financial Officer | SaaS | 501-1000 | | 10 | Chief Technology Officer | Software | 1001-5000 | | 11 | Chief Executive Officer | Technology | 201-500 | | 12 | Chief Financial Officer | SaaS | 501-1000 | | 13 | Chief Technology Officer | Software | 1001-5000 | | 14 | Chief Executive Officer | Technology | 201-500 | | 15 | Chief Financial Officer | SaaS | 501-1000 | --- ## 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-30, then deleted along with the personas and their answers.