The PM's shortlist
The AI tools that actually work for product managers.
Not another directory of 10,000 tools. A ruthlessly maintained shortlist, organized by the job you're trying to do — each with an honest verdict and a recipe to get value in 10 minutes.
- tools reviewed
- 45
- playbooks
- 9
- copy-paste prompts
- 22
- last verified
- Aug 2026
What's eating your week?
Playbooks: real PM struggles solved by a chain of tools — exact prompts, honest time math.
“Every AI session starts with the same 400 words about what your product is, who uses it, and what you already decided not to build — and the output is still generic.”
Build the context pack so you stop re-explaining your product every session
“Your roadmap gets re-litigated from scratch in every exec review.”
From a roadmap that gets re-litigated to a review that ends in a decision
“The weekly status deck eats three hours — and nobody reads slide 4.”
From a three-hour status deck to a one-page memo they actually read
“The data team's queue is two weeks deep — and your decision is today.”
From a two-week data queue to a same-day decision memo
Steal these prompts
Field-tested, copy-paste, guardrail built in. One tap and it's yours.
Ranked themes across multiple interviews, each backed by verbatim quotes with participant attribution — traceable synthesis, not a summary you can't trust.
Given/When/Then acceptance criteria for one user story — happy path, edge cases, and error states — plus an explicit list of what the model couldn't infer and needs you to decide.
A crisp decision memo from a pile of analysis — the question, what the data says, what it pointedly does NOT say, a recommendation with a confidence level, and the line that would change your mind.
A structured read of a competitor from their homepage and pricing page — claimed value, target, pricing model, and gaps — plus a clear-eyed where-we-win / where-we-lose, with every claim traced to the line it came from.
Run a pre-mortem before you ship
Any LLMThe eight most likely ways your launch fails, ranked, each paired with the earliest real signal you'd see it coming — so you can watch for it instead of writing the post-mortem later.
A ruthless critique of a finished PRD from two skeptical reviewers — the holes, bad assumptions, and single riskiest belief — before the people who'll actually build it find them for you.
Editor's picks
The one we'd reach for first in each job.
ChatGPT
The versatile everyday workhorse — drafting specs, quick analysis, and voice-driven interview note capture.
Gamma
Turning a paragraph or a doc into a structured deck in one pass
Granola
Great notes from calls you're actually on, with no bot in the room
Perplexity
Fast, cited competitive facts you can defend in a review
Julius AI
Chatting with a CSV or Excel export and getting charts + stats back, no formulas
Lovable
A non-technical PM turning an idea into a working, shareable app with real login and data
Productboard
Turning a firehose of customer feedback into a prioritized, stakeholder-ready roadmap
promptfoo
A PM who wants to turn 'the AI answer feels worse this week' into a number, without asking engineering for anything.
Pick your job to be done
Writing PRDs & specs
Turn a rough idea into a structured spec — fast.
User research & interview synthesis
Turn hours of interviews into themes you can act on.
Competitive & market analysis
Track rivals, size markets, build battlecards.
Roadmapping & prioritization
Turn inputs into a ranked, shareable plan
Data analysis & SQL for PMs
Answer data questions without booking an analyst.
Prototyping & mockups (AI app builders)
Idea to clickable prototype without engineering
Stakeholder comms & presentations
Turn a decision into a crisp deck, fast.
Meeting notes & async updates
Capture the call, ship the decisions.
Shipping AI features
Define "good" when the output is different every time.
The Cut · every Monday
Most of what's new is not worth your Monday. We test it and tell you.
Every week we sweep what shipped in AI for product work, kill most of it on the adoptability bar, and field-test what's left against a fixture with planted traps before writing a word. Three things follow from that, and they're the whole difference:
-
Receipts, not roundups
Nothing gets named unless we ran it that week. The model and date are on the page.
-
Failures published
When something hyped fails our traps, we say so — and which trap broke it.
-
Empty weeks stay empty
Nothing clears the bar? The issue says so in one paragraph. No padding, ever.
The Cut, in your inbox
One email a week: what cleared the bar, what failed our tests, what got retired — with receipts. Empty weeks stay empty.
One email a week, sent by a human who read it first. Unsubscribe in one click.