Introducing: Build In Public: → Claude Code for building in public Marketing is dead for builders. The ones winning are documenting their work and turning it into distribution. 👇Here's how:

changed my openclaw from opus to gpt 5.4 speaks (and works) like a caveman for some reason i might just suck it up and eat the API costs for opus seems like no other way

am I missing out for not looking into clawdbot or is it just FOMO talking?

built onboarding that starts before you even sign up. landing page hero section = first micro-commit. type one ship moment right there. no account needed. then when you hit onboarding? same data's already waiting for you. psychology trick: get people to micro-commit. They convert better. stole this from checkout flows. works for saas too.

my new content workflow: 1. ship feature 2. custom claude code skill writes commit message (build in public style) 3. buildinpublic.so generates content from it 4. publish takes 5 minutes total. used to spend hours wondering what to post. now i just build and the content follows.

i'd ship every day but post... never 9pm. just finished coding. brain is fried. "i should tweet about this." but then i'd have to: explain what i built. why anyone should care. who it's even for. fuck it. too much thinking. i'll do it tomorrow.

ran a family fast food business doing £5k/week. zero profit. spent 2 years thinking revenue meant success. it didn't. the system was broken from day one. business eventually died. that failure taught me more than any win: surface numbers mean nothing. systems are everything.

3 years ago a single rejection could kill 2 weeks of momentum. i'd spiral. overthink. rewrite everything. convince myself i wasn't good enough. yesterday i got rejected by someone i really wanted to work with. read it. shrugged. moved on in 30 seconds. what changed? i stopped treating each no like a personal attack started treating it like what it actually is: one person's opinion on one day. the game is volume. always has been. remember: you're not getting rejected. you're just finding your people faster.

building in public sounds easy. "just share what you're working on" but here's what actually happens: • you ship a feature. • you forget to post about it. • 3 days later you can't remember what you built. so you post nothing. the gap between building and sharing kills momentum. then when you finally do share , you need: - storytelling - banger hooks - good packaging most builders give up here. so i built something that does both — captures what you ship, and writes the content for you.

you know that feeling when you fix a bug? and the solution is so obvious you want to delete your github account? just spent 3 hours hunting a "silent failure." endpoint returning 200 but not working. turned out my response interceptor was unwrapping data. so response.data didn't exist anymore. i was checking a field that literally wasn't there. changed 2 lines. everything works now. this is what building feels like when you're learning as you go.

my launch flopped yesterday i shipped Claude code for building in public 8 signups. felt like a failure. then i looked at the data: 31 visitors → 8 signups that's a 26% conversion rate. the landing page isn't broken. the distribution is. but here's the thing that's exactly why i built this product. turning your work into content. so more people see what you ship. time to eat my own cooking.