BugReplay

One-click screen/action recorder that captures and replays bug reproductions for engineers in support and QA workflows. · B2B QA Workflow

STOP · SKIP

5.0 ShipScore / 10

Time-leverage decent; entry near zero — free incumbents and stalled clones dominate.

Condition: Only reconsider if you own a wedge incumbents can't copy: e.g. deterministic replay-to-Playwright test generation with verified pilot contracts from 3 paying QA teams before writing code.

Part I — The Verdict what the instruments read

01 — The ShipScore breakdown

Control

Entry barriers

Need

Time-freedom

Scale

What the five commandments measure

C — Control	Do you own the customer, or does a gatekeeper (an app store, an algorithm, one platform) stand between you and revenue? High = you hold the keys.
E — Entry	How hard is this to copy? High barriers protect you once in — but a well-loved incumbent means breaking in is expensive, and scores this low.
N — Need	Is demand proven with money, not vibes — verified rival revenue, funding, exit multiples, complaint volume? No market evidence caps this at 5.
T — Time	Can income detach from your hours? High = earns while you sleep; low = you bought yourself a job.
S — Scale	How far does it reach without linear cost? High = software margins to thousands of customers; low = growth means headcount.

ShipScore = the mean of the five, scored by Opus 5 on the evidence below — the same rubric for every idea, including the ones we generate ourselves. Inspired by MJ DeMarco's CENTS framework. Full rubric →

02 — The pace test — $1M/yr

At $29/mo (assumed category price), you need 2,874 subscribers for a $1M/yr pace.

Nearest tracked rivals on that curve:

Walkthrough - Screen Recording & Sharing

$0k 0%

Lorari

$1k 1%

Part II — The Evidence the receipts, good and bad

03 — Rival scan — corpus tracks 5 similar, 2 stalled under $2k MRR

Walkthrough - Screen Recording & Sharing	verified MRR $0k (trustmrr)
Clipy - Loom alternative for screen recording/sharing	10 upvotes (reddit)
Lorari	verified MRR $1k · CENTS 6.2 (x)
Glideo	69 upvotes (producthunt)
Retrace	88 upvotes (producthunt)

Replay.io — Time-travel debugging with real runtime state — far deeper than screen capture, steady community mentions.
PostHog session replay (plus Lucent AI layer) — Session replay bundled free/cheap inside a product-analytics suite teams already pay for.
Bug0 Studio — Screen record → AI-generated Playwright tests; converts the recording into actual regression value.

04 — Demand evidence

Evidence is thin: 5 tracked similar products, 2 with verified revenue both stalled under $2k MRR (Walkthrough $0k, Lorari $1k).
Zero Reddit demand signals for these keywords — no organic complaint volume to ride.
X chatter is 'some', mostly founder/promotional launches (VeriWasp, Crosscheck, Reproclaim) with hundreds of likes — sentiment, not spend.
Complaints are generic 'can't reproduce' pain, plus explicit notes that replay alone doesn't fix QA bottlenecks.

05 — Risks

Feature, not product: session replay is being absorbed into analytics, observability and bug-tracker suites.
At least eight named entrants in one recent window — commoditised, price-to-zero dynamics.
Buyer confusion: support, QA and eng each own part of the workflow, so no clear budget holder.
Cloneable in weeks; browser-capture APIs and open-source rrweb remove all technical moat.

06 — Kill switches — what kills this with one decision

Chrome Web Store / extension policy — Tighter tab-capture or permission rules delist or cripple the one-click recorder overnight.
Jira/Linear/GitHub integration APIs — Losing or paying for issue-tracker attachment breaks the handoff that makes the tool useful.
Incumbent bundling (PostHog, Sentry, bug trackers) — One 'replay included' release on an existing plan removes the reason to buy separately.

Divergence available · Seeing the cracks? Spin the model — variations of this idea engineered to beat 5.0.

Part III — The Plan if you insist on proceeding

07 — What this scan can't tell you

Cannot see BugReplay's actual current revenue, churn or enterprise logos — only proxies from small clones.
No data on whether QA teams pay per-seat or via existing observability budgets in real deals.
Can't judge whether AI test-generation entrants convert trials to paid or just farm launch attention.

Scores judge the market and business model — not your ability to execute. Verified MRR = independently tracked revenue; reviews/upvotes = platform-reported. Judged 2026-08-05.

08 — The wedge & the next step

Skip the generic recorder; sell the deterministic repro bundle — video plus console, network, device state — that auto-writes a failing Playwright test into the team's tracker, priced per engineering team not per seat.

Cheapest next step: DM 10 QA leads on X/LinkedIn asking what they currently pay for repro capture and what tool the bug lands in; if fewer than 3 name a paid line item, drop it.

Not quite it? Spin the model

Business-model variations of this idea, engineered to beat 5.0 — different vertical, audience, model, or wedge. Same harsh scale.

Monitor this idea

Weekly re-scan against the live corpus. If the market moves this ShipScore by a point, or flips the verdict, you hear about it. Free while we're small.

One inspection a day, by email

App Radar scans TrustMRR, Product Hunt, AppSumo, the App Store, Reddit and X daily — momentum, beatable apps, funding heat.