Questions about PlayHero°

PlayHero° is WebUX intelligence for GTM teams: specialist agents monitor your site, surface high-confidence issues as Rallycards, and log every approve / dismiss / defer decision on a permanent Heroboard. Four launch agents — UX Sentinel, Drift Detector, Page Vitals Enforcer, and Lumen — cover conversion UX, metric drift, Core Web Vitals, and AI discoverability. Humans approve every action; nothing executes on your site without you.

WebUX stands for Web User Experience as it relates to conversion. PlayHero measures WebUX across seven scored dimensions: CTA Clarity, Content Clarity, Signal Hierarchy, Load Intelligence, Messaging Clarity, Conversion Friction, and Agent Visibility. A WebUX score is a 0–100 composite that reflects how well your website converts visitors into leads — not how it looks, but how well it performs at its commercial job.

Enter your URL on the PlayHero homepage and run a free scan. In about 60 seconds you get a WebUX score, seven-pillar breakdown, and up to three Rallycards — no account or card. Create a free account when you want to save results, open a basic Heroboard, and run Compare. Upgrade to Growth when you need continuous monitoring, all agents, more URLs, and team workflows.

Yes. Public scans stay free: unlimited URLs, no account required, no credit card. Credits never apply to scanning — they only pay for optional on-demand outputs (e.g. CRO briefs, competitor comparisons) inside the product after you sign up.

A PlayHero scan completes in 60 seconds or less. The scan runs four detection layers simultaneously: DOM structure analysis, LLM messaging interpretation, Lighthouse performance measurement, and viewport simulation across common screen sizes. Results are available immediately in the browser — no waiting for an email report.

A WebUX score is a 0–100 composite score measuring your website's conversion health. Scores below 60 indicate conversion-critical issues. Scores between 60 and 75 indicate meaningful opportunity. Scores above 75 indicate a well-optimized site with incremental improvement available. The score is calculated from seven pillar scores — each weighted by its impact on conversion — and recalculated on every scan so you can track improvement over time.

Yes — this is one of the fastest-growing use cases for PlayHero°. When a prospect uses an AI assistant to research solutions in your category, that assistant reads and parses your website rather than browsing it visually. PlayHero° scans for signals that affect both human visitors and AI parsers: structured data presence, page content machine-readability, pricing page clarity, and whether key conversion content is accessible without JavaScript execution. The Agent Readiness findings surface as Rallycards the same way human UX findings do — prioritized, confidence-scored, and routed to a human for approval.

A Lumen scan checks whether your website is structured in a way that AI systems can correctly parse, cite, and reason about. This includes: presence of an llms.txt file at your domain root, schema.org structured data markup, OpenGraph tag completeness, machine-readable pricing content, robots.txt directives for AI crawlers, and whether key page content is accessible without JavaScript rendering. These signals determine whether your site appears correctly when an AI assistant researches your product category on behalf of a buyer. PlayHero° monitors these signals on the same cadence as human UX signals — so regressions are caught before they affect your AI search visibility.

llms.txt is a plain-text file placed at the root of your domain (e.g. yourdomain.com/llms.txt) that tells AI systems what your product does, how to cite it, and where to find structured information about your pricing and features. It is to AI crawlers what robots.txt is to search engines. When a buyer's AI assistant researches your category, sites with an llms.txt file are more likely to be correctly identified, cited, and recommended. PlayHero°'s Lumen agent checks for llms.txt presence and quality on every scan. When llms.txt is missing, a Generate button appears in the scan results — one credit synthesizes a ready-to-deploy file from your scan data.

Yes. PlayHero° is accessible to AI agents via email at agent@playhero.ai. Send a URL in the subject line or body and the system will run a scan and reply with the WebUX Score, top Rallycards, and a link to the full results. A programmatic API and MCP server for direct agent-to-agent integration are on the roadmap. If you are building an agentic workflow and want early access to the API, contact agent@playhero.ai.

Yes, and this is the exact profile we built for. Teams using Clay, HubSpot AI, Gong, or agentic outbound tools are typically the ones who notice first that their pipeline attribution data doesn't match their site conversion data. PlayHero° monitors the conversion layer that all of those tools depend on — the pages your buyers land on, your pricing page, your demo request flow. If those pages degrade after a deploy, an update, or a content change, PlayHero° surfaces it before it becomes a quarter-end number conversation.

