Amphora has been implementing its CTRM for over 30 years without using third-party system integrators. Every implementation, and all support after go-live, is delivered by full-time Amphora employees, which removes the second contract, second commercial relationship and long-term dependency on an outside consultancy that the system-integrator model creates elsewhere in the market.
Does Amphora use third-party system integrators to implement its CTRM?
No. Amphora has been implementing its CTRM for over 30 years, and we do not use third-party system integrators. Every implementation, and all ongoing support after go-live, is delivered by full-time Amphora employees with up-to-date knowledge of every current capability, as well as the functionality in our latest and upcoming builds.
What does having no third-party integrator mean when evaluating Amphora?
Look again at the questions our companion piece, Are CTRM system integrators facing the same reckoning as IT consultants?, raises: “Do we need an integrator at all?”, “Are we paying for people, or for outcomes?”, “How much knowledge will remain with us after go-live?” For an Amphora client, those questions answer themselves. There is no separate integrator to appoint, no independent statement of work to negotiate, and no second contract running alongside the software licence.
Compare that with the third-party system integrator route. A client selects a CTRM, then has to separately source, evaluate and negotiate terms with a system integrator, effectively running two procurement processes and managing two commercial relationships for one project. Once live, that integrator relationship typically continues indefinitely, generating its own renewal cycles, change requests and invoices for years after the original go-live.
What does an in-house implementation team mean for a CTRM buyer?
- One point of accountability. If something needs attention, you are dealing with the organisation that wrote the code, not a vendor and an integrator pointing at each other.
- Nothing else to procure. There is no separate contract to negotiate and no independent renewal clause tied to a third party's commercial terms.
- No multi-year dependency on somebody else's consultants. The people who implement your system are the same people who support it, so there is no handover, no loss of institutional knowledge, and no ongoing bill from a partner organisation with its own margin to protect.
- Direct access to the efficiencies AI is bringing to implementation. The gains our companion piece describes flow straight through to you. They are not filtered through a third party's own commercial model.
- A team that already knows your build. Continuity between implementation and support means questions get answered by people who were in the room when your system was configured.
For companies evaluating their next CTRM, it is worth adding one more question to the list our companion piece sets out: “Will we be dealing with your employees, or somebody else's?” It is a simple question, but it may be the one that most affects the total cost, risk and outcome of the project.
For further information on what an implementation involves here at Amphora, please see a previous news release, 90 day implementations, or find out more at www.amphora.net.
