When you get a quote for product development, the choice between fixed price and time and materials comes up almost every time. Both models are legitimate and both are standard in the industry. The real difference is not the number at the bottom of the page — it is who absorbs engineering uncertainty, you or the engineering firm. The sharper the project definition, the easier it is to price as a closed sum. The more technical unknowns, the fairer hourly billing becomes for both sides.

What you are actually buying in each model

With fixed price you buy a defined outcome: a requirements document, an agreed deliverables list, and a known number of revision rounds. The risk that the work takes longer than expected is priced into the number up front, which is why a fixed price almost always contains a risk premium.

With time and materials you buy professional time: you pay for work performed, you see time reports, and you retain the freedom to change direction mid-project. The hourly rate is comparatively lower because the vendor is not pricing risk it cannot control. For prevailing US rate ranges, see product development consultant rates.

  • Budget certainty: high with fixed price, lower with T&M.
  • Flexibility to change: cheap and easy with T&M, expensive and procedural with fixed price.
  • Transparency: better with T&M — you can see where every day went.
  • Total cost: often lower with T&M when the definition is stable and nothing is wasted on scope disputes.
  • Day-to-day management effort: lower with fixed price, since nothing needs approving hour by hour.

The comparison is between scenarios, not numbers. Two firms can quote similar sums where one includes three revision rounds and the other includes one. Compare deliverables lists, not bottom lines.

When fixed price is the right choice

Fixed price fits phases where the engineering is already understood and the only question is how much work is required:

  • Enclosure design around existing, frozen internal mechanics
  • Production drawings and a manufacturing data package
  • A version update or cost-reduction pass on a shipping product
  • Building a prototype from an approved 3D model
  • A defined CAD modeling deliverable with a known part count

The prerequisite is non-negotiable: a written requirements specification before signature. Without one, fixed price becomes a running argument about what was included, and the relationship sours over exactly the ambiguity the model was supposed to eliminate.

When time and materials is better

Whenever there is an open technical question, hourly is nearly always the fairer structure. Feasibility research, algorithm development, evaluating a sensor nobody has characterized in your application, debugging an intermittent electronic fault, or early-stage concept definition are tasks where nobody can honestly predict the duration. Pricing them as a closed sum comes out expensive, because the vendor has to quote the worst case to survive it.

Projects where the client is still forming the product also suit T&M, since in a fixed-price frame every definition change becomes a change order with a fee attached. And research-stage work is where the biggest risk sits — the risk of building the wrong thing correctly. Doing that work hourly with real dialogue is usually cheaper than doing it cheaply and wrongly, a theme running through the product development process.

The hybrid structure we prefer

In practice, for most hardware projects the question is not fixed price or hourly but where the boundary sits between them. The workable answer is to split the program into phases: definition and feasibility on hourly billing or under a capped budget, then design and production phases at a fixed price once the unknowns have shrunk. The client stops paying a risk premium on a phase nobody could price, and gets certainty on the budget-heavy phases.

A close relative is hourly with an agreed cap, where anything beyond the ceiling requires advance approval. That gives you budget protection without forcing the vendor to price undefined risk, and it fits early characterization and test work particularly well.

What to verify in the contract before you sign

  • Exact deliverables. Native CAD files or just STEP exports? Source code or compiled firmware? Drawings with tolerances? Name the file formats.
  • Revision rounds included, and the price of additional ones.
  • The change-order mechanism: how a scope change is priced and who approves it.
  • Milestones and payment triggers tied to deliverables rather than dates.
  • IP ownership and assignment. This is the clause founders most often skim — see who owns the IP when a company develops your product.
  • What happens on termination: what you receive, and in what state, if either side walks away.
  • Named personnel or at least defined seniority for the work.

Reading the quote behind the model

A quote that is dramatically cheaper than others usually reveals itself in the assumptions: fewer revision rounds, thinner deliverables, or an implicit expectation that you will supply engineering the other firms priced in. Our guides on how to choose a product design firm and design firm vs freelance engineer cover how to interrogate a proposal properly.

Get a quote structured for your actual risk profile

Projects House works both ways with US clients, and frequently combines them inside one program — hourly or capped for feasibility, fixed price for design, drawings, and prototype builds, with deliverables and revision rounds written down before anything starts. Describe your project and where the unknowns are through the contact form and we will propose the structure that fits it. See our product development services guide for more.