# Message test — https://www.resolvebim.com/ After reading your page, 11 of 15 personas would take a meeting to learn more. - **Page tested:** https://www.resolvebim.com/ - **Audience tested against:** Resolve sells to design and construction teams on heavy MEP and infrastructure jobs: data centers, water and wastewater, factories and advanced manufacturing, pharma and life sciences, healthcare. Office, retail, and residential are out. Buyers are the people who build the BIM model: VDC/BIM Directors and Managers, Engineers, Coordinators, Design Managers, and Project Managers. Owner-side BIM leaders count too. Buyers are not the daily users. Resolve VR is for pre-jobsite review. BIM managers run it and pull in superintendents, trades, owners, and PMs to catch issues before the build, so sign-off holds while fixes are cheap. Resolve Field is for on-site verification. Field leaders (superintendents, foremen, project engineers, PMs) hold the model on iPads and laptops they already carry, offline, and check field reality against the model without waiting on the office. Not a fit: teams wanting photorealistic VR, presentation VR, or AR overlay. Architects come in too early. Execs rarely convert. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/resolve-construction-3d-bim-across-vr-web-and-CQg75nw > 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 | 84% | 4 without hesitation, 11 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 88% | 7 without hesitation, 8 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? | 11/15 | 63% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 11/15, 63% 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. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Value **Attach project size and baseline to the "4 weeks" and "3 months" stat block.** The numbers float free of any project, so a buyer cannot tell what was measured or against what. Name the project type, model size, and the before-and-after each figure compares. *effort medium · impact high · tested against Proof next to the claim* **Replace "10x avoided risks" with a named customer outcome and timeframe.** A 10x multiplier with no baseline reads as a slogan, not evidence. State what a named team found, over how many weeks, on a project a reader can size. *effort medium · impact high · tested against Specifics beat superlatives* **Add a link to one written case study beside the results stats.** Buyers said they would need a documented case on a comparable project before believing the outcome claims. Put one case study with project scale, model size, and measured result next to the numbers. *effort medium · impact medium · tested against Proof next to the claim* ### Differentiation **Add model size and hardware detail under "render at full detail, every surface intact".** The rendering claim names no file size or device, so readers assume marketing language. State the federated model size in GB, component count, and the headset or iPad it ran on. *effort medium · impact high · tested against Proof next to the claim* **Move the Autodesk, Procore and Revizto sync line into the hero subhead.** The three-way sync with existing tools is the reason buyers gave for choosing Resolve, but it sits far down the page. Name the three tools on the first screen. *effort low · impact high · tested against Give a reason to choose you* **State in the "Massive BIM, now usable" section whether Resolve detects clashes or displays them.** "Catch what clash detection misses" leaves readers unsure whether Resolve runs its own detection or views models from other engines. Say plainly which work Resolve does and which stays in the coordination tool. *effort low · impact high · tested against Answer the live objection* ### Clarity **Change "Catch what clash detection misses" to name what reviewers find in VR.** The line invites readers to guess whether Resolve replaces their clash engine. Say the specific constructability problems VR walkthroughs surface that automated clash reports do not. *effort low · impact medium · tested against Concrete over abstract* ### Brand alignment (side metric) **Name three customer companies beside the "450+ Companies" figure.** A company count with no recognizable logos reads early-stage to VP and budget-holding readers. List named general contractors or owners next to the figure. *effort low · impact high · tested against Proof next to the claim* **Move SOC 2 and security details up beside the integrations section.** Security and compliance sit near the page bottom, so senior buyers evaluating IT risk never reach them. Put SOC 2 status, data handling, and access controls next to the Autodesk and Procore sync block. *effort medium · impact medium · tested against Answer the live objection* **Replace "without the complexity" in the hero with a concrete buyer outcome.** "High-performance BIM without the complexity" says nothing a reader can picture and was called vague. Name what field teams stop doing, such as waiting on the office for a dimension. *effort low · impact medium · tested against Concrete over abstract* --- ## 03 · What is working ### The hero line and role naming make the problem and audience clear on first screen Eleven points said the offer, problem, and intended users were obvious without hunting, crediting the hero line, the explicit role/persona names, and the three-tab layout. Several described it back as a multi-platform BIM coordination tool for field teams. > It was obvious within the first screen — "Give field teams, owners, and reviewers the context they need to stay aligned and accelerate work from design through delivery" > > — BIM Coordinator, Manufacturing, 501-1000 > big BIM files made light enough to actually use, for design review and field verification > > — BIM Coordinator, Manufacturing, 501-1000 > the section headers "Design/Preconstruction" and "Construction/Commissioning" map straight onto the two named user types, which is more explicit than most of these pages > > — Project Manager, Construction, 5000+ > It's a BIM viewing/collaboration layer that sits on top of your existing models — lets you pull in huge federated models from Autodesk and Procore and review them in VR, on iPad in the field, or on the web, and syncs issues with Revizto. > > — Project Engineer, Engineering, 51-200 > They make a BIM viewer/collaboration tool that takes big, dense federated models and makes them usable on VR headsets, iPads on-site, and the web > > — BIM Coordinator, Pharma and Life Sciences, 1001-5000 > the intended readers aren't just implied, they're named by role - reviewers, field teams, owners, superintendents, foremen, project managers. I didn't have to hunt for it; it's in the first two screens. > > — Design Manager, Construction, 5000+ ### Named Autodesk, Procore and Revizto integration is the differentiator respondents could… Five points named the three-way sync with existing tools as the concrete, differentiated strength, saying it proves compatibility, reduces implementation risk, and removes the 'another silo' objection common to BIM viewers. > Resolve pulls models from Autodesk and Procore and syncs issues with Revizto" means it slots into what we already run instead of asking us to rip anything out > > — BIM Manager, Heavy Infrastructure, 201-500 > "Resolve pulls models from Autodesk and Procore and syncs issues with Revizto" — because that's the stuff we already run, and "setup takes less than 5 minutes" > > — BIM Coordinator, Manufacturing, 501-1000 > Resolve pulls models from Autodesk and Procore and syncs issues with Revizto" — because that's concrete and checkable > > — Design Manager, Pharma and Life Sciences, 1001-5000 > if that sync is real and low-friction it removes the usual "another silo" objection I have with every BIM viewer pitch > > — Project Manager, Construction, 5000+ --- ## 04 · What the personas said ### The page never states whether Resolve detects clashes or only displays them Three points flagged unresolved definition: two respondents could not tell if the product detects clashes or is a visualization layer over other engines, and one called the hero word 'complexity' vague. > the only soft spot is the word "complexity" in the hero line, since it never says whose complexity: model size, IT setup, or training — that's the one vague noun I'd want swapped for something concrete. > > — Project Manager, Construction, 5000+ > the page never states plainly whether Resolve does any detection itself or is purely a viewer/sync layer — words like "context," "aligned," and "accelerate work" describe benefits, not mechanism > > — BIM Manager, Manufacturing, 501-1000 > It sits on top of your existing clash detection and coordination tools (Revizto sync for issues) rather than replacing them; it's really a model-access and issue-tracking layer for construction, not a new authoring or detection engine. > > — BIM Manager, Manufacturing, 501-1000 ### Case studies do not cover respondents' own sector or geography Three points found no relevant proof: a European GC at their project scale and regulatory context, and pharma/life-sciences examples despite regulated workflows. > I'd need a named case study from a European GC or data center build near our scale — right now it's all data center stats with no geography > > — Project Manager, Construction, 5000+ > A named pharma or life-sciences case study, or even just a line acknowledging cleanroom/process-piping MEP density and regulatory sign-off workflows, would do it — right now every proof point is a data center or generic commercial job > > — BIM Coordinator, Pharma and Life Sciences, 1001-5000 ### The outcome numbers are compelling but read as unsourced testimonials rather than… Eight points said the quantified claims — 4-week schedule cuts, sign-off and issue-detection speed — lack baseline methodology, project size, named companies, or file-size and timeline detail. Three would need a pilot or documented case study on comparable… > A documented case where a distributed sign-off cycle actually collapsed from weeks to days on a model our size — with the file size, team locations, and before/after timeline spelled out, not just a headline stat > > — VDC Director, Engineering, 51-200 > "4 weeks cut from coordination schedule" and "10x avoided risks" stats are the kind of thing that would justify a meeting, but they're unsourced and vague — cut from what baseline, avoided risks measured how > > — VDC Director, Engineering, 51-200 > A named heavy-infra or large-GC customer with a stated project size saying field verification via iPad actually cut RFIs or rework — one real, checkable reference beats every stat on this page. > > — BIM Manager, Heavy Infrastructure, 201-500 > the "4 weeks cut from coordination schedule" and the data center customer quote about finding "more issues in 30 minutes with Resolve than in hours of page turns" are the kind of concrete numbers that would matter to me, since my whole pain point is getting scattered reviewers and field folks aligned fast. That's worth a demo, but before I'd pitch it internally I'd want to know which of those named customers is closest to my situation > > — Project Engineer, Engineering, 51-200 > those numbers are unsourced testimonials, not a case study I can verify > > — VDC Director, Heavy Infrastructure, 201-500 ### Performance claims are unattributed, so respondents want a load test before believing them Two points rejected the rendering and performance claims as lacking project context or credibility, and asked for a live test on actual 40GB+ federated models. > the performance claims are all unsourced aggregate stats — "3 months ahead of schedule," "4 weeks cut," "10x avoided risks" — with no project type, size, or methodology attached > > — Design Manager, Pharma and Life Sciences, 1001-5000 > I've heard that from three other vendors and watched it choke on our actual federated models, so I'd want to see them open one of our real 40GB+ site models live, not a curated demo file > > — Project Manager, Construction, 5000+ ### The brand looks early-stage and mistargeted for senior buyers Two points undercut credibility with VP-level and budget-holding readers: no recognized customer names despite a stated customer count, and security/compliance and integration depth buried near the bottom. One noted the tone speaks to construction ops, not… > 450+ companies across 38 countries" is a headcount, not a name I recognize, and that's the gap between confident marketing copy and something I'd actually trust enough to book a demo > > — BIM Manager, Heavy Infrastructure, 201-500 > the "Enterprise Ready — SOC 2 Type II" line sitting almost as an afterthought; if they're chasing 5000+ employee companies like mine, I'd expect security/compliance and integration depth pushed harder up front, not buried near the bottom > > — Project Manager, Construction, 5000+ ### The page reads as aimed at enterprise data-center and large-GC buyers, excluding other… Five points placed the positioning at enterprise/large-infrastructure construction based on SOC 2, data-center capacity, and project-scale language. Three noted this excludes mid-size engineering firms, pharma, and regulated industries; one saw the fit as… > The tone is client-services-slick — "It's time to build in months, not years," logos-and-stats format — which reads like it's aimed at owners and GCs on the biggest projects, not really at someone like me doing 2D plan management > > — VDC Director, Engineering, 51-200 > more likely 50-200 people, a few years in market, selling mostly into large GCs and mission-critical/data center builders given how hard they lean on the 8GW data center stat > > — Project Manager, Construction, 5000+ > the "$110B+ of construction projects," "8GW of data center capacity," and "SOC 2 Type II compliant" lines are clearly aimed at someone doing due diligence on a big program > > — VDC Director, Heavy Infrastructure, 201-500 > The tone is aimed at construction VDC/BIM leads and field ops people rather than at someone like me evaluating it as a category purchase — it assumes I already know I need better model access and just need convincing on speed/ROI > > — BIM Manager, Manufacturing, 501-1000 > it's clearly written with a data-center/general-contractor buyer in mind first — the case studies are all 40MW and 1.8M sq ft data centers — so as a pharma BIM coordinator I feel like an adjacent audience they haven't quite tailored the pitch to yet > > — BIM Coordinator, Pharma and Life Sciences, 1001-5000 --- ## 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 strongest numbers are its weakest asset — proof collapses at the moment of evaluation.** *(high)* Eight points said the 4-week schedule cuts and sign-off speed lack baseline methodology, project size, or named companies, and three would need a pilot before believing them. The headline value proposition therefore cannot survive scrutiny. - **Clarity is being mistaken for credibility: readers understand the offer and still refuse to believe it.** *(high)* Eleven points credited the hero line for making problem and audience obvious, yet eight points rejected the outcome numbers as unsourced and two demanded a live load test. Comprehension is high and conviction is absent. - **The page disqualifies buyers it never intended to exclude.** *(high)* Five points read the positioning as enterprise data-center and large-GC only, with three noting the exclusion of mid-size engineering, pharma, and regulated firms; three more found no case study matching their sector or geography. - **Performance claims invite a test the page cannot pass, handing buyers a reason to stall.** *(medium)* Two points rejected rendering and performance claims for lacking project context and asked for a live test on actual 40GB+ federated models. Unattributed specifics convert interest into a procurement hurdle. - **The integration story is the only durable differentiator, and it is carrying the entire page.** *(medium)* Five points named the Autodesk, Procore and Revizto sync as the concrete differentiated strength, while performance and outcome claims were rejected across ten points. Remove the integrations and nothing defensible remains. - **Senior buyers are shown no signal of institutional legitimacy.** *(medium)* Two points flagged the absence of recognized customer names despite a stated customer count, with security, compliance and integration depth buried at the bottom; one noted the tone addresses construction ops rather than budget holders. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | VDC Director | Engineering | 51-200 | | 2 | BIM Manager | Heavy Infrastructure | 201-500 | | 3 | BIM Coordinator | Manufacturing | 501-1000 | | 4 | Design Manager | Pharma and Life Sciences | 1001-5000 | | 5 | Project Manager | Construction | 5000+ | | 6 | Project Engineer | Engineering | 51-200 | | 7 | VDC Director | Heavy Infrastructure | 201-500 | | 8 | BIM Manager | Manufacturing | 501-1000 | | 9 | BIM Coordinator | Pharma and Life Sciences | 1001-5000 | | 10 | Design Manager | Construction | 5000+ | | 11 | Project Manager | Engineering | 51-200 | | 12 | Project Engineer | Heavy Infrastructure | 201-500 | | 13 | VDC Director | Manufacturing | 501-1000 | | 14 | BIM Manager | Pharma and Life Sciences | 1001-5000 | | 15 | BIM Coordinator | Construction | 5000+ | --- ## 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-16, then deleted along with the personas and their answers.