Tada Product Development
Link to Doc
Description: What is it? Tada is a product built for and by PMs. It takes in meeting transcripts and converts them into to-do list items and Jira/Linear tickets.
Problem: What problem is this solving? Currently PMs use multiple disconnected tools (Jira, Zoom, Granola, Claude) to complete this flow. The biggest issue is the lack of a context layer – a PM has to extract action items from meeting transcripts based on their company and role’s context and manually add them to Linear. We want to a) create a shared context layer so users don’t have to add it each time and b) automate micro-coordinating between tools.
Why: How do we know this is a real problem and worth solving? 4/9 PMs we interviewed raised post-meeting visual alignment as an issue without being asked. PMs struggle to update documentation after meetings and have a hard time keeping their teams on the same page. One PM said, “It’s challenging knowing what decisions got made, what’s changed, and what decisions have been made since just yesterday.”
Success: How do we know if we’ve solved this problem? We will know we’ve become the go to new tool for PMs in SF when our churn rate is less than 20%, our activation rate is greater than 50%, and our confirmed tickets rate is over 60%.
Audience: Who are we building for? We’re building for IC PMs that need to align their team. We’re targeting remote/hybrid software teams at mid-size and large companies. We chose these groups because they sharply feel the pain of struggling to align without in person collaboration.
What: Roughly, what does this look like in the product? In order to keep remote/hybrid software teams at mid/large-size companies aligned we will be combining context from Slack messages/updates, meeting notes, and context from any other communication channels, into one combined shared AI context layer that then updates outdated documents automatically and helps PMs find decisions and updates quicker.
How: What is the experiment plan? We plan to conduct 3 experiments before the end of Q4. These include building out a more functional backend for our prototype and putting a fake door test up on our landing page. See our Test Cards to read more.
When: When does it ship and what are the milestones? This quarter (Q4) we’re focusing on validating assumptions, building a prototype, and testing on beta users. We’ll build through Q1 and ship at the end. Some milestones are adding two full time engineers to the team, focusing on marketing, having a free trial group, and getting our first paying customers.
One line from this reading: We used Lenny’s template to complete this assignment. AI moves very quickly, and one of the best ways to stay up to date on new tools is to go to content creators whose job is to compile and share new ideas.
