Know what users report about your product in public.
Each week: the problems users describe on each release and environment, the workarounds other users said worked, and whether reports fell after your last fix. Every factual sentence links to the public post it rests on.
Book a 30-minute walkthroughSee a sample report
For software teams, including vendors that sell to government, and agency program offices. For consumer brands and home builders: in development.
Early access. Reading public sources runs today. Classification, extraction, merging, scoring, report writing and the verifier are built and in testing. Alerts and ticket sync are built and being prepared for production, and the dashboard is in development. Early-access customers will receive reports, evidence files and readouts by email.
What you get
Users describe problems in public in detail: exact error messages, versions, configurations and the steps that triggered them. That signal is spread across forums, issue trackers and help centers, often repeated across many threads. Thread Witness gathers it into:
- A weekly report with the top issues and top feature requests, each with a unique reporter count, trend, severity and status. Every topic keeps the same ID from week to week, so the ID in your ticket matches the one in next quarter’s review.
- Deep dives per issue: symptoms, exact error strings, triggering conditions, an affected-environment matrix, a timeline annotated with your releases, and the workarounds users tried.
- Workaround counts: how many people said a step worked, how many said it did not, and what it costs to apply.
- Release correlation, and fix verification on Business and Enterprise plans: whether reports rose after a release, and whether they fell after a fix shipped.
- Evidence you can check: every factual sentence links to the public post it came from.
- In development: what users praise, grouped beside what they report; spike alerts to Slack, Microsoft Teams or email; and issues pushed to Jira, Linear or GitHub with the ID and evidence attached.
From the sample report
Illustrative sample. Fictional product, invented data.
| ID | Issue | Severity | Priority (0 to 100) | Reporters (week / 8 wk) | Trend |
|---|---|---|---|---|---|
| NWC-ISS-4H8T2C | Sign-in loop after SSO sign-in, rising after certificate rotation | S2 | 74 | 9 / 23 | ↑ Rising |
| Workaround | Label | Worked / partial / did not | Risk badges |
|---|---|---|---|
| Ask an organization admin to re-upload the identity-provider metadata | Confirmed (5) | 5 / 1 / 1 | Requires admin |
| Clear console session cookies and sign in again | Confirmed, temporary (3) | 3 / 5 / 1 | Time burden |
Labels such as Confirmed (5) count what users said about their own attempts. They are not our conclusions.
Coverage and verifier. 1,904 posts scanned, 187 unique reporters. 162 citations checked; every citation in the released report resolves. Before release: 5 claims removed, 3 rewritten, 1 downgraded.
How it works and how we source data
We read public sources through official APIs and feeds first, merge reports of the same problem into one topic, count unique reporters, and have an automated verifier check every citation, quote and number before a report is released. How it works
Public data only, no logins bypassed, review sites and retailer reviews excluded, Reddit read only under license, authors pseudonymized, quotes short and linked. Counts measure public discussion, not failure rates. How we source data · Corrections
Who it is for
Software vendors, including those that sell to government. Product, support-engineering and quality teams that want to know what users on each release and each government-cloud tier are hitting, which workarounds other admins said worked, and whether reports fell after the last fix. For federal teams
Agency program offices. Teams that run public-facing systems and want a cited view of where users say they get stuck, delivered by email with no login. For federal teams
Consumer brands and home builders. Warranty, quality and customer-care teams that want owner-reported failures, months in service and warranty stage, with hazard reports routed to human review. In development. For consumer brands and home builders
Start with a Community Issue Audit
A fixed-price, one-time review of one product: 90 days of public reports, a verified report with an evidence file, human review of any safety- or security-class topic, a 60-minute readout and written answers to three of your questions. $14,500.
We are scheduling the first early-access audits now. Write to reserve one. Typical delivery is 15 business days from kickoff, and the delivery date is confirmed in writing at kickoff. 100% of the audit fee is credited toward an annual Team or Business plan signed within 60 days of report delivery.
Book a 30-minute walkthrough
We show you the report format, then what we can see for your product. Tell us the product, the release or environment you care about, and your role.
Book a 30-minute walkthroughhello@threadwitness.com