Productboard

The platform behind the platforms

Somewhere inside Microsoft, a product manager is dragging a feature card from "Now" to "Next." She is not using a spreadsheet. She is not using a Notion doc tied together with prayer and three Slack channels. She is using Productboard. And so, give or take a few thousand teams, are the product managers at Zoom, UiPath, 1-800-Contacts, Cartier and Avast.

This is the curious thing about Productboard. The company makes the software that makes the software you use. It sits one layer behind the apps on your phone, deciding which buttons get built and which ones quietly die in a backlog. Six thousand organizations now run their roadmaps through it. The company is worth $1.725 billion. And almost nobody outside of product management has heard of it - which is exactly how the people who use it would prefer to keep things.

A job without a tool

For most of the software era, the product manager was a strange professional creature. Part designer, part engineer, part therapist, part traffic cop. The job came with enormous responsibility - tell a company of hundreds what to build, and why - and almost no software designed for it. Engineers had Jira. Designers had Figma. Salespeople had Salesforce. Product managers had a folder of voice memos, an inbox of feature requests, and a deck they would rewrite at 11pm on a Sunday.

The result was predictable. Roadmaps were built on whoever shouted loudest in the last meeting. Customer feedback evaporated between the support team and the engineering team. Companies shipped features nobody asked for, then wondered why churn was rising. It was, to borrow a phrase, the only job in tech where you were judged on your decisions and given no tools to make them with.

A daydream at 36,000 feet

In June 2011, Hubert Palan was flying coach from Prague to New York. He was, at the time, the VP of Product at GoodData - a man who knew the problem intimately because he had lived inside it for years. Somewhere over the Atlantic, with several hours and nothing to do, he started sketching the tool he wished he had. By November 2013 he had quit his job. By 2014 he had a co-founder, the technical and unflappable Daniel Hejl, and a small office in Prague. By 2016 they had a product, a launch at TechCrunch Disrupt, and $1.7 million in seed funding.

The bet was deceptively simple - and the kind of bet that only looks obvious in hindsight. If product managers were the people responsible for deciding what gets built, then product managers should have software designed around that single decision. Not project tracking. Not engineering tickets. Decision-making. The feedback comes in from a hundred places. The themes get extracted. The features get scored. The roadmap writes itself, or at least stops being written at midnight on a Sunday.

What it actually does

The Productboard demo, if you have ever sat through one, is unusual in a category known for unusual demos. There is no animation. There are no fireworks. A salesperson loads a sample workspace and says, with the calm of someone who has said it ten thousand times, "this is where feedback comes in." And then they show you the kind of small, quiet miracle that product people get a little emotional about.

Feature requests from a Zendesk ticket, a Salesforce note, an Intercom chat, a Slack thread, and a Typeform survey arrive in one inbox. The system clusters them into themes. A scoring framework - reach, impact, confidence, effort - sorts them. The output is a roadmap you can actually defend to a skeptical CFO. Then Productboard syncs the result back to Jira so engineering can do its part. Plus a public customer portal where users can submit and upvote ideas, closing the loop the same way it started.

Numbers, and the people behind them

Numbers in private SaaS are slippery things, and Productboard is no exception. What is public is enough. The company has raised roughly $262 million across five rounds from Sequoia, Kleiner Perkins, Tiger Global, Dragoneer, Index Ventures, Bessemer and a handful of others - the kind of cap table that, by itself, is a marketing document. Customer count keeps climbing. ARR has been reported in the $70 million range. The valuation, set at the top of the 2022 market, was $1.725 billion.

Behind those rounds is a customer list that does most of the selling. Microsoft has been a public reference. Zoom, UiPath, 1-800-Contacts, Avast, Envoy, Cartier. The ICP is a product team big enough to feel the pain - somewhere between Series B and the Fortune 500 - and self-aware enough to admit they have it. Productboard's deepest partnerships are with the tools their customers are already using: a two-way Jira sync, a Salesforce integration that pipes account data into the feedback layer, Slack alerts when a top customer files a request. Not glamorous. Useful, which turns out to be better.

Products that matter

The official mission - "to help companies make products that matter" - is the kind of phrase you would expect to find embroidered on a beanbag in San Francisco. But there is something underneath it that the cofounders genuinely seem to mean. Palan has spoken often about the gap between what teams build and what customers want. The pitch isn't really for a roadmap tool. It is for a discipline. Make decisions with evidence. Listen to users before listening to the loudest internal voice. Say no, with data, to the things that don't move the needle.

Whether that discipline can survive the move from a small Prague startup into a 340-person company with offices in four cities and AI features racing into the product is the question every late-stage SaaS company eventually meets. Productboard has had its rough quarters - layoffs in 2023, the same market correction that hit everyone else - and the team has reorganized around efficiency. The product itself, by most independent reviews, keeps getting better.

The decision layer

Software development is in the middle of a revolution that nobody quite knows how to price yet. AI writes code now. Designers prompt their way to interfaces. The bottleneck used to be how fast you could build. Increasingly, the bottleneck is whether you should be building this thing at all. Which is - if you squint - exactly the problem Productboard has been quietly building software for over ten years to solve.

If the next decade of tech is going to be defined less by what we can ship and more by what we choose to ship, the company that owns the decision layer is in a very interesting place. Productboard is not the only player in that race - Aha, ProductPlan, and a handful of AI-native upstarts are circling - but it has a head start, a customer base, and an unusually clear point of view. The roadmap, in other words, looks pretty good.

Back to the product manager at Microsoft. She is still moving cards. The cards now have feedback attached, customers attached, revenue attached. She has not opened a spreadsheet all morning. Somewhere, on a flight from somewhere to somewhere else, another product manager is sketching another idea. The tools, finally, are catching up.