Lanshore: Advancing Intelligence

Solutions

ETRM Vendor Selection for Energy Trading Teams

Lanshore runs ETRM selections for energy companies as a scored evaluation rather than a demo tour: requirements gathered separately from trading, risk, scheduling, and finance, a weighted comparison framework agreed before any vendor presents, a shortlist with a written recommendation to the steering committee, and support through commercial negotiation into a delivery plan. Lanshore resells no trading system and takes no vendor commission, so the recommendation reflects fit rather than a reseller relationship.

Who it is for

Heads of trading, risk officers, CFOs, and IT leaders at energy companies who are replacing a trading system, consolidating several, or buying their first. It fits teams whose current system is a mix of a legacy ETRM and spreadsheets, teams whose vendor has announced end of support, and teams who have been asked to justify a trading system investment to a board that wants to see the alternatives scored. It assumes you want the evaluation documented well enough that the decision survives the people who made it.

The problems it solves

The evaluation becomes a demo tour

Vendors present their strongest workflow against their own sample data, every demo looks capable, and the team ends up choosing on presentation quality and rapport. Nothing in that process tests the trades that actually break systems: a physical deal with multiple delivery locations, a storage agreement, a structured option, or a month where the forward curve moves between capture and settlement. A framework agreed before the first demo, with your own deals as the test, is what turns a tour into an evaluation.

Trading, risk and finance want different systems

Traders want speed of capture and a position screen that matches how they think. Risk wants valuation models, limits, and stress testing they can defend. Finance wants settlement, accrual, and a clean path to the general ledger. These pull toward different products, and when the requirements are collected in one combined workshop the loudest group wins. Collecting them separately, then forcing the trade-offs into the open with weights everyone agreed to, is what produces a decision all three can sign.

Commodity coverage is assumed rather than tested

A system strong in power may be thin in physical gas, crude, refined products, or environmental products, and support for a commodity on a datasheet can mean anything from a native model to a configurable workaround. The same is true of regional market rules, scheduling integration, and exchange and broker connectivity. Each commodity and market you actually trade needs its own line in the comparison, scored on what the vendor demonstrates rather than what the datasheet lists.

Total cost is understated at the point of decision

License fees are the visible number. Implementation, interfaces to scheduling, accounting and market data, environment and infrastructure costs, annual support uplift, and the internal effort to run the system are usually not in the comparison when the decision is made. A cost model that runs several years out, covers both the vendor and your own effort, and is built the same way for every shortlisted product is what makes the options genuinely comparable.

Nobody writes down why the decision was made

A year into implementation, when a gap surfaces, the question becomes why this system was chosen and whether the gap was known. If the evaluation lives in a deck and people's memories, there is no answer. Scores, weights, assumptions, and the known gaps with their agreed mitigations have to be recorded at the time, as the artifact the program is later held to.

How Lanshore delivers it

  1. 1

    Requirements from each function, separately

    We work through trade capture, valuation, risk, credit, scheduling and logistics, settlement, accounting, and reporting with each group in its own sessions, so finance requirements are not shaped by whoever spoke first in a combined workshop. Each requirement is written as something a vendor can be asked to demonstrate, and marked as mandatory, important, or desirable by the function that raised it.

  2. 2

    A weighted comparison framework agreed before demos

    We build the scoring model and agree the weights with the steering committee before any vendor presents. Commodity coverage, valuation and risk, physical logistics, settlement and accounting, integration, usability, vendor viability, and cost each carry a weight the group has signed. Agreeing weights in advance is what stops the criteria from drifting toward whichever product demonstrated best.

  3. 3

    Market analysis and a longlist

    We assemble the candidate list from the vendors that genuinely serve your commodities, trading volumes, and regions, including specialist systems that a general market scan tends to miss, and screen them against your mandatory requirements before anyone spends time on a demo. The longlist and the reason each vendor did or did not progress are documented.

  4. 4

    Scripted demonstrations against your own deals

    We write demonstration scripts from your actual trades and ask each vendor to work them live: the deal structures that are hardest to model, a curve shift between capture and settlement, a physical movement with a scheduling change, and a month-end close. Every vendor runs the same script, so the scores compare the same work rather than each vendor's preferred story.

  5. 5

    An ROI business case and a multi-year cost model

    We build the business case and a cost model covering licensing, implementation, interfaces, infrastructure, support uplift, and internal effort, on the same assumptions for every shortlisted product. The model is handed over so finance can test its own assumptions rather than take ours. Lanshore built the requirements assessment, ROI business case, market analysis, and comparison framework on the PetroChina International America ETRM selection and presented a three-vendor shortlist with a recommendation to the steering committee.

  6. 6

    Shortlist, recommendation and reference checks

    We bring a shortlist with a written recommendation, the scores behind it, and the known gaps with proposed mitigations, so the committee can see what the chosen system does not do before signing. We prepare reference call questions aimed at how the vendor behaves during implementation and after go-live, not at whether the customer is happy.

  7. 7

    Commercial negotiation support

    We support the commercial negotiation with the comparison as leverage: scope of licensed modules, user counts and growth, implementation responsibilities, acceptance criteria, support terms, and the uplift schedule. Having a scored second choice is usually the most useful thing a buyer brings to that conversation.

  8. 8

    Selection turned into a delivery plan

    The evaluation ends in a plan, not a decision memo: scope by phase, the interfaces that have to exist on day one, data migration scope, the test cycles, and the resourcing the program needs from your side as well as the vendor's. Where Lanshore continues into delivery, the same people carry the requirements forward; where another partner implements, the plan and the scored requirements hand over cleanly.

Get an assessment

Related case studies

Related: Energy systems: ETRM and ERP programs · ETRM Implementation Services for Energy Trading · Energy ERP Program Management Services · Oil and gas industry work

ETRM Vendor Selection for Energy Trading Teams: FAQ

Which firms run vendor-neutral ETRM selections?
Lanshore does, and resells no trading system, so the recommendation carries no reseller margin. The large consultancies run ETRM selections as part of wider energy practices, and several boutiques specialise in commodity trading technology. The question worth asking any of them is whether they hold a reseller or implementation partnership with vendors on the shortlist, and whether their evaluation will test your own deal structures or the vendor's sample data.
How long does an ETRM selection take?
It depends on how many functions have to agree and how clean the requirements are at the start. The work divides into requirements, longlist and screening, scripted demonstrations, scoring and business case, and negotiation support, and the demonstration stage is usually the constraint because it needs senior trading, risk, and finance people in the room for each vendor. We size it against your decision deadline at the outset and say plainly if the deadline and the rigour are in conflict.
Should we run the selection ourselves?
Many teams can, and should, where they have run one before and have the time to script demonstrations and hold vendors to them. The parts that most often go wrong in a self-run selection are agreeing weights before demos rather than after, testing the hardest deal structures rather than the common ones, and building a cost model on the same assumptions for every vendor. If you run it internally, those are the three things to protect.
What if we already know which system we want?
Then the work is narrower and worth being honest about: a confirmation exercise that tests the preferred system against your hardest deals and documents the known gaps, plus commercial support for the negotiation. That is a legitimate engagement, and cheaper than a full evaluation. What it should not be is a full selection run to justify a decision already made, which wastes the other vendors' time and your own.
Does Lanshore implement the system it recommends?
It can, and does on some programs, which is why the recommendation is documented with its scores, weights, and known gaps so the committee can judge it on the evidence rather than on trust. Where a client prefers a different implementation partner, or where the chosen vendor implements directly, the selection artifacts are built to hand over: requirements, scoring, cost model, and the delivery plan.

Talk to Lanshore

A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.

832-466-8069Book a call