Three things have the highest impact: (1) Add an llms.txt file to your domain root — PlayHero° can generate one from your scan results. (2) Ensure your pricing page has a machine-readable version — a plain markdown file at /pricing.md that AI agents can parse without rendering JavaScript. (3) Add schema.org structured data markup to your key pages. PlayHero° checks for all three as part of Lumen scanning and surfaces missing or incorrect signals as Rallycards with specific remediation steps.

This is exactly the shift PlayHero° was built for. The buyer journey now has two phases: an AI research phase (where agents parse your site, compare pricing, and shortlist vendors) and a human decision phase (where the actual purchase is made). PlayHero° monitors both surfaces simultaneously — scanning for human UX signals that affect conversion and for agent-readiness signals that affect whether you appear in the AI research phase at all. No other monitoring platform watches both layers continuously.

A Rallycard is a structured decision card generated when a PlayHero agent detects a conversion-impacting issue with sufficient confidence to surface it. Each card contains the detecting agent, severity level, a plain-language finding, estimated pipeline impact, the detection method used, a finding confidence percentage, and a recommended action. Rallycards require an explicit human decision — approve, dismiss, or defer — before anything happens.

The Heroboard is the permanent, searchable record of every Rallycard and every team decision made in response to it. It is a governance layer, not a dashboard or task manager. Every card that passes through the Heroboard — approved, dismissed, or deferred — creates a permanent log entry with the actor's name and timestamp. The Heroboard is institutional memory: a complete, auditable history of every conversion decision your team has made.

Approving a Rallycard moves it to 'In Progress' and creates a permanent audit log entry with your name and timestamp. It is a coordination signal for your team — it does not automatically execute any change on your website. Your team executes the fix. Agents continue monitoring and update the card status when the next scan detects the issue is resolved. Nothing executes without your approval. That is not a limitation — it is the product.

Yes. Dismissing a card archives it permanently with a required reason selection — the reason is logged and searchable. Deferring a card snoozes it for a duration you specify; it returns to the pending queue automatically when the snooze expires. Both dismissed and deferred cards remain in the Heroboard audit trail. No card is ever deleted — the permanent record is a feature, not a limitation.

Finding Confidence is the percentage likelihood that the detected issue is real — it is not a measure of how certain the revenue estimate is. A card with 92% confidence means the underlying UX issue is very likely real. Confidence is derived from agreement between detection methods, consistency of signals across multiple checks, and the strength of the underlying evidence. Pipeline impact is always a separate benchmark-based estimate, always labeled as such, and never conflated with Finding Confidence.

Pipeline impact is a benchmark-based estimate modeled from your WebUX pillar scores mapped to B2B SaaS conversion sensitivity research. It is never sourced from your CRM, your actual traffic data, or your real revenue numbers at the anonymous scan tier. The estimation methodology is disclosed on every Rallycard — not in a footnote, inline on the card. After signup, you can edit the underlying assumptions (traffic volume, average deal value, CVR baseline) to calibrate estimates to your actual numbers.

No. Once a Rallycard is approved, the original finding is locked and cannot be edited or deleted. Status changes (approve, dismiss, defer, resolve) are logged with actor and timestamp, but the underlying finding data is immutable. This is a deliberate trust architecture decision — the audit trail requires immutability to be trustworthy as institutional memory.

PlayHero launches with four specialist agents: UX Sentinel (conversion friction and technical UX signals), Drift Detector (metric drift and CTR anomalies), Page Vitals Enforcer (Core Web Vitals and performance thresholds), and Lumen (agent visibility and AI buyer discoverability). Each agent has a defined domain, a specific detection methodology, and a minimum confidence threshold that must be met before a Rallycard is surfaced. No two agents overlap in mandate.

UX Sentinel monitors conversion friction and technical UX signals. It watches CTA visibility across mobile and desktop viewport sizes, readability thresholds (line-height, font-size, color contrast ratios), heading hierarchy, conversion friction (motion-aware primary-form field thresholds and conversational-interface detection), and visual scannability. It surfaces a Rallycard when finding confidence reaches 70% or above. UX Sentinel never executes changes, never surfaces findings below 65% confidence, and never conflates finding validity with revenue certainty.

