How a Non-Technical Founder Built a $30K/Month AI SaaS in 48 Hours

Core Insight

A non-technical Amazon seller who taught himself to code in 9 months using AI tools built an Amazon FBA copilot in 48 hours — and hit $30,000 MRR within 90 days. No technical co-founder. No ad spend. The secret was combining AI-powered development speed (Cursor, Bolt.new) with a distribution shortcut ("borrowed audience" via equity partnership). This case breaks down exactly how Hasaam Bhatti did it — and how you can replicate the model.

Project Background

Hasaam Bhatti spent 10 years as an Amazon FBA seller in Toronto. He knew the pain of product research firsthand: opening 12 browser tabs, manually copying data into spreadsheets, guessing which keywords to target, and burning thousands on PPC campaigns with no confidence in the outcome.

By mid-2025, Bhatti had attempted and abandoned 12 separate software products. Each one failed for a different reason — wrong market, wrong timing, poor distribution, or building features nobody wanted. He was burning out.

Then he made three critical decisions that changed everything:

1. Stop building for strangers. Instead of trying to attract an audience from zero, he would partner with someone who already had one.
2. Build for a domain he knew intimately. After a decade on Amazon, he understood seller workflows better than any developer could.
3. Use AI coding tools to build faster than a technical team. He had been teaching himself to code for 9 months using Cursor and Bolt.new — not as a hobby, but as a deliberate skill-building path.

The result: Launch Fast, an AI copilot for Amazon sellers that handles product research, keyword analysis, competitor intelligence, and launch planning — all through a Chrome extension and an MCP (Model Context Protocol) integration for Claude.

The initial product was built in a single 48-hour sprint using Cursor. Within 30 days, it hit $10,000 MRR. By Day 90, it reached $21,800 MRR. A few months later: $30,000 MRR — all paying customers, no free tier.

Tool Stack

Total monthly burn: approximately $150 — including API costs. The rest is pure margin.

Revenue Sources

• Revenue 1: Chrome Extension Subscriptions — ~$25,000/mo (83%) The primary revenue driver. Amazon sellers subscribe to the Chrome extension at a monthly rate. No free tier — every user pays from Day 1. Bhatti deliberately avoided the freemium trap that kills so many indie products: "Free users don't pay bills, and they consume just as much support time."

• Revenue 2: MCP Integration Access — ~$4,000/mo (13%) Power users who want to run Launch Fast inside Claude Desktop pay for MCP access. This tier appeals to sellers managing multiple Amazon brands who need batch processing and deeper analysis.

• Revenue 3: Udemy Course Sales — ~$1,000/mo (3%) Bhatti created a "Vibe Coding from Scratch" course on Udemy teaching others how to use Cursor, Bolt, Windsurf, and v0 to build their own products. This doubles as both revenue and top-of-funnel marketing for Launch Fast.

Replicable Steps

Step 1: Pick a Domain You Have Deep Expertise In

Bhatti's biggest advantage was not his coding ability — it was his 10 years of Amazon FBA experience. He knew exactly which workflows were painful, which data sellers needed, and which existing tools charged too much for too little.

Actionable takeaway: Before you write a single line of code, list every painful workflow in your industry. Rank them by (a) frequency — how often do people perform this task, and (b) cost — what do they currently pay to solve it. Build for the intersection of high frequency and high cost.

Bhatti's insight: "Most Amazon sellers still do research like it's 2019. Open 12 tabs. Copy data into sheets. Guess what to test. Burn budget on PPC." This is not a technical insight — it's a domain insight that no engineer fresh to the space would have.

Step 2: Learn AI-Assisted Development Before You Build

Bhatti spent 9 months learning to code with AI tools before building Launch Fast. He didn't wait until he was "ready" — he learned by building. His Udemy course now documents the exact path: start with Bolt.new for visual understanding, graduate to Cursor for real development, use Windsurf for agentic tasks, and v0 for UI components.

The skill stack for non-technical founders in 2026:

• Prompt engineering for code generation
• Debugging AI-generated code (reading error messages, not writing from scratch)
• Understanding the file structure of a web app
• Deploying to production (Vercel, Chrome Web Store, etc.)

You don't need to understand algorithms or data structures. You need to understand enough to prompt effectively and debug when the AI gets stuck.

Step 3: Build the MVP in Under 72 Hours

Bhatti's 48-hour sprint was deliberate — not reckless. He followed a strict scope discipline:

• Hour 1-4: Write the entire product spec as a prompt. Every feature, every workflow, every edge case.
• Hour 5-12: Use Bolt.new to generate the UI and basic frontend scaffolding.
• Hour 13-36: Move to Cursor for backend logic, API integrations, and the Chrome extension manifest.
• Hour 37-48: Testing with real Amazon product pages, fixing bugs, and preparing for Chrome Web Store submission.

