From "Just an Idea" to $3,000/Month: How I Built a Profitable AI Business While Working Full-Time (The Unfiltered Truth)
TL;DR: I went from a side project idea to $3,000 monthly recurring revenue in 12 months while working a full-time job in Lagos, Nigeria. This is the complete playbook: what worked, what failed spectacularly, and the exact steps you can copy—no matter where you're building from.
Month 0: The "Stupid" Idea That Wouldn't Go Away
It was 11 PM on a Friday night. I was watching the Premier League, frustrated because my prediction had failed AGAIN.
"There's got to be a pattern here," I thought. "What if I could build an AI to predict these matches better than I do?"
My friends laughed: "Bro, plenty smart people have tried this. You think you'll be different?"
Fair point. But the idea wouldn't leave me alone.
Red flag #1 I ignored (correctly): Everyone said it was overdone.
Red flag #2 I should have paid attention to: I had no clear idea how to monetize it.
But here's the thing about side projects that work—they start as problems YOU deeply understand and want to solve, not market opportunities you've researched.
The Real Question Wasn't "Can I Build This?"
I knew I could build the tech. I'm a machine learning engineer—that's my day job.
The REAL questions were:
- Will anyone actually use this?
- Can I build it while working 9-5?
- Will people pay for sports predictions?
- Can I compete with established players?
Spoiler: I got 3 out of 4 right. Guess which one almost killed the project?
The 12-Month Journey (Month by Month Reality)
Month 1-2: The "Build in Secret" Phase
What I did:
- Spent weekends and evenings coding
- Built the basic ML model (XGBoost ensemble)
- Created simple Flask API
- Tested with historical data
- Got 68% accuracy (not great, but a start)
Hours invested: ~80 hours
Money spent: $0 (used free tools)
What I learned:
- Building the AI was actually the EASY part
- Getting good data was harder than I expected
- 68% accuracy sounds impressive until you realize that's only slightly better than coin flip
Mistake #1: Building in complete isolation. Should have validated with potential users earlier.
Month 3: The "Oh Crap, Now What?" Moment
I had a working model. Now what?
Reality check: A model sitting on my laptop helps nobody and makes $0.
What I did:
- Created ugly landing page with Carrd ($19/year)
- Built simple frontend with React
- Deployed MVP on Heroku free tier
- Shared with 5 friends for feedback
First users: 5 (all friends, all using it for free)
Money spent: $19
Revenue: $0
Key insight: Friends will lie to be nice. I asked:
- "Do you like it?" → They said yes (useless)
- "Would you pay for this?" → Awkward silence (useful!)
- "What would make you actually use this daily?" → Gold. This was the right question.
Mistake #2: Asking the wrong questions. "Would you pay?" is terrible. Better: "Have you ever paid for something similar? How much?"
Month 4: The Pivot (Sort Of)
Based on feedback, I realized my target audience was wrong.
Original idea: Casual fans who bet occasionally
Reality: They don't care enough to pay
Better audience: People who bet regularly and take it seriously
Changes I made:
- Added "confidence scores" to predictions
- Showed historical performance (transparency)
- Added detailed stats for each prediction
- Built subscription model ($10/month)
First paying customer: My cousin (doesn't count but felt amazing)
MRR: $10
Conversion rate: 1 out of 73 free users = 1.4%
What I learned: Transparency builds trust. Showing when we were WRONG actually increased conversions.
Month 5: The "Holy Sh*t" Moment
I posted on Reddit (r/SoccerBetting) for the first time.
What happened:
- 500+ upvotes
- 200+ signups in 24 hours
- 12 paid subscriptions
MRR: $120
What went right:
- Showed REAL results (wins and losses)
- Transparent about methodology
- Gave away valuable free content
- Didn't oversell ("71% accuracy, not 100%!")
What almost went wrong:
- Site crashed from traffic
- Heroku free tier couldn't handle it
- Had to upgrade infrastructure mid-traffic-spike
- Panic deployed fixes at 2 AM
Cost of panic: $48 emergency server upgrade
Worth it? Absolutely.
Lesson: Build for scale-ability from day one, or be ready to scramble.
Month 6-7: The Grind
No viral posts. No sudden growth. Just consistent work.
What I focused on:
- Improving model (68% → 71% accuracy)
- Better UI/UX (reduced dropoff)
- Email marketing (built list)
- Content marketing (started blog)
Growth: Slow and steady
- Month 6: $280 MRR
- Month 7: $450 MRR
What worked:
- Weekly prediction emails (people opened them!)
- Showing past performance prominently
- Referral program (give 1 month, get 1 month free)
What flopped:
- Twitter ads ($200 spent, 1 conversion)
- Instagram influencer ($150, zero conversions)
- Facebook ads (banned—gambling adjacent)
Lesson: Paid ads rarely work for small B2C products. Organic + content marketing > everything.
Month 8: The Make-or-Break Decision
I was at $620 MRR. Growing but slowly. Still working full-time. Exhausted.
The question: Keep going or quit?
What made me continue:
- Users were actually getting value (inbox full of positive feedback)
- Churn was LOW (people were staying subscribed)
- Path to $1k MRR was clear (just more of what was working)
What almost made me quit:
- Weekends and evenings for 8 months
- Slow growth felt demotivating
- Imposter syndrome ("Am I just lucky?")
The turning point: One email from a user:
"Your predictions helped me win $500 last month. The $10 subscription paid for itself 50x over. Thank you."
That was my North Star. As long as I was creating real value, I'd keep going.
Month 9: The Breakthrough
What changed:
- Doubled down on content marketing
- Published case study: "How I Built This"
- Shared numbers transparently (revenue, accuracy, failures)
- Posted consistently on LinkedIn
Results:
- Blog post went semi-viral (20k views)
- 500+ new signups
- $1,180 MRR
The insight: People don't buy products. They buy stories + transformation.
My story wasn't "AI sports predictions." It was "I built this from my bedroom in Lagos while working full-time, and now hundreds of people use it daily."
THAT resonated.
Month 10-11: Scaling (Sort Of)
MRR: $1,180 → $2,400
What I did:
- Kept publishing (blog + LinkedIn)
- Improved product based on feedback
- Added new features (multi-league support)
- Started email course (free) to build trust
What I should have done:
- Raised prices (realized I was underpriced)
- Automated more (still doing too much manually)
- Hired help (tried to do everything myself)
Key lesson: Your first price is probably too low. I should have started at $19/month, not $10.
Month 12: The Goal (Almost)
Current MRR: $3,100
Users: 350+ active subscribers
Churn: ~8% monthly (pretty good for B2C)
Hours/week: 10-15 (down from 20-25)
Profit margin: ~70% (after infrastructure costs)
Takeaway: You don't need to quit your job to build a profitable side business. But you DO need to be smart about time management.
The Real Numbers (No BS)
Revenue Breakdown:
Month 1-3: $0
Month 4: $10
Month 5: $120
Month 6: $280
Month 7: $450
Month 8: $620
Month 9: $1,180
Month 10: $1,900
Month 11: $2,400
Month 12: $3,100
Total Year 1 Revenue: ~$10,960
Costs:
Infrastructure: $240/year
Domain + hosting: $100/year
Tools (analytics, email): $300/year
Marketing experiments (failed): $500
Misc (coffee, tears): Priceless
Total costs: ~$1,140/year
Net profit: ~$9,820
Time Investment:
Months 1-6: ~20 hours/week
Months 7-12: ~12 hours/week
Total: ~900 hours
Effective hourly rate: $10.91/hour (Year 1)
Honest reflection: Year 1 was NOT lucrative per hour. But the trajectory is what matters.
Year 2 Projection:
Current MRR: $3,100
If I maintain growth: $5,000-7,000 MRR by Month 24
Annual revenue: $60,000-84,000
Time investment: ~10 hours/week (more automated)
Effective hourly rate: ~$115-160/hour
NOW it makes sense financially.
What Worked (Do These)
1. Solve a Problem You Deeply Understand
I didn't research "market opportunities." I scratched my own itch.
Why this works:
- You understand the pain intimately
- You know what's missing in existing solutions
- You're passionate enough to push through hard times
How to apply:
- What frustrates you regularly?
- What do you wish existed?
- What would you pay for yourself?
2. Build in Public
I shared everything: wins, losses, revenue, failures.
Results:
- Built trust faster
- Attracted engaged users
- Got valuable feedback
- Created content organically
Where I shared:
- Twitter: Weekly updates
- LinkedIn: Longer posts
- Reddit: Case studies
- Blog: Deep dives
Example post that did well:
"Month 8 update: $620 MRR, still not profitable per hour spent. But churn is 7% and users are happy. Feeling tired but optimistic. Here's what I learned..."
People LOVE transparency.
3. Start with a Tiny Niche
I didn't try to predict ALL sports. Just football (soccer). Just major leagues.
Why this worked:
- Easier to become the "expert"
- Focused my limited time
- Clear target audience
- Better product faster
Anti-pattern: Trying to be everything to everyone.
4. Price Higher Than You Think
My biggest mistake? Starting at $10/month.
Should have been $19 or $29. Here's why:
- Higher price = perceived higher value
- Attracts more serious users
- Reduces support burden (fewer tire-kickers)
- More revenue per customer = more resources to improve product
Lesson: If nobody complains about your price, it's too low.
5. Content Marketing > Paid Ads (For Small Budgets)
Money spent on ads: $500
Result: 1 customer ($10 MRR)
Money spent on content: $0 (just time)
Result: 200+ customers ($2,000+ MRR)
Why content won:
- Builds trust organically
- SEO benefits compound over time
- Shows expertise
- Shareable
Types of content that worked:
- "How I built this" stories
- Transparent revenue numbers
- Prediction results (wins AND losses)
- ML tutorials (technical audience)
- Business lessons (entrepreneurial audience)
6. Consistency Beats Intensity
I didn't have 40-hour weeks to dedicate. I had 10-15 hours max.
What I did:
- Same time blocks every week (Saturday mornings, weekday evenings)
- Small, consistent progress
- Focused on ONE thing per week
Better than:
- Working 40 hours one week, then nothing for 3 weeks
- Burning out
- Quitting
Mantra: "1% better every week > 100% effort once."
What DIDN'T Work (Avoid These)
1. Paid Ads (At This Stage)
Spent: $500
Gained: 1 customer
Why it failed:
- Wrong stage (needed product-market fit first)
- Small budget = hard to test/optimize
- Sports betting = expensive keywords
- Didn't understand targeting well enough
Lesson: Paid ads work when you have PMF and can spend $5k+ to learn.
2. Building Too Many Features Too Fast
Early on, I tried to add everything users requested.
Result:
- Bloated product
- Bugs everywhere
- Distracted from core value
- Confused new users
Better approach:
- Focus on ONE killer feature
- Say "no" to most requests
- Add features slowly, deliberately
- Measure impact of each addition
3. Trying to Do Everything Myself
I designed the logo. Wrote all the copy. Coded everything. Did customer support.
Cost:
- Burn out
- Slow progress
- Mediocre results in areas where I'm not skilled
What I should have done earlier:
- Hired designer on Fiverr ($50 for logo)
- Used Notion AI for better copy
- Outsourced customer support (eventually did this)
- Focused on my zone of genius (ML + strategy)
4. Ignoring Customer Feedback (At First)
First 3 months: built what I thought people wanted.
Result: 1.4% conversion rate.
Next 3 months: built what people told me they wanted.
Result: 12% conversion rate.
Lesson: Talk to users CONSTANTLY. Build what they ask for, not what you assume.
5. Perfectionism
Waited 2 months before showing anyone because "it wasn't ready."
Better approach:
- Ship embarrassingly early
- Get feedback ASAP
- Iterate based on real usage
- Perfect is the enemy of profitable
Mantra: "Done is better than perfect."
The Unfair Advantages (Why It Worked for Me)
Let me be real: I had advantages. Not privilege in the traditional sense, but skills and circumstances that helped:
1. Technical Skills
I'm an ML engineer. Building the prediction model was in my wheelhouse.
If you're non-technical:
- Partner with someone technical
- Use no-code tools
- Outsource development
- Start with simpler ideas
2. Low Cost of Living
Living in Lagos means lower expenses. $3k MRR goes further here than in San Francisco.
Advantage: Could take more risk.
3. Full-Time Job
Sounds counterintuitive, but having steady income meant I could:
- Take my time
- Not stress about money
- Make long-term decisions
- Avoid desperate pivots
Risk: Burnout. Manage it carefully.
4. Existing Audience
I had ~500 LinkedIn followers from sharing technical content.
Made first 50 users easier to find.
If you're starting from zero:
- Build audience in parallel with product
- Post weekly for 6 months before launch
- Engage, don't just broadcast
5. Domain Knowledge
I've watched football (soccer) for 20+ years. I understand the sport deeply.
Why this mattered:
- Built credibility
- Knew what features mattered
- Understood user psychology
- Could create better content
Lesson: Build in domains where you have credibility or deep interest.
The Playbook (Your Step-by-Step Guide)
Want to replicate this? Here's the exact playbook:
Phase 1: Idea Validation (Weeks 1-4)
Week 1: Identify the problem
- What frustrates YOU?
- What would you pay to solve?
- Do others have this problem?
Week 2: Research existing solutions
- What exists already?
- What are the gaps?
- Read reviews (1-star reviews = opportunity)
Week 3: Talk to 10 potential users
- Don't pitch, just listen
- "Tell me about the last time you [had this problem]"
- "What have you tried to solve it?"
- "Would you pay for a solution? How much?"
Week 4: Decide
- Is there enough pain?
- Can you build something better?
- Is the market big enough?
- Go/No-Go decision
Phase 2: MVP (Weeks 5-12)
Goal: Ship ASAP, even if embarrassing.
Week 5-8: Build core feature
- ONE killer feature
- Not perfect, just working
- Minimal UI (use templates)
Week 9-10: Beta test with 5-10 people
- Friends, colleagues, internet strangers
- Watch them use it (don't explain)
- Note where they get confused
Week 11-12: Iterate and launch
- Fix critical issues only
- Ship publicly
- Start collecting emails
Phase 3: Feedback Loop (Months 4-6)
Talk to users CONSTANTLY:
- Weekly feedback calls
- NPS surveys
- Usage analytics
- Support tickets = feature ideas
Iterate every 2 weeks:
- Pick ONE thing to improve
- Ship it
- Measure impact
- Repeat
Metric to track: Retention, not growth
- Are people coming back?
- If yes, focus on growth
- If no, fix retention first
Phase 4: Content Engine (Months 4-12)
Goal: Organic growth through content.
Weekly:
- 1 blog post or long-form post
- 5 social media posts
- 1 email to subscribers
Topics that work:
- Your journey (build in public)
- How you built specific features
- Lessons learned
- Transparent metrics
- User success stories
Distribution:
- Cross-post everywhere
- Engage authentically (not just posting)
- Join relevant communities
- Answer questions generously
Phase 5: Monetization (Month 6+)
When to start charging:
- You have clear value
- Users are engaged
- You can support paying customers
Pricing strategy:
- Start higher than comfortable
- Offer money-back guarantee
- Have 2-3 tiers
- Annual discount (get cash up front)
My tiers:
Free: Basic predictions, ads
$10/month: All predictions, no ads
$19/month: Priority support, advanced stats
$99/year: Best value (saves $91)
Phase 6: Scale (Month 9-12)
Focus areas:
- Reduce churn (improve retention)
- Increase LTV (add features, upsells)
- Automate operations
- Hire for weaknesses
- Raise prices gradually
NOT focus areas (yet):
- Paid ads
- Complex funnels
- Scaling team
- New products
Mantra: "Do things that don't scale until they break, then scale."
The Mental Game (Nobody Talks About This)
The Emotional Rollercoaster
Month 2: "This is amazing! I'm a genius!"
Month 3: "Nobody cares. I'm an idiot."
Month 5: "OMG it's working!"
Month 6: "Growth stalled. It's over."
Month 9: "We're back baby!"
Month 11: "Am I just lucky?"
This is normal. Every founder feels this.
Dealing with Doubt
What helped me:
- Weekly wins journal (writing down 3 wins every week)
- Founder community (other people building)
- Detaching self-worth from metrics
- Celebrating small wins
What didn't help:
- Comparing to others
- Reading TechCrunch success stories
- Obsessing over metrics daily
- Hiding struggles (talk about them!)
The Loneliness
Building solo is lonely. You will:
- Work while friends party
- Sacrifice weekends
- Feel misunderstood
Counter-measures:
- Find a founder community (online is fine)
- Share your journey publicly
- Schedule social time (don't sacrifice everything)
- Remember your "why"
Imposter Syndrome
The voice: "Who are you to charge money? You're not an expert. Someone will call you out."
The reality:
- You know more than 99% of people in your niche
- Your customers don't care about credentials, just results
- Done is better than perfect
My mantra: "I'm 10 steps ahead of my users. That's enough to help them."
Common Questions (Brutally Honest Answers)
"Should I quit my job to do this?"
NO. Not at first.
Quit when:
- ✅ Revenue > 2x your salary
- ✅ 6 months of expenses saved
- ✅ Growth is consistent
- ✅ You're turning down opportunities because of job
Keep your job while:
- ❌ Revenue < your salary
- ❌ Growth is inconsistent
- ❌ You haven't validated product-market fit
Exception: If you have a safety net (savings, spouse's income, etc.)
"How do I find time with a full-time job?"
Real talk: It's hard. But possible.
My schedule:
- Saturday mornings: 4-6 hours (deep work)
- Sunday evenings: 2-3 hours (planning)
- Weekday evenings: 1-2 hours (smaller tasks)
- Commute: 30 min (email, social media)
Total: 10-15 hours/week
What I sacrificed:
- Less TV/Netflix
- Fewer parties
- Less sleep (temporarily—not sustainable)
What I didn't sacrifice:
- Family time
- Health/exercise
- Close friendships
Tip: Timeboxing works. Parkinson's Law: work expands to fill time available. Give yourself less time, you'll be more focused.
"What if someone steals my idea?"
Truth bomb: Ideas are worthless. Execution is everything.
Reality:
- Nobody will execute like you
- Your unfair advantage is YOU
- Speed of iteration > secrecy
Do this anyway:
- Don't sign NDAs (red flag)
- Share openly
- Build in public
- Focus on execution, not protection
"How technical do I need to be?"
For AI/ML products: Pretty technical, or partner with someone who is.
For most products: Not very. No-code tools are incredible now.
My advice:
- Learn enough to be dangerous
- Understand what's possible
- Hire/partner for execution if needed
- Focus on your strengths
"What about competition?"
Good news: Competition validates the market.
Your advantage:
- You're nimbler (they're slower)
- You care more (it's your baby)
- You can niche down further
- You're more transparent/authentic
Don't worry about competition. Worry about solving the problem better.
The Next 12 Months (What I'm Doing Now)
Goals:
Revenue: $3k → $7k MRR
- Raise prices ($10 → $15 base tier)
- Add annual tier ($120/year)
- Reduce churn (8% → 5%)
Product:
- Multi-sport support
- Mobile app (currently web only)
- API for partners
- Improved accuracy (71% → 74%)
Content:
- 2 blog posts per week
- YouTube channel (starting Q2)
- Podcast appearances
- Course on building ML products
Hiring:
- Part-time VA for support
- Designer for UI improvements
- Content writer for blog
Time investment:
- Current: 10-15 hours/week
- Goal: 8-10 hours/week (more automated)
When I'll Quit My Job:
When MRR hits $7k consistently for 6 months + I have 12 months expenses saved.
Not before.
Security > hustle culture BS.
Conclusion: You Can Do This Too
I'm not special. I'm not a genius. I didn't have rich parents or VC funding.
What I had:
- A problem I understood deeply
- Technical skills (but you can outsource this)
- Willingness to work 10-15 extra hours/week
- Persistence through the boring middle
That's it.
If you're thinking "I could never do this," you're wrong.
If you're thinking "This sounds hard," you're right.
If you're thinking "Is it worth it?" — for me, absolutely yes.
Why?
Not because of the money (though that's nice).
Because:
- I built something people use daily
- I'm learning at 10x speed
- I'm in control of my time
- I'm solving problems I care about
- I'm proving to myself I can build things
That's priceless.
Your Turn: Start Today
Don't wait for the perfect idea, perfect timing, or perfect skills.
Start with this:
- This week: Identify one problem you have that others might share
- Next week: Talk to 5 people about that problem
- Week 3: Build the simplest possible solution
- Week 4: Get it in front of users
Then iterate for 12 months and report back.
I'll be here cheering you on.
Let's Connect
Questions? Comment below or DM me. I respond to everyone.
Want the detailed playbook? Join my email list for:
- Weekly lessons on building profitable side projects
- Behind-the-scenes revenue numbers
- Technical guides and templates
Need help with your AI/ML project? Let's talk.
See the product: Try SabiScore