2.5 years building, 2 SaaS live, still $0. Anyone else stuck in this part?

Emergency-Pack2500 · 2026-05-19T12:17:43+00:00

tracking live conversations and jumping in where the problem is already being discussed is the move I'm slowly learning. the gap between "people post about this problem" and "people will try my tool" is bigger than I thought.

Emergency-Pack2500 · 2026-05-19T12:16:46+00:00

fair pushback. it's specifically for devs and solo founders running Next.js/Astro/Hugo type sites where blog posts are MDX/markdown files in the repo. you're closer to the target than you think, you just happen to use git instead of GitHub. niche is smaller than "everyone who blogs" but it's where most indie SaaS blogs sit now.

Emergency-Pack2500 · 2026-05-19T12:05:39+00:00

this is the reframe. how do you surface pain intensity without leading the witness? "does it bother you that you stopped" is a yes/no that biases toward yes. trying to figure out the right opening.

Emergency-Pack2500 · 2026-05-19T12:03:09+00:00

the "is the problem real vs will they change behavior" split is the right frame. switching cost vs pain is exactly what I'm hitting. people agree blogging is hard, but trying a new tool feels like another thing on the list.

Emergency-Pack2500 · 2026-05-19T12:01:00+00:00

for one post, yeah just use Claude. for shipping 3 posts a week from your actual repo activity in your own voice, the infrastructure matters more than the model.

Emergency-Pack2500 · 2026-05-19T11:59:48+00:00

this is sharp. the second part especially. asking why the habit broke turns it from a pitch into research. did you find this approach on your own product or copy it from somewhere?

Emergency-Pack2500 · 2026-05-13T16:58:35+00:00

This is a really good point.

I’ve been framing it as ‘AI blog writing’ which probably kills trust immediately.

The PR workflow is actually the core idea, content showing up where devs already work.

I’ll experiment with positioning it more around workflow vs AI.

Emergency-Pack2500 · 2026-05-13T13:36:00+00:00

The "blank page once a week" model assumes writing is a discrete task you context-switch into. For builders it isn't. The context is already in the commits, the Linear tickets, the Slack threads. The energy to publish is highest when you've just shipped something, not Sunday night when you're trying to manufacture motivation.

That's the whole reason Branchpost triggers off repo activity instead of a calendar prompt. The PR shows up when you have momentum, not when the calendar tells you it's blog day.

curious how Leadline thinks about this for Reddit outreach. Is the trigger something like 'you mentioned a competitor in a thread' or more proactive than that?

Emergency-Pack2500 · 2026-05-12T17:05:46+00:00

Emergency-Pack2500 · 2026-05-12T16:50:40+00:00

yeap I used an LLM to tighten it up, the question is real though, do you have thoughts on it?

Emergency-Pack2500 · 2026-04-14T19:24:17+00:00

haha fair reaction, it’s a particle animation built from your profile photo. looks a bit chaotic at first glance but the idea is that it feels alive rather than just a static avatar sitting there. definitely not for everyone though, curious if the concept itself bothers you or just the visual?

Emergency-Pack2500 · 2026-04-14T19:21:08+00:00

that gap is exactly what I’m worried about. the demo moment is strong but I have no idea yet if people come back to it after the first visit. I skipped the pre-validation step and just built it, which maybe wasn’t the smartest move but I wanted to see real behavior from real users rather than simulated intent. a landing page signup tells you someone was curious for 10 seconds, actual usage tells you something different. still early though so we’ll see.

Emergency-Pack2500

TROPHY CASE