Why I'm Building a Product Thinking Tool

There's a version of product work that nobody talks about honestly. The one where a pivot gets decided on a Tuesday, someone needs a PRD by Thursday, and you're sitting there knowing that doing it properly takes hours you don't have.

I've been in that position more times than I can count across the startups I've worked at. Things move fast at early stage companies. New features get scoped over a Slack thread. A direction change gets agreed in a meeting and suddenly someone needs to translate that into something a designer and developer can actually work from. The pressure isn't coming from bad intentions, it's just the pace. But the result is often product documents that are rushed, missing the questions that would have saved everyone two weeks of rework.

Writing a thorough PRD takes time. Working through the problem statement properly, defining the right users, scoping what's in and what's out, thinking through edge cases, writing user stories with actual acceptance criteria. When you do it well it takes a few hours minimum, and that's when you already know what you're building.

Where generic AI falls short

When AI tools became genuinely useful I started using them to speed this up, like most people did. And they help to a point. You can ask for a PRD structure and get one back quickly. Paste in some notes and get a rough draft.

But the output tends to be generic in a way that's hard to articulate at first. It looks right, has the correct sections, and then you read it properly and realise it made assumptions that aren't true for your product, glossed over decisions you actually needed to make, and gave you something that feels complete without being useful. It generates text. It doesn't do product thinking.

That difference matters. Product thinking means knowing which questions to ask before you start writing. It means flagging what's missing, what's risky, what hasn't been decided yet. A generic AI tool doesn't do that because it responds to what you ask, not to what you haven't thought to ask yet.

What I kept seeing in coaching

This shows up differently depending on who you're talking to. Junior PMs often come with a rough idea and no real structure around it, not because they don't care but because nobody has shown them what good product thinking actually looks like in practice. They'll spend time with a generic AI tool, get something back that looks like a PRD, and not realise until much later that half the foundational decisions were never actually made.

It's not a capability problem. It's a scaffolding problem. They need something that meets them where they are, asks the right questions, and helps them think through the product rather than just producing a document that looks finished.

What I'm building

PRDstudio started as an answer to my own frustration. I wanted something that would handle the structural thinking and research while keeping me in the driving seat on the actual product decisions. Something that asked the right questions rather than making assumptions. Something that could look at what I'd written and tell me what was missing before it went anywhere near a developer.

The more I sat with it the more I realised that tool would be just as useful for a junior PM building their first product brief as it would be for a founder who needs to move fast but can't afford to get the foundations wrong. So that's what I'm building. An AI product thinking workspace that helps you get from rough idea to structured, build-ready document without the hours of staring at a blank page or the false confidence of a generic AI output that looks complete but isn't.

It's still in progress. But the problem has been sitting in front of me long enough that I stopped waiting for someone else to build it.