Most disputes in technology projects trace back to things that were never written down. Use this checklist in your last conversation with a partner, before the contract is signed.
Scope and deliverables
- Which modules, processes and reports are in scope, and which are explicitly out?
- How many users, entities, locations and currencies does the price assume?
- Which integrations are included, and who owns the work on the other system?
Data and migration
- Which data will be migrated, from which systems, and in what format?
- Who cleans the data? Cleaning is often the largest hidden task and is usually the customer's job.
- How many trial migrations will be done before the final one?
People and responsibilities
- Who is the named project manager on each side?
- How many hours per week will your team need to give, and in which roles?
- Who approves designs and changes, and how quickly?
Testing and training
- What testing is planned, and who signs off?
- How many training sessions are included, for which groups, and are they recorded?
- Will you receive user guides written for your processes, not generic manuals?
Go-live and support
- What does a successful go-live mean, in measurable terms?
- What support period follows launch, and what are the response times?
- What happens if the key consultant leaves the partner?
Contract basics
- Payment is linked to milestones you can verify, not only to dates.
- A change process exists for new requests, with an agreed way of pricing them.
- You own your data and can export it at any time.
- There is a clear exit route and handover if the relationship ends.
Keep the answers in writing, attached to the contract. A partner who welcomes these questions is usually one worth hiring. To compare companies before you ask them, start with verified partners on SARVO.