to eight distinct product areas: Workflows, Sequences, Call Intelligence, Reporting, a Developer Platform, Universal Context, data enrichment, and infrastructure stats. By the time the visitor reaches the second scroll, the page has stopped arguing for one thing and started cataloguing a platform. The buyer who landed on "the AI CRM engineered for scale" came to understand why Attio beats Salesforce or HubSpot on the specific job they're trying to do; instead they get a product menu. The move is to pick the one capability that no competitor can credibly claim — the agent orchestration layer, if that's genuinely differentiated — and build every section around proving that one thing works, with the other features subordinated as supporting evidence rather than co-equal headlines.

The three customer quotes are all about the CRM itself — "dev company's dream CRM," "next generation of CRM," "understand our customers" — none of them describe agents doing anything. The infrastructure stats ("1000+ agents running now," "sub-50ms latency") are self-reported numbers with no customer attached to them. The visitor is being asked to believe that autonomous revenue agents are working around the clock, and the only evidence offered is a counter Attio controls. Find one customer — a named person at a named company — who can say what an agent did for their pipeline, in specific terms, and put that above the fold. That single piece of proof does more work than all four feature sections combined.

The self-serve path ("Start for free," "14 days of Pro") targets a founder or early sales hire who wants to try before committing. The enterprise path ("Talk to sales," ISO 27001, GDPR, CCPA, infrastructure scale claims) targets a revenue ops leader at a company with compliance requirements and a procurement process. These two buyers read the same page and each finds signals that confuse them: the self-serve buyer hits "Talk to sales" and wonders if this is actually a sales-led product; the enterprise buyer hits "Start for free" and wonders if this is mature enough for their stack. The fix is sequencing, not removal — lead with the self-serve path for the first two CTAs, then introduce the enterprise path after the infrastructure and security section, so each buyer encounters the right signal at the right moment in their read.

A buyer evaluating whether to leave HubSpot needs to know migration is handled before they'll engage with anything else on the page. Pull the migration claim out of the footer and put it in its own section, with a specific time claim ("migrate your HubSpot data in under 30 minutes") and a link to the docs. That one move removes the objection that kills the most consideration-stage visitors.