# MVP Sprint

> A production-grade first version of your product, at a fixed price and on dates fixed after the scoping week.

- Page: https://deependra.in/services/build/mvp-sprint
- Type: Service, part of Product engineering
- Last updated: 2026-11-02
- Line page: [Product engineering (Build)](https://deependra.in/services/build)
- Author: [Deependra Vishwakarma](https://deependra.in/about), senior software engineer in Mumbai

## In short

MVP development is building the smallest version of a product that a first customer can use; the MVP Sprint does it at a fixed price, on a base you won't rewrite. It is for funded founders: we agree the scope in week one, then I build and hand over the whole foundation.

## Key facts

- Engagement: fixed-price
- Price: Fixed price, agreed at the end of the scoping week
- Timeline: Set at the end of the scoping week
- First step: **Week 1: scope.** We cut the feature list to what a first customer needs, write it down with acceptance criteria, and fix the price and the dates.
- Build line: A small first step
- Works with: Next.js, Laravel, Node.js, PostgreSQL, Redis, Docker, GitHub Actions, AWS or Google Cloud
- Based in: Mumbai, India · UTC+5:30. I plan my working day around my clients' hours. The overlap with your timezone is shown on the [contact page](https://deependra.in/contact).

## What MVP development means in the MVP Sprint

The MVP Sprint is a fixed-price, fixed-scope build of the first production version of a web product: authentication and roles, the core flows a first customer needs, the database, the API, CI/CD and hosting, handed over documented and deployed in your own accounts. It is for funded founders and companies starting a new product line who want one accountable engineer rather than a loose team.

"Minimum" refers to the feature list, not the foundations. The product does the few things its first customer needs, and does them on a base you won't have to rewrite when the second and third customers arrive.

## Who it is for, and who it is not

### Who this is for

- Funded founders with a validated idea and a clear first customer
- Companies launching a new product line who want one accountable engineer rather than a loose team
- Non-technical founders who need the foundation done right, with a handover their future team can build on

### Who this is not for

- Landing pages or brochure sites
- Native iOS or Android apps (I build web apps and the APIs mobile apps use)
- Ideas still looking for a first customer: an architecture review is the better first step

## What you get

1. A deployed web application with the agreed core flows
2. Authentication, roles and permissions (RBAC)
3. A database schema designed for the next stage of growth, not just the demo
4. CI/CD pipeline with staging and production environments
5. API documentation for future mobile apps or partner integrations
6. A handover session and written runbook, with the repository and IP assigned to you

## What an MVP should include, and what it should skip

The scoping week decides the scope, and it is written down with acceptance criteria before the build starts. A typical first version includes sign-up and sign-in, roles and permissions, the two or three flows that deliver the product's value, an admin view for your team, transactional email, and the API that a future mobile app or partner would use. Payments are included when the first customer pays inside the product.

Anything that doesn't serve the first customer moves to a written next-phase list. That list is part of the handover, so nothing is lost; it just isn't built yet.

How long all of this takes depends on the scope you choose, not on a typical figure. The method, and the time-boxes that established product methods publish, are in [How long a SaaS MVP takes](https://deependra.in/writing/how-long-a-saas-mvp-takes).

## What gets built underneath

The parts users never see get the same attention as the screens. The database schema is designed for the next stage of growth, with migrations in version control. Every change runs through automated tests and a CI/CD pipeline into a staging environment first. Production has monitoring and alerts from the first deploy. Secrets live in the cloud provider's secret store, not the repository. The runbook explains how to deploy, roll back, restore a backup and add a developer, in plain steps.

## What it is not

It is not a landing page, a brochure site or a clickable prototype, and it is not a native iOS or Android app: I build web apps and the APIs mobile apps use. It is also not a way to find out whether anyone wants the product. If you don't have a first customer in sight yet, an [architecture review](https://deependra.in/services/lead/architecture-review) or a conversation about what to test first will save you money. If what you need is a larger custom platform rather than a first version, [SaaS development and web platforms](https://deependra.in/services/build/web-platforms) is the better fit.

## How the engagement runs

1. **Week 1: scope.** We cut the feature list to what a first customer needs, write it down with acceptance criteria, and fix the price and the dates.
2. **Build.** Weekly demos on a staging URL. You see progress every week and can change priorities within the agreed scope.
3. **Launch and handover.** Production deploy, monitoring and alerts, a runbook, and a handover session with you or your first engineering hire.

## Technologies I use for this

Next.js, Laravel, Node.js, PostgreSQL, Redis, Docker, GitHub Actions, AWS or Google Cloud

## How this works in your market

### How this works in the United States

For founders in [the United States](https://deependra.in/markets/united-states), the weekly demo sits in your morning, which is my evening, and the rest of the week runs on a written update you can read on your schedule. I work under your master services agreement and statements of work, the repository lives in your GitHub organization from the first day, and intellectual property is assigned to you on payment.

[United States page](https://deependra.in/markets/united-states)

### How this works in South Korea

For teams in [South Korea](https://deependra.in/markets/south-korea) building for the US or Europe, the scoping week also lists what those markets expect from a first release: consent and opt-out handling, data deletion that really deletes, and accessible forms. Designing for them in the first pass costs far less than retrofitting. Korea is three and a half hours ahead of me, so your afternoon is my morning and demos are easy to schedule.

[South Korea page](https://deependra.in/markets/south-korea)

## Case studies behind this service

- [Exhibit Social](https://deependra.in/work/exhibit-social-platform): B2B SaaS platform. 10,000+ influencers indexed.
- [Vayudoot Aviations](https://deependra.in/work/vayudoot-aviations-platform): Education platform.

## Questions about MVP Sprint

### How is this different from hiring a freelancer by the hour?

You get a fixed scope, a fixed price and the foundations a product needs from the first day: CI/CD, environments, monitoring and documentation. You're paying for an outcome, not hours.

### What happens after the MVP launches?

You own the code. We can continue on a monthly retainer, or I can help you hire and hand over to your own team.

### How long does the sprint take?

The dates are fixed at the end of the scoping week, once the scope is written down, and they don't move unless you change the scope. The scoping week exists to make the dates realistic: anything that doesn't serve the first customer moves to the next phase, in writing.

### Do you do the design?

I implement interfaces to a high standard and work well with designers. If you don't have one, I build from a well-chosen component system, or we bring in a designer for the key screens.

### What if we need to change something mid-build?

Priorities can change inside the agreed scope at any weekly demo. A change that adds scope is written down with its effect on price and dates before it's built, so there are no surprises at the end.

### Which stack will you use for the MVP?

Usually Next.js with a Laravel or Node.js API, PostgreSQL and Redis, on AWS or Google Cloud. If your future team already knows a stack, we choose that one.

### Can investors or a future CTO review the code?

Yes. The repository, the architecture notes and the runbook are written to be read by someone who wasn't there.

### How much does MVP development cost?

The price follows the scope, not the calendar. What moves it is how many distinct flows a first customer needs, how many kinds of user and permission levels there are, what the product must connect to, such as payments, an existing system or a partner's API, and how much design is already decided. That is why the price is fixed only at the end of the scoping week, once the scope is written down, and it changes only if you change the scope. [How long a SaaS MVP takes](https://deependra.in/writing/how-long-a-saas-mvp-takes) covers the same variables for time.

### What should an MVP include, and what should it skip?

It should include what a first customer needs to get the value: sign-up and sign-in, roles and permissions, the two or three flows that deliver the product's value, and the foundations underneath, such as a sound data model, tests and a deploy pipeline. It should skip everything else for now, and the scoping week is where each feature is marked yes or no. What is skipped goes on a written next-phase list that is part of the handover, so nothing is lost, only sequenced.

## Related services

- [Architecture review and due diligence](https://deependra.in/services/lead/architecture-review) (Technical review): An independent, written view of a system: what's solid, what's risky, and what it will cost to fix.
- [SaaS development and web platforms](https://deependra.in/services/build/web-platforms) (Product engineering): Custom web applications, APIs and integrations, built to be inherited.

## Sources

1. [The Lean Startup: principles (minimum viable product)](https://theleanstartup.com/principles)

## Related writing

- [How long a SaaS MVP takes: the method, not a number](https://deependra.in/writing/how-long-a-saas-mvp-takes) (10 October 2026): Why any single number for an MVP is a guess, what actually decides the time, the published time-boxes product teams use, and how to fix dates you can keep.
- [Working with an engineer in India: hours, contracts and data transfers](https://deependra.in/writing/working-with-an-engineer-in-india) (2 November 2026): What a US, UK, European, Gulf or East Asian team should sort out before working with an independent engineer in India: the shared hours, the contract, and how personal data may move.

## Where this work happens

- [United States](https://deependra.in/markets/united-states) (New York, Chicago, San Francisco): A senior software engineer for US startups and product teams, working remotely from Mumbai so that the East Coast morning falls inside my evening. It is for founders and CTOs who need senior engineering without a full-time hire: MVPs, AI features, performance work and rescuing apps built in a hurry.
- [South Korea](https://deependra.in/markets/south-korea) (Seoul): A software engineer for Korean teams, working remotely from Mumbai with my morning in your afternoon. It is for startups and scale-ups going global that need AI and product engineering at speed, built to meet US and European privacy expectations from the first release.

## Teams that start here

- [New York, US](https://deependra.in/markets/united-states/new-york)
- [San Francisco, US](https://deependra.in/markets/united-states/san-francisco)
- [Austin, US](https://deependra.in/markets/united-states/austin)
- [Denver, US](https://deependra.in/markets/united-states/denver)
- [Berlin, EU](https://deependra.in/markets/europe/berlin)
- [Paris, EU](https://deependra.in/markets/europe/paris)
- [Madrid, EU](https://deependra.in/markets/europe/madrid)
- [Dubai, UAE](https://deependra.in/markets/uae/dubai)

## Start

Book a scoping call for the MVP Sprint: https://deependra.in/contact

---

Cite as: Deependra Vishwakarma, "MVP Sprint", https://deependra.in/services/build/mvp-sprint (last updated 2026-11-02).

This is the Markdown version of https://deependra.in/services/build/mvp-sprint; the page is the canonical source. Start a project: https://deependra.in/contact