HOW IT WORKS 4 agents activev1.0

The mechanics behind
every Rallycard.

This is the page for the skeptical buyer. Every detection method is disclosed. Every confidence score is explained. Every design decision has a reason. Here's exactly how PlayHero works.

THE SYSTEM

From free scan to always-on monitoring.

SCAN

Score any site in minutes.

Point PlayHero at any URL. Seven pillars scored in parallel — no account, no snippet, results before you've signed up.

playhero.ai/scan
74WEBUX SCORE
Load Intelligence
78
Signal Hierarchy
84
Messaging Clarity
71
Content Clarity
88
CTA Clarity
62
Conversion Friction
74
Agent Visibility
69
RALLYCARD

Findings priced, not just flagged.

Each finding ships as a governed decision artifact: verb-first title, disclosed method, and a benchmark-based pipeline figure.

Rallycard · UX Sentinel
Restore CTA contrast on /pricing
contrast 2.8:1 · WCAG AA 4.5:1 · mobile + desktop
High
$41,200 est. pipeline at risk
Benchmark estimate. Methodology disclosed on every card.
HEROBOARD

One board. Every approved fix.

Approved Rallycards land on a single prioritized board — institutional memory for every UX decision your team makes.

Heroboard
CTARestore CTA contrast on /pricing$41,200Approved
LoadDefer third-party scripts above fold$28,400In review
ContentClarify ICP in hero subhead$19,800Approved
FrictionCut demo form from 9 fields to 4$33,100Deferred
MONITORING

Always on. Never autonomous.

Specialist agents watch every monitored page. Detection is continuous. Execution always waits for a human.

Agents
UX SentinelWatching
Drift DetectorWatching
Page Vitals EnforcerWatching
LumenWatching
0 auto-executions · every action human-approved
01
Scan Pipeline

Four detection layers. One URL. 60 seconds.

Every scan runs four passes in parallel: structured DOM analysis, rule-based threshold checking, Lighthouse performance measurement, and LLM qualitative interpretation. Click each stage to see exactly what it detects and how it contributes to finding confidence.

Total scan time≤ 60s
Stage 01 / 4

DOM Fetch

Structured / Deterministic

PlayHero fetches the full rendered DOM of the target URL across three viewport widths: 375px (mobile), 768px (tablet), 1440px (desktop). This is not an HTTP request — we render the page in a headless browser to capture the post-JavaScript DOM, exactly as a visitor would see it.

Signals detected
DOM tree structure
CTA position in viewport
Heading tag sequence (H1→H3)
Form field inventory
Link dead zones
Confidence basis
Objective. DOM position is a fact. CTA above-fold at 375px is measurable.
02
Rallycard Anatomy

Every field exists for a reason.

A Rallycard is a governed decision artifact — not a notification. Every field is designed to give the human reviewer exactly what they need to make a confident decision. Hover each field to see why it's there.

Live Rallycard anatomy — hover any field
UX Sentinel
● Critical
Hero CTA invisible on mobile viewports
Your primary CTA ('Start Free Trial') is positioned below the fold on 74% of mobile screen sizes tested. Visitors who never see the CTA cannot convert — the issue is structural, not stylistic.
Decision Impact (est.)
−$22k–$48k / quarter
Benchmark estimate — B2B SaaS mobile CVR sensitivity bands. Not your CRM data.
Detection:DOM structureViewport simulation
Recommended Action
Move CTA above fold or implement sticky mobile CTA bar. Hero height can be reduced by 20% with minimal brand impact.
Hover any field on the Rallycard to see why it exists and what it means.
Card immutability

Once a card is approved, the original finding is locked. Status changes (In Progress, Resolved) are appended as a log — the original card is never overwritten. This is how the Heroboard becomes institutional memory, not just a task list.

03
6 Pillars

Six scored dimensions. Specific thresholds. No guesswork.

The WebUX Score is not a proprietary black-box metric. It is the weighted composite of seven pillar scores, each measured against published or well-established thresholds. Click any pillar to see the exact thresholds used and why they were chosen.

04
Four Agents

Four specialists. Defined domains. No overlap.

Each agent has a stable identity, a specific detection domain, and a confidence methodology suited to its signal type. Domain isolation is deliberate — a UX finding from UX Sentinel and a CWV finding from Page Vitals Enforcer are detected by fundamentally different methods, and conflating them would lower the credibility of both.

