The building-in-public system that actually stuck (after failing every "just be consistent" framework)
I spent the first year of my product treating social media like something I'd get to eventually. Posted sporadically, disappeared during crunch, felt guilty about it constantly.
Here's the system that finally stuck — and it works because it makes content a byproduct of building, not a separate job:
1. Keep a decision log
Every real product decision gets one sentence: why did I do this. Not a post. Just a log. 30 seconds. This becomes the content backlog.
2. One post per week from the log
Pick the decision that felt most uncertain at the time. Those are always the most honest posts. Honest posts outperform polished ones in every community I've tried.
3. Replies are reactions, not performances
Stop trying to write the perfect reply. React genuinely, add one observation the person might not have considered, move on. 30 seconds per reply. It compounds.
The last piece was fixing the AI problem. Generic prompts made everything sound the same. Switched to training on my own tweet archive — replies actually sound like me now. I built this into XreplyAI as a BYOK tool — you connect your own Gemini or OpenAI key and pay the provider directly (usually under $5/mo).
Curious what systems other solo builders have landed on. Especially anything that makes replies less of a time sink.
Top comments (0)