Scope clarity
Require a component list, exclusions, dependencies and responsibility matrix. Avoid comparing package names that hide different scopes.
Architecture quality
Ask for a system diagram showing customer systems, platform, connectivity, infrastructure and third parties.
Integration capability
Review documentation, test environments, authentication, error handling and ownership of ongoing API changes.
Operations and support
Define support hours, severity levels, escalation, maintenance communication and responsibilities during third-party incidents.
Security
Review privileged access, secret management, logging, change control and recovery procedures relevant to the delivered scope.
Commercial model
Separate implementation, recurring platform, hosting, support, third-party and usage-dependent costs.
Exit and portability
Understand data access, configuration ownership, documentation and the practical steps required to change components later.