Fixed price and milestone delivery answer different questions. Fixed price describes how cost is agreed; milestones describe how work and acceptance are divided. A project can use fixed prices for individual milestones.
For a founder, compare proposals by who carries uncertainty and what evidence releases payment. A low headline total is difficult to evaluate if the proposal leaves integrations, testing, or operational setup undefined.
Separate commercial terms from delivery checkpoints
A fixed scope works best when the expected behaviour and dependencies are understood. If access to a third-party system is uncertain, ask whether the quote includes discovery, assumes access will work, or excludes the integration entirely.
Milestones should represent reviewable outcomes rather than calendar events. “Backend complete” is hard for a founder to verify. “An authorised user can submit a record, see it after signing in again, and export it without another tenant's data” is concrete.
Compare two fictional customer-study proposals
Imagine proposal A quotes one fixed amount for a study builder, shared response page, private review, and payments. It excludes changes after design approval. Proposal B prices three stages: a reviewed workflow brief, a complete free-study path, and paid access with launch checks.
Neither structure is automatically better. Ask A what happens when the payment provider's access requirements differ from the assumption. Ask B what assets and running software you receive if you stop after stage two. Ask both how defects differ from scope changes and who verifies acceptance.
Build a comparison table with rows for deliverable, test evidence, access dependency, included revisions, operating setup, handover, and stop cost. Put missing answers in the table rather than mentally treating them as included.
The amounts themselves are not the key example here. A proposal that appears cheaper can become more expensive if essential work sits outside its definition of completion. Conversely, a broad contingency allowance may be unnecessary when discovery has already removed uncertainty.
Write a change mechanism before the first build
Require a short change note stating the requested behaviour, reason, affected acceptance cases, cost or time impact, and decision owner. Allow the founder to replace lower-priority work rather than treating every change as an addition.
Do not use milestones merely to defer hard integration risk until the final payment. Put uncertain dependencies early enough that the project can change direction while stopping remains affordable. Contract interpretation and ownership clauses deserve appropriate professional review; this article provides a delivery comparison method, not legal conclusions.
The StackFlight case study offers a concrete product-workflow reference for judging deliverables. Its shipped features are not a pricing benchmark for your project.
Questions about MVP pricing
Can milestones have fixed prices?
Yes. The two concepts are compatible. Define the scope and acceptance evidence for each priced stage.
What should happen if access is blocked?
The proposal should name the assumption, owner, fallback, and effect on the next milestone. Avoid paying for a supposedly complete workflow that cannot reach its external system.
What should a founder compare first?
Compare included outcomes and exclusions before totals. Bring the proposals and one acceptance scenario to a product scope review.