UX Sentinel
Drift Detector
Page Vitals Enforcer
Lumen
DomainConversion friction & technical UXWebUX signal drift & page anomaliesCore Web Vitals & performanceAI discoverability & agent readiness
Detection methodDOM analysis + LLM + rule-basedPage signal monitoring + trend analysisLighthouse + script enumerationStructured data + llms.txt + content extraction
Confidence thresholdDOM evidence + LLM agreementStatistical significance vs. 30-day baselineObjective threshold breachDeterministic signal presence
All four agents run in parallel on every monitoring cycle. A single URL check produces outputs from all active agents simultaneously — findings are not sequential.
Full agent specifications →
05
Heroboard

Governance layer. Institutional memory.

The Heroboard is not a task manager. It is the permanent, searchable record of every UX decision your team has made against your monitored pages. Every card that passes through it — approved, dismissed, or deferred — creates a log entry that cannot be deleted.

Agent detects signal
Severity rated by the detecting agent
Card held or surfaced
High / critical → Rallycard. Below that stays with the agent
Alert sent
Email or Slack with direct approve link
Human decision
Approve / Dismiss / Defer — required
Action executed
Team executes fix. Agents track progress
Result logged
Next scan delta linked to card. Permanent record
Card lifecycle states

Card has been surfaced by an agent and is waiting for a human decision. The agent continues monitoring while the card waits — additional evidence may update the finding.

Permanent record

Every decision — approve, dismiss, defer — is logged with actor identity and timestamp. Deletions are not permitted. Over time, the Heroboard becomes the only complete history of every UX decision that touched your pipeline.

06
Script Audit + Competitor Mode

Script audit and competitor mode. Both free. No account.

Script audit runs on every scan automatically — no configuration needed. Competitor observation mode activates automatically when you scan a URL you don't own, suppressing pipeline estimates that would be speculative.

Script Audit

Every third-party script, sized and risk-rated.

Included free on every scan. PlayHero enumerates all third-party scripts loaded on the page, identifies them by origin, sizes them by transfer weight, and risk-rates them based on their contribution to LCP and Total Blocking Time.

Analytics scripts
GTM, GA4, Segment, Heap — load weight + LCP contribution
Support widgets
Intercom, Drift, Zendesk — often the largest TBT contributors
Unknown origins
Scripts with no identifiable owner flagged as high risk
Optimization suggestions
Linked to Page Vitals Enforcer findings where relevant
Script audit is included with every free scan. No account required.
Competitor Observation Mode

Scan any URL. Pipeline estimates removed automatically.

When you scan a URL you don't own, PlayHero automatically enters observation mode. The full 7-pillar analysis runs, but pipeline dollar estimates are suppressed — you can't model conversion impact for a site you don't have traffic data for, and fabricating those numbers would undermine the credibility of the findings.

What you get in observation mode
Full 7-pillar score comparison
Relative UX positioning vs. your own score
Qualitative findings (no pipeline $ estimates)
Script audit and CWV measurements
Legal clarity: Observation mode removes all revenue projections from competitor scans. UX quality is observable. Revenue impact from someone else's site is not.
07
Trust Contract

Five things that are non-negotiable.

Every feature we ship is evaluated against these five commitments. They are not marketing copy — they are constraints that have shaped product decisions from day one. The ones that slow us down are the ones that matter most.

01Detection method always disclosed

Every Rallycard shows which technical method detected the finding. DOM structure analysis is objective — a CTA below fold is measurable. LLM interpretation is probabilistic — a value proposition missing ICP clarity is an assessment. Users see the difference on every card.

02Severity is not revenue certainty

Severity is the detecting agent's rating of the issue. It is never shown as a measure of revenue impact certainty. The pipeline impact range is always a benchmark-based estimate, always labeled as such, with methodology disclosed inline — not in a footnote.

03Nothing executes without your approval

No agent moves a card to execution. No change is made to your site. No action is taken on your behalf. Approval is a governance signal — it moves the card to In Progress and notifies your team. Your team executes. Agents track what's running.

04Assumptions are editable after signup

The traffic volume, average deal value, and CVR baseline underlying every pipeline impact estimate are editable post-signup. The default assumptions are disclosed on every card. You can calibrate them to your actual site data, making every subsequent impact estimate more accurate.

05The audit trail is permanent

Every decision — approve, dismiss, defer — is logged with actor identity and timestamp. This record cannot be deleted. Over time, the Heroboard becomes institutional memory: the only complete history of what was found, who decided what, and what changed afterward.

Free. No account required.

See the system work on your site.

One URL. 60 seconds. Your first Rallycard before you've created an account.

No credit cardNo accountNo auto-executionsResults in 60 seconds
How PlayHero Works — WebUX Monitoring | PlayHero