Audited for a VP of Data evaluating replacement analytics stacks. Goal: booked technical demos.
The page reads as competent and confident but leaves the buyer to assemble the value on their own. The hero speaks in generic outcomes, pricing is present but unanchored to team size, and social proof does not include a name a VP of Data at a mid-market SaaS would recognize.
'Book a demo' appears as a solid dark button in the header and as an outlined link-style control in the mid-page band, teaching two visual meanings for one action.
Fix:Use the solid treatment everywhere for the primary action; reserve the outline for genuinely secondary paths.
The inline form requests work email, company size, and current stack before the page has explained what the product replaces.
Fix:Ask for work email only. Collect the qualifying fields on the confirmation step, after the commitment is made.
The hero uses isometric 3D renders, the features section uses flat two-color spot illustrations, and the customer logos strip breaks into duotone photography. Nothing binds them.
Fix:Pick one family — the spot illustrations are strongest and cheapest to extend. Remove isometrics; treat logos as monochrome.
Section headings appear at 32, 28, and 26px on the same page, and body copy alternates between 17 and 16px with no consistent rule.
Fix:Collapse to a three-step scale — display, section, body — and enforce it with tokens rather than one-off overrides.
The 'Book a demo' button renders with outline removed and no replacement indicator. Keyboard users tabbing from the nav lose their position at the most important control on the page.
Fix:Restore a visible focus style on the button — a 2px ring in the accent color with 2px offset satisfies the design and WCAG 2.4.7 at once.
Secondary paragraphs and the pricing fine print use a light gray on white that measures near 3.4:1. This affects the feature descriptions and every 'starting at' line.
Fix:Darken the muted text token one step until it clears 4.5:1 on white. Keep the visual hierarchy by adjusting size and weight instead of lightness.
The integrations grid uses logo marks alone, and the nav uses a bare chevron for the product menu. Nothing announces their purpose to assistive tech.
Fix:Give each icon a text label or an aria-label naming the destination; mark purely decorative marks aria-hidden.
The headline says 'Modern data, decided.' The subhead adds 'Analytics that move at your speed.' Neither phrase names the product category. A VP of Data cannot tell if this is a warehouse, a BI tool, a semantic layer, or a metrics store.
Fix:Rewrite the hero to name the category in the first six words. Reserve the second beat for the poetry.
Tiers are labeled Starter, Team, and Enterprise with per-user prices, but nowhere on the page does a mid-market buyer see a shape that matches a 200-person org.
Fix:Add an anchor row above the tiers: 'Teams of 50–500 typically start on Team at ~$X/mo.' One line, no calculator.
Logos strip shows early-stage consumer brands. No mid-market SaaS logos, no data-team quotes, no analyst mention.
Fix:Swap two logos for peer-recognizable mid-market SaaS names. Add one quote from a Head of Data.
The quote naming a measurable outcome sits in slide three of four and rotates away after roughly five seconds.
Fix:Replace the carousel with two static quotes and lead with the one that carries a number.
The hero claims teams make decisions 10x faster, but no customer, study, date, or method is attached to the number.
Fix:Attach a named customer, dated benchmark, and short methodology note to the claim, or replace it with a supportable outcome.
Security, migration, and support details appear only near the footer, after every primary demo prompt on the page.
Fix:Place a compact trust row beside the first demo CTA linking to security, migration, support, and data-export details.
The page is legible to search engines but hard for an AI assistant to answer from. The category is never named in plain words, the strongest facts live inside images, and there is no self-contained sentence a model could quote when someone asks what this product is or who it is for.
The H1 sells an outcome instead of naming the product category, so the page competes on brand terms it does not own yet.
No single sentence states what the product does, for whom, and at what price — the three things assistants lift most often.
Two named customers and one dated benchmark are citable; the rest of the proof is unattributed superlatives a model will skip.
The hero reads 'Decisions at your speed' with no sentence naming what the product is, so a model has nothing to match against a category question.
Fix · Add one sentence under the H1: 'Acme is warehouse-native analytics for mid-market SaaS teams running on Snowflake or BigQuery.'
Tier prices render inside a visual table with no adjacent text stating price, seat count, or what changes between tiers.
Fix · Restate each tier in a plain text line — 'Team: $499/mo, up to 25 seats, unlimited dashboards' — directly beneath the table.
'Trusted by thousands' and '10x faster queries' carry no source or date, so an assistant will drop both rather than cite them.
Fix · Replace each with a dated, sourced fact: '10x faster median query time vs. our prior stack — internal benchmark, March 2026, 4.2B row table.'
Every section heading is a slogan; none matches how a buyer phrases the concern the section answers.
Fix · Rewrite three headings as the buyer's question — 'How long does migration actually take?' — and answer in the first sentence below.
Commit to the developer-first read. The code sample is the only element on this page a competitor cannot copy in an afternoon — move it above the fold and let the buyer-facing proof follow it.
The page leans on outcome language — 'decided', 'at your speed', 'without the drag' — that any competitor in the class could publish unchanged. Three claims ('10x faster queries', 'trusted by thousands', 'zero migration effort') carry no source, date, or method, and the last one is contradicted by the migration guide linked in the footer. Either substantiate each claim inline or remove it; unsourced superlatives are the fastest way to lose a technical buyer who is already suspicious of the category.
We do not guess. These require live testing.
Every finding, the fix list, editor prompts, and the distinctiveness read. One payment, no subscription.
Paste any of these straight into Lovable, Cursor, or whichever AI editor builds your page. Each one carries the evidence, the change, and the constraints needed to land the fix without collateral damage.
Fix this on acme-analytics.example.com/pricing: Task: Name the product category in the first six words of the hero Problem observed: The headline says 'Modern data, decided.' The subhead adds 'Analytics that move at your speed.' Neither phrase names the product category. A VP of Data cannot tell if this is a warehouse, a BI tool, a semantic layer, or a metrics store. Recommended change: Rewrite the hero to name the category in the first six words. Reserve the second beat for the poetry. Why it matters: A VP of Data can qualify the page in one glance instead of scrolling to the features grid Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: A VP of Data can qualify the page in one glance instead of scrolling to the features grid and the change is visible above the relevant section on both mobile and desktop.
Fix this on acme-analytics.example.com/pricing: Task: Restore a visible focus ring on the primary CTA Problem observed: The 'Book a demo' button renders with outline removed and no replacement indicator. Keyboard users tabbing from the nav lose their position at the most important control on the page. Recommended change: Restore a visible focus style on the button — a 2px ring in the accent color with 2px offset satisfies the design and WCAG 2.4.7 at once. Why it matters: Keyboard and screen-reader users can reach and confirm the most important control on the page Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: Keyboard and screen-reader users can reach and confirm the most important control on the page and the change is visible above the relevant section on both mobile and desktop.
Fix this on acme-analytics.example.com/pricing: Task: Anchor pricing to a recognizable team size Problem observed: Tiers are labeled Starter, Team, and Enterprise with per-user prices, but nowhere on the page does a mid-market buyer see a shape that matches a 200-person org. Recommended change: Add an anchor row above the tiers: 'Teams of 50–500 typically start on Team at ~$X/mo.' One line, no calculator. Why it matters: Mid-market buyers self-select a tier without contacting sales to find the shape that fits them Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: Mid-market buyers self-select a tier without contacting sales to find the shape that fits them and the change is visible above the relevant section on both mobile and desktop.
Fix this on acme-analytics.example.com/pricing: Task: Reduce the page to one illustration family Problem observed: The hero uses isometric 3D renders, the features section uses flat two-color spot illustrations, and the customer logos strip breaks into duotone photography. Nothing binds them. Recommended change: Pick one family — the spot illustrations are strongest and cheapest to extend. Remove isometrics; treat logos as monochrome. Why it matters: The page reads as one product from one company rather than three campaigns stitched together Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: The page reads as one product from one company rather than three campaigns stitched together and the change is visible above the relevant section on both mobile and desktop.
Fix this on acme-analytics.example.com/pricing: Task: Cut the demo form to work email only Problem observed: The inline form requests work email, company size, and current stack before the page has explained what the product replaces. Recommended change: Ask for work email only. Collect the qualifying fields on the confirmation step, after the commitment is made. Why it matters: Fewer abandoned submissions at the exact moment intent is highest Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: Fewer abandoned submissions at the exact moment intent is highest and the change is visible above the relevant section on both mobile and desktop.
Fix this on acme-analytics.example.com/pricing: Task: Darken the muted text token until it clears 4.5:1 Problem observed: Secondary paragraphs and the pricing fine print use a light gray on white that measures near 3.4:1. This affects the feature descriptions and every 'starting at' line. Recommended change: Darken the muted text token one step until it clears 4.5:1 on white. Keep the visual hierarchy by adjusting size and weight instead of lightness. Why it matters: Feature descriptions and pricing fine print become readable for low-vision users and in daylight Constraints: - Reuse the existing design tokens, components, and typography — do not introduce new styles or colors. - Only touch the section(s) involved in this task; leave the rest of the page unchanged. - Match the existing voice and reading level of the page copy. - Keep the layout responsive and accessible (contrast, focus states, semantic markup). Done when: Feature descriptions and pricing fine print become readable for low-vision users and in daylight and the change is visible above the relevant section on both mobile and desktop.