u/NoahGallagherSummers

this is going to feel a bit recursive — i built a tool for founders building in public, and the audience for it is literally this subreddit.

quick context: i'm 17, solo, sydney. spent 2 weeks talking to founders before writing code. one conversation changed the product completely. someone said:

"if it just turns my commits into captions i'd pass. if it finds the moment — the 4-day bug, the 3 failed attempts before the first sale, the boring decision in march that made july's feature possible — and writes it in my voice, i'd pay."

so that's what outpost does.

connects to your github. doesn't just read your commits — also pulls PR descriptions, review comments, closed issues, and the rejection layer (what almost shipped but didn't). that's where the actual story lives. then drafts posts in your voice using writing samples you paste in.

i need 5 people from here to actually use it. you get free access while we're in beta and i'll personally review the first draft outpost generates for you to make sure it's not changelog garbage. if it reads like AI homework i want to know immediately so i can fix it.

what i'm looking for: people who already ship regularly but post about it inconsistently. if you've ever stared at twitter on a sunday night thinking "i shipped 47 commits this week and have nothing to say about any of them" — that's the person this is for.

drop a comment or DM if you want in. happy to share more about what i've learned from validation too if useful.

I'm 17, solo, based in Sydney. Before building anything I spent two weeks asking founders on Reddit and X the same question: why do you ship constantly but post about it almost never?

The answers were all variations of the same thing.

"I have 47 commits this week and nothing to say about any of them."

"By the time I sit down to write, the moment has passed."

"AI writing tools sound like AI. Editing them takes longer than writing fresh."

One reply changed how I was thinking about it:

"If it just turns commits into captions I'd pass. If it actually finds the story — the 3 failed attempts before the first sale, the bug that took 4 days — and writes it in my voice, I'd pay."

So I've been building Outpost.

Connects to your GitHub. Reads your commits. Finds the most interesting narrative from the last week. Drafts posts that sound like you wrote them — learned from your past writing samples, not a generic AI voice. Auto-generates branded milestone graphics for moments worth sharing (first sale, MRR jumps, user count, shipping). You review, edit, approve, copy to post.

Not pitching anyone. The product is live but I'm only letting in 10 people first for free because I want to personally make sure the first drafts are good. After that it goes properly live.

If you ship code and don't post about it — drop a comment or DM me. I'll send you the waitlist link.

Curious to hear from anyone who has tried other AI writing tools too — what made you give up on them?

I'm 17, based in Sydney, and I've spent the last two weeks talking to founders on Reddit and X before writing any code.

The problem I kept hearing: founders ship constantly and post about none of it. Not because they don't want to — because sitting down to write about what you built is harder than building it.

The most useful piece of feedback I got:

"If it just turns commits into captions I'd pass. But if it actually finds the story arc — the 3 failed attempts before the first sale, the bug that took 4 days — and writes it in my voice, I'd pay."

That stuck with me. So I've been working on something that:

- Connects to your GitHub and reads your commits

- Finds the most interesting narrative from the last week

- Drafts posts in your actual voice by learning from your

past writing

- You review, edit, approve, and copy to post

Still in development. Not trying to pitch anyone.

My actual question is: what would make you trust a tool like this with your voice? The "AI sludge" problem is real — most AI writing tools sound like AI. How do you think about that?

Also if you'd want to try it when it's ready, I'm building a small waitlist — first 10 people get free access and I'll personally make sure the first drafts are good. Drop a comment or DM me.

Happy to share more about what I've learned from the validation process too if that's useful.

Hey all,

I'm 17 and building in Sydney. For the past week I've been validating an idea before writing any code — a tool that reads your GitHub commits and Stripe activity, finds the story arc, and drafts build-in-public posts in your voice.

Before I automate anything I want to do it manually first.

Here's the deal:

— You share your GitHub activity and any milestones from the past week (commits, first sale, failed experiments, anything)

— I read through it, find the most interesting story arc, and draft 2-3 posts in your voice

— You tell me honestly whether you'd actually post them and what you'd change

— Completely free, no pitch, no strings

This is purely to figure out if the narrative layer is worth automating before I build it. If the drafts are bad, that's useful data. If they're good, that's also useful data.

The only thing I ask is honest feedback — not "yeah these are great" but "I'd change this because..."

If you're interested drop a comment or DM me. First 5 people get a week's worth of posts drafted manually.

Landing page if you want context on what I'm building: outpostapp.dev

Hey all — looking for honest feedback before I build this.

The problem I'm trying to solve: indie hackers and SaaS founders are constantly told to "build in public" but actually doing it weekly is brutal. I shipped 4 features last week and posted about zero of them because I never sat down to write the post.

The idea: a tool that connects to your GitHub, Stripe, and other accounts, watches for activity (commits, milestones, first sale, etc.), and auto-drafts posts in your voice. You edit and click schedule. It posts to X, LinkedIn, and IndieHackers.

Pricing would be \~$19/month. Free tier with 4 posts/month.

My honest questions:

1. Would you actually use this, or is it solving a fake problem?
2. What's missing from existing tools (Buffer, Hypefury, Typefully)?
3. What would make you NOT pay for it?

Genuinely want to validate before writing code. Brutal feedback welcome.

[ Removed by Reddit on account of violating the content policy. ]