The workflow I wish I had when I started building MVPs I use this...

@PrajwalTomar_
Prajwal Tomar@PrajwalTomar_
64 views Jun 25, 2025 ~3 min read
Advertisement
1
The workflow I wish I had when I started building MVPs

I use this to plan, design, build, and ship full MVPs in 2-3 weeks.

After 18 builds, here’s the exact system that works.

Bookmark this ↓
2
1/ Plan with ChatGPT or Gemini

Before diving into the code, fully grasp the idea.

This phase is about achieving clarity. By its end, you should understand every aspect of the idea: the tech stack, core features, target audience, EVERYTHING.

Use ChatGPT or Gemini to create these docs:
- PRD/ MVP Plan
- UI Development Plan
- Database Design
- Implementation Plan
- Launch Checklist (you can generate this later, but use the same conversation)

Spend time here; it saves you from chaos later.
3
2/ Design with @uxpilotai

Once the plan is ready, I go to UX Pilot.

Use your UI development plan for building out all the screens.

Why I use it:
- Faster than dragging UI blocks manually
- Prompt to UI in minutes
- Gives clients something visual in hours, not days

It’s like an AI-powered product designer.

Once happy, take the screens one by one into lovable and build out the entire UI in a day.
4
3/ Build the UI with @lovable

Lovable helps me ship 70–80% of the frontend visually, without touching code.

It lets me:
- Generate the entire UI with auth, forms, routing
- Connect real data and backend logic using Supabase
- Preview instantly on mobile and web

By Week 1, the product already works.
5
4/ Refine with Cursor, CodeRabbit, and Taskmaster

Once the MPV is 70-80% done, I move to the Cursor.

In @cursor_ai, I handle everything:
- Add complex backend logic and API calls
- Auto-refactor files with context
- Review every commit with @coderabbitai to catch bugs, bad practices, and security issues
- Make the MVP launch ready by looking for security issues, performance bottlenecks, etc using the launch checklist.

This trio functions like a dev, tech lead, and PM, on command.
6
5/ Use MCP to automate database changes

With Cursor + Supabase + MCP, you can:
•Apply schema changes without SQL
•Sync code with your DB live
•Auto-generate migrations

It’s like Git, but for your database models.
7
6/ @supabase is my backend of choice

It gives me:
•Auth (magic links, OAuth)
•Postgres with RLS
•File storage and edge functions
•Instant scaling, no ops

All my production MVPs run on it.
8
7/ Secure it before you launch

Here’s my baseline pre-launch checklist:
- Enable RLS on all tables
- Add rate limits using Vercel middleware
- Implement CAPTCHA for login/signup
- Store secrets in the .env file
- Validate all inputs server-side
- And more...

Fast doesn’t mean insecure.
9
8/ Deploy with @vercel in minutes

Push to GitHub, and Vercel takes care of the rest:
•Instant global deploys
•Serverless backend support
•Previews for every PR

Your product is live before most teams finish designing.
10
9/ Final takeaway

You don’t need more hours.
You need better structure.

Here’s mine:
•ChatGPT = Planning
•UX Pilot + Lovable = Design + Build
•Cursor + CodeRabbit + Taskmaster = Refine + Review
•Supabase + Vercel = Backend + Deploy

This is Vibe Coding.

If this helped, bookmark it.
11
Want to have your own MVP built in just 2 weeks? Book a call, and we will help turn your idea into reality 👇🏻

creme.digital/prajwal
12
I hope you've found this thread helpful.

If you have any questions, please feel free to ask below. :)

Like/Repost the quote below if you can:
@PrajwalTomar_
Prajwal Tomar@PrajwalTomar_
The workflow I wish I had when I started building MVPs

I use this to plan, design, build, and ship full MVPs in 2-3 weeks.

After 18 builds, here’s the exact system that works.

Bookmark this ↓
Actions
What You Can Do
  • Export as PDF or Markdown
  • Batch Export to Notion
  • Bookmark & Highlight
  • LinkedIn & Instagram Carousel Maker
Create Free Account

Includes 7-day Premium trial

Advertisement