Counting method: by theme/feature. Each person or note is counted once per theme; counts are a judgement call where feedback overlapped. P0 do first · P1 soon · P2/P3 later bets.
Every theme raised about the product, with who raised it. Click any column header to sort; filter by category or search.
| Theme | Status | Mentions | Category | Priority | Raised by |
|---|
Adjacent problems and product bets surfaced in research calls. Same controls as the Cedarloop table.
| Theme | Mentions | Category | Priority | Raised by |
|---|
Senior-IC bias. Two of the strongest "who's working on what" signals came from senior ICs (Ada PM, Sanity design-systems lead). Allen's own note: senior ICs often have a bee in their bonnet that execs won't fund. Validate with executives (Sam Pillar / Forest at Jobber, Brett at Wealthsimple) before committing.
The durable-problem test. People increasingly vibe-code their own fix. A problem is only worth building if it can't be cheaply vibe-coded — needs to be hard to get right, or needs a central system an individual can't run.
Median vs frontier. Open strategic question: build for the median company (Jobber-style) that will pay to be levelled up, or the frontier team that mostly solves its own problems. Unresolved on purpose.
Generated from Allen's research channel posts and the standup transcripts provided. Counts reflect distinct people/notes per theme and are a judgement call where feedback overlapped.