Nothing I've tried so far has shown me the result I was hoping for.
But every day I learn something new.
I still believe my first internet dollar is coming.
Maybe not today.
Maybe not tomorrow.
But until that day arrives, I'll keep building.
6 weeks of building in public. here's what I actually learned.
STEP 1: consistency beats virality.
my best performing posts were not my most polished ones. they were the ones I posted when I had nothing to say but said it anyway.
STEP 2: replies > posts.
10 good replies under other people's posts built more awareness than 10 original posts. show up in conversations, not just feeds.
STEP 3: honest numbers outperform good numbers.
"17 impressions, 0 clicks, 1 user my sister" got more engagement than any metric I was proud of.
STEP 4: the audience you build is the product's first sales channel.
every reply is a warm introduction. every conversation is a future customer or a referral.
most founders treat build in public as a broadcast. it's actually a conversation.
QUICK RECAP:
consistency > virality โ replies > posts โ honest > polished โ conversation > broadcast.
6 weeks of building in public. here's what I actually learned.
STEP 1: consistency beats virality.
my best performing posts were not my most polished ones. they were the ones I posted when I had nothing to say but said it anyway.
STEP 2: replies > posts.
10 good replies under other people's posts built more awareness than 10 original posts. show up in conversations, not just feeds.
STEP 3: honest numbers outperform good numbers.
"17 impressions, 0 clicks, 1 user my sister" got more engagement than any metric I was proud of.
STEP 4: the audience you build is the product's first sales channel.
every reply is a warm introduction. every conversation is a future customer or a referral.
most founders treat build in public as a broadcast. it's actually a conversation.
QUICK RECAP:
consistency > virality โ replies > posts โ honest > polished โ conversation > broadcast.
Ship Log #4 is out.
the honest version of week 5:
โ 17 Google impressions. 0 clicks.
โ 1 free user. my sister.
โ 0 paying customers. 4 days left.
not dressing it up.
the whole plan for this week: stop broadcasting, start diagnosing. find the person with the pain, lead with their problem, not my product.
4 days to find one person willing to pay $9/mo.
Ship Log #4 is out.
the honest version of week 5:
โ 17 Google impressions. 0 clicks.
โ 1 free user. my sister.
โ 0 paying customers. 4 days left.
not dressing it up.
the whole plan for this week: stop broadcasting, start diagnosing. find the person with the pain, lead with their problem, not my product.
4 days to find one person willing to pay $9/mo.
accidentally found a 4 year old Reddit account I forgot I had.
1 karma. completely dormant.
second chance at the channel that got me shadowbanned last month.
not making the same mistake this time 5 comments a day, no links for a week, slow and steady.
Built something recently that actually works.
Not "works" as in compiles and ships works as in I open it every day, I use it without thinking, and it genuinely makes my workflow better.
That feeling hit me hard with Posthive.
I built it to solve my own problem switching between 10 tabs just to post the same update everywhere. Bluesky, Threads, Instagram, LinkedIn, Mastodon, YouTube... it was exhausting.
So I built the thing I wished existed.
And somewhere between the hundredth bug fix and the first time it actually fired a post automatically at the exact second I scheduled it I realized I was addicted to my own product.
That is a strange and really good feeling.
If you are a creator tired of the tab-switching grind, Posthive is open source, self-hostable, and free to try for 14 days.
cold DMs get ignored. here's what actually works.
I sent 4 cold DMs last week. 0 replies.
then someone told me: lead with their problem, not your product.
here's the framework:
STEP 1: find someone who publicly posted their pain.
"no idea which channel is driving my signups" that's your person.
STEP 2: diagnose before you pitch.
don't open with "I built a tool for this."
open with: "I saw your post looks like you're getting direct traffic with no UTM tags. that's why it shows up as unknown source."
STEP 3: one screenshot. no pitch.
show them what their problem looks like. not what your solution looks like.
STEP 4: end with a question, not a CTA.
"is that the issue or is it something else?"
most founders pitch. the ones who diagnose get replies.
QUICK RECAP:
find the pain post -> diagnose the problem -> one screenshot -> ask a question -> then pitch.
100 commits in on Posthive
what shipped:
โข 11 platform integrations
โข first comment automation
โข bulk CSV scheduling
โข MCP server for AI agents
โข drag-to-reschedule calendar
all open source. all in ~2 weeks.
each adapter implements the same interface createPost, createComment, refreshTokenIfNeeded. auth is per-platform: OAuth tokens encrypted AES-256-GCM at rest, app passwords for Bluesky, bot token for Telegram, keypair for Nostr.
biggest headache was Meta's 60-day token refresh and X charging $0.20/post with a link ๐
you can check the repo for more details
100 commits in on Posthive
what shipped:
โข 11 platform integrations
โข first comment automation
โข bulk CSV scheduling
โข MCP server for AI agents
โข drag-to-reschedule calendar
all open source. all in ~2 weeks.