u/AWGV_G

I’ve had this pattern more than once, and I’m trying to be more honest about it now. Building is comfortable for me. I studied engineering, I like product problems, and it is very easy to convince myself that one more feature, one cleaner onboarding flow, or one better landing page is still progress.

The first SaaS I built failed mostly because of that. I was spending my energy making the product feel better while the real problem was that not enough people knew it existed or cared enough to switch. It sounds obvious when I write it, but in the moment product work feels productive and sales work feels messy.

For indie founders who are more builder than salesperson, how do you force the balance back toward distribution without turning every week into guilt and fake discipline? Do you set hard rules, like no product work before outreach, or is there a better way to structure it?

I’m working on an early B2B SaaS in a space where the pain is real, but the words people use for it are all over the place. Some prospects describe it as AI SEO, some as brand visibility, some as AI search, and some just talk about not showing up where buyers ask questions.

My first instinct was to pick the clean category term and build around that, because it makes the website and content plan look coherent. The problem is that clean terms are often not the words people use before they understand the category. It feels neat for us, but I sometimes have to explain the meaning behind each word during demos ahah.

For people who have grown products in a new or fuzzy category, did you start by attaching yourself to existing search intent and pains, or did you push the new category language from day one? I’m especially curious where you drew the line between clarity and educating too much.

I’m selling an early B2B SaaS as a founder, and I’m finding the first demo is doing two jobs at once. It is supposed to move a real deal forward, but it is also where I still learn how people describe the problem and what they compare us to.

The part I’m unsure about is how strict to be before accepting the call. If I qualify too lightly, I can spend time with people who are curious but not really in pain. If I qualify too hard, I might filter out useful conversations before the ICP is fully clear.

For people who have sold SaaS at this stage, what do you need to know before a first demo is worth taking? Budget, current workaround, urgency, role, company size, or something else?

I’m working on growth for my current B2B SaaS, and the part I’m struggling with is not finding ideas. It is deciding when one deserves real focus.

We got our first customers through very direct founder work, which makes sense at the beginning. Now I’m trying to move toward something more repeatable, but every channel has this awkward middle stage where it is not clearly dead and not clearly working either. Content, outbound, partnerships, paid tests, they all produce some signal if you stare at them long enough.

My engineering reflex is to test too many things because it feels rational, but in practice it can become a way to avoid committing. For people who run growth in early B2B, what makes you say something is worth a proper push instead of identifying as noise?

I’m working on growth for my current B2B SaaS, and the part I’m struggling with is not finding ideas. It is deciding when one deserves real focus.

We got our first customers through very direct founder work, which makes sense at the beginning. Now I’m trying to move toward something more repeatable, but every channel has this awkward middle stage where it is not clearly dead and not clearly working either. Content, outbound, partnerships, paid tests, they all produce some signal if you stare at them long enough.

My engineering reflex is to test too many things because it feels rational, but in practice it can become a way to avoid committing. For people who run growth in early B2B, what makes you say something is worth a proper push instead of identifying as noise?

I’m working on content for a technical B2B startup, and the part I find hardest is not producing more drafts. It is keeping a real point of view in the piece once everyone has touched it.

In theory AI should help with the boring parts, like turning messy notes into a structure or checking if an article actually answers the question. In practice, when a draft starts from AI, it can get this smooth, generic tone where every paragraph could belong to any company in the category. Maybe it is my process, not the tool tho.

For people doing content marketing in serious B2B or technical niches, where do you draw the line? Do you allow AI for outlines only, editing only, research cleanup, or not at all before a human has written the first ugly version?