If you sit on the board or hold an investment position in a charging network operator, this piece is written for you. It examines three areas of a strategic asset your company built years ago, and closes each with one question worth raising at your next board meeting.
The operators who built their own CPMS (Charge Point Management System) platforms were not wrong. In the years when commercial alternatives were too immature, too hardware-dependent, or too inflexible to trust with the complexity of a real charging network, building in-house was the correct strategic call. A platform built to the exact specifications of one network, under full engineering control, was not just an operational necessity; it was a genuine competitive asset. The CPMS is the backbone that orchestrates everything a charging operator does: hardware, energy flows, driver experience, B2B relationships, payments, regulatory compliance. A platform purpose-built for a specific network, with engineering capacity directed at differentiating it, can produce capabilities no off-the-shelf alternative can match.
That premise is what made the original build decision rational. The question worth putting on your agenda is whether the premise is still being delivered on.
The moat test
Every strategic asset has a condition: it produces competitive advantage proportional to the investment required to maintain it. For an in-house CPMS, that condition translates directly into a question about what the engineering team is actually building.
Maintaining the infrastructure is real work. Protocol updates, payment terminal certifications, regulatory compliance cycles, firmware version management across hardware manufacturers: every charging network must do all of this, and none compete on any of it. On an in-house platform, it falls entirely to one engineering team, for one network, on deadlines set by regulators and standards bodies. The fraction of your engineering investment this consumes determines how much remains for the work the platform was built to enable: the custom billing logic, the vertical-specific workflows, the commercial models unique to this network.
The diagnostic is direct: in the last 12 months, what unique, network-specific capability has the engineering team shipped that a competitor running on a commercial CPMS platform does not have access to? If the answer is clear and specific, the asset is functioning as designed. If the question is hard to answer, or if the honest answer is that most engineering output was maintenance and compliance, the asset has drifted from what it was built to be.
Call it the moat test: not a measure of the engineering team’s capability, but of whether the model is still delivering the differentiation it was built to produce. The question for your next board meeting:
What unique capability has our engineering team shipped in the past year that a competitor on a commercial platform cannot access?
Strategic optionality
Strategic assets are valued not only for what they enable today, but for how quickly they enable response to what comes next. For an EV charging operator in 2026, that question is practical: when the commercial team wants to launch a dynamic pricing model, enter a new market segment, or deliver a partnership integration that a B2B relationship depends on, how quickly can the platform support it?
A platform that turns each of these into a multi-month engineering project is not neutral infrastructure. It is a direct constraint on the speed at which the business can act. Every commercial experiment carries an opportunity cost in engineering time, and every market move is slower than it needs to be. The ability to respond when competitors move, when a customer’s requirements shift, or when a new commercial model becomes viable is bounded by what the platform can absorb and when.
You apply this lens to every other significant capital allocation: is this asset returning what we expect, and does it serve the strategy at the speed the market requires? The platform decision rarely receives the same scrutiny, because it was made before most current board members were in the room. The engineering investment it commands is substantial. Whether that investment is returning competitive advantage or producing a speed constraint is a question worth asking explicitly. The question for your next board meeting:
If the commercial team needed to launch a new pricing model or enter a new market next quarter, what would that actually require from the engineering team, and how long would it take?
The timing question
Software categories mature. The transition follows a consistent pattern: fragmented, then consolidated, as commercial platforms develop to the point where the calculus shifts for even the most capable in-house teams. The EV charging software market is making this transition now.
The operators who act during the maturation window retain the most degrees of freedom. They enter transitions with time and options rather than under operational duress. Those who wait tend to move in crisis: a compliance gap, a leadership change, a competitive advantage that has grown too wide to close on the current trajectory.
Evolt, now part of SWARCO, operated an in-house CPMS for fifteen years and managed more than 10,000 charge points on it. In 2025, they re-examined the commercial market and changed their answer. Justin Meyer, Managing Director: “AMPECO stood out as the clear partner for us, demonstrating the technical depth and long-term development capability aligned with how our business, our customers’ needs and the wider market are evolving.” That evaluation came with fifteen years of in-house investment behind it. The question for your next board meeting:
When did your board last formally evaluate whether the in-house platform still represents the right strategic choice, and what would it take to run that evaluation now?
The bet worth examining
Running an in-house CPMS is an active strategic position, even when it has not been made explicitly. It encodes a specific assumption: that the EV charging market will not move faster than one engineering team can absorb and respond to. That assumption was reasonable when most of these platforms were built. The question is whether you would make it again today, deliberately, with current information.
The strategic review you apply to every significant capital asset (is this still the right investment, is it delivering the return we expected, does it serve the strategy we have now rather than the one we had when the decision was made) is rarely applied to the platform. The decision was made once, in a different market, and has been renewed by default since.
If you were deciding today, knowing what the commercial CPMS market can now offer, would you make the same choice?
If the evaluation reveals a platform that has drifted from its original purpose, the Proof of Concept is where that conversation starts: your architecture, your team’s current workload, your specific capability gaps, mapped against what a transition would look like in practice.
Could your board articulate, today, the specific strategic assumption your in-house platform encodes, and would you make that assumption explicitly if asked to?
For the supporting analysis your board may want to review:
The Case for Building Your Own CPMS Has Expired — the full strategic argument: how the conditions that made in-house CPMS rational have shifted, and the category transition analogy that frames what is happening now.
The In-House CPMS Costs Nobody Talks About — the costs that do not appear in any budget line, including the deferred roadmap, knowledge concentration risk, and the compounding gap between an in-house operator and one running on a commercial platform.
