Where these 14 reports land
Build it2
Scope it8
Keep it4
Category report
User Research
14 products ranked by how much of their useful core an AI coding agent can reproduce: 2 strong builds, 8 scoped builds, and 4 weak replacements.
How the score breaks down here
- Interface
- 52
- Core workflow
- 50
- Data access
- 46
- Operations
- 39
- Trust & safety
- 47
49/100 average buildability
Why people keep paying here
- collaboration10 of 14 reports
Permissions, presence, and shared workflows are difficult to simplify.
- execution polish7 of 14 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
- integrations6 of 14 reports
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The typical achievable core in this category: store interview notes, tag observations, and synthesize themes across sessions.
Build it
Nolt
The core loop is small enough for a capable coding agent to produce a useful local version. For Nolt, publish a feedback board with voting, comments, statuses, and a roadmap. The hard boundary is hosted simplicity, custom domains, integrations, and low maintenance, plus participant network, synthesis workflow, and collaboration.
Build it
Frill
The core loop is small enough for a capable coding agent to produce a useful local version. For Frill, publish feedback, roadmap, and announcements for one product. The hard boundary is hosted polish, custom domain, integrations, widgets, and simple pricing, plus participant network, synthesis workflow, and collaboration.
Scope it
WishKit
The data model here is four tables and a sort function: wishes, votes, comments, statuses. An agent can produce the whole web board plus a REST API in a focused implementation, and it will work fine for a side project. The part that is actually work is everything after that: a native in-app widget for each platform you ship on, anonymous device identity so the same user cannot vote fifty times, spam and profanity handling, and an endpoint that stays up for people who already installed your binary. Nothing there is hard, it is just a real backend you now own forever. Build it if you like owning it, pay if your roadmap board is not the thing you want to be on call for.
Scope it
Featurebase
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Featurebase, run a feedback portal, changelog, roadmap, and lightweight support widget. The hard boundary is integrated suite, ai, custom domains, sso, and hosted delivery, plus participant network, synthesis workflow, and collaboration.
Scope it
IdeaFast
The pipeline is honest work an agent can do: pull public Reddit JSON, prefilter complaint-shaped text, classify with an LLM, embed and cluster, rank by frequency times severity times recency. A contained gets you ranked pain themes with real permalinks for two or three subreddits you already know. What does not fall out of one session is everything after the demo: staying inside Reddit's rate limits at scale, picking which communities are worth scanning when you do not already know, deduping the same pain across runs so week two is not week one again, and keeping the LLM bill under the price of the subscription. Verdict is kinda, not yes, because the first run is easy and the tenth is where the product actually lives.
Scope it
Canny
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Canny, collect feature requests, merge duplicates, publish statuses, and maintain a roadmap. The hard boundary is customer identity, integrations, changelog, prioritization, and team workflow, plus participant network, synthesis workflow, and collaboration.
Scope it
Productlane
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Productlane, connect interview notes and support feedback to product issues and decisions. The hard boundary is linear integration, call workflows, customer portal, sync, and team collaboration, plus participant network, synthesis workflow, and collaboration.
Scope it
Savio
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Savio, centralize manually imported feedback, tag it, and connect it to feature decisions. The hard boundary is crm and support integrations, customer revenue context, workflow, and collaboration, plus participant network, synthesis workflow, and collaboration.
Scope it
Ideabrowser
Scraping Reddit/search trends and having an LLM draft a business-opportunity writeup per idea is a focused build. What's genuinely hard to replicate is the editorial curation, the accumulated database of 1,000+ pre-researched ideas, and the trend-signal pipeline built up over time. A DIY version can generate plausible-sounding ideas on demand but starts from zero data and zero curation.
Scope it
Aurelius
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Aurelius, organize interview notes, code excerpts, and synthesize themes into findings. The hard boundary is research-specific tagging, collaboration, reporting, and import workflows, plus participant network, synthesis workflow, and collaboration.
Keep it
Dovetail
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Dovetail, store research notes, tag evidence, and create themes without recreating Dovetail's enterprise repository. The hard boundary is media transcription, participant data, integrations, governance, and collaboration scale, plus participant network, synthesis workflow, and collaboration.
Keep it
Productboard
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Productboard, link manually imported feedback to features and a small roadmap. The hard boundary is customer-insight integrations, prioritization, roadmap governance, and organizational adoption, plus participant network, synthesis workflow, and collaboration.
Keep it
UserVoice
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For UserVoice, run a focused feedback portal and manual research repository. The hard boundary is enterprise customer identity, integrations, analytics, governance, and consulting, plus participant network, synthesis workflow, and collaboration.
Keep it
Maze
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Maze, run small unmoderated prototype tasks with consent and basic completion analytics. The hard boundary is participant panel, prototype integrations, testing infrastructure, analytics, and recruitment, plus participant network, synthesis workflow, and collaboration.