Kenil Vaghasiya

Process guide

Building a new SaaS product? My MVP-first process in 6 stages

Scholar World web app landing page shown on a desktop monitor

The safest way to build a new SaaS product is to build less of it first. I use an Agile, MVP-first approach: build the product in small stages, put it in front of real users, and improve it using their feedback. Here are the six stages.

What "MVP-first" means

An MVP, or minimum viable product, is the smallest version of your product that solves the main problem for real users. It is not a prototype and it is not a half-finished product. It does one thing properly. Starting there means you spend less before you learn whether people want it, and what you learn decides what gets built next.

StageWhat happensWhat you get
1. DiscoveryUnderstand the problem, the users and the business goalsA clear problem statement and target user
2. PlanningDefine core features, architecture and milestonesA feature list, a technical plan and a timeline
3. UI/UX designCreate wireframes and interactive prototypesA clickable prototype to test and approve
4. DevelopmentBuild the MVP in short, focused sprintsWorking software at the end of each sprint
5. TestingCheck functionality, usability, security and performanceA release that is ready for real users
6. LaunchDeploy, monitor and collect real user feedbackA live product and a list of what to improve

1. Discovery

We start with the problem, not the feature list. Who has this problem, how do they deal with it today, and what does the business need the product to achieve? If the answers are vague, this is the cheapest place to find out.

2. Planning

Here the idea becomes a plan: the core features for the first release, the architecture, and milestones. The most useful thing this stage produces is a list of what is not in the MVP. Every feature moved to "later" brings the launch closer.

3. UI/UX design

I create wireframes first, then interactive prototypes you can click through. You can show these to potential users and investors before development starts. Changing a screen at this stage takes minutes. Changing it after it is built takes much longer.

4. Development

The MVP is built in short, focused sprints. Each sprint ends with something you can open and use, so progress is visible and feedback is regular. My usual stack for SaaS work is Next.js on the front end, .NET or Node.js for the back end, and a managed database and authentication service such as Supabase, which removes weeks of setup from a first release.

5. Testing

Before release I check four things: that every feature works, that people can use it without help, that accounts and data are secure, and that it stays fast under load. Problems found here cost far less than problems found by your first customers.

6. Launch, then improvement

Launch means deploying the product, monitoring it and collecting feedback from real users. That feedback starts the next cycle: refine the features people use, fix what confuses them and grow the product in the direction the data points. The MVP is the first release, not the last one.

Common questions

What should be in a SaaS MVP?

Sign-up and login, the one core feature that solves the main problem, and a way to hear from users. Payments belong in the MVP only if charging is part of what you need to test. Most other things can wait.

Do I need a finished design before development starts?

No. You need agreed wireframes and a prototype for the core flow. The visual polish can be refined sprint by sprint.

Can you handle both design and development?

Yes. I cover UI/UX design, front end, back end, deployment and launch, so you do not have to coordinate separate freelancers.

From zero to hero, concept to launch

If you are planning a new SaaS product and want it designed and built this way, tell me about the idea and I will reply with how I would approach the first release.

Kenil Vaghasiya

About the author. Kenil Vaghasiya is a freelance full stack web developer, Framer developer and designer with 5+ years of experience building web applications with React, Next.js, Node.js, .NET and Azure. He works remotely from Surat, India. More about me · Services

More work