Press Space to continue
Press Space to continue
The PRD stopped being the document everyone signs off on. Pavneet's reframe is the sharpest answer I have heard to a question every PM is quietly sitting on, which is what a requirements doc is even for once anyone can generate twenty pages in a minute. Historically it was a gate. All stakeholders align on it, then building starts. Together treats it as a trigger for ideation instead. One to two pages. The customer problem defined well enough that everyone shares an understanding of it. A few…
Aakash Gupta@aakashguptaSep 15
Together AI just raised $800M at an $8.3B valuation. I got their product team to open up the actual repo they run on: 0:00 - Slop is the new party foul 1:44 - Why individual output backfired 3:26 - Inside the shared product repo 8:57 - Who owns the context files 10:41 - Team skills vs personal skills 11:57 - Picking a harness and a model 15:17 - Feature research running live 16:57 - What stays human in the loop 19:56 - The PRD skill that interviews you 23:09 - Half a day of research in 5 min 24:25 - Their customer insights MCP 27:31 - What a good PRD looks like now 32:02 - Reading the finished PRD 35:07 - Every repo in one place 40:24 - Context is a hierarchy, not a pool 41:20 - Build your own orchestrator 44:19 - Agent evals on shipped features 49:41 - Design validated every few hours 52:26 - Where PM ends, engineer begins 55:10 - What it actually cost them
View