Fixed price software development
The first question is whether data mapping sits inside the written scope. If the specification says the integration covers order retrieval and the acceptance criteria describe a portal that displays orders accurately, there's a reasonable argument that mapping is included and the supplier absorbs the effort. If the specification is silent, it isn't included.
Where it falls outside, you get a change request. Someone prices the extra work and someone with authority approves it, so the contract price moves. The schedule moves too, because fixed price software development plans the sequence tightly and inserted work pushes everything behind it.
That's the honest trade in fixed price vs time and materials. You bought certainty about a defined thing, so anything outside the definition needs a decision before work continues. Which means the quality of your exclusions list matters more than the quality of the price.
Time and materials contract software development
Under time and materials, the mapping requirement goes into the backlog like any other item and gets estimated. No contract variation is needed. The forecast changes instead, because the hours reported against the project now point at a different total.
That's only safe if the controls are written down. Time and materials contract software development without them is an open tab, and fixed price vs time and materials becomes a genuinely unfair comparison. What should be in the agreement:
-
Burn reporting at a stated frequency, showing hours used and hours remaining against the forecast, along with what changed since the last report.
-
An approval threshold, so any item above an agreed size needs your sign-off before anyone starts it.
-
A stop-work trigger at a defined percentage of the budget, where work pauses until you authorise more.
-
A named approver on your side with a known spending limit.
Acceptance in this model happens continuously rather than at the end, which is why the reporting has to be good enough to act on.
Capped delivery phases
A capped phase commits you to a ceiling for a defined slice of work and nothing beyond it. The Cabinet Office guidance for government buyers makes the same point about managing commercial exposure through fixed-price sprints "contracted for in phases rather than contracting for the entirety of the requirement on a fixed-price basis at the outset". Central government buys this way in practice through statements of work priced as capped time and materials on the Digital Outcomes framework.
The mapping discovery lands differently here. The work either fits inside the current phase ceiling or it doesn't. If it fits, it's delivered and the knowledge feeds the next phase estimate, which is the point of the discovery phase described in the GOV.UK Service Manual.
If it threatens the cap or a milestone date, you have a decision. Defer the mapping to the next phase or raise the ceiling, with the option to drop something else from this one. Fixed price vs time and materials leaves that decision implicit. Capped phases force it into the open on a schedule.
Show the cost calculation
Numbers make this concrete. A piece of work estimated at 100 hours, charged at £80 per hour, comes to £8,000. An approved change of 20 hours adds £1,600 and brings the total to £9,600.
These figures are illustrative. They aren't Evolved Ideas rates or market benchmarks, and they exclude tax. UK supplies of professional services carry the standard VAT rate of 20%, so your actual commitment is the net figure plus whatever tax treatment applies to your organisation and jurisdiction.
The important part isn't the arithmetic. Under time and materials contract software development, that £1,600 only becomes real when someone with authority approves it, and no calculation of this kind authorises anyone to exceed a cap. A ceiling is a hard limit.