Fixed Price vs. Time and Materials: Choosing the Contract That Fits the Project

Every software or design engagement starts with the same question: what will this cost? The answer arrives wrapped in a contract model, and that model quietly shapes everything that follows — how scope gets discussed, how problems get reported, and who absorbs the surprise when something turns out harder than expected.

Most buyers default to fixed price because it feels safe. Most developers default to time and materials because it is honest about uncertainty. Both instincts are partly right, and both fail in predictable ways.

What Fixed Price Actually Buys You

A fixed price transfers budget risk to the agency. It does not transfer outcome risk. If the scope was misunderstood, the price is still fixed, but the thing you receive may not be the thing you needed.

To protect itself, the agency prices in a buffer, often 20–40%, for everything it cannot see yet. It also has a structural incentive to treat every new request as a change order, because each unplanned hour comes out of its margin. The result is a relationship where both sides spend energy defending a document instead of improving the product.

Fixed price works well when:

• The scope can be written down in testable terms: screens, behaviours, integrations, acceptance criteria.
• The technology is boring and well understood. A brochure site on a known CMS is a fixed-price job. A novel integration with an undocumented partner API is not.
• Requirements will not change meaningfully during delivery.
• You have the time to run a proper discovery phase first.

What Time and Materials Actually Buys You

Time and materials (T&M) gives you flexibility. You pay for the work done, priorities can change every sprint, and discoveries get absorbed rather than litigated. Nobody pads the estimate for risk, so you only pay for the risk that materialises.

The cost is that budget control now depends on discipline instead of paper. Without a cap, a visible backlog and a regular burn report, T&M drifts. The agency has little incentive to finish and you have little visibility into whether you are on track.

T&M works well when:

• The problem is genuinely exploratory: new product, unclear users, unproven approach.
• You expect to learn things mid-project that will change direction.
• The work is ongoing: a product that needs continuous improvement rather than a single delivery.
• You are comfortable owning prioritisation, because someone has to say “this is enough.”

The Variable That Decides It: How Well Is the Scope Understood?

Strip away preference and the choice mostly comes down to one question: how confident are both sides that they know what is being built?

If the honest answer is “very”, fixed price is efficient. If the answer is “roughly”, the estimate has a wide error band, and pretending otherwise just moves the argument to month three. If the answer is “not yet”, you should not be signing a delivery contract at all.

This is why a discovery phase is the most underrated line item in any proposal. A short, paid, fixed-price discovery (two to four weeks of workshops, wireframes, a technical spike on the riskiest integration) converts “not yet” into “very.” It produces a scope you can actually price, and it tells you whether you want to work with this team before you commit the bulk of the budget.

The Hybrid Most Projects Should Use

In practice, the best structure is rarely pure. A pattern that holds up well:

1. Fixed-price discovery. Defines scope, surfaces risks, produces a prioritised backlog.
2. Fixed price for the well-understood core. The parts with clear acceptance criteria.
3. T&M or a capped budget for the uncertain parts. Integrations, migrations, anything dependent on third parties.
4. A monthly retainer afterwards. Improvement is continuous, so the billing should be too.

Another useful variant is a T&M contract with a not-to-exceed cap and a mandatory check-in at 50% of budget. You keep the flexibility, and the cap forces a decision before the money is gone rather than after.

Questions to Ask Before You Sign

• What is assumed in this estimate, and what happens if an assumption is wrong?
• How are changes handled, and who decides whether something is a change or a clarification?
• What do I see every week, and how will I know the burn rate before the invoice arrives?
• If we find the scope was larger than we thought, what are our options?

A good partner answers these without defensiveness. If the answers are vague, the contract model is not the real problem.

Neither model is a safeguard on its own. What protects a project is a shared, specific understanding of what “done” means, and a contract that makes it cheap to talk honestly when reality disagrees with the plan.

---

PNK WORKS scopes projects with a paid discovery phase first, so the price you agree to reflects the work that is actually there. Start a project.