I am working for a 20-person startup. @Linear is our product development system, which we really enjoy.

Currently, our operations team receives support requests via their personal email and then publishes requests in the Slack channel, where developers are picking up issues, but we would like to upgrade to a more comprehensive system with a shared inbox. I would like it to have an integration with Linear, and the ticket creation to be automated as much as possible. It would be great to have a help center (documentation), too, as a part of the offering.

For those who ve had a waitlist up before launching, what did you find converted best on your landing page?

I m not sure a minimal page can convert, but as a solo founder there s sometimes limited capacity to build a fully fleshed out landing page.

I have two bad habits that make this harder. I procrastinate, and I give up on things too easily. So I'll put off the boring task that matters, start something new and more fun instead, and then drop that one halfway through too.

I'm trying to fix it by deciding up front what I won't build, so there's less to wander off into. I haven't found a rule that sticks yet.

For the longest time my weekly dopamine hit was watching the signups counter tick up. I thought traction meant volume.

Then we started tracking 7-day and 30-day active usage, and the reality check was brutal. We were pouring water into a leaky bucket, celebrating every new registration while users slipped away silently within 48 hours.

For founders who survived this transition: what specific metrics or milestones forced you to stop celebrating signups and actually fix your activation loop?

Something I've been noticing: when people ask an AI assistant about a product, the answer often comes from old blog posts, third-party listicles, or a pricing page from 2 years ago, not from the current site.

For those of you running SaaS products: have you changed how you write your docs, changelog, or pricing page because of this? Things like structured FAQs, llms.txt, or a public changelog. Did any of it make a difference you could measure?

When I started building, I used my own tool all the time. That was kind of the whole reason I made it. I had a problem, nothing out there fixed it the way I wanted, so I built something.

But lately I ve noticed something.

Most of my time now goes into fixing bugs, answering emails, thinking about pricing, writing posts... and I barely use the product the way a normal user would anymore. I open it to test things, not to actually get stuff done with it.

And I m not sure if that s a problem or just what happens as things grow.

I want to separate the mythology from the data here, because I keep hearing two contradictory things.

Version A: PH launches are a vanity metric now the upvotes don't convert, the badge is a participation trophy, and the real value is the backlink.

Version B: people still get their first 100 paying customers from a single good launch.

My situation: no audience, no list, product is B2B and costs $29/month. A launch would be my first real distribution moment. I'm trying to decide whether to spend six weeks building an audience first, or launch now and use PH as the audience-building event itself.