$300 MRR in 7 days. Here's exactly how I launched PostClaw.

the reddit ads result doesn't surprise me honestly. paid channels are brutal when you're pre-product-market-fit, there's no social proof, no retargeting pool, and the landing page hasn't been battle tested yet. the organic-first approach is actually the smarter move because it builds the exact feedback loop you need - real words from real users that later become your ad copy and landing page headlines. curious if you'd consider layering paid back in once you have more retention data, or are you going all-in on organic for now?

the paid vs free comparison is wild but makes total sense. paid ads need trust signals to convert — testimonials, polished landing page, social proof — and early on you just don't have any of that. organic works because the post itself IS the trust signal. you sharing real numbers and honest context is the proof people need.

ran into something similar with pricing decisions on my own launch. went with a $1.99 one-time upgrade instead of monthly subscription because the trust bar is so low when people first discover you — nobody's committing to recurring payments for something they just found. lowering that initial friction made a real difference in early conversions. curious if you considered a cheaper entry tier alongside the 29/month to capture people who are interested but not ready to commit yet

The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.

Once you have 20-30 customers you can look at patterns — same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.

What was the common thread across your early customers?

Pricing being hard is a symptom of not knowing the value precisely enough.

The cleaner framing: what does this save/earn the customer, and what's that worth to them? If the tool saves 5 hours/week at $50/hour equivalent, that's $1,000/month in value. Charging $49 is leaving most of it on the table.

One-time pricing for tools often underprices because the value is ongoing. Subscription makes sense when the value is recurring. The pricing model should match how value is delivered.

00 MRR in 7 days is a great start — the early momentum matters more than the number.

One thing worth wiring up now while your customer count is small: automated recovery for failed Stripe payments. At this stage losing even one paying user to a card failure that could've been recovered stings disproportionately. tryrecoverkit.com/connect takes 30 seconds, runs silently in the background, and sends a Day1/Day3/Day7 sequence automatically when a payment fails. Better to have it before you need it.

Congrats on the launch!

The €70 → 0 vs free post → 9 table is the clearest possible proof that paid traffic needs a warm audience to land on. You can't buy the trust-building step.

One thing worth watching: chat-based UX means the "aha moment" takes longer to arrive. Users need to complete the full loop — schedule a post, see it go live — before they feel the value.
Might be worth mapping out what Day 3 and Day 7 look like before you scale acquisition.

Building in public has never been more beneficial. Traditional paid outlets still have their place, but it’s getting smaller. Thanks for the insight

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

The first $1K MRR is harder than $1K to $10K because you're still finding who actually buys.

Once you have 20-30 customers you can look at patterns — same job title, same company size, same trigger that made them buy now. That pattern is worth more than any marketing playbook because it tells you exactly who to go find next.

What was the common thread across your early customers?

Really resonate with this. I ran into the same issue when building my own tool — eventually just shipped it and let user feedback drive the roadmap. Seems like you did the same.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

Congrats on the launch! The organic vs paid lesson is one most founders learn the hard way. One thing worth reflecting on at Day 30: do you still find yourself using PostClaw daily? I ask because I built something for myself, launched it, and realised once it was live I stopped reaching for it. Loved building it, but the repeated daily pain wasn't strong enough. If you're genuinely using your own tool every day to manage your own social media, that's a strong signal. If not, it's worth figuring out why before you scale distribution further.

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

Building in public has a timing problem people don't talk about enough.

Sharing early creates accountability and sometimes attracts early users. But premature sharing can also lock you into ideas before you've had a chance to discover what actually needs to be built. The sequence matters.

What I've seen work: share the problem and constraints publicly, share solutions privately with early users until there's signal, then share results publicly. Keeps the exploration honest without performing conviction you don't have yet.

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

The paid-to-organic shift is almost universal in early launches. Paid channels need trust signals to convert - social proof, reviews, a recognizable product. Without those, you are paying to send strangers to an unknown product. The math never works.

Organic works early because the person choosing to engage with your free post is self-selecting. They read it, they like it, they click. Higher intent than someone who saw an ad.

The interesting part of your story is the 9 signups from a free post vs 0 from 100 paid clicks. That gap is not just about paid-vs-organic. It is about the audience. Reddit users who found your organic post were the exact right people. The paid traffic was probably not.

I have been distributing B2B sales tools through IH, write.as articles, and community comments. Zero paid spend. Slower than I would like but the people who engage are genuinely in the problem space. That signal is useful even before there is revenue.

What was the free post about? Was it a launch post or something more educational/value-first?

Congrats on $300 MRR in 7 days — the Reddit ads vs free IH post contrast is a great reminder that distribution channel fit matters as much as product-market fit.

One thing worth keeping an eye on as you scale: with €29/month subscriptions, involuntary churn from failed payments (expired cards, bank declines) typically eats 5–15% of MRR silently. Stripe's default handling doesn't catch most of it. Worth setting up a Day1/Day3/Day7 recovery email sequence before it compounds — tryrecoverkit.com/connect automates that if you want a quick solution. Keep building!

The comparison between ads and a single honest post is fascinating.

With ads you're interrupting someone who has zero context. With a build-in-public post, people already understand the why before they even click. That changes the entire conversion dynamic.

It’s almost like the post itself becomes part of the onboarding experience.

Are you planning to keep leaning into the build-in-public strategy long term?

$300 MRR in 7 days is solid proof that distribution matters more than product polish at the early stage.

The pattern I see in launches that work fast: the founder had already been present in the community (commenting, helping, sharing) long before the launch. The "launch day" is really just the day you announce to people who already know and trust you. All the conversion work happened before that.

What community had the most traffic for you - IH, Reddit, Twitter, or somewhere else? Curious what the distribution breakdown looked like.

The interesting part here isn’t just organic beat ads, it’s that your best channel was the one where you explained the product in a human way. Makes me think the real win wasn’t distribution alone, it was narrative. Did you notice any specific phrasing or positioning that got people to convert faster?

Out of curiosity would you reddit ads again, if yes, why?

nice is it open source

Impressive reaching $300 MRR in 7 days. How long does it take you each day to write those updates on IH, Reddit and X?

The paid vs. organic breakdown is consistent with what I see. The IH community specifically reads differently — a builder sharing honest progress data gets attention that a landing page never would.

The zero-cost method that's worked best for me: commenting on existing threads where someone is discussing a problem your product solves, rather than creating your own post. Lower surface area, but the people reading that thread are already in problem-aware mode. Your signal-to-noise ratio is higher because you're not explaining the problem from scratch.

One question worth tracking at Day 30: of those 10 paying users, how many are still active? The launch MRR is exciting but the second hard problem is holding it. Especially for a social media tool where the 'aha moment' might arrive on a delay (you need to actually schedule posts and see engagement before you feel the value).

The IH community is genuinely better for B2B SaaS than most founders expect — not because it's large, but because it's full of people who are actively building and actively looking for tools.