In brief
Choosing a CTRM is a structured process, not a single decision. It usually runs through initial contact, a scoping call, a broad demo, a scenario-based demo using your own trades, commercial terms and contracts. The buyers who get the best outcome prepare real trading scenarios, involve every affected team from the start, and judge the vendor on the quality of the output rather than a yes/no feature checklist.
How does the CTRM selection process actually work?
It runs through a recognised sequence of stages, each one narrowing the field. With thirty years of selling and delivering CTRM software, Amphora has seen the same path work repeatedly:
1Initial contact. You send the vendor a short brief covering your needs and the commodity groups to be covered, for example crude oil and refined products.
2Initial call. The vendor asks what you use today, why you think you need a CTRM, how many users you have and where they are based, your primary commodity and whether a budget is agreed. The call ends with an honest view on whether the fit is there.
3Initial demo. A broad, forty-five minute walk-through of the look and feel and the core applications, covering the whole trade lifecycle for your main commodity: trade entry, logistics, risk management, out-of-the-box reporting, accounting and VaR.
4Scenario demo. You provide real trading scenarios. The vendor's business analysts model them using your trades, operational activities, reference data and market prices, then walk you through the results with P&L explanations. This can take a vendor's analysts one to two weeks to prepare.
5Optional trial. A short hands-on period where your users enter their own reference data and trades with the vendor's business analyst guiding them.
6Commercial terms. With the requirements understood, the vendor can price the implementation and confirm whether cloud or on-premises suits you.
7Contract. Terms are set out covering support and maintenance, professional services and the modules included.
8Implementation begins. A team is assigned, often starting the Monday after contracts are signed, with reference data collection first.
Is an RFP a good way to choose a CTRM?
It is fast but it can be misleading. A Request for Proposal (RFP) typically lists hundreds of functional and technical questions, often scored using the MoSCoW approach (must, should, could, won't), and produces a quick comparative score for each vendor.
The weakness is that a binary or lightly scored checklist ignores user experience and the quality of the output. As Amphora puts it, if you ran an RFP on baking a cake, a child might score the same as a professional chef on paper, but the result would cost more, take longer and taste worse. A better indication is to watch the cake being made, then taste it. In CTRM terms, that means judging the scenario demo, not just the questionnaire.
What do the CTRM buzzwords actually mean?
Vendors lean on a familiar set of terms. It helps to know what each one really implies:
Out-of-the-box:
the function is standard and needs no further coding, though you may still need to add your own reference data to switch it on.
Scalable:
you can add business entities, commodities and markets yourself, later, at no extra cost.
One-branch:
all clients sit on the same core version, so everyone upgrades regularly and for free, and benefits from enhancements other clients funded.
Fixed-fee:
the implementation and licence fees are agreed and will not spring surprises such as time-and-expenses billing.
SaaS:
the vendor carries the burden of infrastructure, application management, security, availability and monitoring.
Tenancy:
multi-tenancy is cheaper because clients share; single tenancy lets you choose the location, upgrade independently and tighten security.
Proven and legacy:
shorthand for a track record measured in decades, which is a reasonable proxy for stability.
Knowing the vocabulary lets you ask sharper questions in the demo, which is where the real differences show.
How should I read a vendor's marketing?
As a way to build a shortlist, not to make the decision. Every CTRM vendor uses a familiar toolkit: content and whitepapers, press releases, SEO and paid search, LinkedIn, trade-show stands, partnerships, advertising and awards. Most of it is legitimate, and its honest job is to make sure buyers have heard of the vendor. The skill is reading which signals are earned and which are bought.
Awards are the clearest example of a bought signal. Many industry awards are ones a vendor effectively pays to enter or win, so an award badge is not, on its own, evidence of quality. It is a fair question to ask any vendor directly: do you pay to win your awards?
Thought-leadership content is useful, but it is vendor-produced, so it demonstrates expertise rather than proving it. The signals that carry real weight are the ones closest to peer-to-peer: genuine case studies and reference calls with actual users.
Press announcements are useful, but the scarcity of named customers is telling. Firms are often reluctant to be quoted, which is why genuine case studies are rare and valuable.
Word of mouth is the signal vendors can least control, and precisely why it matters most. It is made when users talk to each other, happy or unhappy, and no marketing spend manufactures it. Press releases about new customers and published case studies are prized because they are the closest a vendor can get to borrowing that credibility. But the real thing comes from talking to actual users.
Use marketing to build the shortlist. Use a scenario demo built from your own trades, and reference calls with real users, to make the decision.
The single strongest predictor of instability is the compounding pattern of high employee turnover combined with customer dissatisfaction.
When clients stop acting as enthusiastic references, the commercial trajectory of the business often follows. That is why the reference call you arrange yourself, and unscripted conversations with peers in the industry, tell you more than any product demo.
Eight questions worth asking any vendor directly:
01How many new clients have you signed in the last twelve months?
02What is your client retention rate?
03How many implementation specialists do you employ full-time?
04What is average employee tenure?
05Can you provide references from clients who went live in the last two years?
06What happens if a key person leaves during my project?
07How many active clients are running the current version of the platform?
08Is the current ownership private-equity funds, which can carry pressure for a rapid exit, or private investors?
Assess financial health, operating history, customer retention, product investment and leadership continuity with the same discipline you apply to any counterparty. In an industry where certainty is often in short supply, confidence in the company behind the software matters just as much as confidence in the software itself.
How should I judge one CTRM vendor against another?
Judge the output and the partnership, not the checklist. A CTRM selection is a significant project, but at any stage you can stop without incurring extra cost. The buyers who choose well tend to do three things: they prepare scenarios that reflect their genuine complexity, they involve every affected function early rather than at the end, and they weigh the quality and usability of the result above a raw feature count.
