LYTMS
The tab toggle promises two buyers a different page; both get the same one.
“AD: "Get actionable strategic recommendations to integrate Agentic AI into your IT ecosystem and drive business value." | LP: "End-to-end incident...”
Either change ads 1 and 3 to lead with the free trial product CTA (cheaper, aligns with LP), or create a separate landing page for the strategic recommendations/resource download to match the ad promise.
Get the ship-ready rewrite →Visitors clicking ads 1 and 3 expect a strategic consulting resource or whitepaper with recommendations for their IT transformation. They land on a product trial signup instead. The ad frames this as advisory/guidance-driven, but the LP...
Not five scoring areas. Five questions, asked in sequence. The page is judged on how many it answers before the visitor gives up.
The page is trying to reposition PagerDuty as an AI-first platform while the product the buyer already knows is an incident management tool — and it never resolves that tension.
▸ Read the full takeCollapseThe 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 page carries two simultaneous positioning claims that point at different buyers, and neither one wins.
▸ Read the full takeCollapseThe 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.
“AD: "Get actionable strategic recommendations to integrate Agentic AI into your IT ecosystem and drive business value." | LP: "End-to-end incident management that gets smarter over time. AI agents automate the toil, freeing you to focus on what matters. Start free trial"”
“The page carries eight named testimonials and several stat callouts (30% faster response, 25% fewer responders, 90% SOX audit reduction) but no linked case studies. The footer navigation lists 'Customer Stories' as a resource, but no customer story content surfaces on the homepage or links from any testimonial. Surface”
“We chose PagerDuty because we had to do less work to make PagerDuty work with our systems. Mean-time-to-action has dropped from multiple minutes to seconds. minutes to seconds change in mean-time-to-action Senior Engineering Manager, Cloudflare”
Every finding named, quoted, and paired with the rewrite — that’s how Lytms reads a page. Run it on your own site to see all of yours, free.
Proof architecture, named-customer recognition, imagery authenticity, claim-vs-evidence gaps.
Hero value, conversion-killing sentences, cliché density, awareness fit, buyer-language gap, competitive differentiation.
A live feed of what the category is moving toward, with a drafted response for the moves worth responding to.
Pick one competitor on Pro. Same scoring this page is held to. Same-day alert when they ship a homepage change.
Mine reviews, transcripts, support, social. Ranked, attributed, matched against the homepage.
Accept, edit, ship. An action queue tied to a CMS or copied straight to clipboard.
Lytms reads any B2B homepage the same way — verdict, five scores, every line that costs the visit. Free to run. Full report and drafted rewrites on Pro.
The proof on this page is abundant but structurally misplaced.
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 page names "AI agents" as the central claim but never shows the buyer what an agent actually does in a moment they recognize.
▸ Read the full takeCollapseThe 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.