Every brief here started as somebody complaining in public. Shipbrief keeps the quotes, counts how often the complaint comes back, and writes up what you would actually have to build.
17 briefs published, each one linked back to the posts it came from.
2 briefs
Mixpanel's pricing is 'the most obscure pricing model of any SAAS i've ever tried to integrate with' (jordo, HN). Multiple founders explicitly said 'I wish Mixpanel wasn't this expensive for a few 1000 users' (nojvek). Mixpanel + Amplitude both bill on MTU/events in ways that punish growth before revenue. PostHog exists but is Kubernetes-heavy if self-hosted and not cheap if hosted.
u/TadpoleRemarkable828 (r/SaaS, 2 upvotes / 5 comments): 'I spent 2 weeks manually scraping Reddit, Twitter, and HN for posts with phrases like I wish there was..., I would pay for..., so frustrated that... Found some legit problems with real engagement. But the process was brutal — took hours.' u/HopefulBread5119 hit 771 upvotes doing this manually for 6 months and processing 9,363 posts. Multiple builders in this corpus (p_G_034, p_G_038, p_G_068, p_G_076) are independently building toy versions of exactly this product.
A scraper reads public posts on X, Reddit and Hacker News every day — the ones where somebody is describing a problem rather than launching something.
Claude pulls the specific complaint out of each post. The same complaint, from different people in different places, collapses into one node in a graph that keeps growing.
Once a cluster has enough corroboration it becomes a brief: the problem, who has it, who already tried to solve it, and what you would have to build. Nothing is published off a single post.