Insights / October 20, 2026

Fixed price vs time and materials: how to pay for software development

How you pay for software affects more than your budget. It shapes how your project is planned, how changes are handled, and whose side the risk sits on. Here’s how the three common models compare, and when to use each.

Fixed price

You agree on a scope and a price up front, often paid in milestones.

Good for: work that can be clearly defined. A specific set of features, a rescue with a known list of fixes, a prototype to test an idea.

The upside: you know the cost before you start, and the risk of overruns sits with the developer.

The catch: fixed price only works when the scope is truly fixed. Every change becomes a negotiation, and developers price in the uncertainty, so a vague scope gets an expensive quote. Fixed price on an unclear project usually leads to arguments about what was “in scope.”

Hourly (time and materials)

You pay for the time spent.

Good for: small, unpredictable tasks, and exploratory work where nobody can say up front how long it will take.

The upside: total flexibility.

The catch: you carry all the risk, and it’s hard to plan a budget. Hourly billing also gives nobody an incentive to be efficient.

Monthly

You pay a set amount each month for a block of time from a dedicated team.

Good for: ongoing development, products that are live and changing, and anything where the scope is still moving.

The upside: a predictable budget, a team that knows your product, and changes that don’t need a new quote. You can reprioritize every week as you learn from users.

The catch: you need to be engaged in setting priorities, so the hours go to what matters most.

Which one should you choose?

A simple rule: fixed price when the scope is clear, monthly when it isn’t.

Most products need both at different times. The first version, or a rescue with a known list of problems, suits a fixed price. Once the product is live and you’re learning from users, a monthly plan lets you keep building without re-quoting every change.

How to protect yourself either way

  • Break work into milestones you can see and test, rather than one big payment for one big delivery.
  • Get regular updates and working software at each milestone, whatever the model. Seeing it work is the only real progress report.
  • Own your code and accounts from day one.
  • Agree how changes are handled before the first one comes up.
  • Know how to stop. A reasonable notice period on monthly work, and a clear handover either way.

How we price

At Park23, we do both. Clear scopes get a fixed price, in milestones. Ongoing work runs on monthly plans from $2,900 a month for a dedicated block of senior engineering hours, with 30 days’ notice to cancel.

LET’S TALK.

Book a free 30-minute call with Virgil

Pick a time that suits you. You’ll get a straight answer on what you need, what it should cost and the fastest path to launch.

Loading available times…

Open the calendar in a new tab

Send us your project

Virgil replies personally within one business day.

Book a free strategy call