Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Lean MVP to scale to operations: planning a product by business stage with fixed-price milestones

Plan a product in three business stages, lean MVP, scale and operations, and buy each stage as fixed-price milestones only after the previous stage has proven its point. Netbase plans this way: every milestone gets a written outcome and acceptance criteria before work starts, and the contract model changes when the work stops being predictable.

Book a solution review See the SaaS product accelerator

By Huy Nguyen (David), Founder & CEO · Updated · 11 min read

star

This guide is for founders, product owners and business leaders who are about to hire an MVP development company and want a plan that reaches past launch. It sits in our series on choosing a delivery partner and complements our custom software development service, which delivers each stage.

In this guide

Why plan beyond the MVP before you hire anyone?

Most MVP proposals stop at launch day. The scope, the price and the acceptance tests all describe the first release, and nothing says what happens when the first users arrive, when the product needs to grow, or who keeps it running. That gap is where projects get expensive: the next phase is negotiated under time pressure, the architecture was never asked to grow, and nobody owns monitoring.

A lifecycle plan fixes the order of questions. The MVP stage asks whether people use and value the core job. The scale stage asks whether the product can grow without breaking its users or its budget. The operations stage asks whether it can run reliably, be supported and keep improving. Each answer is the entry ticket to the next stage, which is the logic of build, measure, learn applied to the contract, not only to the product.

You do not need to sign all three stages at once. You need a plan that names them, so the MVP is built with the later stages in mind and each later contract starts from evidence instead of hope.

What should each lifecycle stage prove before the next one is signed?

The stage-gate plan below is the core of this guide. Use it to read a proposal or to brief a partner.

  1. Lean MVP

    Do target users complete the core job and come back?

    Milestones that fit a fixed price
    Discovery and scope; clickable prototype; core workflow release; launch hardening
    Acceptance evidence
    Agreed user stories pass in a demo on working software; launch checklist signed
    Exit test before the next stage
    Usage evidence on the core job; a short list of what users asked for next
  2. Scale

    Can the product grow in users, data and features without breaking?

    Milestones that fit a fixed price
    Each new module or integration with its own scope; performance and security work with stated targets
    Acceptance evidence
    Module acceptance tests; measured performance against the agreed targets
    Exit test before the next stage
    Growth plan for the next period; known technical debt listed and priced into the roadmap
  3. Operations

    Can the product run, be supported and improve every month?

    Milestones that fit a fixed price
    Hand-over pack; monitoring and alerting setup; first support period with written service terms
    Acceptance evidence
    Runbooks tested; alerts firing on test incidents; reporting in place
    Exit test before the next stage
    Agreed service objectives met for the period; backlog owned and prioritised

Two rules make the table work. First, a stage's exit test is decided before the stage starts, so neither side can move the goalposts after the fact. Second, the work inside a stage is only fixed-price where it can be specified: a module, an integration, a hardening task. Open-ended discovery of what users want next belongs in a different commercial model.

Fixed price, retainer or KPI-linked terms: which fits each stage?

Option Strength Risk Choose it when
Fixed-price milestones Cost and acceptance agreed up front; the partner carries delivery risk Every unplanned change becomes a change request The milestone can be written as user stories and acceptance tests, typically the MVP build, a defined module or a hardening task
Monthly team retainer Priorities can change weekly without new paperwork The buyer carries more delivery risk and must steer the backlog The scale stage is driven by user feedback that changes faster than a statement of work
KPI-linked terms Part of the reward tied to an agreed business or service metric Hard to set fairly before there is a baseline Operations, once the product has a measured baseline to improve on
Time and materials without milestones Maximum flexibility Weak cost control and unclear acceptance A short spike where nobody can write acceptance criteria yet

The usual pattern is fixed price for the MVP, a mix of fixed-price modules and a retainer in the scale stage, and service terms, possibly KPI-linked, in operations. Our guide on dedicated teams versus fixed price compares the first two models in depth, and engagement models lists the options Netbase offers.

When should you NOT use fixed-price milestones?

Fixed price is the wrong tool in three situations. The idea has not been through discovery, so nobody can write acceptance criteria and any price is a guess with a margin on top. The work is a growth experiment whose next step depends on this week's numbers, which welcomes changing requirements by design. Or the product has not yet proven that anyone uses it, in which case scaling it at any price is premature.

In each case, buy a short discovery or a time-boxed spike first, then return to milestones once the scope can be written down. Our sibling guide on what a consulting company does before code explains how that discovery turns into a fixed-price proposal.

How do you plan the stages, step by step?

  1. Write the core job in one sentence

    Who the user is, what they need done and how you will know they valued it. This becomes the MVP exit test.

  2. Run discovery before the first price

    Users, workflows, integrations and risks, ending in a scope a partner can price. Netbase starts every engagement with discovery and strategic alignment.

  3. Cut the MVP to the smallest release that tests the core job

    A minimum viable product is a learning tool, not a small version of the final product.

  4. Split the MVP into milestones with written acceptance

    Each milestone ends in an increment that meets an agreed definition of done and is demonstrated on working software.

  5. Name the scale stage in the MVP contract

    Not its price, its shape: the architecture choices that must not block growth and the modules likely to follow.

  6. Define operations before launch

    Monitoring, backups, support hours, who answers incidents and which service level objectives the product must meet.

  7. Review at every gate

    Compare the exit test with the evidence, then sign the next stage, change the commercial model or stop.

