I'm trying to decide between building several small, focused SaaS products or keeping everything under one product.

Let's say the tools are related and aimed at roughly the same users, but each solves a different problem.

My feeling is that a focused product might be easier to sell. If someone has one specific problem, paying $20 30/mo for a tool that does exactly that feels reasonable.

But if I put 5 10 tools together and charge $70 100/mo, even if technically it's much more value, some people may feel like they're paying for a lot of stuff they don't need.

Hello!

Anyone here building something around sustainability? I ve been browsing for a while and haven t seen many products tackling climate change or other global challenges.

I ve been thinking about another problem with AI autonomy.

An individual action can look completely reasonable, while the cumulative behavior becomes risky.

For example, maybe an agent is allowed to:

What are some of the best GTM strategies for an open-source developer-facing efficiency tool?

I am working my open-source, local-first tool for developers that turns day-to-day engineering activity into useful project updates, without timers or manual busywork.

My current GTM plan is fairly founder-led:

Start with Product Hunt and developer communities where people already discuss productivity, worklogs, AI coding agents, Jira, Linear, GitHub Issues, and engineering visibility.

I ve been working on a product for podcasters and while I m excited about the idea, it s been tricky to consistently connect with the right people for feedback.

I ve tried a few things: replying in niche communities, asking questions on Reddit, and even testing out some cold outreach. A couple of early chats helped shape my thinking, but it s been tough to keep the momentum going.

I believe this topic is relevant to you as well, since there are many company founders here at various stages of starting up or running their businesses.

Visual Capitalist shared the results of Glassdoor reviews, revealing which companies are most admired by their employees. (See the infographic below.)

I'm a product manager. My job used to have clear handoffs: I'd gather the material, hand it to a designer for mockups, then pass it to a front-end teammate to build.

Now, with AI, I do all of it myself. I've been building a product landing page almost entirely with AI, and I can go from an idea to a decent-looking page in one sitting. The first impression is genuinely impressive "wow, this actually looks like a real page."

While building an AI system for startup analysis, I ran into a problem with the usual workflow.

The prompt is often something like:

Is this a good startup idea?

The problem is that this produces one big conclusion from a bunch of smaller assumptions.