Technology selection worksheet
Test the awkward requirement
Select a constraint that is easy to omit from a sales demonstration, such as bulk export, delegated administration or a failed integration.
Treat a dependency as a long-term commitment
Include migration, support and exit effort in the comparison. An attractive first-year price does not describe the full operating cost.
Make provider responsibilities explicit
An application can depend on several organisations without any one of them owning the complete customer journey. Identify who manages the application, hosting, identity service and business system integrations. Write down who can investigate each boundary and who has authority to approve a change.
Consider a portal that cannot retrieve an invoice. The application team may see a timeout while the accounting provider sees no request. A useful operating agreement identifies the evidence needed at both ends and the person coordinating the investigation. It should not require the customer to understand every technical boundary before they can ask for help.
Evaluate working arrangements as well as technology
Ask how a provider handles incidents, planned changes, access requests and service retirement. Obtain the applicable contractual terms and compare them with the business hours and recovery expectations of the application. A public product description is not a substitute for the agreement that covers your organisation.
Check the implementation relationship too. Establish who owns configuration, who maintains custom extensions and whether another team can take over. Request a practical handover example rather than relying on a promise of documentation. Cobnex does not claim a certification, reseller status or formal provider partnership through the inclusion of a platform in its service descriptions.
Manage a shared change without gaps
For changes involving several providers, nominate one coordinator and keep a common readiness record. Include the change window, dependency order, verification steps and rollback authority. Confirm that the relevant people are available when their part of the change is needed.
After the release, verify the business transaction across all systems. A successful infrastructure deployment does not prove that a customer can complete their task. Record outstanding work with an owner and a due date. This gives the organisation one coherent view of the service while allowing each provider to remain responsible for its own technical area.
No partnership or certification is implied. Platform references describe technologies that may be evaluated for an appropriate solution.