The hero ("Ship faster, resolve smarter, sleep better") and the subheadline ("AI agents automate the toil") are written for a buyer who doesn't know PagerDuty yet, but the actual visitor is product-aware: they're an SRE or engineering leader who already uses or has evaluated PagerDuty, and they came to understand what's changed. The page never answers that question directly. It announces a new identity without explaining what's new, which means the buyer who already knows the brand gets no upgrade signal, and the buyer who doesn't know the brand gets no category anchor. The move is to add a single orienting sentence in the hero — something that names what PagerDuty was and what it is now — so both audiences can place themselves.

The tab toggle "Practitioners / Developers — Technical Leaders" promises two distinct paths, but both paths lead to the same page with the same copy. The hero is written for a practitioner ("sleep better," "build, not firefight"), the data foundation section is written for a technical leader ("16 years of data, 750+ integrations, AI agents orchestrate across your entire tech stack"), and the proof section mixes individual contributor quotes with director-level outcome metrics without separating them. A Director of Technology Operations evaluating a platform consolidation decision and an SRE evaluating whether to adopt the SRE Agent are not the same buyer, they don't share the same objections, and they shouldn't be reading the same page. The move is to either commit to one primary buyer in the homepage and route the other to a dedicated landing page, or make the tab toggle actually do something — different hero, different proof, different CTA for each audience.

The strongest evidence — "30% reduction in response times at SAP," "mean-time-to-action dropped from minutes to seconds at Cloudflare," "25,000 automated jobs daily" — appears below three feature sections and a platform overview. The first thing the visitor encounters after the hero is a stat card row ("Reduced Disruptions 59%," "More Productive Teams 27%") attributed to a "Total Economic Impact study," which is PagerDuty's own commissioned research, not a customer. The named customer proof that would actually move a skeptical engineering leader doesn't appear until the buyer has already read through the product pitch. Move the SAP and Cloudflare quotes — with their specific metrics — into the second section, directly after the hero, before any feature description. The buyer needs to see that someone they recognize has already made this bet.

The SRE Agent section says it "detects, triages, diagnoses, and fixes incidents on its own" — which is a significant claim — but the only evidence offered is a 2-minute demo video and a "Learn more" link. Newer, smaller competitors like Incident.io and FireHydrant are making similar autonomous-response claims, and the buyer who has read those pages will arrive here asking the same question: what does this actually look like when a real incident fires at 2am? The page has a 2-minute demo video buried in the platform section; that video should be surfaced immediately after the SRE Agent claim, not after the buyer has already decided whether to believe it.