2
5 Comments

I spent a day trying to get our first alpha users. 0 applications.

Yesterday I spent most of the day trying to get the first founders into the alpha of something we’re building.

We got 0 applications.

At first that obviously doesn’t feel great, but it’s also useful information. It forced me to question whether I was asking people to try a product before properly understanding whether they actually experience the problem.

We’re building Tempest, a decision workspace for founders navigating fragmented context.

The problem we’re exploring is what happens when the context behind a startup gets spread across customer conversations, AI chats, notes, docs and your own head. You make a product decision, move on, and a few weeks later you remember what you chose but not always the full reasoning behind it.

So I’m changing how I approach the alpha.

Instead of starting with “want to try our product?”, I’d rather understand how founders currently deal with this.

If you’re actively building something, how do you keep track of the reasoning behind important product decisions, especially when customer feedback, AI conversations and your own assumptions all played a role?

posted toAvatar for product Tempest
Tempest
  1. 1
    I’m in a very similar stage right now. I recently launched a Spanish learning app, and I’m currently trying to find my first 5 real users. I’ve also realized that asking “would you try my app?” is probably less useful than first understanding what people actually struggle with. I’m now trying direct outreach and talking to people one by one :)
    1. 1
      Same here. Direct outreach has been way more useful than just posting and hoping people show up. The interesting part for me has been how much you learn from the way people describe the problem in their own words. How’s the one-to-one outreach going for you so far? Getting actual conversations?
  2. 1
    0 alpha applications is the useful signal. Have conversations shown founders already feel enough pain around lost decision context to change their workflow, or is that problem still mostly theoretical?
    1. 1
      That’s exactly the question we’re trying to answer now. The pain itself doesn’t seem theoretical anymore. We’ve spoken to founders who said the reasoning behind decisions mostly lives in their head, across AI chats/docs, and a few have even built their own internal systems to deal with it. What we haven’t proven yet is whether that pain is strong enough to make them change their workflow. Since this post we’ve had our first alpha application, but that gap between “yes, I have this problem” and “I’ll actually use something for it” is still the main thing we’re testing.
      1. 1
        That gap between agreeing the pain exists and changing the workflow is worth digging into. Could be easier to continue that over email sometime.