Drift Detector monitors for conversion rate drift and CTR anomalies — catching declining trends before they become missed quarters. It requires a 7-day observation window to establish a per-URL baseline before surfacing cards, which means it will not alert on single-day anomalies. It watches CTR deltas week-over-week against a rolling 30-day baseline, MQL velocity, demo request form completion rates, and pricing page engagement depth.

Page Vitals Enforcer monitors Load Intelligence signals (LCP, FCP, CLS, TBT) against Google's conversion thresholds — aligned with Core Web Vitals methodology where applicable: LCP ≤2.5s, CLS ≤0.1, TBT ≤200ms. It fires a Rallycard automatically when a threshold is breached. It also monitors for deploy regressions by detecting performance changes after new site deployments. Page Vitals findings are objective measurements, not probabilistic assessments — an LCP of 3.4s is a fact, not an interpretation.

Monitoring requires Growth or above. On Growth, up to five URLs run in continuous monitoring with all four launch agents (daily cadence). On Scale, up to twenty URLs with configurable cadence. Free includes on-demand scans, Compare, and Heroboard — not continuous monitoring.

No. PlayHero is read-only on your site: agents detect and surface; they never deploy or edit your pages. Approving a Rallycard is a team coordination signal — your stack, your change. Any future automation will still require explicit human approval.

Yes. PlayHero supports competitor URL scanning in observation mode. When you scan a URL you do not own, the full seven-pillar analysis runs but pipeline dollar estimates are removed — revenue impact requires your actual traffic data to be credible. You receive relative UX scores, qualitative findings, and competitive positioning without speculative revenue projections.

The observation queue holds signals that agents have detected but that have not yet met the confidence threshold to surface as a Rallycard. Low-confidence signals are held — not discarded — and re-evaluated on each monitoring run. If a signal strengthens across multiple checks, it is promoted to a Rallycard automatically. If it weakens or disappears, it is dismissed silently. You never see a low-confidence card because the queue filters it before it reaches you.

Yes. PlayHero's agents evaluate your pages against the signals AI systems use to assess and recommend sites — structural clarity, conversion path legibility, Core Web Vitals, and messaging consistency. A page that converts human visitors but confuses agent evaluators is still a pipeline risk. PlayHero surfaces both.

Rallycards are triggered by what PlayHero's agents detect during scans — not by session type. If an issue affects the pages an AI agent would evaluate on behalf of a buyer (pricing, demo request, signup), it will surface as a Rallycard with severity and pipeline impact context.

Three public tiers: Free ($0) — unlimited scans, Compare, three Rallycards per scan, basic Heroboard. Growth — $119/mo billed annually or $149/mo monthly: five URLs monitored, all four launch agents, real-time Rallycard alerts (email + Slack), team handoffs, Heroboard history; credits via welcome grant + purchased packs. Scale — $223/mo annual or $279/mo monthly: twenty URLs, API access, white-label exports, portfolio dashboard, priority routing, custom terms for 50+ URLs.

Credits pay for on-demand agent outputs — not scans, not Compare, and not simply surfacing Rallycards from monitoring. Typical credit actions: CRO Experiment Brief (five ICE-scored ideas), A/B Test Hypothesis with success metrics, SuperScan° (multi-URL journeys). Script analysis on a scan is included. New accounts get 2 welcome credits; add more with packs ($12 per credit or $89 for ten). There are no monthly plan credit grants in v1.

No. Resolution Briefs are included at no additional credit cost on paid plans. A Resolution Brief is the full implementation specification generated after a Rallycard is approved — it includes a technical implementation spec, verification criteria that the next scan will check automatically, an effort estimate, and export-ready format for Jira, Linear, and GitHub Issues. The fix is part of the signal. You already paid for the detection; the brief is included.

No. Unused credits never expire. There is no month-end expiration and no use-it-or-lose-it pressure. Welcome credits and purchased packs carry forward until you use them.

Monitoring, scanning, Compare, and Rallycard surfacing continue without interruption when credits reach zero. Only on-demand agent work outputs — like CRO Experiment Briefs and SuperScan° — pause until you buy a pack. Your core monitoring never stops regardless of credit balance.

