My AI posted 1,532 times while I was cooking burgers. Nobody noticed.
That's not a metaphor. I run a burger shop in Japan. Since January 2026, I've been running an autonomous AI system — I call it Sage AI — that posts content to Bluesky on two accounts (one English, one Japanese) around the clock. No manual scheduling. No copy-paste. The system wakes up, checks Notion for topics, generates posts, and publishes them while I'm prepping food or cleaning the kitchen.
By any measure of output, it works. By any measure of results, I built the wrong thing first.
The backstory
I had no marketing background when I opened the restaurant. Still don't, technically. I didn't know what 3C analysis was. I didn't know what STP meant. I just knew that my competitors seemed to know something I didn't, and that figuring out what that was took me about 3 hours every week of manual research I didn't have time for.
So I did what I do: I built software. First Growl — an AI tool that automates competitor research and marketing strategy for small business owners like me. Then Sage AI — the content engine that would market Growl to the world while I stayed behind the counter.
The system is technically real. Flask/Python backend, 13 autonomous background threads, LangGraph for multi-step reasoning, CrewAI for agent orchestration, Groq for fast generation, Cloudflare Workers for 24/7 uptime. It actually runs. It actually posts. It actually generates content while I'm at the restaurant.
The mistake was thinking that was the hard part.
The numbers (honest version)
Here's what 140 days of autonomous content looks like:
- kanagawatable (English Bluesky account): 247 posts. 6 followers.
- kanagawajapan (Japanese Bluesky account): 1,285 posts. 24 followers.
- Combined: 1,532 posts. 30 followers. ¥0 in revenue.
I want to be precise: the Stripe payment links for Growl are real. If someone clicked and subscribed, the money would actually arrive. The infrastructure works end-to-end. But nobody has clicked, because nobody is watching.
Automation solved the wrong problem. I thought the bottleneck was content production. It wasn't. It was credibility and community — and those things don't scale the same way posts do.
The lesson
1,532 posts at 10-15 per day taught me something I couldn't have learned any other way:
Volume into a void just creates more void.
Posting 15 times a day to 6 followers doesn't compound. It doesn't build trust. It creates a record that, when someone does finally visit the profile, looks automated — because it is. The algorithm can't save you if no real person has ever engaged with your content. The engagement signals don't exist.
Meanwhile, the one post I wrote honestly about failure — this one, right here — is already reaching more people than a week of automated output.
The insight isn't that automation is bad. Sage AI is genuinely useful — I don't want to go back to doing any of that manually. The insight is that automation works after you've built the community, not instead of it.
What I'm changing
Three things, starting now:
1. Community first. Honest story, honest numbers, genuine conversation. I've been ignoring the best channels for my actual audience while posting into the Bluesky void.
2. Bluesky: volume to conversation. Switching from 10-15 posts/day to 1-2 posts/day that end with a real question. Every post must invite a reply or it doesn't go out.
3. ProductHunt launch. Growl is ready. Real product, real payments, real use cases. If you want the full technical architecture — how I built the autonomous posting system, the Cloudflare Workers setup, the LangGraph pipeline — I documented everything in the Sage 3.0 Developer Blueprint ($49, one-time).
Growl itself is free to try at growl-app.vercel.app — no signup required.
The question
I know I'm not the only builder who built the engine before the audience. If you've been through this — the "I have a working product and no one knows it exists" phase — what actually moved the needle for you first? Platform? One specific post? A community like this one?
Asking because I'm going to try to replicate whatever actually works.
A solo developer in Japan. Building Sage AI + Growl. Day 140 of building in public.
Top comments (0)