# Message test — https://tsh.io/ After reading your page, only 0 of 15 personas could name what kind of product this is, unprompted. - **Page tested:** https://tsh.io/ - **Audience tested against:** The Software House sells to CTOs and VP Engineering at scale-ups (Series A to C) and enterprises of roughly 51 to 500 people, in fintech, IT/software, B2B SaaS, marketplace and insurtech, with revenue from 4M dollars up or Series A funding of 2M dollars up. Best-fit geographies are the USA, UK, Netherlands and Saudi Arabia, with the Nordics workable, and best-fit stacks are Node.js, React, AWS and PHP, with Java workable. They come in on a hard deadline with an insufficient team, legacy modernization, scaling faster than hiring allows, or a new AI feature. They want a partner who takes ownership of delivery rather than a vendor who needs supervising, and they buy through referral or research over a few weeks, compressed to days when a deadline forces it. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/the-software-house-effective-software-delivery-Imhez-Q > 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? | 0/15 | 76% | 1 without hesitation, 13 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 90% | 8 without hesitation, 7 with reservations | | 3. Value | Do they actually want it? | 12/15 | 67% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 9/15 | 56% | 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: Clarity.** 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. ### Clarity **State plainly that TSH supplies an engineering team, not software.** Readers finished the page unsure whether they were buying an installable product or an outsourced engineering team, and the mix of 'AI-native delivery', 'AI Development Framework' and 'Specialists on demand' pushed several to conclude it was staffing dressed up as product. Add one line under the hero that says what is delivered in literal terms — e.g. 'A dedicated engineering team of TSH developers, tech leads and AI agents, embedded in your delivery process and managing itself.' Say who is on… *effort low · impact high · tested against Concrete over abstract* **Rewrite 'AI-native delivery, four ways' as a plain service label.** 'AI-native delivery, four ways' plus 'AI-native system', 'AI-agentic engineering team' and 'Ship AI' read to several readers as existing agency work relabelled for sales. Replace the section heading with something a CTO would say out loud, such as 'Four ways we plug into your delivery' or 'What you can hire us for', and cut 'AI-native' from headings where it is not doing work. Reserve AI language for the framework section where it is actually explained. *effort low · impact high · tested against Plain language* **Break the run-on 'We help CTOs and product teams…' line into two sentences.** The mashed line 'WehelpCTOsandproductteamsscale fastwhenopportunityhits,unblock delivery,andship new ideaswithoutstretchingtheteam' has to be reread to separate the problem from the pitch, and it sits immediately after the hero, which is the strongest thing on the page. Split it: name the problem first ('Deadlines slip. Hiring takes months. Your team is already at capacity.') then the answer in a separate short sentence. Fix the missing word spacing. *effort low · impact medium · tested against Problem before solution* ### Differentiation **Name the sectors and stacks TSH actually specialises in.** The positioning reads as any competent engineering shop: 'CTOs and product teams', '160+ product teams', a Clutch rating. Nothing there is a reason to choose TSH over the next vendor. The page already hints at fintech ('fintech-native engineers', Bakkt, Obligate, xpate, Pension Lab) — promote that into the top third as an explicit specialism line, e.g. 'Most of our work is fintech and marketplace platforms — payments, pensions, regulated data.' Add the stacks you take on so a Java or Node.js… *effort medium · impact high · tested against Give a reason to choose you* **Answer 'Why TSH over any other engineering partner?' on the page.** That question is currently a collapsed FAQ row at the very bottom — the single most important differentiation question on the page is hidden behind a click after the reader has already decided. Pull the answer up into visible copy and make it specific: team composition, the two-week standup, the self-management model, the sectors, what TSH declines to do. Keep the FAQ row, but do not let it carry the whole argument. *effort medium · impact high · tested against Answer the live objection* **Attach 'fintech-native engineers' to evidence beside the claim.** 'Quality control: 6 AI agents & fintech-native engineers' asserts a specialism with nothing behind it, and readers said that phrase in particular needs proof before it separates TSH from any other shop. Put the supporting facts next to it: how many fintech engagements, which regulated environments (Bakkt payments across 63+ countries, Pension Lab, Obligate, xpate), and what compliance regimes the teams have worked under. *effort medium · impact medium · tested against Proof next to the claim* ### Value **Attribute the 40% and 15-minute figures to named projects.** '40% faster delivery, built in', 'Average lead time reduced by up to 40%', 'Backlog creation from 1–2 days to 15 min' were read as unverifiable marketing numbers. Say where they come from directly beside them: how many projects the average covers, over what period, measured against what baseline, and name one client where it held. A smaller, sourced number beats a larger unsourced one. *effort medium · impact high · tested against Proof next to the claim* **Explain what 'self-managed' means operationally after month one.** The hero promise 'self-managed team in 2 weeks, no handholding required' is the line readers repeat back, but they immediately asked whether it holds past the third month without hand-holding. Add a short block describing the operating model: who the tech lead is, what reporting cadence you commit to, how scope changes are handled, and what happens if a team member rotates off. This turns the strongest line on the page into a durable promise rather than an onboarding claim. *effort medium · impact high · tested against Answer the live objection* **Replace 'Proven Results' block with a concrete delivery commitment.** 'Proven Results' followed by the Clutch score repeats what the hero already showed and adds no new value at the point of decision. Use that space for what a buyer weighing the spend actually needs: what is contractually committed in the first two weeks, response and staffing guarantees, and what a reference call or trial sprint looks like. Readers said the numbers would only prompt a meeting once something verifiable stood behind them. *effort medium · impact medium · tested against Specifics beat superlatives* ### Relevance **Group case studies by sector and stack so readers self-select.** The four cases — Wren Kitchens, eSky, Bakkt, Pension Lab — span unrelated verticals, so a reader in regulated fintech or legacy modernization cannot find a match to their own situation and the proof stops carrying. Label each case with sector and the technical problem solved (e.g. 'Fintech · payments platform', 'Legacy backend rebuild'), and lead the section with the two closest to the buyer you want. *effort medium · impact medium · tested against Name the audience* --- ## 03 · What is working ### The hero line lands: readers repeat back 'self-managed team in 2 weeks' and name the… Eight respondents singled out the opening line as doing its job — it states the offer (a self-managed team in two weeks) and names the audience (CTOs and product teams under delivery pressure) without confusion. Several described the problem-solution pairing as stated clearly upfront. This was the single most consistently praised element of the page. > "When you're behind on a deadline, scaling fast, or modernizing something critical, TSH fields a self-managed team in 2 weeks." > > — VP Engineering, B2B SaaS, 51-200 > the hero line "When you're behind on a deadline, scaling fast, or modernizing something critical... TSH fields a self-managed team in 2 weeks, no handholding required" tells you both the problem (understaffed, deadline pressure, need to modernize) and the buyer > > — VP of Engineering, software development, 201-500 > the hero line "When you're behind on a deadline, scaling fast, or modernizing something critical... TSH fields a self-managed team in 2 weeks, no handholding required" tells me the problem (capacity/delivery gaps) and the fix (bolt-on team) in one read > > — CTO, marketplaces, 201-500 > the opening line "When you're behind on a deadline, scaling fast, or modernizing something critical, TSH fields a self-managed team in 2 weeks, no handholding required" tells you both the problem (delivery bottlenecks, legacy modernization, scaling pressure) and the fix > > — Chief Technology Officer, software development, 51-200 > We help CTOs and product teams scale fast when opportunity hits, unblock delivery, and ship new ideas without stretching the team > > — CTO, insurtech, 201-500 > headline names CTOs/product teams, deadline/scaling/modernizing. Clear enough, no hunting. > > — Chief Technology Officer, B2B SaaS, 51-200 ### Named clients with quantified outcomes are the page's strongest proof asset Four respondents credited the named client logos and specific percentage outcomes as concrete and credible, explicitly contrasting them with competitors' vaguer case studies and vague speed claims. Two said the outcomes were concrete enough to chase up. > named client logos with specific outcomes (eSky's 75% time-to-market cut, Pension Lab's 95% document processing reduction) — those are concrete enough that I'd want to chase a reference call > > — VP Engineering, B2B SaaS, 51-200 > The named clients like Wren Kitchens, eSky, and Pension Lab with specific numbers (75% faster time to market, 95% less doc processing time) are what make me believe it's real work and not just vapor > > — Chief Technology Officer, software development, 51-200 > The "2 weeks, no handholding" promise plus the specific numbers — "backlog creation from 1-2 days to 15 min" and "average lead time reduced by up to 40%" — are what would tip me toward TSH over a vaguer competitor > > — CTO, marketplaces, 201-500 > those are checkable claims, not just logos. Against that, "40% faster delivery" and "backlog creation from 1-2 days to 15 min" are asserted with no methodology or client attribution > > — Chief Technology Officer, marketplaces, 51-200 ### The direct, pain-point tone is read as correctly pitched at a CTO buyer Three respondents said the tone speaks directly to CTO concerns — vendor babysitting, staff constraints, resource pressure — and felt appropriately targeted rather than generic marketing voice. > "no handholding required" and "self-managed team" are speaking directly to a CTO's fear of babysitting a vendor > > — Chief Technology Officer, marketplaces, 51-200 > "CTOs and product teams" and "no handholding required" is direct, not fluffy > > — VP of Engineering, B2B SaaS, 201-500 > The tone does feel aimed at someone like me: no fluff about "digital transformation journeys," just direct hits on my actual pain — "behind on a deadline, scaling fast, or modernizing something critical" > > — CTO, software development, 201-500 --- ## 04 · What the personas said ### The proof does not match the reader's own stack or sector, so it does not carry Five respondents said the named clients sit in unrelated verticals and asked for a match to their situation — regulated fintech, MENA, or Java/Node.js legacy modernization — before the case studies would advance a deal. Two specifically wanted a named Java legacy modernization case study plus an SLA. > legacy Node.js modernization gets a passing mention under "Platform Modernization" but with no specifics — I'd want a case study that looks like my stack, not just eSky and Wren Kitchens in unrelated verticals > > — Chief Technology Officer, insurtech, 51-200 > What would actually tip it: a named case study with before/after metrics from a Java-based client my size, and a contract clause tying the "2 weeks" promise to an SLA, not just marketing copy > > — VP of Engineering, software development, 201-500 > I'd need a line naming our actual situation — regulated fintech, GCC/SAMA compliance, AWS stack — instead of generic "CTOs and product teams"; something like "we've shipped inside SAMA-regulated environments" would make me feel named > > — VP of Engineering, fintech, 201-500 > I'd want to know if they've done JVM/legacy modernization specifically, not just the eSky and Pension Lab cases they cite, since those read as backend rewrites and doc automation, not necessarily Java migrations > > — Chief Technology Officer, software development, 51-200 ### The performance statistics are not believed because no methodology, source, or client… Six respondents flagged the numbers — 40% faster delivery, the 15-minute metric, Clutch rating — as unverifiable. They asked for audited sources, methodology, client attribution, SLAs or reference calls before the claims would move a deal. Two said the metrics would prompt a meeting only once verified. > "40% faster delivery" and "backlog creation from 1-2 days to 15 min" numbers are the kind of specifics that would matter if they held up, but they're asserted with no methodology or case link attached > > — VP Engineering, B2B SaaS, 51-200 > The "40% faster delivery" and "backlog creation from 1-2 days to 15 min" numbers are the kind of thing that would matter, but they're unsourced claims on a marketing page, not something I can verify. > > — CTO, fintech, 201-500 > The "40% faster delivery" and "backlog creation from 1-2 days to 15 min" numbers are the kind of specifics that would matter if I could see where they came from — client, project type, before/after methodology — but as written they're unsourced claims > > — VP of Engineering, software development, 201-500 > If that call checks out, the two-week team claim becomes credible enough to pilot; without it, this stays a nice-sounding agency pitch > > — Chief Technology Officer, insurtech, 51-200 > The 40% faster delivery and specific numbers like "backlog creation from 1-2 days to 15 min" are the kind of concrete claims that would make me take a call > > — CTO, marketplaces, 201-500 > neither has a mechanism behind it here — no SLA, no methodology detail on how they onboard into our codebase and standards in that timeframe > > — VP Engineering, fintech, 51-200 ### The self-managed promise raises a durability question the page does not answer Two respondents said the value hinges on whether 'self-managed' holds past month three without hand-holding, and noted no onboarding methodology or SLA backs it. One respondent also found the opening run-on sentence required rereading to separate problem from pitch. > the run-on opening line with no punctuation — "scaling fast, or modernizing something critical" mashed into "self-managed team in 2 weeks, no handholding" — made me reread it once to separate the problem from the pitch > > — Chief Technology Officer, software development, 51-200 > The one outcome that matters is my team's ticket velocity and code quality staying flat or improving through month three - if the 'self-managed' claim holds and I'm not pulled into daily hand-holding, that's the whole value > > — Chief Technology Officer, marketplaces, 51-200 ### The positioning is generic: no vertical or regional specialization and the… Four respondents described the CTO-level positioning as generic, lacking fintech or regional customization, and said the fintech-native claim needs proof to separate the company from any other shop. One added that headline stats like the Clutch rating and client count do nothing to differentiate. > it's generic enough that it could be pitched to any mid-market tech buyer, not tailored to fintech or our regulatory/regional context > > — VP Engineering, fintech, 51-200 > "fintech-native" is my hook, but it's a hook, not proof yet — I'd want the actual case study behind that phrase before it moves this above a competitor with a similar pitch > > — Chief Technology Officer, insurtech, 51-200 > "no handholding required" and "without stretching the team" are exactly the phrases a CTO googling "we're drowning, need bodies fast" would respond to - but it's generic enough that it's clearly written for CTOs everywhere, not fintech or MENA specifically, so it doesn't feel tailored to my situation. > > — CTO, fintech, 201-500 > "4.8/5 on Clutch" and "160+ product teams" are the kind of generic stats every shop in this space has, so they don't differentiate anyone on a shortlist > > — Chief Technology Officer, insurtech, 51-200 ### The page reads as an outsourced dev shop, not a product, and the AI-native framing is… Five respondents concluded the offer is staffing or outsourced engineering placement rather than an installable product. Three went further and described the AI-native framework and four pillars as existing agency and project work relabelled for sales purposes. > staff augmentation plus project delivery, now repositioned with an "AI-native" framework > > — VP Engineering, B2B SaaS, 51-200 > an outsourced software engineering shop — you plug in their team to augment your own dev capacity > > — CTO, marketplaces, 201-500 > It's a dev/consulting shop, not a product; the named clients like eSky and Wren Kitchens are the only reason I'd take the call. > > — Chief Technology Officer, marketplaces, 51-200 > Think fractional/augmented engineering team, not a software product I'd buy and install. > > — VP Engineering, marketplaces, 51-200 > It's an outsourced software engineering shop — augmented staffing plus dev delivery, with an "AI-native" framework bolted on for pitch purposes. > > — CTO, insurtech, 201-500 --- ## 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 entire proof layer is inert: the numbers are not believed and the clients are not relevant, so nothing on the page can advance a deal.** *(high)* Six respondents called the 40% faster delivery, 15-minute metric and Clutch rating unverifiable and demanded audited sources, methodology, attribution, SLAs or reference calls first; five separately said the named clients sit in unrelated verticals and asked for a match to their own situation. Proof that is neither credible nor applicable is proof that does nothing — eleven mentions across the two failures against four who credited the logos. - **The page's one clear win is only the headline, and the clarity stops there.** *(high)* Eight respondents repeated back 'self-managed team in 2 weeks' as the single most consistently praised element — but five read the actual offer as outsourced staffing rather than a product, three called the AI-native framework and four pillars relabelled agency work, and two questioned whether 'self-managed' survives past month three. A hero line that lands and a body that gets recategorised as a dev shop means the page sells a promise it then walks back. - **The central differentiator is read as a rebrand of ordinary outsourcing, which makes the strongest claim on the page a liability.** *(high)* Three respondents described the AI-native framework and four pillars as existing agency and project work relabelled for sales purposes, and five concluded the offer is staffing placement. Four called the positioning generic with no vertical or regional specialization, and one said the Clutch rating and client count do nothing to differentiate. When the framing itself is heard as sales language, the framing damages trust rather than building it. - **Every positive on the page is a first-impression effect; every negative is a buying-decision blocker.** *(high)* The wins are tone (three respondents) and hero clarity (eight) — both surface reads. The losses are verification of metrics (six), proof relevance (five), differentiation (four), and durability of the self-managed promise (two). Respondents explicitly said metrics would prompt a meeting only once verified and case studies would advance a deal only once matched to their situation. The page earns attention and then forfeits it at exactly the point money moves. - **The page has no answer for the buyer who asks 'and then what?' — there is no operational commitment behind any claim.** *(high)* SLAs were demanded independently across three separate failures: two respondents wanted an SLA alongside a Java legacy modernization case, respondents asked for SLAs or reference calls before the metrics would move a deal, and two said no onboarding methodology or SLA backs the self-managed promise. The same missing artefact breaks relevance, credibility and durability at once. - **The page is written for a generic CTO and therefore closes no specific one.** *(medium)* Four respondents called the CTO-level positioning generic with no fintech or regional customization and said the fintech-native claim needs proof to separate the company from any other shop; five asked for a match to regulated fintech, MENA, or Java/Node.js legacy modernization. The three who praised the tone praised its aim at CTO pain in general — which is precisely the level of abstraction the others rejected. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Technology Officer | marketplaces | 51-200 | | 2 | CTO | fintech | 201-500 | | 3 | VP Engineering | B2B SaaS | 51-200 | | 4 | VP of Engineering | software development | 201-500 | | 5 | Chief Technology Officer | insurtech | 51-200 | | 6 | CTO | marketplaces | 201-500 | | 7 | VP Engineering | fintech | 51-200 | | 8 | VP of Engineering | B2B SaaS | 201-500 | | 9 | Chief Technology Officer | software development | 51-200 | | 10 | CTO | insurtech | 201-500 | | 11 | VP Engineering | marketplaces | 51-200 | | 12 | VP of Engineering | fintech | 201-500 | | 13 | Chief Technology Officer | B2B SaaS | 51-200 | | 14 | CTO | software development | 201-500 | | 15 | VP Engineering | insurtech | 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-08-25, then deleted along with the personas and their answers.