Annual billing is roughly a fifth lower than month-to-month on published tiers: Growth is $119/mo when paid annually vs $149/mo monthly; Scale is $223/mo annual vs $279/mo monthly. You can choose either path at checkout and change on renewal where your plan allows.

Growth includes a 14-day trial with no credit card required; if you do not subscribe, you return to Free with no charge. Scale is usually sold with sales-assisted onboarding — ask hello@playhero.ai for trial options that match your URL count and integrations.

No. PlayHero does not require access to your CRM, analytics platform, or internal revenue data to scan your website or surface Rallycards. Scans run against the publicly accessible DOM of your website. Pipeline impact estimates use benchmark data from B2B SaaS conversion research — not your actual traffic, leads, or revenue numbers. After signup, you can optionally input your own traffic and deal value assumptions to calibrate estimates to your real numbers.

PlayHero uses four detection methods across its agents: DOM structure analysis (objective measurement of page elements — a CTA below the fold is a measurable fact), LLM messaging interpretation (probabilistic AI assessment of copy quality and ICP alignment), Lighthouse integration (Google's open-source Core Web Vitals measurement tool), and viewport simulation (testing CTA and layout visibility across common device screen sizes). Every Rallycard discloses which detection method produced the finding.

No. PlayHero never writes to your site or your repo. It is read-only monitoring and analysis. Human approval records intent on the Heroboard; your team ships the fix.

Yes. Approved, dismissed, and deferred Rallycard decisions are permanently logged with the actor's name and timestamp. Deletion of decisions is not permitted — this is a deliberate architectural choice. The Heroboard functions as institutional memory, and institutional memory requires permanence to be trustworthy. Full decision history is exportable as CSV on Growth and Scale plans.

Pipeline impact ranges are benchmark-based estimates, not guarantees. They are modeled from B2B SaaS conversion sensitivity research and are disclosed as estimates on every Rallycard — inline on the card, not in a footnote. Finding Confidence (the likelihood the issue is real) and pipeline impact are always stated separately and never conflated. PlayHero will never present a revenue estimate as a revenue guarantee.

Free accounts do not include continuous monitoring. Growth monitors up to five URLs with daily scans. Scale monitors up to 20 URLs with configurable cadence. Custom pricing is available for portfolios requiring 50 or more URLs — contact the team via the Scale plan.

Free includes unlimited scans (with Rallycards per scan), Compare, and a basic Heroboard. Continuous monitoring — UX Sentinel, Drift Detector, Page Vitals Enforcer, and Lumen on a scheduled cadence — requires Growth or Scale.

Yes. Slack alert integration is included on Growth and Scale plans. When an agent surfaces a new Rallycard that meets the confidence threshold, an alert is sent to your configured Slack channel containing the finding title, confidence score, estimated pipeline impact range, and a direct link to approve, dismiss, or defer the card from the Heroboard.

Yes. Growth and Scale plan accounts can export their full Heroboard decision history as a CSV file. The export includes every card, every decision, the actor, the timestamp, the agent, the finding, and the outcome. Free plan accounts can view their history inside PlayHero but cannot export it.

Yes. Scan results and Resolution Briefs are shareable via a read-only link. The recipient does not need a PlayHero account to view the scan result or the brief content. Export buttons (Jira, Linear, GitHub Issues) are visible to link recipients but require the account holder to execute the export.

API access is included on the Scale plan — programmatic scan triggers, Rallycard and Heroboard retrieval, and integration with your existing tooling. It is not available on Free or Growth. A public REST API and Model Context Protocol (MCP) server are also in development; the MCP server will let AI coding tools like Claude Code and Cursor call PlayHero° as a tool from an agentic workflow. Until those surfaces are live, agent@playhero.ai accepts scan requests via email and returns structured results. Early access inquiries: agent@playhero.ai.

A Resolution Brief is a full implementation specification generated by the detecting agent after a Rallycard is approved. It includes a technical implementation spec for the fix, structured verification criteria that the next automated scan will check to confirm resolution, an effort estimate, and one-click export to Jira, Linear, or GitHub Issues. The brief is shareable via a read-only link — no account required for the developer or recipient who receives it.