For SaaS products, our SaaS MVP architecture guide covers the technical decisions behind steps 3 and 5.

Where AI fits

AI changes each stage a little. In delivery, AI-assisted coding, test generation and documentation can speed up a milestone, but engineers review every change before it reaches an acceptance demo. In the product, an AI feature belongs in the MVP only if it is part of the core job; otherwise it is a scale-stage module with its own acceptance criteria, such as answer quality on an agreed test set. In operations, model behaviour drifts, so AI features need monitoring and a review owner after launch. Netbase works with the major commercial and open-source AI tools and models, chosen per project; our guide to AI-native software development explains what changes in scope and review terms.

What delivery record exists, and what does not?

  • What exists. Most Netbase projects are delivered on fixed-price contracts, with milestone-based, monthly team retainer and KPI-linked models also offered. Netbase runs a six-step lifecycle: discovery and strategic alignment, team assembly and architecture planning, agile execution with outcome-based milestones, modular and productized components, training and rollout, and ongoing support and co-building.
  • Milestones in practice. For a founder launching a bilingual classifieds marketplace, a client that is not named, Netbase delivered consultancy, design, a Laravel backend, payments, AI-powered content filtering into an admin moderation dashboard, deployment, training and a support period in six milestones; the portfolio record describes the scope.
  • Governance and ownership. Weekly reviews, KPI dashboards and a dedicated project manager run through every engagement. The client owns the IP created for custom development; Netbase productized modules are licensed, not transferred.
  • What does not exist. Netbase publishes no fixed MVP price, no standard stage duration and no success rate for products after launch. Schedules are set after discovery, from the scope.

Alternatives: other ways to plan a product from MVP onwards

Route Selection criterion Trade-off
One partner across all three stages You want continuity of architecture knowledge and one accountable party Depends on the partner offering both projects and ongoing teams
MVP partner, then an in-house team You plan to hire engineers once the product proves itself Hand-over must be planned in the MVP contract, or knowledge is lost
Product agency for the MVP, dedicated team to scale You want speed first, then a team that reprioritises weekly Two contracts and a transition; compared in our SaaS team versus agency guide
Reusable modules for the commodity parts Your product needs accounts, roles and billing before its unique feature Reused modules are licensed, not owned; see the SaaS product accelerator
No-code prototype first You need to test demand before any engineering spend Often rebuilt from scratch for the scale stage

Netbase can serve the first, third and fourth routes: dedicated teams, project-based development, on-demand support and fully managed delivery are all offered, and teams combine business analysts, project managers, solution architects, developers, QA and UI/UX designers. Consulting and custom development lead; staffing is a secondary option. The productized module library includes a CRM and B2B sales engine, a workflow automation toolkit, an AI chatbot integrator, Smart ERP Light, a real estate toolkit and an e-commerce accelerator.

Does the same plan fit a small business, not only a startup?

Yes, with a smaller first stage. A small business usually replaces a spreadsheet or a package that no longer fits rather than testing a market, so the first fixed-price milestone is one workflow, accepted on working software, and the next one is signed only once it is in daily use. Founders can compare the startups route.

Limits of this guide

  • It describes a planning method, not a quote; every stage is scoped and priced after discovery.
  • It assumes a product with users; internal tools follow the same stages with fewer growth questions.
  • Regulated products add compliance gates to every stage that this guide does not list.

Plan the next step with a Netbase consultant

Frequently asked questions

It should deliver working software that passes the acceptance criteria agreed for each milestone, the source code and documentation you own, a launch checklist, and a short plan for the scale stage based on what users did.

Only the parts that can be specified in advance. The MVP build, defined modules and hardening tasks fit a fixed price; open-ended growth work usually fits a retainer, and operations fit service terms.

It is ready when the exit test agreed before the MVP started is met, typically repeat use of the core job by target users, and when the known technical debt is listed so it can be planned rather than discovered.

You stop, change direction or run another small milestone. A stage-gate plan makes stopping cheap, because no later stage was signed in advance.

Next step

Share your product idea or current MVP plan and we will map it to stages and milestones: book a solution review.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
AI-ready SaaS development from a team that runs its own SaaS AI-ready SaaS development from a team that runs its own SaaS

Netbase provides SaaS development for founders and product teams to launch and scale multi-tenant subscription software with AI features customers will pay for. We build and operate our own SaaS platforms, Printcart and the AI-powered Cloodo workplace, and bring that experience to client products. Discovery fixes the MVP scope and schedule.

Learn More
line
Product discovery that validates AI features and ends in a release roadmap Product discovery that validates AI features and ends in a release roadmap

Netbase provides product discovery workshops for founders and product leaders to turn a product idea into validated scope, architecture options and a release roadmap. We test the problem with real users, prototype the riskiest flows, check whether planned AI features have the data and accuracy they need, and agree what the first release must prove before committing a build budget.

Learn More
line
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules

A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase