Fixed Price, Time and Materials, or a Monthly Retainer? How to Buy Software Development Without Getting Burned
There are only three ways to pay for software, and each of them has a way of going wrong. Most founders choose the one that sounds safest, which is usually the one that fails most expensively for the shape of project they have. This is the guide we wish every client had read before the first proposal.
The three models in one paragraph each
Fixed price. You agree on a scope, a number and a date. The vendor carries the risk of running over. It works when the scope is genuinely understood, which in practice means after a discovery phase, and it fails when the scope changes, because every change becomes a negotiation.
Time and materials. You pay for the hours worked at an agreed rate. You carry the risk of running over, and you get the freedom to change direction without a change order. It works when requirements are moving and you are close enough to the work to steer it. It fails when nobody is watching the clock.
A monthly retainer. You pay a flat amount for a defined amount of capacity, usually a team or part of one, month to month. It is time and materials with a predictable invoice and a standing relationship. It works when the work is continuous, which is most of a product's life. It fails when the capacity sits idle because nobody is feeding it decisions.
The failure modes, in detail
Fixed price without a specification
The most common disaster in our rescue work. A shop quotes a fixed price from a short brief, because the client wants certainty and the shop wants the deal. Then one of two things happens. Either the shop builds exactly what the brief said, which is not what the client meant, and the result is a product nobody wants on time and on budget. Or the client clarifies as they go, each clarification is a change order, and the "fixed" price doubles in increments of $4,000.
A fixed price is only as fixed as the document it is attached to. If that document is two paragraphs, the price is a guess and the dispute is scheduled.
Time and materials without a cap or a cadence
Hourly billing is honest, and with the right vendor it is the cheapest way to build something whose shape is still changing. But it hands the client two jobs: deciding fast and watching the burn. Clutch's data shows the average project on its platform costing about $132,000 over about 13 months. Very few of those were sold as thirteen-month projects. They became thirteen-month projects at the hourly rate, one unreviewed week at a time, because nobody set a point at which to stop and look.
A retainer with no roadmap
A retainer buys a team's attention, and attention without direction is expensive. The retainers that go wrong are the ones where the client stops showing up: no weekly session, no prioritised list, and a team that fills the month with whatever seems reasonable. The invoice arrives on schedule either way.
Which one fits which project
In practice the model should follow the state of the project, not the preference of the buyer.
Before you know what you are building: time and materials or a short fixed-price discovery. A define phase of a few days, with a written output, is the one thing that should always be fixed price, because its scope is the one thing that is clear.
Building a first version with a clear specification: fixed price, with the specification attached and the change process written down. This is where fixed price earns its reputation for safety.
After launch, when the product is live and learning: a retainer. The work no longer has an end date, and the questions arrive weekly. A team that already knows the code, on a predictable monthly number, beats a new quote for every change.
Taking over someone else's code: time and materials for a fixed-scope audit, then whichever model the audit supports. Nobody can fix-price what they have not read.
Most successful engagements we have been part of used two of these in sequence: a fixed-price discovery or build once the scope was settled, then a retainer while the product grew.
The hybrids that actually work
A few structures are worth asking any vendor about.
- Fixed-price phases inside a retainer. The monthly plan covers the standing team; a specific large feature gets its own written scope and price, so a big piece of work does not quietly consume three months of capacity.
- Capped time and materials. Hourly billing with a ceiling the vendor cannot pass without written approval. It keeps the flexibility and puts the watching-the-clock job on the vendor.
- Equity for part of the fee. For early-stage companies, a vendor that takes part of the price in equity has aligned incentives in a way no contract clause produces. It only works with a vendor whose business model allows it, which is most venture studios and very few agencies.
What we do, and why
AW3 is a venture studio, so our pricing follows stage rather than one model. Founders before their first round work with us for sweat equity or on a payment plan. From seed to Series A, plans start at $999 a month and scale with the team you need, with no long contract. Enterprise work, and any first version with a settled scope, is priced per engagement in writing after a short define phase.
We arrived at this the hard way. Fixed-price builds from thin briefs produced the disputes described above; pure hourly work produced long projects. Writing the scope down first, pricing it, and then moving to a monthly plan once the product is live is the sequence that has produced the fewest surprises for the companies we work with and for us. The detail is on our MVP development and custom software development pages.
The questions to ask before you sign
Whatever model a vendor proposes, five questions settle most of the risk:
- What document is this price attached to, and can I see it?
- How is a change priced, and who approves it?
- What do I see every week, and where?
- What is excluded from this number?
- What does it cost to keep the same team after the first version ships?
A vendor who answers all five plainly can be trusted with any of the three models. One who cannot should not get the fixed price they are offering you, because you will be the one paying for the uncertainty.
Sources
- Toggl, Time and Materials vs. Fixed Fee: Which Is Right for Your Project?
- Imaginary Cloud, Software development contracts: time and materials vs fixed price
- Clutch, Software Development Pricing Guide, 2026
- AW3 Technology, How to choose a software development agency
