I’ll be honest: I’ve never really built in public.
Sure, I’ve posted wins. Shared insights. Let people peek behind the curtain. But when I watched CJ Zafir scale his AI startup CodeGuide to $42K/month in just 90 days, something hit hard:
He wasn’t just documenting the journey — he was driving the business by sharing it.
Every step went live on Twitter/X: the bugs, the wins, the “is this even working?” moments. That raw transparency didn’t just build trust — it sharpened his vision.
Behind the scenes, I’ve been quietly developing a personal assistant workflow. But the more I study CJ’s playbook, the more I realize:
Should a public strategy be viable?
Let me show you what CJ did — and how I’m possibly applying it to my own AI project.
🔍 The 3 Big Questions Every AI Founder Faces
Before CJ wrote a single line of code, he asked the questions that matter most:
1. What Problem Am I Solving?
CJ didn’t chase trends. He chased pain.
As a developer, he struggled with bloated docs and unclear code examples. So he built a tool that fixed it.
Try this:
Write down three moments in your workday that feel clunky or frustrating.
Then ask: “Are other people annoyed by this too?”
That’s not a to-do list. That’s your idea mine.
2. Will Anyone Pay for This?
CJ skipped months of development and mocked up a no-code prototype.
Then he launched a landing page and waited — not for compliments, but for signals.
Real validation looks like:
- Users giving detailed feedback
- Early adopters offering to pay
- DMs like “When does this launch?”
No buzz? No build.
3. How Do I Get the Word Out?
This is where CJ went full throttle.
He built in public every day:
Quick updates. Honest progress. Screenshots. Failures. Wins.
And that created three things fast:
- A real audience
- A feedback loop
- A community of early adopters
I’ve said it before: attention is earned. CJ earned his by being relentlessly real.
From Idea to $42K MRR — The Blueprint
Here’s how CJ did it — and how I’m following suit with my own assistant workflow.
1. Spot the Pain
CJ fixed his own developer headache — clear problem, clear pitch.
→ My pain? Losing time to scattered tasks. So I’m building an AI assistant that keeps my day focused and friction-free.
2. Build the Quickest MVP
CJ used Figma, no-code tools, and GPT prototypes.
→ I’m using n8n + Supabase to build a lightweight scheduler and smart recap engine. No full app needed (yet).
3. Launch Early — Even If It’s Ugly
CJ showed the rough version and improved in public.
→ I’ll post test runs and walk through bugs and breakthroughs weekly.
4. Price for Progress
CJ’s freemium model gave real value upfront, with premium perks to upgrade.
→ Mine? A free tier with daily summaries. Paid tier unlocks automation + analytics.
5. Let Behavior Guide Features
CJ didn’t guess — he watched users.
→ I’m tracking: What triggers usage? What features get skipped? What moments spark “Whoa, this helps”?
6. Prioritize Retention Over Vanity
CJ replied to support tickets personally. He earned loyalty.
→ I’ll bake in feedback prompts and send monthly check-ins tied to usage habits.
🧠 What I’m Taking With Me (And You Should Too)
CJ didn’t have funding or a team.
He had focus, feedback, and follow-through.
The takeaway?
Don’t wait to be ready. Be real. Be consistent.
That’s the energy I’m channeling as I start sharing my assistant project in public.
And that’s the mindset you need — whether you’re building a chatbot, an app, or just testing an idea.
🎯 Your first 10 users will teach you more than 100 strategy blogs.
📺 Watch CJ Zafir’s full story on YouTube →
What are you building?
Drop a comment or DM me:
→ What’s your AI idea?
→ What’s holding you back from sharing it?
→ What would a “build in public” milestone look like this week?