The Product Tool Built by Someone Who Hated Guessing

The idea for Zeda.io did not arrive in a boardroom. It arrived in the worst week of Prashant Mahajan's career. It was 2020, the pandemic was closing offices, and he had just been laid off from a product management job. He had done that job on four different continents - India, the United States, Indonesia, Japan - and in each place he had run into the same quiet absurdity. Product managers, the people supposedly deciding the future of a product, spent most of their days updating spreadsheets and most of their decisions on a hunch.

So instead of polishing a resume, Mahajan started building the tool he wished he had been handed years earlier. Alongside co-founder and CTO Vaibhav Devpura, he set out to answer the single most expensive question in software: what should we build next? Zeda.io is their attempt to make that question something you research rather than something you guess.

01 / WHAT IT DOESTurning noise into a decision

At its core, Zeda.io is a product discovery and strategy platform. The pitch is deceptively plain: your customers are already telling you what to build, they are just telling you in a hundred different places at once. A complaint sits in a Zendesk ticket. A feature request hides in a Slack thread. A pattern lurks in an Intercom conversation nobody re-read. Individually, each is a shrug. Collectively, they are a roadmap.

Zeda.io pulls all of that into one place - customer portals, in-app widgets, support tools, sales conversations - and then points AI at the pile. The system clusters similar requests, reads sentiment, ties feedback to revenue and customer segments, and surfaces the handful of problems actually worth solving. What used to be a PM reading tickets until midnight becomes a ranked shortlist.

"Until now, there hasn't been a consolidated platform that allows Product Managers to collect the right data and customer feedback and translate it into clear and actionable insights."Prashant Mahajan, Founder & CEO

02 / WHO USES ITBuilt for the people who get blamed

Zeda.io's customer is the product manager, and by extension the product leader who has to explain the roadmap to the rest of the company. These are people who sit between engineering, sales, and support, absorbing everyone's opinion about what the product should do next and then owning the consequences when the bet is wrong. The tool is aimed squarely at B2B software teams that describe themselves as customer-focused and want the receipts to prove it.

The company reports roughly $3.5M in revenue on a team of about 25, split across India and the United States. That ratio matters. It is a small operation deliberately serving a demanding audience, which tends to keep a product honest - product managers are, after all, the least forgiving users of a product-management tool.

The buyer is usually the same person who feels the pain most acutely: a head of product tired of walking into planning meetings armed with anecdotes instead of evidence. The appeal is less about dashboards and more about defensibility - being able to point at the reason a feature made the cut, and the several that did not. In practice that turns a subjective argument about priorities into something closer to a shared reading of the same customer signal.

03 / THE PROBLEMThe cost of building the wrong thing

Every wasted feature has a price tag: engineering months, sales promises that never land, churn from customers who wanted something else entirely. Mahajan's frustration was never that PMs were lazy. It was that they were flying blind and dressing it up as strategy. Feedback existed in abundance; the ability to act on all of it did not.

Zeda.io frames its whole job around a single moment - the moment a team decides what not to build. That is a sharper wedge than a prettier roadmap. A roadmap tells you where you are going. Discovery tells you whether you should go there at all.

There is a second, quieter problem underneath the first: scale. A single product manager can read a week of feedback by hand. No human can read a quarter of it across five channels while also shipping. As the volume of customer signal grew, the gap between what was said and what was actually read widened into something structural. That gap is exactly the space Zeda.io tries to close, which is also why the AI came later - the reading problem got big enough to need it.

04 / THE PRODUCTSFrom feedback hub to AI copilot

The platform bundles a few pieces that are meant to feel like one. There is the Voice of Customer feedback hub that centralizes and segments incoming signal. There is the discovery layer that walks a team from a raw customer problem to a defined opportunity to a strategy. And in 2024 the company shipped Insights 2.0, an AI copilot built to do the reading a human never finishes - scanning thousands of pieces of feedback and returning the complaints that need attention and the requests worth prioritizing.

Notably, the founder is not a wide-eyed AI evangelist. He has argued that many companies adopted AI out of a fear of being left behind rather than out of any clear plan. Zeda.io's counter-move was to point the technology at the one place fear cannot help you: genuinely understanding what a customer said.

"While many leading companies have prioritised AI, they've done so out of a fear of being left behind."Prashant Mahajan

05 / THE BUSINESSOne price, whole team

Here is a detail that says more than any feature list. Most product tools charge per seat, which means inviting a stakeholder - a designer, an executive, a support lead - quietly costs you more. Zeda.io went the other way with a flat rate reported around $499 a month for the entire team, all modules included. That single pricing decision tells you exactly who it is fighting. When your competitor's most useful plan runs into the hundreds per month and scales with headcount, flat pricing is not a discount. It is a position.

The business model underneath is standard B2B SaaS - recurring subscriptions plus custom enterprise arrangements - but the flat structure reflects a company that wants adoption to spread across a whole team rather than being rationed to a few licensed PMs. It is also the kind of pricing a company chooses when it is aiming for profitability, not just a bigger user count.

06 / THE COMPETITIONWhere it sits on a crowded shelf

The product-management aisle is not empty. Productboard, Aha!, Canny, Craft.io, and ProductPlan all want the same buyer. Zeda.io's answer to the crowd was to not compete on the same square. Rather than pitch itself as another roadmapping tool - the part that happens after decisions are made - it planted its flag in discovery, the messier phase before anyone draws a roadmap. It is a smaller category with less established branding, which is either a gap or a gamble depending on the day.

The product-management aisle is crowded. Zeda.io's move was to sell fewer wrong bets, not a prettier roadmap.

07 / THE PEDIGREEProduct people, product problem

The credibility here is lived, not borrowed. Mahajan spent years as a working product manager across several countries and studied at Harvard Business School Online before starting the company. Devpura runs the engineering. The team stayed small on purpose. Building a product-management tool as a former product manager is a specific kind of advantage - you know precisely which corners of the job are miserable, because you cut yourself on them.

That background shows up in the recognition, too. Zeda.io landed at #2 Product of the Day on Product Hunt, was tagged an upcoming startup to watch in both Delaware and India, and its founder joined the Forbes Technology Council. None of it is a unicorn headline. All of it is the slow accumulation of a company being taken seriously by the people it built for.

08 / THE MARKETWhat is worth stealing

For anyone watching from the outside, the transferable lesson is not the software. It is the framing. Zeda.io does not sell more features. It sells fewer wrong bets. It organizes an entire product around one under-served moment - the decision of what not to build - and prices it so a whole team can pile in rather than a gatekept few. From a pandemic layoff to an AI copilot pitched at American software teams, the through-line was never geography. It was a grudge against guesswork that the founder never quite got over.