I built 18+ MVPs, scaled my agency to $20K/month, and got acquired....
Prajwal Tomar@PrajwalTomar_
51 views
Jun 07, 2025
~4 min read
Advertisement
1
I built 18+ MVPs, scaled my agency to $20K/month, and got acquired.
This is the exact AI dev workflow that made it happen ↓
This is the exact AI dev workflow that made it happen ↓
2
1/ The Problem With Traditional Agencies
Traditional dev agencies:
- Spend weeks on UI/UX before writing a single line of code
- Operate with large teams, slowing down decision-making
- Have high costs before validating an idea
The modern dev agency:
- Skips lengthy design phases and builds while iterating
- Uses small, efficient teams powered by AI
- Optimizes costs so founders can validate first
- Launches MVPs in under 4 weeks
I started @ignytlabs as a solo founder and delivered my first 6–7 MVPs alone.
Only after proving the model did I bring in other developers without bloated processes.
Traditional dev agencies:
- Spend weeks on UI/UX before writing a single line of code
- Operate with large teams, slowing down decision-making
- Have high costs before validating an idea
The modern dev agency:
- Skips lengthy design phases and builds while iterating
- Uses small, efficient teams powered by AI
- Optimizes costs so founders can validate first
- Launches MVPs in under 4 weeks
I started @ignytlabs as a solo founder and delivered my first 6–7 MVPs alone.
Only after proving the model did I bring in other developers without bloated processes.
3
2/ AI-Powered Planning to Reduce Scope Creep
Before writing a single line of code, we define:
- What the product does
- Who it is for
- What problem it solves
We use:
- ChatGPT for quick brainstorming
- @CodeGuideDev to generate PRDs & technical documentation
- The MoSCoW Method to prioritize essential features
Every project starts with:
- A clear PRD
- A step-by-step implementation plan
- A flexible UI structure
This prevents scope creep and ensures we build what’s needed first.
Before writing a single line of code, we define:
- What the product does
- Who it is for
- What problem it solves
We use:
- ChatGPT for quick brainstorming
- @CodeGuideDev to generate PRDs & technical documentation
- The MoSCoW Method to prioritize essential features
Every project starts with:
- A clear PRD
- A step-by-step implementation plan
- A flexible UI structure
This prevents scope creep and ensures we build what’s needed first.
4
3/ No Full Design Phase - Straight to Lovable
Instead of wasting weeks on Figma, we go straight to Lovable to build UI screens.
By week one, clients already see a real, functional UI instead of static wireframes.
They provide feedback, we refine, and finalize the UI while we build by week 2.
This approach:
- Saves weeks of unnecessary design work
- Reduces back-and-forth
- Ensures the MVP looks professional without delays
Instead of wasting weeks on Figma, we go straight to Lovable to build UI screens.
By week one, clients already see a real, functional UI instead of static wireframes.
They provide feedback, we refine, and finalize the UI while we build by week 2.
This approach:
- Saves weeks of unnecessary design work
- Reduces back-and-forth
- Ensures the MVP looks professional without delays
5
4/ Mini Design Phase (If Requested)
Sometimes, if the client specifically asks for it, we do a short design phase.
We use:
- UX Pilot to generate flows
- Figma to polish specific screens
We try to avoid this step, but when needed, we adapt.
It’s fast, focused, and never slows down the build timeline.
Sometimes, if the client specifically asks for it, we do a short design phase.
We use:
- UX Pilot to generate flows
- Figma to polish specific screens
We try to avoid this step, but when needed, we adapt.
It’s fast, focused, and never slows down the build timeline.
6
5/ Build 70–80% of the MVP in Lovable
This is the key to moving fast.
@lovable is not just for UI, it helps us build real app logic:
- Connect frontend components to real data
- Implement authentication
- Set up API calls and user interactions
- Build a functional MVP with minimal manual coding
By the time we leave Lovable, most of the MVP is already working.
The remaining 20–30% is handled in Cursor.
This is the key to moving fast.
@lovable is not just for UI, it helps us build real app logic:
- Connect frontend components to real data
- Implement authentication
- Set up API calls and user interactions
- Build a functional MVP with minimal manual coding
By the time we leave Lovable, most of the MVP is already working.
The remaining 20–30% is handled in Cursor.
7
6/ GitHub Sync Between Lovable and Cursor
Lovable syncs everything to GitHub, making it easy to continue development in Cursor.
With this setup:
- UI and basic functionality are already done
- Developers can pick up exactly where Lovable left off
- No need to rewrite components from scratch
Keeping everything in sync avoids duplicate work and speeds up iterations.
Lovable syncs everything to GitHub, making it easy to continue development in Cursor.
With this setup:
- UI and basic functionality are already done
- Developers can pick up exactly where Lovable left off
- No need to rewrite components from scratch
Keeping everything in sync avoids duplicate work and speeds up iterations.
8
7/ Advanced Backend Development in Cursor
While Lovable gets us 80% of the way, Cursor is where we refine and scale the backend.
Cursor is great for:
- Implementing advanced features
- Debugging and refining performance
- Making the MVP secure and scalable
- Ensure that the code is clean and not bloated (using @coderabbitai)
Sometimes, manual coding is necessary. This is where Cursor shines.
While Lovable gets us 80% of the way, Cursor is where we refine and scale the backend.
Cursor is great for:
- Implementing advanced features
- Debugging and refining performance
- Making the MVP secure and scalable
- Ensure that the code is clean and not bloated (using @coderabbitai)
Sometimes, manual coding is necessary. This is where Cursor shines.
9
8/ Supabase - A Backend That Scales Without Complexity
Instead of setting up complex backend infrastructure, we use Supabase.
Why?
- Fully managed: No need to maintain database servers
- Real-time updates: Syncs data instantly across the app
- Scalable pricing: Only pay for what you use
Supabase handles:
- Authentication: Email, OAuth, magic links
- Database: PostgreSQL with built-in scaling
- Storage: Secure file and image uploads
- Edge Functions: Serverless backend logic
- Real Time features
This lets us focus on building, not managing servers.
Instead of setting up complex backend infrastructure, we use Supabase.
Why?
- Fully managed: No need to maintain database servers
- Real-time updates: Syncs data instantly across the app
- Scalable pricing: Only pay for what you use
Supabase handles:
- Authentication: Email, OAuth, magic links
- Database: PostgreSQL with built-in scaling
- Storage: Secure file and image uploads
- Edge Functions: Serverless backend logic
- Real Time features
This lets us focus on building, not managing servers.
10
9/ Deployment & Launch Strategy
Once everything is built, we deploy the MVP on Vercel.
Why Vercel?
- No need for complex CI/CD pipelines
- Automatic scaling
- Global edge network for fast load times
By weeks four to five, the MVP is live and ready for testing.
From there, we:
- Gather user feedback
- Fix any bugs
- Plan Phase 2 based on real data
Once everything is built, we deploy the MVP on Vercel.
Why Vercel?
- No need for complex CI/CD pipelines
- Automatic scaling
- Global edge network for fast load times
By weeks four to five, the MVP is live and ready for testing.
From there, we:
- Gather user feedback
- Fix any bugs
- Plan Phase 2 based on real data
11
10/ When to Choose a Lean MVP vs. a Traditional Agency
Enterprise software still needs traditional agencies for:
- Large teams & complex integrations
- Extensive planning & custom design
- Long-term development cycles
We focus on:
- Speed: MVPs in weeks, not months
- Cost-efficiency: Build only what’s essential
- Iteration: Improve based on real user feedback
If you’re a founder looking to launch fast, let’s talk.
Enterprise software still needs traditional agencies for:
- Large teams & complex integrations
- Extensive planning & custom design
- Long-term development cycles
We focus on:
- Speed: MVPs in weeks, not months
- Cost-efficiency: Build only what’s essential
- Iteration: Improve based on real user feedback
If you’re a founder looking to launch fast, let’s talk.
12
11/ The Future of AI-Powered Dev Agencies
The future of lean, AI-driven agencies is clear:
- AI-assisted coding beats bloated teams
- No long design phases, just execution
- MVPs built FAST
- Iteration over perfection
If you’re serious about building an AI-driven dev agency, this is the model that works.
The future of lean, AI-driven agencies is clear:
- AI-assisted coding beats bloated teams
- No long design phases, just execution
- MVPs built FAST
- Iteration over perfection
If you’re serious about building an AI-driven dev agency, this is the model that works.