The key constraint: no new features during the sprint. Every "wouldn't it be cool if" idea went into a backlog document. The 48-hour window forced brutal prioritization.

Step 4: Borrow Distribution Instead of Building It

This is the step most indie hackers skip — and the one that made Launch Fast explode.

Instead of posting on Product Hunt and hoping for traction, Bhatti approached Legacy X, an established Amazon FBA coaching company with a large built-in audience of sellers. He gave them equity in Launch Fast in exchange for distribution.

The math: Legacy X had thousands of Amazon sellers in their ecosystem who already trusted their recommendations. One email blast to their list generated more signups than 6 months of organic content marketing would have. The equity Bhatti gave up was small compared to the revenue the partnership unlocked.

How to replicate this:

1. Identify 5-10 companies/influencers in your target niche with established audiences
2. Build a specific value proposition for their audience (not a generic tool)
3. Offer a revenue share or equity deal that makes the partnership a no-brainer
4. Co-brand the product if necessary — Launch Fast lives at launchfastlegacyx.com, explicitly tying it to Legacy X

Step 5: Ship MCP Integration as a Competitive Moat

In 2026, MCP (Model Context Protocol) is becoming the standard for connecting AI assistants to real-world tools. Bhatti shipped an MCP server that lets Amazon sellers run product research, keyword analysis, and competitor tracking directly inside Claude.

This matters for two reasons:

1. Differentiation: Most Amazon seller tools are standalone web apps. Launch Fast MCP integrates directly into the AI tools power sellers already use.
2. Higher pricing: MCP access justifies a higher pricing tier because it enables power-user workflows that a Chrome extension alone can't match.

Actionable takeaway: If your tool processes data or automates workflows, shipping an MCP server is one of the lowest-effort, highest-ROI features you can add in 2026. The protocol is open, the documentation is solid, and the competitive landscape is still thin.

Step 6: Kill the Free Tier

Bhatti's most controversial but effective decision: Launch Fast has no free tier. Every user pays from Day 1.

His reasoning:

• Free users generate the same support burden as paying users
• A credit card gate filters out tire-kickers
• Revenue from Day 1 forces you to build something people actually value
• You can't optimize conversion funnels if you don't have a conversion event

For founders worried about slow initial growth: the Legacy X partnership solved the top-of-funnel problem. Without that distribution, a paid-only launch would have been much harder. If you're not borrowing an audience, consider a time-limited free trial (7-14 days) rather than a permanent free tier.

Results Timeline

Risks & Pitfalls

• Pitfall 1: The 12-Failure Curse Before Launch Fast, Bhatti built and abandoned 12 products. Most founders quit after 2 or 3. The lesson is not "build 12 things" — it's "learn from each one and accumulate domain-specific insights." Each failure taught Bhatti something about distribution, pricing, or market fit that made Launch Fast possible.

• Pitfall 2: Equity Partnership Risk Giving away equity for distribution works brilliantly when the partner delivers. When they don't, you've diluted yourself for nothing. Bhatti mitigated this by (a) vetting Legacy X's actual audience engagement before signing, and (b) structuring the deal so equity vested over time tied to performance milestones.

• Pitfall 3: AI-Generated Code Debt Building a production SaaS with AI-generated code in 48 hours means the codebase is not clean. Bhatti has been transparent about technical debt. As Launch Fast scaled past $20k MRR, he had to refactor significant portions. Budget for a "pay down the AI debt" phase once revenue validates the product.

• Pitfall 4: Single-Platform Dependency Launch Fast's primary distribution is the Chrome Web Store + one partner's audience. If Chrome changes extension policies (as it has done multiple times) or the Legacy X partnership ends, the business takes a major hit. Diversify distribution channels as early as revenue allows.

• Pitfall 5: AI Coding Skill Inflation In early 2025, being a "non-technical founder who ships with Cursor" was a competitive advantage. By mid-2026, it's the baseline. The window for "first-mover advantage via AI tools" is closing. The enduring advantage is domain expertise — Bhatti's decade of Amazon knowledge, not his Cursor proficiency.

📖 Related Cases

• How a Solo Founder Built a $6,000/Month Chrome Extension in 30 Days with Cursor AI
• From Zero to $10K MRR: The Indie Hacker's AI Tool Stack for 2026
• How to Build and Monetize an MCP Server: The 2026 Developer's Guide

Sources: Indie Hackers interview (June 2, 2026), Hasaam Bhatti's LinkedIn posts, weekly-opportunities.com founder profile, startupseries.io case study, Launch Fast official changelog and documentation.