The Middle of the Founder Grind: What to Do When Traction Stalls

Nobody writes about the middle.

You get a flood of "here's what I'm building" posts before launch, and then a wave of "here's how we scaled" retrospectives after someone exits or raises. The part in between, where the product is real and working and the dashboard just... sits there, that part stays mostly private. Which is exactly why so many founders think they're doing something wrong when they hit it.

I'm in it right now with ManagerForge. The product works. Paying customers are using it. The feedback is genuinely good. And the growth curve looks like a horizon line. That's the trough, and it's uncomfortable in a specific way that "just keep building" doesn't fix.

Why "Build More" Feels Like Progress

There's a reason founders reach for the product when traction stalls. Building is the thing you know how to do. It produces a tangible output. At the end of a day spent coding or designing or refining a feature, you have something you can point to. That feeling of movement is real, even when the actual movement it produces is zero.

Distribution doesn't feel like that. Cold outreach feels awkward. Writing LinkedIn posts feels exposing. Pitching podcast hosts feels presumptuous. Posting on Hacker News feels like screaming into a cave and waiting to see if anything screams back. None of it produces the clean feedback loop that shipping a feature does.

So you ship another feature. And another. And you tell yourself you're not ready to market it yet because the onboarding isn't quite right, or the pricing page needs work, or you need one more integration before it's really ready to show people. That's the trap. I've lived in it. I know what it feels like to optimize a tooltip while your user count holds steady.

The point being, the product isn't the problem; the obscurity is.

The Actual Job in the Trough

When growth stalls, the honest diagnosis is almost always the same. Not enough people know the thing exists, not that "not enough people want it," or "the market timing is wrong," or "the positioning needs a complete overhaul." Just: not enough eyeballs. The product is fine, the awareness is the gap.

That realization should change what you do every day. The instrument changes. You go from building to distributing, from product to story, from your own platform to other people's audiences. That switch is uncomfortable for a lot of technical founders because distribution work is inherently social and inherently slow, and the feedback loops are longer and messier than anything you get from a clean deployment.

But here's what the math actually says: if 200 people know your product exists and 15 of them convert, you have 15 customers. If 2,000 people know it exists and 15% of them convert, you have 300. The product didn't change; the denominator did.

That's the only lever you have when the product is already working.

What a Distribution Sprint Actually Looks Like

I want to be specific here because "do more marketing" is useless advice. What I mean is a compressed, uncomfortable, seven-day sprint where distribution is the only job.

Day one is picking the lane. You're not doing all of this at once. You're doing one channel with intention. Product Hunt, Indie Hackers, Hacker News, a newsletter swap, a LinkedIn push, a podcast pitch sequence. Pick one. Commit to it. The hedged version where you dabble in all five produces nothing.

Days two and three are prep. If it's Product Hunt, you're writing your tagline, your maker's comment, your gallery. If it's HN, you're drafting a "Show HN" post that leads with the problem and doesn't feel like a press release. If it's a newsletter swap, you're identifying five writers in adjacent spaces and composing a pitch that's actually interesting to them rather than to you. This work is slower than it sounds.

Day four is the launch or send or post. This is the day where everything feels simultaneously too late and too early, and you hit publish anyway.

Days five through seven are the responses. Every comment, every reply, every direct message. This is where the actual product feedback hides, and it's also where the signups come from, because people buy from founders who show up in the thread.

What does this actually produce? Honestly, it depends. My first Indie Hackers post got 200 views and four signups. That's not a rocket ship. But those four people gave me feedback that reframed how I talk about the product, and two of them are still customers. That's real. The sprint isn't about going viral; it's about getting reps in an unfamiliar muscle.

Being Publicly Bad at Marketing

There's a specific discomfort that comes with distribution work when you're a builder at heart. You feel like you're performing. You feel like you're doing it wrong. Your posts don't land the way you hoped, your copy sounds stiff, your outreach gets ignored. That's normal and it's not a signal to stop.

I spent twenty years managing people and running operations before I started writing publicly. My first few LinkedIn posts were pretty bad. I knew it. They weren't getting traction because I hadn't figured out how to translate what I actually knew into something a stranger would stop and read. That's a skill. It takes reps to develop it, and the reps are going to be uncomfortable while you're developing it.

The alternative is staying quiet until you feel ready, which is a way of never starting.

Every founder I've watched get traction on a bootstrapped product went through a phase of being publicly mediocre at distribution before they got good at it. The ones who skipped that phase either had an existing audience, a well-connected network, or capital for paid acquisition. If you have none of those things, you earn the distribution by doing the work badly until you do it better.

What the Dashboard Doesn't Tell You

One more thing. When you're in the trough, the metrics feel like a verdict. Flat signups feel like the market saying no. Flat revenue feels like confirmation that you're building something nobody wants. That interpretation is usually wrong, but it's seductive because it gives you permission to either quit or pivot when neither is actually warranted.

The dashboard tells you what happened. It doesn't tell you why. Low signups during a period when you didn't distribute is not evidence that people don't want the product. It's evidence that not enough people saw the product. Those are different problems with different solutions.

When I check my ManagerForge numbers on a week when I've been heads-down building and haven't published anything, the numbers are flat. When I publish consistently and engage, they move. The product didn't change. The output of the distribution work did. That's the clearest real-time evidence I have that the trough is not a product problem.

You're probably not too late. You're probably not building the wrong thing. You probably just need more people to know it exists.

Switch instruments. Get uncomfortable. Do it badly at first. That's the job.