Comparing agency proposals: fixed price, Time & Material, or Dedicated Team

Three proposals, three different calculations

Anyone who requests multiple proposals for a software project runs into the same pattern every time: the numbers differ more than the seemingly identical task would justify. The reason is rarely arbitrary; it's usually the contract model behind the calculation. An agency pricing on a fixed-price basis builds in risk buffers that a Time & Material quote doesn't carry. Another agency offers a Dedicated Team from the outset because it expects a longer collaboration. Before comparing totals, it's worth looking at the model behind the number.

That holds regardless of the type of project, whether it's custom software, a web application, an app, or a SaaS product. The calculation logic behind the three models stays the same across project types, even though the absolute amounts differ significantly.

The three contract models compared

The table shows tendencies, not fixed rules. Some agencies combine models, for example fixed price for a first version and Time & Material for ongoing development afterward. In your first conversation, ask specifically why the agency proposes this particular model for your project.

Fixed price: certainty against flexibility

A fixed-price proposal gives you planning certainty. You know what the software will cost before the project starts, and you don't carry the risk of a miscalculation yourself. The tradeoff: any later change to the agreed scope goes through a change order, and change orders are often more expensive in practice than comparable work within the original proposal, because they get negotiated individually.

Fixed prices are therefore only as reliable as the requirements specification they're based on. An agency that names a fixed price without a prior requirements phase is either calculating with a generous risk markup or working from a definition of "done" that will surprise you later. For how to document requirements upfront so that a fixed-price proposal actually holds up, see Software requirements specification. For a rough sense of what order of magnitude your project falls into before that, see What does software cost?

A fixed price makes the most sense where the scope can genuinely be described upfront: a website with defined subpages, an interface between two known systems, an app with a clearly bounded feature set. For projects where the scope only emerges during the course of the work, such as ongoing development of an existing product, a fixed price rarely fits, no matter how detailed the underlying requirements specification is.

Time & Material: ongoing billing by effort

With Time & Material, you pay for hours or days actually worked, typically billed monthly with an agreed upper limit. This model fits projects where requirements only sharpen during development, for example because early user feedback shifts direction. You then pay only for work that actually happens, and you can adjust scope on an ongoing basis without negotiating a change order every time.

The downside is the oversight burden on your end. Without regular sprints with clear outcomes and without your own point of contact tracking progress, Time & Material projects easily run off track, both on budget and on schedule. So agree on fixed reporting dates and have the remaining effort shown to you regularly, not just at the end of the month.

Dedicated Team: fixed capacity for longer projects

A Dedicated Team is capacity reserved over months, usually a fixed set of developers working exclusively for your company. This model pays off once the collaboration extends beyond a single project, for example with ongoing product development or several projects running in parallel. A team that has worked together for a while knows your system, your processes, and your contacts, which removes the onboarding time for later work.

In the ramp-up phase, a Dedicated Team is usually more expensive than the other two models, because you pay for the capacity regardless of current utilization. It only becomes economical once there's enough work over a longer period to keep the team fully occupied. For a one-off, clearly bounded project, it's rarely the right choice.

With this model, also clarify what happens when staff change. If a key person leaves the agency, the contract should state how quickly a replacement is provided and how onboarding is documented. Without that provision, you as the client carry the full risk of losing institutional knowledge, even though you're paying for fixed capacity.

Evaluating proposals systematically: the scoring matrix

Once you have several proposals in hand, a simple matrix with weighted criteria helps more than a pure price comparison. For each proposal, enter a score from one to five per criterion and multiply it by the weighting.

You can adjust the specific weightings to your project, for example giving more weight to credentials for security-critical applications. What matters most is using the same matrix for every proposal, so the scores are actually comparable. For what the code ownership and handover criterion should specifically cover in the contract, see Who owns the code?

Warning signs in proposals

A fixed-price proposal without a prior requirements phase is one of the most common warning signs, because it either rests on rough assumptions or was deliberately priced low to make up the difference later through change orders. You should also pay attention if a proposal contains no statement on code ownership and handover, if case studies come without a measurable result, or if an hourly rate sits well below the usual German range of €100 to €180 without the agency explaining how it gets there, for example through a nearshore team.

In such cases, ask specific questions: about the planned team, about comparable projects with metrics, and about what's explicitly excluded from the proposal. A reputable agency will answer directly.

Reaching a decision

If you have a requirements specification with clear requirements in hand, you can apply the scoring matrix directly to the proposals you receive. When scores differ significantly across criteria, a second conversation with the two top-ranked agencies is worth having before you decide, especially if price and team quality scored differently. Write down open questions right after each conversation, because details tend to blur quickly after the third or fourth meeting.

On techagenturen.de, you can filter agencies upfront by contract model and verified credentials, so you only reach out to providers that fit your project from the start. For how the ranking of results comes about, see the methodology. Through a project request, you get proposals from several matching agencies at once, which makes comparison easier from the beginning.