LYTMS
Your page declares a new category but never shows what changes for the buyer who stays in the old one.
“Customer logos are detected on the page, but the visual notes reference only Juniper Networks and Lenovo in testimonial context. No logo bar with...”
Add a named logo bar (6–8 logos, company names visible) between the hero and the body section. Enterprise buyers scan for peer-company recognition before reading further.
Get the ship-ready rewrite →Your customer logos are present but unnamed — visitors see brand marks without knowing which companies trust you at enterprise scale.
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 win a category war and a feature battle at the same time, and the two goals cancel each other out.
▸ Read the full takeCollapseThe headline declares "The First AI-Native GTM Platform" — a category-level claim that asks the buyer to stop shopping in the old frame and adopt a new one. But the body immediately drops into a feature inventory: Workflows, Actions, Agents, Tables, Chat, Infobase, Brand Voice, 2,000+ integrations, six named use cases. A buyer who landed on a category claim is now reading a product catalog. The page never answers the one question the category claim creates: what does it mean to be "AI-native" versus what HubSpot or Salesforce Einstein is doing right now, and why does that difference matter to this buyer's quarter? Cut the feature inventory from the body section and replace it with a single concrete demonstration of what the platform does that a stack of copilots cannot — one workflow, one outcome, one number.
The page has three testimonials that each prove a completely different thing, and the cumulative effect is that none of them land.
▸ Read the full takeCollapseJean English's quote proves pipeline volume ("5x more meetings"). Roman Olney's quote proves cost savings ("$16 million dollars"). Ashley Levesque's quote proves discovery — she didn't know she needed this. These are three different buying motivations, three different buyer stages, and three different objections being addressed simultaneously. A CMO evaluating a platform consolidation play reads all three and can't tell which one is meant for her. The page should pick the proof that matches the primary buyer it's built to convert — if that's the enterprise GTM leader consolidating tools, Roman Olney's $16M claim is the one to lead with, expand, and repeat — and move the others to a dedicated proof page or use-case-specific sections.
The page's single CTA is "Get a Demo," and it appears to be the only conversion path on the page.
“Customer logos are detected on the page, but the visual notes reference only Juniper Networks and Lenovo in testimonial context. No logo bar with named enterprise accounts appears above the fold or in a dedicated social proof section separate from the three testimonial quotes.”
“Every CTA on the page routes to a demo request. No free trial link, no interactive product tour, no 'explore the platform' path exists. The offer_strength module found nothing to evaluate because the offer is structurally thin — one action, one outcome.”
“Competitor data is available. HubSpot, Salesforce Einstein, and 6sense are direct category peers. The page's differentiation copy ('LLM Model Agnostic,' '2,000+ integrations,' 'unified platform') is feature-level, not architectural. No comparison table, no 'why not HubSpot' section, no named contrast exists.”
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.
Call-to-action clarity, visual weight, offer strength, form friction, CTA-to-page match.
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 business profile shows a pricing page exists and a login link is in the nav, which means some portion of the 17 million users the page cites arrived through a self-serve path — but the homepage offers none. A marketing leader at a 200-person SaaS company who lands here and wants to explore before committing to a sales conversation has nowhere to go except away. The "Get a Demo" gate is appropriate for the $16M Lenovo buyer; it is a dead end for the mid-market operator who came from a search or a peer recommendation and wants to see the product before talking to anyone. Add a second path — a free trial, a sandbox, or a live product tour — and let the buyer self-select. The page is currently filtering out the segment it claims to have 17 million of.
The headline says "Goodbye AI Copilots.
▸ Read the full takeCollapseGoodbye Point Solutions." — a positioning move that only works if the buyer already knows they have a copilot problem. The ICP here is a marketing leader or GTM operator at a mid-market to enterprise SaaS company. That buyer may be running Outreach, a content tool, an ABM platform, and a forecasting tool, and experiencing real pain from the fragmentation — but they don't call it a "copilot problem." They call it "our stack is a mess" or "we can't get a consistent view of pipeline" or "every team is doing AI differently." The page speaks in the vendor's language about the vendor's category frame, not in the buyer's language about the buyer's felt pain. The subheadline gets closer — "GTM bloat" is a phrase that might resonate — but the hero never names the specific operational failure the buyer is living through before it offers the solution. Open with the buyer's situation, not the category declaration.