Separate the types of cost
Record one-off implementation work separately from recurring software, hosting, data and support services. List third-party charges alongside the party that contracts and pays for them. Add the work required to connect the components: an included product does not necessarily include every integration you need.
Preserve assumptions such as the initial instrument set, required interfaces, operating regions and support boundary. They explain why two proposals with similar product labels can cover very different work.
Use a like-for-like comparison schedule
| Category | Scope to record | Question to settle |
|---|---|---|
| Implementation | Configuration, integration, migration and acceptance work | Which deliverables and revisions are included? |
| Recurring operation | Platform arrangement, compute, storage, data and connectivity | Which limits or usage changes alter the cost? |
| Support and recovery | Monitoring, incident ownership, backup and restore work | What is supplied routinely and what is separately scoped? |
| Future change | Extra instruments, regions, systems or provider migration | How is additional work approved and quoted? |
For MT5, the project scope tool can prepare a structured enquiry. It does not calculate a binding fee or replace a reviewed proposal.
Compare exclusions before totals
Illustrative comparison: two offers both mention CRM connectivity. One includes a specific account-creation workflow; the other supplies access to an interface but excludes adapter development. Price comparison is incomplete until the missing implementation, testing and support ownership are added to the schedule.
Ask suppliers to return the same worksheet with included, optional, client-supplied and unavailable items marked. Confirm billing periods, prerequisites and the procedure for approving scope changes directly in the proposal. A clear cost boundary supports a better purchasing decision without requiring public price claims.