# SaaS MVP scope and cost: what to build first > A first SaaS version needs only what lets one type of customer sign up, do the one job your product promises and pay for it. Everything else, such as team roles, reports and integrations, can wait. Scope is the biggest lever on cost, so decide it before you ask for quotes. Canonical: https://erdibuilds.app/guides/saas-mvp-scope-and-cost Last updated: 2026-11-06 (November 6, 2026) SaaS means software that people use in the browser and pay for on a subscription. Many founders start with a long feature list because every item feels important. The cost of a first version grows with each one, and so does the time before you learn anything from real users. ## The core loop comes first Write your product as one sentence: a [type of user] can [do one valuable thing] without [the old pain]. Anything that does not serve that sentence is a candidate for later. This is the heart of an MVP (Minimum viable product: the smallest version that real users can try). If the term is new, start with [what is an MVP](https://erdibuilds.app/guides/what-is-an-mvp). ## Must have, should have, can wait **Typical split for a first SaaS version** | | Must have now | Often later | | --- | --- | --- | | Accounts | Sign up, login, password reset | Single sign-on, team invitations, fine-grained roles | | Core feature | The one job the product does | Secondary workflows and power-user options | | Billing | One plan, one way to pay | Several plans, coupons, usage-based pricing, invoices | | Data | Safe storage with access rules per user | Exports, advanced search, audit history | | Admin | A simple way for you to see and fix data | Full back office with reports | | Emails | Confirmation and password reset | Newsletters, drip campaigns, in-app notifications | | Integrations | Only the one your core loop depends on | Everything customers ask for later | | Design | Clean, clear and consistent | Custom animation, themes, white-label options | Your own product may move items between columns. The point is to decide on purpose. ## What makes SaaS scope grow quietly - Multiple user roles. Each role means extra screens, rules and tests. - Teams and organizations. Letting several people share one account changes how data is stored and protected. - Subscription billing details. Upgrades, downgrades, failed payments and taxes are each small projects. - Mobile apps. Adding a phone app doubles many decisions. If you need both, see [SaaS plus mobile app](https://erdibuilds.app/build/saas-plus-mobile-app). - Security and privacy. Customer data needs Row Level Security (A database rule that decides which rows each user may see) or an equivalent access design from the start. Adding it late is harder. ## How scope turns into cost Cost is effort multiplied by the developer's rate, plus the extras that come with hosting and services. Cutting scope reduces effort directly. We do not quote prices here because the real number depends on your choices. [How much does it cost to build an app](https://erdibuilds.app/guides/how-much-does-it-cost-to-build-an-app) explains the drivers in detail and how to collect comparable proposals. A practical method is to price the product in layers. Ask for a quote for the core loop alone, then for each extra as its own line. You then see exactly what every addition costs and can decide with facts. ## An example: a booking tool for dog walkers Imagine a founder who wants a SaaS for independent dog walkers. The long list has client profiles, a calendar, group walks, route maps, invoices, reviews, a mobile app and a referral program. The core sentence is: a dog walker can let clients book a slot without any messages back and forth. - Version one: sign up, a weekly availability setting, a booking page clients can open without an account, an email to confirm each booking and one subscription plan for the walker. - Later, once walkers ask for it: invoices, group walks, reviews and the phone app. - Never in version one: the referral program and route maps, which solve problems nobody has proven yet. This is an invented example to show the method. The right split for your product comes from talking to your first users. ## Running costs after launch A SaaS has monthly costs from the first user. Two common services state their starting prices on their own pages, checked on 6 November 2026: [Supabase](https://supabase.com/pricing) lists a Free plan at $0 per month and a Pro plan from $25 per month with a spend cap that is on by default, and [Vercel](https://vercel.com/pricing) lists a Hobby plan at $0 per month for personal and non commercial use and a Pro plan at $20 per month per developer seat. A real product with many users can cost more, so ask your developer to estimate it for your expected volume. ## Typical mistakes - Building billing before anyone has said they would pay. - Adding a second user role before the first one works well. - Copying the feature list of a large competitor. - Leaving data access rules for the end, when they are hardest to add. - Counting a feature as done because it works on the developer's screen. Done means a real user could do the job. ## Plan the build in milestones Split the work so that each part ends with something you can open and test, for example login first, then the core feature, then billing. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Milestones are from 50 to 2,000 each in your project currency. Smaller milestones also make it easier to change direction after early feedback. The [milestone planner](https://erdibuilds.app/tools/milestone-planner) and the guide on [splitting a project into milestones](https://erdibuilds.app/guides/how-to-split-a-project-into-milestones) help you set this up. > Launch with a handful of real users, watch what they do, then spend your next budget on what they actually ask for. ## Frequently asked questions ### What must a SaaS MVP include? Accounts, the single core feature, a simple way to pay and safe data handling. Anything else is optional for a first release. ### Should billing be in the first version? If you want to test whether people will pay, yes, in its simplest form. If you are only testing whether the idea is useful, you can start with a manual invoice and add billing next. ### Should my SaaS start on web or mobile? Web is usually the quicker start because it works on every device without app store review. Add a phone app once you see people need it. ### Can AI tools build my first version? They can speed up a prototype. Before you charge customers, have an experienced developer review security, payments and data handling. See [finish your AI-built app](https://erdibuilds.app/help/finish-your-ai-built-app). ### How do I estimate cost before I hire? Write a brief, list features in priority order and ask for each extra as a separate line. The [project brief tool](https://erdibuilds.app/tools/project-brief) can help you start. ## Related - [Build a SaaS with an independent developer](https://erdibuilds.app/build/saas): Plan a SaaS product: accounts, subscriptions, technologies, an example milestone plan, what to write in the brief and how to pick a developer. - [What Is an MVP? A Plain Guide for Founders](https://erdibuilds.app/guides/what-is-an-mvp): An MVP is the smallest version of a product that real users can try. Learn what it includes, what it leaves out and how to plan one. - [How Much Does It Cost to Build an App?](https://erdibuilds.app/guides/how-much-does-it-cost-to-build-an-app): What drives the cost of an app, SaaS, website or game, and how to turn a rough idea into a real quote you can compare and trust. - [How to Split a Project Into Milestones](https://erdibuilds.app/guides/how-to-split-a-project-into-milestones): Split a software project into milestones that each deliver something you can see and approve. Rules, an example plan and a free planner tool. - [Free milestone planner for your project](https://erdibuilds.app/tools/milestone-planner): Turn your project into an editable plan of milestones with lengths that fit the rules. Runs in your browser, stores nothing and estimates no prices.