Hi HN, I'm building PRDFlow because I lived this problem as an engineer and a team lead.
Every week I'd get asked "what did engineering ship?" and I'd spend 45 minutes scrolling Slack and GitHub to piece together an answer.
My engineers hated writing status updates. My PM was always behind on the roadmap. Sales kept promising features that were cut weeks ago.
PRDFlow connects to your GitHub repo and watches every merge. It reads the code changes and auto-generates updates in plain English, tailored by role; founders see business impact, PMs see acceptance criteria, sales sees what's demo-ready.
We're in pre-launch (waitlist) right now and looking for early feedback from technical founders, PMs, Sales, and engineering leaders.
Would love to hear: how does your team currently handle the gap between what engineering ships and what the rest of the company knows?
Remember to post again once it's launched. Waiting list never get traction here.
The Business <---> Engineering translation layer is an important role, if you convince everyone you are good at it and get a nice salary. It also adds some opportunities to discuss the trade off and add your own opinion.
Hi HN, I'm building PRDFlow because I lived this problem as an engineer and a team lead.
Every week I'd get asked "what did engineering ship?" and I'd spend 45 minutes scrolling Slack and GitHub to piece together an answer.
My engineers hated writing status updates. My PM was always behind on the roadmap. Sales kept promising features that were cut weeks ago.
PRDFlow connects to your GitHub repo and watches every merge. It reads the code changes and auto-generates updates in plain English, tailored by role; founders see business impact, PMs see acceptance criteria, sales sees what's demo-ready.
We're in pre-launch (waitlist) right now and looking for early feedback from technical founders, PMs, Sales, and engineering leaders.
Would love to hear: how does your team currently handle the gap between what engineering ships and what the rest of the company knows?
Remember to post again once it's launched. Waiting list never get traction here.
The Business <---> Engineering translation layer is an important role, if you convince everyone you are good at it and get a nice salary. It also adds some opportunities to discuss the trade off and add your own opinion.
[dead]