Get yours — $79

Sample teardown: AnySearch AI

A real 15-point PageRoast teardown, published with blunt honesty. anysearch.ai — multi-tenant AI search for telecom & enterprise. Reviewed Aug 8, 2026.

1. The headline is a category label, not a pitch.HIGH

"Multi-Tenant AI for Telecom & Enterprise" tells me what it is, not what I get. The subhead ("Years of data, answers in seconds") is the actual hook — it's sharper and should lead.

Fix: lead with the outcome, qualify with the niche: "Every answer in your company's data, in seconds — with enterprise-grade tenant isolation."

2. Two competing CTAs with no hierarchy.HIGH

"Request a Demo" and "Sign In" sit side by side in the hero with equal visual weight. "Sign In" is for existing customers — it has no business sharing the hero with your one conversion action.

Fix: one primary button ("Request a Demo"), demote Sign In to the nav.

3. Eight product surfaces = eight reasons to leave.HIGH

Multi-Agent AI Search, Structured Explorer, Field-Service Analytics, Customer Map, Passwordless+Passkey, Multi-Tenant Isolation, AEPD Audit, Mobile+API — each is a full product. A first-time visitor can't tell which one they're buying.

Fix: pick the one that closes deals (Multi-Agent AI Search) and make the rest "also included" proof points.

4. Your stats are unsubstantiated self-claims.MED

"15+ Years of Telco Data · 800M+ Records Indexed · 99.9% Uptime · <50ms Avg Response" — impressive numbers with no source, logo wall, or case study behind them. Enterprise buyers discount unsourced numbers to zero.

Fix: attribute them ("across N production tenants") or anchor one to a named customer.

5. Zero named customers anywhere.HIGH

For an enterprise product asking for a sales call, there is not a single customer name, logo, quote, or case study on the page. "Join enterprises that are already using AnySearch AI" — which enterprises?

Fix: even one named quote ("Head of Ops, Spanish ISP") outperforms every feature card.

6. The demo screenshot is buried and tiny.MED

The phone mockup showing "Show fiber installs this month → Found 24 fiber installations" is the most convincing asset on the page — a real query returning a real answer — and it's an afterthought at the bottom.

Fix: make a full-width version of that interaction the hero image.

7. "How it works" is generic SaaS filler.MED

"1 Connect 2 Index 3 Search" could be pasted onto any data product. It answers no buyer question (How long is setup? What breaks? Who maintains it?).

Fix: replace with "Live in a week: we connect to your stack, no warehouse required" — address the real objection.

8. No pricing signal at all.MED

"Usage-based pricing" appears once in a badge row. Enterprise buyers need to know whether this is $5k or $500k before booking a call — silence reads as "expensive."

Fix: "From €X/month" or "Pilot pricing available" removes the mystery tax on demo requests.

9. The compliance flex is mis-positioned.LOW

"Cross-tenant queries are structurally impossible — not just policy" is a genuinely great line... for the security page. In the features grid it competes with value props.

Fix: keep one trust line in the hero subhead, move the deep detail to a security section.

10. Passwordless auth as a feature card?LOW

Passkeys/TOTP are table stakes in 2026, not a differentiator — it spends a feature slot on something buyers assume.

11. Jargon density filters out non-technical buyers.MED

"OpenSearch index prefix, RBAC scope, audit ledger, JWT contract" — the person who signs (COO/VP Ops) doesn't speak this. The person who evaluates does. You serve neither fully.

Fix: outcome language up top, spec sheet linked below.

12. "Born from a simple observation" story says nothing.LOW

The origin paragraph is interchangeable with every enterprise SaaS about page. A specific moment ("a Tier-1 carrier's support team spent 6 hours finding one install record") would make it real.

13. Mobile apps before product-market proof.LOW

"Request Beta Access — iOS/Android" for apps that aren't out, mid-page, splits attention from the demo CTA. Park it in the footer until launch.

14. The final CTA is weaker than the first.MED

The page ends on "Contact Sales" — a third CTA variant (after "Request a Demo" and "Request Beta Access"). Three different asks across one page means none of them are optimized.

Fix: one ask, repeated verbatim, top and bottom.

15. Language switcher hints at a market the page doesn't serve.LOW

A "Language" toggle in the footer for a single-language page suggests unfinished internationalization — small trust ding for detail-oriented buyers.

Rewritten hero (paste-ready)

BEFORE

"Multi-Tenant AI for Telecom & Enterprise — Years of data, answers in seconds"

AFTER

"Your support team spends hours hunting answers. Ours answers in seconds."

AnySearch AI indexes your customer records, tickets, and field data into one AI search — with tenant isolation and audit trails your compliance team will actually sign off on. Live on your data in a week.

[ Request a Demo ] SOC 2 · AEPD-grade audit · 99.9% uptime

Priority order

If you change five things, in this order: (1) hero headline → outcome, (2) one CTA everywhere, (3) name one customer, (4) source the stats, (5) make the demo interaction the hero visual.

Get this for your page — $79, <24h

Full refund if it's not actionable. Questions: kimmy@inkboxmail.com