# Message test — https://www.megaport.com/ After reading your page, only 1 of 15 personas could name what kind of product this is, unprompted. - **Page tested:** https://www.megaport.com/ - **Audience tested against:** Network, cloud and IT infrastructure leaders - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/megaport-compute-network-storage-on-demand-eTFtoR8 > 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? | 1/15 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 8/15 | 52% | all with reservations | | 3. Value | Do they actually want it? | 14/14 | 78% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 8/15 | 53% | 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. ### What they thought you sell 4 of the personas who named a category got it wrong: - 4× “Network-as-a-service / interconnection platform” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Clarity **Rewrite the H1 to name what Megaport is: private network connectivity between clouds and data centers.** "Compute. Network. Storage." and "Launch automated infrastructure on demand, globally" could belong to any cloud vendor. Say in the headline that Megaport provisions private connections between clouds, data centers and offices in minutes. *effort low · impact high · tested against Lead with the use case* **Replace "Mission control for your entire stack" with the job the buyer does.** Space metaphors like "Mission control" and "Ready for liftoff" tell a network engineer nothing about the product. Use the plain job instead: connect multiple clouds, sites and providers without ordering circuits. *effort low · impact high · tested against Plain language* **Add a line under the H1 naming the buyer: network, infrastructure and cloud architecture teams.** Nothing on the page says who it is for until the case-study job titles far below. State the roles and the situation, such as enterprises running workloads across several clouds and regions. *effort low · impact high · tested against Name the audience* **Move a product screenshot or portal view above the stats block.** A reader scrolls through three taglines and four stats before seeing anything concrete about the product. Show the portal where a connection is configured, with a one-line caption saying what is happening. *effort medium · impact medium · tested against Show the product early* ### Relevance **Replace "31+ Countries Connected" with a link to a region and location list.** A buyer in APAC or EMEA cannot tell whether their metro is covered. Link the stat to a searchable list of locations and on-ramps by region. *effort low · impact high · tested against Specifics beat superlatives* **Name the industries served in the "Why Megaport" intro, including telecom and carriers.** The page never says which industries it serves, so carrier and telecom buyers have to guess from customer logos. List the named sectors and link each to the matching case study. *effort low · impact medium · tested against Name the audience* **Add provisioning time in minutes next to "Fast" and delete "at lightspeed".** "Configure and connect ... at lightspeed" gives no number a buyer can plan against. State the typical time from order to live connection, and where that time applies. *effort low · impact medium · tested against Specifics beat superlatives* ### Differentiation **Add a section comparing Megaport to carrier circuits and single-provider fabrics.** Standing next to Equinix Fabric or a telco circuit, the page offers no reason to pick Megaport. Name the alternatives and state the difference: provider count, contract term, time to provision. *effort medium · impact high · tested against Give a reason to choose you* **Name specific providers under "410+ leading cloud, network, and service providers".** The count tells a buyer nothing about whether their clouds and SaaS platforms are reachable. List the major on-ramps by name and link to the full directory. *effort low · impact high · tested against Specifics beat superlatives* **Date and source the stats block, naming the measurement period for 170+ Tbps.** Numbers with no date or method read as marketing rather than evidence. Add an "as of" date and a footnote saying how capacity and locations are counted. *effort low · impact medium · tested against Proof next to the claim* ### Value **Add the before-and-after numbers to the NXP card heading, not only the quote.** The strongest proof, six months down to a week, sits inside a quote a skimmer skips. Put the timeline compression in the heading so it reads without the body copy. *effort low · impact medium · tested against Front-load the meaning* --- ## 03 · What is working ### Customer quotes and the stats block, not the tagline, are what make the offering legible Six respondents said case studies, the Solutions header, customer timelines and the stats block told them the product is a cross-cloud interconnection platform and who it is for. They named these as clearer than the hero taglines. > the actual product category from the Solutions headers and case studies instead of the top copy > > — VP of Infrastructure, IT Services, 501-1000 > The customer quotes anchor it for me: Framestore connecting to clouds quickly, NXP going from six months to a week — that's the real signal, not the "mission control for your stack" tagline. > > — Head of IT Operations, Telecommunications, 1001-5000 > They're a network connectivity provider with compute and storage bolted on — basically SDN-driven interconnection, letting you provision private links between clouds, data centers, and offices on demand > > — Cloud Infrastructure Manager, Cloud Services, 501-1000 ### The NXP deployment-time case study is the proof point that lands Four respondents cited the NXP case study and the provisioning-time reduction as the concrete ROI, framing value as timeline compression and reduced vendor sprawl across 410+ providers. > provisioning time and vendor sprawl: instead of raising a ticket with Juniper-based carriers and waiting weeks for cross-connects or new circuits to a cloud or data center, I'd be doing it through one console in days, across 410+ providers > > — VP of Infrastructure, IT Services, 501-1000 > If it actually works like NXP's "half a year to a week" or Framestore's "we have Megaport, it's done" — that's deployment time for new cloud connections or sites collapsing from a procurement/carrier-provisioning cycle to self-service. That's a real line item for my team, since we're explicitly trying to cut infrastructure deployment time right now. > > — Head of IT Operations, Telecommunications, 1001-5000 --- ## 04 · What the personas said ### Hero copy is generic and does not name the product, buyer, or pain point Nine respondents called the hero abstract marketing fluff — abstract verbs instead of named products, no buyer persona, no specific pain. Several said the actual value proposition only surfaces further down the page. > Not fully sure where the compute/GPU piece fits versus being a reseller tie-in. > > — Network Infrastructure Director, Enterprise Software, 201-500 > The intended reader is never named outright — no "for network engineers" or "for infra teams" — I pieced it together from the solutions list and the logos/case studies > > — Cloud Infrastructure Manager, IT Services, 5000+ > the top half with "Mission control for your entire stack" and "Ready for liftoff" is marketing fluff aimed at a broader exec audience, not infra engineers > > — Cloud Infrastructure Manager, IT Services, 5000+ > It took a bit of piecing together, not instant. The hero copy — "Compute. Network. Storage. Launch automated infrastructure on demand, globally" — is vague marketing fluff on its own; I didn't get the real problem until the Solutions section and the customer quotes further down > > — Head of IT Operations, Telecommunications, 1001-5000 > these are verbs and metaphors, not nouns I can act on. None of them tell me if I'm provisioning a cross-connect, a VXC, a virtual router, or a bare-metal box > > — VP of Infrastructure, IT Services, 501-1000 > The top of the page ("Compute. Network. Storage. Launch automated infrastructure on demand, globally") is generic infra-as-a-service fluff that could describe a dozen vendors, and I had to scroll to the testimonials to actually get the problem > > — Cloud Infrastructure Manager, Cloud Services, 501-1000 > the hero copy ("Mission control for your entire stack," "Launch on demand, scale in minutes") is generic marketing-deck fluff that could be aimed at anyone, but the Solutions and quote sections shift into language I recognize — bandwidth, cross-connects, provisioning timelines — so it feels like it was written by marketing for a broad audience first, with the actual substance for someone like me buried further down > > — VP of Infrastructure, IT Services, 501-1000 > the actual problem being solved — slow manual circuit/carrier provisioning — I had to infer from the customer quotes, not the hero copy > > — Cloud Infrastructure Manager, IT Services, 5000+ ### Industry and region specifics respondents needed were absent Three respondents wanted telecom/carrier named, an APAC PoP list, a role-specific heading and concrete artifacts like a topology diagram. One could infer audience from case studies but said it was never stated explicitly. > I'd want a line near the top naming the role directly — something like "for network and infrastructure teams managing multi-cloud and data center connectivity" — plus a concrete artifact like a topology diagram or a sample provisioning screen > > — VP of Infrastructure, IT Services, 501-1000 > I'd need my industry named outright — "telecom" or "carrier" — plus an APAC PoP list > > — VP of Infrastructure, Telecommunications, 5000+ > it's inferable within seconds from the customer logos and quotes — Framestore, Heidelberg Materials, Goodman Fielder, NXP — so I'd say this is infrastructure/network teams at mid-to-large enterprises managing multi-cloud or multi-site connectivity, not SMBs. So yes, fast to get the problem and the audience, but only because I triangulated it from case study roles, not because the page stated "this is for network infrastructure directors" anywhere explicit. > > — Network Infrastructure Director, Cloud Services, 1001-5000 ### One anecdote is not enough evidence; respondents want mechanism, failover detail, and a… Four respondents said the page gives a single customer story with no technical explanation of the speed advantage, no failover comparison against existing Cisco setups, and no region-specific provisioning times. All wanted a pilot on their own infrastructure… > A measured time-to-provision on our own pilot — say, a new GCP interconnect live in days instead of our current weeks-to-months carrier dance. That's the single number I'd need to see reproduced > > — Cloud Infrastructure Manager, Enterprise Software, 5000+ > A straight answer on failover — specifically what happens to my live cloud connections if Megaport's control plane or network goes down — because that's the actual risk > > — Senior Infrastructure Engineer, Cloud Services, 201-500 > the page gives me one customer anecdote, not a mechanism for why it's faster than what Cisco or the cloud providers' native interconnect already does > > — Senior Infrastructure Engineer, Cloud Services, 201-500 > A verified, like-for-like provisioning time comparison for my actual regions — e.g. "new cross-connect to AWS Singapore: 3 days vs. your current 6 weeks" > > — VP of Infrastructure, IT Services, 501-1000 ### No competitor comparison is offered, so respondents could not rank the product Five respondents said they could not choose Megaport without a side-by-side against Equinix Fabric, Console Connect or cloud on-ramps, plus a named-provider list and region-specific pricing. One flagged missing VMware interoperability and telecom references. > What would tip it for Megaport is a side-by-side showing named GCP interconnect regions/latency or pricing versus those two — right now the page just asserts scale without letting me compare > > — Cloud Infrastructure Manager, Enterprise Software, 5000+ > I'd need Megaport's page to show provisioning architecture and named failover behavior side by side with provider counts — right now the stats are the only concrete thing > > — Senior Infrastructure Engineer, Cloud Services, 201-500 > to pick Megaport over them I'd need a named-provider list I can check against my own target regions, not just a round number, plus pricing that's clearly cheaper or faster than those options > > — VP of Infrastructure, IT Services, 501-1000 > But it wouldn't let me pick this over a competitor outright: there's no telecom-sector customer and nothing about VMware interoperability, so I'd rule nothing in or out from this page alone > > — Head of IT Operations, Telecommunications, 1001-5000 ### The large headline stats lack dates, methodology, or baselines Two respondents said figures like Tbps capacity carry no date, methodology or competitive comparison, which left them unable to treat the numbers as evidence. One noted three co-equal pillars imply a full stack the stats only support on the network side. > The words 'compute, network, and storage' sitting as three co-equal pillars is what muddied it — that phrasing implies a full infrastructure stack, but the stats block only backs up the network side (Tbps, countries connected), so I had to infer storage and compute were secondary add-ons rather than core offerings the copy ever actually proved. > > — Infrastructure Leader, Data Centers, 5000+ > "170+ Tbps Network Capacity," "31+ Countries Connected," "1,200+ Enabled Locations" — are just dropped in with no methodology, no date, no comparison baseline, so they don't help me differentiate against another shortlisted vendor; anyone can print a big Tbps number > > — VP of Infrastructure, IT Services, 501-1000 ### Space and boardroom metaphors read as mismatched to an infrastructure buyer Five respondents flagged phrases like "Mission control" and space-opera framing as generic exec marketing, inconsistent with the technical case-study language elsewhere on the page. > The tone is aimed at someone like me in parts — "Mission control for your entire stack," the compute/network/storage split, the customer quotes about provisioning speed — but it's still marketing-first: "Ready for liftoff" > > — Senior Infrastructure Engineer, Cloud Services, 201-500 > "Mission control for your entire stack" and "Trusted by globally recognized businesses" — that's not written for me, that's written for a boardroom slide > > — VP of Infrastructure, Telecommunications, 5000+ > "Mission control for your entire stack" and "Ready for liftoff" is trying a bit too hard to be punchy/aspirational for an audience that's more interested in uptime and procurement cycles than space metaphors > > — Infrastructure Leader, Enterprise Software, 501-1000 > the top half with "Mission control for your entire stack" and "Ready for liftoff" is marketing fluff aimed at a broader exec audience, not infra engineers > > — Cloud Infrastructure Manager, IT Services, 5000+ > it feels like two different writers — one who's talked to actual network engineers and one doing generic SaaS positioning. > > — Network Infrastructure Director, Enterprise Software, 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 hero is dead weight — the page only starts working after the reader scrolls past it.** *(high)* Nine respondents called the hero abstract fluff with no named product, buyer or pain, while six said case studies, the Solutions header and the stats block were what made the offering legible. The page's own hero is the weakest asset on it. - **The messaging depends entirely on readers doing the work the copy refused to do.** *(high)* Comprehension came from inferring the audience from case studies rather than any explicit statement, and value proposition surfaced only further down the page. Anyone who stops at the fold leaves with nothing. - **The page gives no basis for a purchase decision, only for a vague favourable impression.** *(high)* Five respondents could not rank the product without a side-by-side against Equinix Fabric or Console Connect, four wanted mechanism and failover detail, and all of those wanted a pilot before committing. Interest without ranking criteria is a stalled deal. - **The single proof point that works is carrying the entire evidentiary load, and it is not enough.** *(high)* Four respondents named the NXP provisioning-time story as the concrete ROI, but four others said one anecdote with no technical explanation or failover comparison does not constitute evidence. The same artifact is both the page's only win and its named… - **The headline statistics actively undermine credibility rather than build it.** *(medium)* Figures like Tbps capacity carry no date, methodology or baseline, leaving respondents unable to treat them as evidence, and three co-equal pillars imply a full stack the numbers only support on the network side. Unsubstantiated scale claims read as overreach. - **The page speaks in two incompatible voices and neither audience is fully served.** *(medium)* Five respondents flagged "Mission control" and space-opera framing as generic exec marketing inconsistent with the technical case-study language elsewhere, while others wanted topology diagrams and role-specific headings. The tonal split satisfies neither… --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Cloud Infrastructure Manager | Enterprise Software | 5000+ | | 2 | Senior Infrastructure Engineer | Cloud Services | 201-500 | | 3 | VP of Infrastructure | IT Services | 501-1000 | | 4 | Head of IT Operations | Telecommunications | 1001-5000 | | 5 | Infrastructure Leader | Data Centers | 5000+ | | 6 | Network Infrastructure Director | Enterprise Software | 201-500 | | 7 | Cloud Infrastructure Manager | Cloud Services | 501-1000 | | 8 | Senior Infrastructure Engineer | IT Services | 1001-5000 | | 9 | VP of Infrastructure | Telecommunications | 5000+ | | 10 | Head of IT Operations | Data Centers | 201-500 | | 11 | Infrastructure Leader | Enterprise Software | 501-1000 | | 12 | Network Infrastructure Director | Cloud Services | 1001-5000 | | 13 | Cloud Infrastructure Manager | IT Services | 5000+ | | 14 | Senior Infrastructure Engineer | Telecommunications | 201-500 | | 15 | VP of Infrastructure | Data Centers | 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-10-05, then deleted along with the personas and their answers.