Do not fix the answer before the unknown is visible
A fixed quote for an undefined integration is not certainty. It is an agreement about who will absorb ambiguity, avoid it, or negotiate it later. Before choosing a commercial model, identify which parts of the work are understood and which depend on discovery.
Use a fixed scope when the deliverable, assumptions, and acceptance conditions can be described clearly. Use time and materials when learning is expected to change the work and the client can actively govern priorities and spending. This is delivery guidance, not legal advice; the actual agreement needs appropriate commercial and legal review.
What makes a fixed scope credible
A bounded deliverable needs observable acceptance. “A modern customer portal” is an aspiration. Defined user journeys, supported integrations, data responsibilities, and failure behaviour are closer to something that can be accepted.
The proposal should explain what the client supplies, which dependencies are assumed, and how a changed assumption is handled. A fixed price does not mean unlimited revisions or a guarantee that an external system will behave as hoped.
The UK government's agile contracting guidance discusses fixed-price and time-and-materials approaches. Its procurement context is specific, but it reinforces that agile delivery and commercial structure are separate design choices. There is no need to pretend one billing model makes every project agile.
What time and materials asks from the buyer
Payment for effort makes room to adapt as evidence arrives. It also means the buyer needs visibility into how effort is used and the authority to stop low-value work. An unattended backlog is not a spending control.
Agree a review rhythm, an approved spending boundary, and the evidence expected at each checkpoint. Completed behaviour, discovered constraints, and updated forecasts are more useful than an unexplained list of hours.
A cap can limit authorized expenditure, but it does not automatically guarantee all desired features fit inside it. When scope exceeds the remaining budget, someone must choose what changes. That choice should be visible while there is still room to act.
Separate discovery from delivery commitments
An uncertain project does not always need an open-ended engagement. A bounded discovery phase can investigate the hardest assumptions and produce a revised implementation decision. The output should include evidence, unresolved risks, and a practical scope, not simply a presentation recommending more work.
A hybrid arrangement can fix well-understood slices while leaving uncertain work explicitly subject to review. Be careful not to hide uncertainty in vague exclusions that the buyer cannot interpret.
Clodron's AI automation work often requires understanding existing systems before a useful implementation boundary can be drawn. The briefing guide explains the inputs that make a quote meaningful. Product engineering needs the same discipline when requirements depend on unknown integrations or workflows.
Prepare a comparable brief this week
Write the desired outcome, required journeys, known dependencies, and acceptance evidence. Separate confirmed facts from assumptions. Mark the decisions the supplier cannot make on the business's behalf.
Request alternatives against that same brief: a bounded delivery proposal where feasible, and an adaptive proposal with explicit spending and review controls. Compare exclusions, responsibilities, change handling, and exit conditions, not only the headline figure.
Choose fixed scope for work that can genuinely be bounded. Choose time and materials when adaptation is valuable and the client can manage it. If the team cannot yet describe the uncertainty, buy a focused investigation before buying a promise.
