Energy · Charge point management and payment back ends (CPMS)
The long tail fills your inbox. The top tier pays.
You sell charge point management, payment or roaming back ends to charge point operators. Small site hosts send most of the demo requests and buy self-serve. The revenue sits with large networks that tender formally and want a live migration of their own scale.
- Pricing (top-tier networks)
- Per socket, plus fees
- Sales cycle (large networks)
- 3–18 months, about 9 Illustrative
- Buying group
- 6–9 people Illustrative
Updated 5 October 2026 · Based on Panelhop research, October 2026
At a large network re-platforming its back end6–9 people Illustrative
The short answer
How do CPMS vendors sell to charge point operators?
Charge point management system (CPMS) and payment back-end vendors sell to large EV charge point operators through formal tenders, where proof of a comparable migration counts heavily. Buyers range from specialist networks to the charging arms of oil majors and energy suppliers. The EU’s AFIR card payment deadline and back-end consolidation open most windows, while small site hosts buy self-serve.
Charge point management and payment back ends (CPMS) · How a deal really moves
AEs work site hosts that buy self-serve. Tenders want a same-scale migration. Yours is still running. The same pipeline, tiered by network size. Inbound routed by fit, and security opened at requirements.
One large charge point network, 6–9 people and an estimated 3–18 months, about 9 months, from first signal to signature.
What opens a deal
- AFIR card payment retrofit: Deadline · EU
- AFIR data and price duties: Regulation · EU
- Back-end re-platforming: Technology
- CPMS provider exits: Technology
- Network acquisition: Consolidation
Signal Desk · weekly: In-market accounts, scored and mapped
Your buyer and who decides
A charge point operator
Specialist network or a major’s charging arm
Top 148 run just over half of German stations
Panel Check · coverage baselined
- Head of e-mobility, can Veto: A vendor that is acquired, cuts the product or fails.
- Finance, can Veto: Per-socket fees that scale faster than revenue.
- Procurement, can Veto: Having to justify a single source.
- IT and architecture, can Veto: Platform outages that stop charging sessions.
- OT and IT security, can Veto: A supply-chain attack through a software provider.
- Head of charging ops: Being blamed for a missed AFIR deadline.
How the deal moves
Targeting
- Where it stalls
- Small site hosts fill your AEs’ week
- With Panelhop: Leak Fix
- Operators tiered by network size, and inbound routed by fit to an owner
First meeting
Requirements Typical time: 1–3 months
Tender Typical time: 1–4 months
- Where it stalls
- No live migration of their scale to show
- With Panelhop: Leak Fix
- A qualification model weighs network size and your same-scale migration
Security review Typical time: 1–3 months
- Where it stalls
- Charger security reviewed after the yes
- With Panelhop: Leak Fix
- The security thread opens at requirements, with status on the deal
Commercial close Typical time: 1–3 months
Migration
- Where it stalls
- The last network you won is still migrating
- With Panelhop: Leak Fix
- A handoff document from the deal: chargers, countries and dates as sold
Expansion
Panel Ops · monthly: Scores and plays tuned against the baseline
Illustrative Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; Energiewende-Navigator; the services as described on the Services page. Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.
At a glance
| Pricing (top-tier networks) | Per socket, plus fees |
|---|---|
| Sales cycle (large networks) | 3–18 months, about 9 Illustrative |
| Buying group | 6–9 people Illustrative |
| Motion | Formal tender at large networks, self-serve for small site hosts |
Source: Panelhop research, October 2026. Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.
The leak starts in the inbound queue.
Where do sales pipelines leak for CPMS vendors?
CPMS vendors’ sales pipelines leak where inbound from small site hosts crowds out the large networks, and where the AFIR payment pitch outlives the deadline. Revenue sits with networks that run formal tenders, while most demo requests come from small site hosts.
Where the pipeline leaks: 5 points across 8 stages.
Small site hosts eat your account executives’ week
- What you see
- Account executives work demo requests from small hosts while top-tier networks see no meetings.
- Why it happens
- No tiering by network size, share of DC fast chargers or country footprint, and inbound routed by hand instead of by fit.
Stage Targeting
Operators on a discontinued platform tender before you call
- What you see
- Operators on a discontinued platform run a tender before you know they are looking.
- Why it happens
- No alerts on platform exits, product cuts or insolvencies, and no list of the operators affected.
Stage Targeting
Your AFIR pitch reaches operators that already chose
- What you see
- Prospects say they already chose a retrofit partner, and campaigns keep selling compliance.
- Why it happens
- Campaigns run on a flat calendar instead of each operator’s retrofit status.
Stage First meeting
Your newest network is still migrating at the next tender
- What you see
- Signed networks are still migrating when the next tender asks for a live reference.
- Why it happens
- Migration effort underestimated in the sale, and no handover from onboarding to expansion.
Stage Migration
Customers add chargers and buy modules elsewhere
- What you see
- Customers add chargers and countries, and buy payment or analytics modules elsewhere.
- Why it happens
- No footprint, acquisition or regulatory triggers feeding expansion plays.
Stage Expansion
AFIR dates and platform exits start CPMS tenders.
What makes a charge point operator change its back end?
AFIR deadlines, back-end consolidation, platform exits and acquisitions open most CPMS windows at charge point operators. Each leaves a public trace before the tender.
The 5 events that open or close the window for a deal.
Regulation
AFIR card payment retrofit
- What happens
- AFIR requires paid public charging points of 50 kW or more on the TEN-T network or at safe and secure parking to accept card or contactless payment from 1 January 2027.
- Where to spot it
- The Bundesnetzagentur charging register, filtered for older fast chargers, and national access points.
- Window
- Operators retrofitting points built before 13 April 2024 buy before 1 January 2027; back-end consolidation and data work continue through 2027.
Regulation
AFIR data duties
- What happens
- Operators must publish static and dynamic data on their public charging points, including ad hoc prices, for national access points: by API since 14 April 2025, and in DATEX II format since 14 April 2026.
- Where to spot it
- National access points and operators’ published data feeds.
- Window
- Operators with incomplete or non-compliant data feeds need back-end and data work.
Technology
Back-end re-platforming
- What happens
- A large network that has grown through new sites and acquisitions moves its chargers from several back ends onto one CPMS.
- Where to spot it
- Trade press on back-end migrations, and job ads for CPMS migration, OCPP or roaming roles.
- Window
- Signals appear months before a tender, and the migration then runs for several quarters.
Technology
Platform discontinuation
- What happens
- A CPMS provider exits, is sold or shuts its platform, and the operators on it must migrate, often at short notice.
- Where to spot it
- Trade press, insolvency notices and operators’ own announcements.
- Window
- Opens at the announcement; operators look for a back end that migrates their chargers without replacing them.
Consolidation
Operator M&A
- What happens
- A network acquires another and must run both on one back end.
- Where to spot it
- Deal announcements and charging trade press.
- Window
- Selection starts at or just after completion.
Operations champions the CPMS. IT, security and finance can veto.
Who decides on a new CPMS at a charge point operator?
At a large charge point operator, the head of e-mobility or the operator’s managing director signs off a new back end, and the head of charging operations champions it. IT, security, procurement and finance can each stop it. Small operators and site hosts often decide with far fewer people.
At a large network re-platforming its back end, 6–9 people sit on the panel and 5 seats can stop the deal.
At a large network re-platforming its back end: 6–9 people
Head of e-mobility or managing director
Can Veto
Head of E-Mobility · Managing Director
- Cares about
- A back end that stays up through migration and stays supported for the full contract.
- Worries about
- Choosing a vendor that is acquired, cuts the product or fails.
Head of charging operations
- Cares about
- Workflows proven on their own chargers and scenarios.
- Worries about
- Being blamed for a missed AFIR deadline.
Network operations centre
NOC Operator · Control Room Operator
- Cares about
- Reliable real-time data and fewer manual steps.
- Worries about
- Workload spikes during migration.
IT and architecture
Can Veto
CIO · IT Director · Enterprise Architect
- Cares about
- OCPP, roaming and payment integration, with data portability.
- Worries about
- Platform outages that stop charging sessions.
Information and OT security
Can Veto
CISO · OT Security Lead
- Cares about
- IEC 62443 evidence for charger-connected software and NIS2 supplier clauses.
- Worries about
- A supply-chain attack through a software provider.
Procurement
Can Veto
Procurement Manager · Category Manager IT
- Cares about
- Comparable offers in a formal tender they can defend.
- Worries about
- Having to justify a single source.
Finance
Can Veto
CFO · Head of Controlling
- Cares about
- Total cost over the term, set against charging revenue.
- Worries about
- Per-socket fees that scale faster than revenue.
You sell the back end every charging session runs on.
What do CPMS vendors sell, and to whom?
CPMS and payment back-end vendors sell the software that runs chargers, payments, pricing and roaming to the operators of public charging networks. Germany alone has 12,914 registered operators, yet in April 2026 the top 148 ran just over half of all public charging stations. The long tail of small site hosts is mostly too small for an enterprise deal.
What vendors of this type sell
- Charge point management systems for public networks
- Ad hoc card and contactless payment back ends
- Roaming connections and settlement with mobility service providers
- Smart charging and energy management across sites
- Charge point data feeds for national access points
- Back-end migration without replacing chargers
Which energy companies buy it
- Specialist charging networks
- Charging arms of oil majors and energy suppliers
- The top tier of Germany’s 12,914 registered operators
- Networks consolidating back ends after acquisitions
Large networks buy through a formal tender.
How does a charge point operator buy a CPMS?
A large charge point operator usually buys a CPMS through a formal tender, then migrates its chargers, roaming and payments over several quarters. By our estimate, the cycle typically runs 3–18 months, about 9 months, while small site hosts buy self-serve in weeks.
Stage by stage: what you do, what the energy company does, and what changes at the 4 stages where deals stall.
| Stage | What you do | What the energy company does | Today | With Panelhop |
|---|---|---|---|---|
| Targeting | Works the inbound queue, where small site hosts outnumber large networks. | A back-end contract end, a platform exit, an acquisition or the AFIR retrofit exposes the need. | Inbound from small site hosts worked first. Stalls: The long tail fills the queue. Small site hosts send most demo requests but buy self-serve, so account executives spend their week on accounts too small for an enterprise deal. | Operators tiered by network size, share of DC fast chargers and country footprint, and inbound routed by fit to a named owner. Leak Fix We build the fixes |
| First meeting | Demos the platform to the head of charging operations. | Tests charger compatibility, roaming connections and payment flows. | A compliance pitch on a flat calendar. | Scored accounts with the trigger that fired, such as a platform exit or retrofit exposure, and a brief your rep approves. Signal Desk In-market accounts, weekly |
| Requirements Typical time: 1–3 months | Often hears of the formal selection only when the tender is published. | Lists chargers, roaming partners and payment providers, and builds a long list. | Tenders found when they are published. | Back-end migrations, platform exits and CPMS hiring flagged weekly, with the buying group mapped. Signal Desk In-market accounts, weekly |
| Tender Typical time: 5 weeks to 4 months | Answers a formal tender and shows a live migration of similar scale. | Scores the bids and invites a shortlist to demos. | Every tender answered, and losses blamed on price. Stalls: No migration of the same scale. Large networks weigh proof of a comparable live migration heavily, so a vendor without one rarely makes the shortlist. | A written qualification model, fit plus engagement, that weighs network size and whether you hold a live migration reference of that scale. Leak Fix We build the fixes |
| Security review Typical time: 1–3 months | Answers charger security, hosting and NIS2 questions. | IT and security review IEC 62443 evidence, NIS2 clauses and data hosting. | Security questions arrive after the verbal win. Stalls: Charger security reviewed last. Software that controls chargers and payments meets IT and security late, and a vendor without a security pack waits for weeks. | Stage exit criteria that open the security thread at requirements and track review status on the deal. Leak Fix We build the fixes |
| Commercial close Typical time: 1–3 months | Negotiates per-socket, platform and transaction fees. | Finance models the fees against charging revenue as the network grows. | Close dates move with no recorded reason. | Forecast accuracy reported monthly against the baseline, with the deal risk score and slipped close dates reviewed against each network’s finance approval. Panel Ops We run it monthly |
| Migration | Moves chargers, roaming connections and payment flows to the new back end. | Migrates the network in waves while sessions and payments keep running. | What the tender promised lives in a folder. Stalls: References stuck in migration. A migration that runs for several quarters leaves the next tender without a live reference of the same scale. | A handoff document from the deal, so migration inherits the chargers, countries and dates as sold. Leak Fix We build the fixes |
| Expansion | Adds chargers, countries and modules such as payment, analytics or smart charging. | Adds sites and countries, and reviews the back end after an acquisition. | New chargers and countries at customers found by chance. | New sites, countries and acquisitions at your customers flagged as signals and reviewed in the weekly signal review. Panel Ops We run it monthly |
Route the long tail away from your account executives.
How does Panelhop change a CPMS vendor’s pipeline?
Panelhop tiers operators by network size and routes the long tail away from your account executives, so they work the networks that tender. A Panel Check (GTM audit · 2–3 weeks) baselines the pipeline from your CRM first.
What we baseline and report
- Share of top-tier operators held, tiered and covered in the CRM, against the baseline
- Inbound from small site hosts routed away from account executives, against the baseline
- Roles engaged per open opportunity, with IT, security and finance included
Other vendor types in energy.
What other vendors sell to energy companies?
The same energy companies buy from these vendor types too, through different panels and pipelines.
- Vendor type
Renewable and storage portfolio platforms
SCADA, asset performance, portfolio software and storage optimisation for owners of wind, solar and battery storage portfolios.
Read the pipeline - Vendor type
ETRM/CTRM for energy traders
ETRM/CTRM platforms plus REMIT and EMIR trade reporting for energy traders, producers’ marketing arms and supplier procurement desks.
Read the pipeline - Vendor type
Methane measurement and MRV
Methane sensors, aerial and drone surveys, emissions models and MRV software for oil and gas operators facing OGMP and EU rules.
Read the pipeline - Vendor type
Billing and customer platforms for energy retailers
Billing, meter data, tariff and customer platforms for competitive electricity and gas suppliers in GB and Europe.
Read the pipeline
The words your buyers use, defined.
What do terms like “CPMS” and “OCPP” mean?
Plain definitions of the terms that come up when you sell charge point management and payment back ends (CPMS) to energy companies.
- CPMS
- Charge point management system: the back-end software a charge point operator uses to run its chargers, payments, pricing and roaming across the network.
- OCPP
- Open Charge Point Protocol: the open standard chargers use to communicate with a CPMS. It lets an operator change back end without replacing its chargers.
- Roaming
- The connections and agreements that let drivers using another provider’s app or card charge on an operator’s network, settled between the operator and mobility service providers.
- Ad hoc charging
- Charging without a contract or app, paid on the spot. AFIR requires it at every public charging point, and card or contactless payment at many fast chargers.
- National access point
- The national platform through which charge point operators make data on their public charging points available, such as location, availability and price, as AFIR requires.
- DATEX II
- The European data standard for road traffic and travel information, used to publish charge point data such as location, availability and price to national access points.
Answers before your next energy company deal.
What do vendors of charge point management and payment back ends (CPMS) ask about selling to energy companies?
How do you sell to charge point operators before the AFIR deadline?
Selling to charge point operators before the AFIR deadline starts with the operators it covers. AFIR requires paid public points of 50 kW or more on the TEN-T network or at secure parking, including those built before 13 April 2024, to accept card or contactless payment from 1 January 2027. Track each operator’s retrofit status from the charging register, reach the ones still exposed and move the pitch to back-end consolidation and data duties once the date passes.
How do large charge point operators choose a CPMS?
Large charge point operators usually choose a CPMS through a formal tender. Proof of a comparable live migration, OCPP and roaming support, payment integration and a documented migration plan count most. The tender usually follows a platform exit, an acquisition or a decision to consolidate back ends.
Who can veto a CPMS purchase at a charge point operator?
IT, information and OT security, procurement and finance can each veto a CPMS purchase at a large charge point operator. The head of e-mobility or the managing director signs off the new back end, and the head of charging operations champions it. By our estimate the buying group has 6–9 people, while small operators and site hosts often decide with far fewer.
How long does it take to sell a CPMS to a charge point operator?
Selling a CPMS to a large charge point operator typically takes 3–18 months, about 9 months, by our estimate. A formal tender, scripted demos, security review and finance approval set the pace, and the migration then runs for several quarters. Small operators and site hosts buy self-serve in weeks. The AFIR deadline compresses decisions for operators still exposed to it.
How should CPMS vendors route inbound from small charge point hosts?
CPMS vendors should route inbound by fit as soon as it arrives: small charge point hosts to a self-serve or low-touch path, and top-tier networks to an account executive with a named owner. Tier operators by network size, share of DC fast chargers and country footprint first. Targets set on inbound volume flood the sales team with the long tail and starve work on the networks that tender.
How do CPMS vendors expand within charge point operator accounts?
CPMS vendors expand within charge point operators as the network adds chargers, sites and countries, and as the operator adds payment, analytics, smart charging or energy management. A structured expansion motion tracks each customer’s footprint and acquisitions and plans plays before a rival is invited in. A customer still migrating rarely buys more, so expansion starts with a migration that finishes on time.
Where the numbers come from.
Sources
Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.
- EUR-Lex, Official Journal of the European Union, Regulation (EU) 2023/1804 on the deployment of alternative fuels infrastructure (AFIR) (2023)
- electrive.net, reporting Bundesnetzagentur Ladesäulenregister data, Deutschland überschreitet Marke von 212.000 öffentlichen Ladepunkten (2026)
- Panelhop, Services (2026)
- EUR-Lex, Official Journal of the European Union, Commission Implementing Regulation (EU) 2025/655 on the availability and accessibility of data on alternative fuels infrastructure (2025)
- Energiewende-Navigator, Ladeinfrastruktur in Deutschland 2026: die Karte hinter den Schlagzeilen (analysis of the Bundesnetzagentur Ladesäulenregister, April 2026) (2026)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers for charge point management and payment back ends (CPMS) in energy, from public sources. Vendor names are not published.
Find where your pipeline to energy companies leaks.
