# Message test — https://spd.tech/ After reading your page, only 5 of 15 personas could quickly tell what problem it solves and who it is for. - **Page tested:** https://spd.tech/ - **Audience tested against:** Product-led SMBs, scaleups and enterprises looking to modernize legacy systems, embrace AI-native engineering and build custom software from scratch/evolve, scale and automate. Industries: fintech and payments, legal, insurance, healthcare, construction, horeca and more - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/spd-technology-software-product-development-co-Y9Om0qA > 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 | 85% | 5 without hesitation, 10 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 5/15 | 39% | all with reservations | | 3. Value | Do they actually want it? | 9/15 | 56% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 8/15 | 52% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 10/15, 59% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Relevance.** 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. ### Relevance **Add a line under the H1 naming the buyer by role and company stage.** Nothing on the page says who it is for, so readers guess from client logos. Write a line naming the buyer, such as CTOs and heads of engineering at fintech and insurance companies scaling existing products. *effort low · impact high · tested against Name the audience* **Replace "Technology Expertise for Future-Ready Businesses" with the job buyers hire you for.** The headline names no work and no customer, so a reader cannot tell this is custom software development done by an outsourced engineering team. State the job in the H1, such as building and modernizing regulated financial software with dedicated engineering… *effort low · impact high · tested against Lead with the use case* **Add a problem sentence above the numbered capability list.** The list opens on capabilities with no reference to what the reader is dealing with, legacy systems, stalled roadmaps, compliance reviews blocking release. Name that situation in one sentence before the first capability. *effort low · impact medium · tested against Problem before solution* ### Differentiation **Move compliance-first architecture with GDPR, HIPAA and PCI DSS above the capability list.** The one claim that separates you from any other dev shop sits in an unfinished Security section at the bottom. Lead with it and say what it lets the buyer skip, such as passing audit without a rewrite. *effort medium · impact high · tested against Give a reason to choose you* **Add the 13-year PitchBook retention figure to the stats bar at the top.** The long client tenures are the most checkable thing here, yet they are buried in body copy while the top shows unlabeled Years, Projects, NPS counters. Put named clients and the length of each relationship where scanning readers look. *effort low · impact high · tested against Proof next to the claim* **Add one non-fintech case example to the Application Modernization and Data Analytics sections.** Every proof point is fintech or insurance, so a healthcare or construction buyer sees nothing that applies to them. Add a short named result from another industry, or say plainly that regulated financial software is your focus. *effort medium · impact medium · tested against Answer the live objection* ### Value **Add baseline and timeframe beside the 10x performance and 20x report claims.** The Cloud and DevOps numbers have no starting point, workload or duration, so they read as marketing arithmetic. State what the before figure was, over what period, on what system. *effort medium · impact high · tested against Proof next to the claim* **Add methodology line under the "3 times at 5x cost effectiveness" data analytics claim.** Cost effectiveness with no cost breakdown cannot be checked or repeated. Say what was measured, infrastructure spend, engineer hours, or throughput per dollar, and against what previous setup. *effort medium · impact high · tested against Specifics beat superlatives* **Offer a reference call in the CTA beneath the Pie Insurance result.** The 3x payment user growth result is the most concrete claim on the page, but there is no way to verify it. Add a next step that puts the reader in touch with a client who can confirm it. *effort low · impact medium · tested against One clear next action* ### Clarity **Rewrite the numbered headings to name the outcome, not the technology category.** Headings like "Cloud & DevOps" and "System Integration & APIs" read as a service menu and leave the business model to be inferred. Make each heading state the job done, such as moving legacy platforms to cloud without downtime. *effort medium · impact medium · tested against Headings stand alone* ### Brand alignment (side metric) **Cut "empower", "streamline", "seamless" and "leading" from the section intros.** Sentences like crafting robust digital platforms that empower businesses to streamline operations could belong to any vendor. Replace each with what the team actually built and what it changed. *effort medium · impact medium · tested against Concrete over abstract* --- ## 03 · What is working ### The Pie Insurance 3x payment user growth result landed as concrete proof One respondent cited the Pie Insurance case showing 3x payment user base growth from adding a billing feature as a persuasive outcome, though another wanted a reference call before acting on it. > the Pie Insurance case (3x growth in payment user base from adding billing features) > > — VP of Software Engineering, insurance, 201-500 ### Named long-tenure clients were the most credible thing on the page Six respondents singled out the named, long-term client relationships — the 13-year PitchBook retention in particular — as checkable, specific and a signal of genuine partnership rather than marketing. > They lean on named clients like PitchBook and Poynt with 10+ year relationships and specific numbers (3x processing speed, 10x cloud performance) which is the one thing that made it credible > > — Director of Engineering, healthcare, 501-1000 > The 12-13 year PitchBook relationship and the named client quotes (Fabrice Forget, John Gabbert actually attaching their names and titles) is the one thing that would push me toward a call — that's harder to fake than generic testimonials, and longevity like that suggests they don't get fired after year one > > — Head of Product Development, construction, 1001-5000 > "some of our clients have been with us for over 12 years," plus the PitchBook founder saying "for the last 13 years" — because in outsourcing the biggest risk is churn and losing institutional knowledge halfway through a migration, and that's a specific, checkable claim > > — Engineering Manager, hospitality, 5000+ > the John Gabbert 13-year PitchBook quote is the one thing here I'd actually bring into a reference-call conversation > > — CTO, fintech, 51-200 > PitchBook's founder saying "for the last 13 years, SPD Technology has helped us scale product development" and Morningstar's Head of Technology comparing them to an internal team — that's a real, named, long-tenure reference in fintech > > — Chief Technology Officer, payments, 201-500 > "some of our clients have been with us for over 12 years" and the PitchBook founder quoting a 13-year relationship. For a healthcare enterprise where I'm not looking for a quick project but a partner who'll stick through compliance audits and platform growth, that's a harder thing to fake > > — Head of Product Development, healthcare, 5000+ ### Compliance-first architecture is the one claim that separates them from generic dev shops Two respondents named the compliance-first architecture with GDPR, HIPAA and PCI DSS as differentiating and as addressing an internal bottleneck. > the "compliance-first" architecture pitch (GDPR, HIPAA, PCI DSS baked in from the start) speaks directly to what slows us down internally > > — VP of Software Engineering, insurance, 201-500 --- ## 04 · What the personas said ### Respondents had to reverse-engineer what the company actually sells Ten respondents said umbrella branding phrases, verb-free capability lists and repeated filler obscured the business model. Capabilities read as a menu rather than positioning, and the offering — custom dev outsourcing — had to be inferred. > Vague umbrella phrases like "Technology Expertise," "Future-Ready Businesses," and "software product development company" — none of those say outsourced dev team, so I had to reverse-engineer the model from the numbered service list and case studies instead of being told plainly. > > — Head of Product Development, construction, 1001-5000 > The page opens with generic capability headings ("Artificial Intelligence and Machine Learning," "Digital Platforms," "Cloud & DevOps") that read like a services menu, not a problem statement. > > — Engineering Manager, hospitality, 5000+ > It's the stacking of capability nouns with no verbs tying them to an outcome — headings like "Digital Platforms," "System Integration & APIs," "Application Modernization" read as a menu, not a positioning statement > > — Engineering Manager, hospitality, 5000+ > The generic filler phrases — 'Technology Expertise for Future-Ready Businesses,' 'end-to-end software product development services that go beyond design and programming,' 'transformative software solutions' — those are the words that could describe literally any dev shop. > > — CTO, fintech, 51-200 > The repeated self-labeling — 'leading software product development company,' 'software product development services,' 'top software development company' — used interchangeably across every section without ever just saying 'we're a dev shop you hire on a contract basis.' > > — VP of Software Engineering, legal, 501-1000 > It's a custom software development outsourcing shop — a dev vendor that builds and modernizes platforms (AI/ML, data, cloud, apps) for other companies, mostly fintech-flavored, positioning around "compliance-first engineering" and long-term client relationships like the PitchBook and Poynt case studies. Not a product at all, really — it's a services/staffing firm dressed up with case studies and buzzwords. > > — Director of Engineering, insurance, 1001-5000 > there's a vague "10x boost" and "reduced costs" line under Cloud & DevOps, but no pricing model or engagement structure > > — Head of Product Development, healthcare, 5000+ ### The target buyer is never stated and has to be guessed from logos Eight respondents said the audience and value proposition were only inferable from client logos and case studies, and not until the fintech section several scrolls down. None found an explicit statement of who the page is for. > The reader isn't explicitly named as a "CTO" or "Director of Engineering" anywhere, but the client logos (PitchBook, Poynt, Morningstar) and the fintech/healthcare industry section made it obvious this is aimed at someone like me > > — Director of Engineering, healthcare, 501-1000 > the reader is inferred from client logos (PitchBook, Poynt, Morningstar) and the fintech/healthcare/legal compliance language, not spelled out > > — CTO, fintech, 51-200 > It's reasonably clear but not stated as a clean value prop up front — I had to piece it together from the numbered service list. The problem/audience only became obvious once I hit the fintech section > > — Chief Technology Officer, payments, 201-500 > There's no single line up top that says "we're for VPs of Engineering at regulated companies who need X" — the closest is buried further down under "Compliance-First Engineering Architecture," > > — VP of Software Engineering, legal, 501-1000 > the "what" (custom dev services) and "who" (mid-to-large regulated companies, fintech-heavy) come through fast from the client logos and case studies rather than any explicit "this is for you if..." statement — I inferred the reader from who they name-drop, not from a stated target line. > > — Director of Engineering, insurance, 1001-5000 > The page never states "we help X type of company solve Y problem" in one clean line — it's a scroll of eight capability sections > > — Head of Product Development, healthcare, 5000+ > The closest thing to my actual problem — cloud costs — is buried in section 4, "10x boost in software performance, while reducing the time required for financial report generation by a factor of 20," which is a specific metric but not framed as "here's how we cut your cloud bill." > > — Head of Product Development, healthcare, 5000+ > it's not written for someone like me trying to solve one specific problem today — there's no line that says "here's what we do for infra costs," I have to assemble that from scattered case metrics, so it feels aimed at a broader technical audience > > — Head of Product Development, healthcare, 5000+ ### Performance and case-study numbers are unverifiable without baselines Seven respondents rejected the multiplier and performance claims because no baseline, timeframe, workload profile, cost breakdown or methodology was given. Several wanted named references or pilot data before believing them. > those figures come from PitchBook and Poynt's environments, not mine, and healthcare with GDPR/HIPAA isn't the same as fintech payments. Before I'd take a meeting I'd want to know who vets vendors like this for us internally > > — Director of Engineering, healthcare, 501-1000 > the "10x boost in software performance" and "20x faster report generation" numbers on the GCP migration are the kind of thing that would matter to me, but I have zero idea what baseline they're measuring from, so I can't tell if that's real leverage or marketing. > > — Head of Product Development, construction, 1001-5000 > that case has zero mechanism attached: no baseline infra, no workload profile, no cost breakdown, just a headline multiplier > > — Engineering Manager, hospitality, 5000+ > time-to-market gains like "12x" with no baseline or timeframe are marketing math, not a business case > > — CTO, fintech, 51-200 > those numbers (3x, 10x, 12-fold) have no baseline or methodology attached, and I'm not signing anything or restructuring my team's workload off case-study copy alone > > — Chief Technology Officer, payments, 201-500 ### Proof is all fintech, so buyers outside fintech saw nothing for them Four respondents said every proof point was fintech-specific, leaving healthcare and construction buyers without a relevant case study and weakening competitive positioning. > What would rule them out is the total absence of a named healthcare client — every proof point is fintech (PitchBook, Poynt, Morningstar), and the "Compliance-First" section just lists GDPR/HIPAA/PCI DSS as things they "integrate" without a single healthcare logo or case study to back it up > > — Director of Engineering, healthcare, 501-1000 > The PitchBook longevity detail — "for the last 13 years" from the founder's own quote — is the one thing that would tip it toward a shortlist call, because a 13-year retention on a real named client is harder to fake than a percentage stat. > > — Director of Engineering, insurance, 1001-5000 > if a shortlisted competitor showed me even one case study with before/after numbers and a named technical contact I could call, I'd drop SPD in favor of them > > — Chief Technology Officer, payments, 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 makes the buyer do the work of writing its positioning for it.** *(high)* Ten respondents reverse-engineered the offering from capability lists, and eight could only infer the audience from logos several scrolls down. Two separate inference tasks — what it is and who it's for — stack before any value registers. - **Every quantitative claim on the page is dead weight.** *(high)* Seven respondents rejected multiplier and performance claims for missing baselines, timeframes and methodology, and the one persuasive result — Pie Insurance 3x — still drew a demand for a reference call. Numbers are being read as marketing, not evidence. - **Credibility rests entirely on client names, not on anything the page says about itself.** *(high)* The two strongest positives are named long-tenure clients (six respondents, 13-year PitchBook) and logos used to infer audience. Strip the logos and nothing checkable remains — the copy contributes no proof of its own. - **The page is a fintech page pretending to be a horizontal one.** *(high)* Four respondents in healthcare and construction found no relevant case study, and the audience only becomes legible at the fintech section. Any non-fintech buyer reaches the proof and disqualifies themselves. - **The one genuine differentiator is buried where almost nobody found it.** *(medium)* Only two of fifteen respondents named compliance-first architecture (GDPR, HIPAA, PCI DSS) as separating them from generic dev shops, while ten were still decoding the business model. The sharpest claim is losing to filler. - **Compliance proof and industry proof are misaligned, wasting the strongest asset.** *(medium)* HIPAA and PCI DSS signal healthcare and payments, but four respondents found every case study fintech-only. The compliance claim promises regulated-industry breadth the evidence never delivers. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | VP of Software Engineering | insurance | 201-500 | | 2 | Director of Engineering | healthcare | 501-1000 | | 3 | Head of Product Development | construction | 1001-5000 | | 4 | Engineering Manager | hospitality | 5000+ | | 5 | CTO | fintech | 51-200 | | 6 | Chief Technology Officer | payments | 201-500 | | 7 | VP of Software Engineering | legal | 501-1000 | | 8 | Director of Engineering | insurance | 1001-5000 | | 9 | Head of Product Development | healthcare | 5000+ | | 10 | Engineering Manager | construction | 51-200 | | 11 | CTO | hospitality | 201-500 | | 12 | Chief Technology Officer | fintech | 501-1000 | | 13 | VP of Software Engineering | payments | 1001-5000 | | 14 | Director of Engineering | legal | 5000+ | | 15 | Head of Product Development | insurance | 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.