Problem & Market Need

• Reproducing customer-reported bugs is painful for support and QA teams; they constantly ask for screenshots, env. info and steps to reproduce.
• The HN thread (id=32937902, 116 comments) has multiple comments saying “I’d pay good money for this” and comparing it favourably against Loom & LogRocket.

Existing Solutions / Competitors

• Loom – general purpose async video, not DOM-selector aware, no automatic redaction or issue export. ARR > $100 M, shows willingness to pay for screen-based communication.
• Screenjar – very similar concept but only captures video + console, no DOM selector timeline. One-person indie project -> room for better product.
• Zipy.ai, Highlight.io, LogRocket, FullStory – session-replay APM tools; heavy SDK install, pricey ($1k+ /mo) and aimed at developers rather than support reps requesting one-off captures.
• BugHerd, Usersnap, Marker.io – “visual bug reporting” widgets (screenshots + annotations), but not full video + system info.

Presence of these paid tools validates that companies spend money to shorten bug-reproduction time.

Demand Signals in Communities

• HN post: >100 up-votes, 100+ comments.
• Reddit r/...