Team 8 (Bumblebees): Alexis Tuchinda · Christian Roy · Efrain Angon-Cruz · Natnael Tadesse
Our Week 8 tests changed how we think about launching. Of the 9 teammates we invited, only 4 logged in and only 2 finished a core workflow. Most of the drop-off came from manual profile setup. We also learned from our PM interview that feedback usually starts in Slack and email, so asking people to go to a separate app first was working against us. Most of this plan comes back to those two problems.
Who we’re launching to
We’re starting with small product teams, around 5 to 10 people with one PM, that already use Slack every day. The PM sets up the project and decides whether to use Product Hub. Everyone else on the team either sends feedback or owns a requirement.
We thought about going after bigger companies, but they usually need security reviews and longer approval before trying a new tool, and we don’t have results from real projects yet. With a small team, one PM can decide to try it the same week.
Distribution channels
Our main channel is a Slack app, listed in the Slack Marketplace. A PM installs it, signs in with Slack, imports the team roster, and picks which channels to watch. When someone posts feedback in one of those channels, Product Hub checks it against the scope and sends it to the right person. Nobody has to open another tool to make that happen.
The web app is still where the PM sets up scope and decides on CONFLICT and ADDITION items. For stakeholders who mostly use email or aren’t in the team’s Slack, there’s the quick-capture link for each project.
We looked at a few other options:
- Web app only. This is basically what we tested in Week 8, and it’s where we lost people. It asks users to change where they work.
- Jira or Linear app. These track tasks, but feedback doesn’t show up there first. We’d like to connect to them later.
- Microsoft Teams. It’s bigger in large companies, but the teams we’re starting with use Slack. We can add it once the Slack version works well.
- Mobile app stores. PMs set this up once per project at a desk, so a phone app doesn’t add much.
Sales strategy
We’re going with self-serve and freemium. A PM can install it and set up a project without talking to us. Anyone the PM invites is free, forever. If stakeholders had to pay to submit feedback, a lot of them just wouldn’t, and then the tool has nothing to route.
One option is to keep one active project free and charge for more projects and integrations. We haven’t tested any pricing, though. We planned a $15/month smoke test back in Week 5 but didn’t run it, so we’re leaving the price open for now.
Self-serve fits because the PM is the one who feels the problem, and a PM on a small team can usually start using a tool like this without asking anyone. It also lets us see exactly where people drop off in our activation funnel, which matters since activation (KR2) is the goal we missed by the most.
Direct sales doesn’t make sense yet. We’d need case studies we don’t have, and a small team isn’t going to take a sales call for this. Reseller partners like agencies have no reason to push us until we can show it works. We also ruled out a 14-day free trial, since scope changes happen over the whole project and a trial would end before most teams saw much value.
Marketing and promotion
We don’t have a budget, so we’re sticking to things that take time instead of money.
We’ll start with the PMs we’ve already interviewed. They told us about this problem in the first place, so we’ll ask them to try it on a project they’re running now.
After that, we’ll post in PM communities like Lenny’s Newsletter Slack and r/ProductManagement. People there already talk about scope creep and late feedback, so we’ll share a short demo of Product Hub catching a real conflict instead of writing a sales post.
We also expect some spread through the product itself. Each project brings in a whole team, and every stakeholder who uses the quick-capture link gets to see where their feedback went and who owns it. That’s 5 to 10 people seeing it for every PM who signs up.
We think PMs will care because we’re leading with something they already deal with, which is rework from feedback that showed up too late. A lot of the PMs we talked to said they don’t really have a fix for this, they just put up with it. It also helps that we can say it runs inside Slack, so it doesn’t add one more place to check.
We’re holding off on Product Hunt. It would bring a lot of attention for a day or two, but most of those people wouldn’t be PMs on an active project, and right now we’d lose more than half of them at setup anyway. It makes more sense once onboarding is fixed.
Customer service strategy
Most people we lost in Week 8 dropped off in the first few minutes, so a lot of our support has to be inside the product:
- New PMs start with a sample project and scope, so they can see a verdict before setting up their own.
- Roster import and Slack sign-in replace manual profiles, since that step is what kept 5 of 9 invitees out.
- Every verdict has a “report a wrong route” button. It tells us when routing is off, and it also gives us a way to measure accuracy.
- When the AI can’t tell what someone means (UNCLEAR), it asks that person a follow-up question instead of dropping a vague item in the PM’s inbox.
Outside the product, we’ll set up a shared Slack channel with each early team so they can message us where they already are. Everyone else can email us, and we’ll have a short FAQ that covers setup, what each verdict means, and how to fix a wrong route. There are four of us and we’re students, so live chat or phone support isn’t realistic. A community forum would just sit empty until there are a lot more users.
To catch people before they quit, we’ll check the activation funnel for each team. If someone logs in but doesn’t finish a core workflow, we’ll reach out to their PM instead of messaging them directly, so we don’t throw off the “comes back without a reminder” part of KR2. We’ll also keep an eye on the admin evaluation dashboard for wrong routes and slow responses. One UNCLEAR case in our evals took 15.1 seconds, and a delay like that inside Slack would make the app seem broken.
Launch sequence
We’re launching in steps and only moving to the next one once we hit its goal.
- Fix onboarding (now through Dec 1). Swap manual profiles for roster import and Slack sign-in, finish Slack channel capture, and invite a new group of teammates. We move on once at least 70% of them finish a core workflow (KR2).
- Early teams. Get 3 to 5 teams from our interviews using it on a real project. We help them set it up and join their Slack. We move on once at least 80% of feedback from Slack gets the right verdict and owner (KR5) and we pass 9 of 10 evals on real scopes (KR1).
- Public beta. List it in the Slack Marketplace, open the free tier, and start posting demos in PM communities. We move on once teams are signing up and finishing setup without our help.
- Paid plan. Test pricing, add Jira or Linear, think about Teams, and do a Product Hunt launch. The goal here is teams that keep using it through a whole project.
From the reading
Gourville’s 9x effect says users overvalue the tools and habits they already have, while builders overvalue what they made. We used this in our distribution plan by putting Product Hub inside Slack, where feedback already happens, instead of asking teams to switch to a new tool.
