Symphony Apps Development logo — teal interlocking S monogram beside the studio wordmark
All writing

The fixed-price quote nobody liked

We turned down a fixed price on a project with agent-assisted estimation built in, and the client was glad of it eight weeks later.

Category
Process
Reading time
5 min
Published
28 Apr 2026
Topics
Process, Delivery, Clients

A prospective client wanted a fixed price for a project that involved a genuinely novel integration with a vendor whose API documentation was, by their own admission, unreliable. We said no to fixed price and explained why, and it was not the answer they wanted to hear at the time.

Why fixed price fails on genuine unknowns

A fixed price is a bet on a known scope. Where the scope is well understood, that bet is reasonable and we quote it happily. Where a meaningful part of the work depends on how a third-party system actually behaves — not how it's documented to behave — nobody can honestly price it in advance, and a studio that does is pricing in a cushion for their own risk, which the client pays for either way.

What we offered instead

Time and materials for the integration specifically, ring-fenced with a hard cap and a checkpoint at 50% of that budget to report back on what we'd actually found. The rest of the project, which was ordinary and well understood, was quoted fixed as normal.

What the vendor's API actually did

Roughly a third of its documented endpoints behaved as described. The rest had undocumented rate limits, one returned success codes on requests that had silently failed, and a support ticket to the vendor took nine days to get a useful answer. None of this was discoverable without building against it.

A fixed price on an unknown isn't confidence. It's a guess wearing a suit.

What the checkpoint conversation looked like

At the 50% mark we showed the client exactly what we'd found, including the vendor's silent failures, and gave a revised estimate for the remaining work with the reasoning attached. It came in over the original estimate, which is normally an uncomfortable conversation, and it was not, because the client had been shown the evidence as it accumulated rather than presented with a number at the end.

Why we'd do this again

The alternative was quoting fixed and either eating the vendor's chaos ourselves or cutting corners to hit the number. Neither outcome is one we want attached to our name, and the client, once the frustration of an unfamiliar arrangement passed, told us afterwards that the visibility was worth more to them than the certainty of a single number would have been.

Tell us what you’re trying to ship

A first call is thirty minutes and costs nothing. Bring the problem, not a spec — working out what to build is the part we are good at.

Or email office@symphonyapps.ro. We reply within one business day, in English or Romanian.