What Can You Build in an MVP Fixed at $3,460? What Fits in v1, and When Your Idea Needs a Custom Quote

What's included in the standard v1

This list comes straight from our MVP Development page. Founders often assume a few of these items cost extra. They don't. Delivery takes about 20 days, and you see progress every week. Here is each item and what it means for you:

• Core product features scoped for v1 launch. What it means for you: the one job your users come for, built properly.
• iOS, Android and responsive web. What it means for you: your users reach you on any device.
• Modern stack (Next.js, React Native, Supabase, etc.). What it means for you: tools any developer can pick up later.
• User authentication and onboarding. What it means for you: real accounts from the first user.
• Stripe / payment integration. What it means for you: you can charge from launch day.
• Database and API setup. What it means for you: your data is stored and ready to build on.
• Mobile-first UI design. What it means for you: design is included, no separate designer needed.
• App Store and Google Play submission support. What it means for you: you get help getting into the stores.
• Full code ownership transferred to you. What it means for you: 100% of the code is yours, on your GitHub.
• Post-launch handoff documentation. What it means for you: another team can take over without starting again.
• 2 weeks of post-launch bug-fix support. What it means for you: bugs real users find get fixed.

What "core product features" really covers

"Core product features" is the line that decides most quotes, so it's worth being precise about it. Core means the features one type of user needs to get the main result your app promises. A good way to check this is to write your app as one sentence: a user does X and gets Y. Here are three scope examples. They show how the test works. They aren't past client projects or quotes. If your sentence needs "and also" more than once, you're probably describing two products. Pick the one that brings in your first users.

• Habit tracker. A user picks a habit, checks it off each day and sees their streak. One user type, one loop, a paid plan through Stripe. This is the kind of scope the standard v1 is built for.
• Booking app for a single studio. A client picks a class, pays and gets a confirmation. The studio owner handles the schedule by hand at first. This usually fits too.
• Two-sided marketplace for tutors. Students search, tutors set prices, the platform takes a cut and pays tutors out. That's two user types plus payouts, and marketplaces are on the custom quote list.

A quick self-test before your call

Go through your feature list and ask four questions about each item. Anything that fails question 1 or 2 can wait. Anything that hits question 3 or 4 is a sign you're moving towards a custom quote. Features you put on the "later" list don't disappear. You add them once real users tell you which ones matter. Our feature cost guides explain how individual features change the size of a build, and the app feature cost estimator lets you check your own list.

• 1. Does a first user need this to get the main result?
• 2. Is it for your users, or for your internal team?
• 3. Does it serve a second type of user?
• 4. Is it on the custom quote list below?

When your idea needs a custom quote

Our MVP Development page names five kinds of work that go beyond the standard package. These aren't bad ideas for an MVP. Many strong products are marketplaces or AI tools. They just involve more work than a single core journey, so they get scoped separately. Here's what each one means and why it adds scope:

• Marketplaces. Why it adds scope: two or more user types, each with their own flows, plus the logic that connects them.
• AI features. Why it adds scope: model calls, prompts, edge cases and testing on unpredictable outputs.
• HIPAA / fintech compliance. Why it adds scope: rules about how data is stored, accessed and logged.
• Admin dashboards. Why it adds scope: a second interface built for your team, not your users.
• Multi-tenant SaaS. Why it adds scope: several organisations on one product, with their data kept separate.

What happens next

For work like this, the MVP Development page says we'll send a fixed quote or a phased roadmap. That way you know what you're buying before any build starts. A phased roadmap can help when the full idea is large. You launch one part first, learn from real users, and then build the next part.

Signs you might fit the standard v1 after all

Some founders think they need a custom quote when they don't. Not sure where your idea lands? Book a call and bring your list. You'll leave knowing whether it's the standard package or a custom quote. Watch for these:

• "We need an admin panel." Ask yourself if you need a full dashboard on day one. Sometimes viewing data in the database console is enough at the start. On the call we'll tell you which way your case goes.
• "Our app uses AI." If AI is the core of the product, that's custom quote work. If it's a nice extra, think about leaving it for later and launching the core journey first.
• "We have two kinds of users." If one side can be handled by hand for the first weeks, your v1 might only need to serve the other side.

How the build runs

Our services page breaks the process into four steps. You won't pay discovery fees, and the code goes on your GitHub. To see the kinds of apps we've delivered, browse our projects.

• 1. Free Call. 30 minutes on your idea, your users and your deadline.
• 2. Fixed Quote. A written scope before any code is written. If it fits the standard package, the price is Fixed at $3,460.
• 3. Build Sprint. About 20 days, with progress shown every week.
• 4. You Ship. Launch on the web and app store submission support, followed by 2 weeks of bug fixes.

How to prepare for the scoping call

Bring these three things and the 30 minutes will go much further. If you've already built a prototype with an AI tool, bring that too. It shows us what you have in mind faster than a written spec does. We also offer AI prototype to production as a separate service.

• Your one sentence. A user does X and gets Y.
• Your feature list, in priority order. Even a rough note on your phone is fine.
• Your deadline and why it exists. A launch date, a demo or a pilot customer can each change what goes into v1.

What can I build for $3,460?

One core product on iOS, Android and responsive web. It comes with user authentication and onboarding, Stripe payments, database and API setup, mobile-first UI design, App Store and Google Play submission support, full code ownership and 2 weeks of post-launch bug-fix support.

How long does it take to build an MVP with BuildMVPFast?

About 20 days, and you see progress every week.

What doesn't fit the standard MVP package?

Marketplaces, AI features, HIPAA or fintech compliance, admin dashboards and multi-tenant SaaS. These go to a custom quote, and for those our MVP Development page says we'll send a fixed quote or a phased roadmap.

Is design included in the price?

Yes. Mobile-first UI design is part of the standard package, so you don't need to hire a separate designer.

Do I own the code?

Yes. 100% of the code is yours, on your GitHub, along with handoff documentation so any developer can keep building. Want to know what your v1 looks like? Book a call. It's free, it takes 30 minutes, and you'll leave knowing exactly what fits in your build.