A map of the category, a stack that is actually implementable, what is publicly known about how large tech companies work, and a benchmark by company size. Followed by the part that matters most: what AI does not take off the PM's plate.
Two caveats before reading. First, this category moves fast — tool capabilities and pricing change quarterly, so treat every product name as a starting point for your own evaluation, not a recommendation. Second, section 03 describes tooling at Airbnb, Stripe and Meta: these companies build heavily on internal tools that are not publicly documented. What follows is the publicly reported pattern and the product culture it reflects — read it as an illustration of three approaches, not as a verified inventory.
— six families of tools, by the job they do
— six layers, one tool each, no overlap
| Layer | Tool | Role |
|---|---|---|
| Brain | Claude / ChatGPT | Drafting, structuring, thinking through problems |
| Knowledge | Notion AI | PRDs, specs, the team knowledge base |
| Discovery | Dovetail | Interviews, user insights, synthesis |
| Feedback | Productboard | Centralisation and prioritisation |
| Analytics | Amplitude | Usage, funnels, retention |
| Delivery | Linear | Tickets, backlog, execution |
On the time savings
Reported gains cluster around 40–60% less time spent on drafting, synthesis and documentation. Treat that as directional: it comes from vendor and practitioner reports rather than controlled study, and it measures the artefact-production part of the job — which was never the part that determined whether the product succeeded.
— Airbnb, Stripe, Meta: what the tooling says about the product culture
The transferable lesson
None of these stacks is copyable — they rest on internal platforms built over a decade. What is transferable is the alignment: each company's tooling matches how it actually decides. Airbnb invests in research because it decides on judgement; Meta invests in experimentation because it decides on data. Pick tools that match your decision-making culture, not the culture of a company you admire.
— the constraint changes, so the stack changes
— the strategic reading
Three trends are visible across the whole category:
No tool currently replaces three things, and they are the three that determine whether a product succeeds:
Where the bottleneck moved
The PM becomes less of a writer and more of a decider. The constraint used to be producing the artefacts — specs, decks, summaries. Now that those are cheap, the constraint is choosing the right problems. A tool that helps you produce twice as many specs for the wrong roadmap has made things worse, not better.
The practical distinction worth holding onto: the best PMs orchestrate AI tools rather than simply using them. Using a tool means faster artefacts. Orchestrating means designing the chain — where insight enters, where it is challenged, where a human decides — so the speed compounds into better decisions instead of just more output.
← Back to the Playbook