Clients often ask for a fixed price before anyone knows what will be built. It is an understandable request and a poor way to start. The engagement model should follow from how certain the scope is and how long the roadmap runs.
Fixed scope: when requirements are known
A fixed-scope project suits a defined ERP module, a portal with agreed features or a corporate platform. Discovery and architecture phases produce the specification that makes a fixed price honest. Changes go through a visible change process.
Dedicated team: when the roadmap is long
Product companies and groups with ongoing digital programmes do better with named engineers working month on month. You get continuity, domain knowledge that compounds and capacity you can scale up or down with notice.
Time and material: when you are exploring
Integrations, R&D and evolving requirements fit a pay-for-effort model with weekly check-ins and transparent timesheets. It is the most flexible and the one that most depends on trust and reporting.
Support and AMC: once it is live
Live systems need monitoring, patches, fixes and improvement. An annual contract with SLAs by severity and a bank of enhancement hours keeps the system an asset.
Mix them
Most of our relationships combine models over time: a fixed-scope first phase, a dedicated team for the roadmap and an AMC for operations. Start with the model that matches your certainty today.