EV Charging Management Software: Build a CPMS, or Stay on AMPECO, Monta and EV Connect
Hardware mix decides this, not charger count. Under roughly 50 chargers on one or two brands, standard public tariffs, no roaming settlement and no federally funded sites, buy: AMPECO, Monta or EV Connect will serve you and the subscription is cheaper than owning a platform.
On this page
Hardware mix decides this, not charger count. Under roughly 50 chargers on one or two brands, standard public tariffs, no roaming settlement and no federally funded sites, buy: AMPECO, Monta or EV Connect will serve you and the subscription is cheaper than owning a platform. The build case turns when the platform becomes your profit and loss rather than a convenience, meaning a multi vendor fleet, tariffs the vendor cannot express, or demand charge exposure.
When is off the shelf genuinely the right call here?
Buy if you run under roughly 50 chargers on one or two hardware brands, sell on standard public tariffs, do no roaming settlement and have no federally funded sites. AMPECO, Monta and EV Connect are real products maintained by people who understand this domain, and at that scale the subscription is cheaper than owning a platform and considerably cheaper than owning one badly. Spend the difference on chargers.
Buy also if your constraint is commercial rather than technical. An operator whose real problem is site acquisition, utility interconnection timelines or capital access will not be helped by a custom charge point management system, and we would say so on the call. Software does not shorten a utility queue.
There is a smaller tier below both, and it is worth naming so you do not overpay for it. A read only dashboard that polls one manufacturer's cloud interface and shows session and status data in your own branding is $20,000 to $40,000. It is useful, it is not a charge point management system, and it will not survive the day you add a second brand. If someone quotes a full platform at that number, they are quoting the dashboard.
The test that settles it: count your hardware brands and count the tariff shapes you actually sell on. Two brands and one tariff means a packaged product fits you properly, and most operators discover that three of their five tariff variants exist because nobody ever removed them.
When does a custom build actually pay off?
Two or more of these need to hold, and none is a screen count argument.
You run a multi vendor fleet you cannot consolidate onto one certified hardware list. You buy on price and lead time, so you have Alpitronic and Kempower on the fast sites, Autel and Wallbox on the slower ones and legacy ABB cabinets still earning, and each vendor shipped you into its own cloud dashboard. Your operations manager keeps six browser tabs open to see one network.
Stacked per charger and per transaction fees now cost more than an amortised build at your volume. Your tariffs or fleet contracts cannot be expressed in the vendor's rating model, meaning idle fee grace rules, negotiated corporate rates, time of use bands or a demand charge pass through to fleet customers. You want to settle roaming on your own contract terms rather than through a templated arrangement. Or you have demand charge exposure that generic smart charging will not manage, where four cars pulling full power on one transformer can set a monthly peak whose charge dwarfs the energy you sold.
The structural reason underneath all of them is who terminates the connection. Once your own backend holds the open channel from each charger, you control the charger state model, you can send a reset or a charging profile on your own terms, and every downstream capability becomes possible. Until then you are reading somebody else's summary of your own network, and you cannot patch a vendor quirk on Monday when a firmware update broke metering on Tuesday.
How do they compare on the things that matter in this industry?
- Hardware normalisation. Protocol conformance is not uniformity. One vendor reports energy in watt hours and another in kilowatt hours, one sends a fault with a manufacturer specific code you decode from a document and another simply stops sending heartbeats. A subscription platform onboards you to its own backend, which is progress, and still boxes you in by its certified hardware list.
- Fault to remediation. A packaged dashboard shows status. Fingerprinting a fault against a known error library and firing a reset, a connector release or an availability change before dispatching a technician is a different loop, and it is the difference between a ten second fix and a ninety minute drive each way.
- Rating and reconciliation. A session export is not a ledger. Matching charge detail records against processor payouts and inbound roaming settlements is where disputed sessions get recovered rather than quietly written off.
- Uptime measurement. Federally funded sites carry a 97 per cent uptime minimum, and the figure has to be computed on the programme formula with the correct excluded outage causes rather than on your own definition of available.
- Load orchestration. Generic smart charging does not know your transformer rating, your utility rate schedule or your on site battery. Per connector setpoints against a fifteen minute demand window do.
- Availability bar. A charger that loses its connection is a dead charger, so the connection tier needs redundancy a normal web application never needs.
What does total cost of ownership look like at your scale?
In Digital Heroes delivery experience a focused first release is $60,000 to $130,000 over 12 to 16 weeks, covering live protocol ingestion across your hardware, one clean billing flow and an operations dashboard with fault alerting. A full platform with roaming, smart charging, payment reconciliation and compliance reporting is $150,000 to $400,000 phased over 6 to 12 months.
An operator with 300 chargers across 55 sites and five hardware brands, certifying three that cover roughly 80 per cent of connectors, prices out at $118,000: the protocol backend with a canonical site, charge point, connector and session model $32,000, three hardware adapters at $8,000 each $24,000, the operations console with live network view and fault fingerprinting $18,000, the auto remediation playbook with ticket handoff on failure $9,000, the rating engine plus payment processor integration $21,000, the reconciliation ledger with variance flagging $8,000, and infrastructure with a redundant connection tier and load testing $6,000. The two remaining brands cost about $16,000 to add later.
Running cost is 15 to 20 per cent of build a year, so $18,000 to $24,000 on that example. Hosting sits higher than a normal application because every charger holds a persistent connection that never scales to zero. Firmware drift is the recurring engineering line, because a manufacturer update that changes metering behaviour will break an adapter, and that is the nature of the category rather than a defect.
Compare it properly: take the per charger monthly figure on your renewal, multiply by charger count and twelve, add the transaction component and anything billed separately for roaming, reporting or extra users, then set that against build plus 15 to 20 per cent.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is scope discipline inside the build rather than keeping a platform beside it, and it is what turns a $250,000 wish list into a $118,000 system the operations team runs daily.
Certify the two or three brands that carry most of your sessions and leave the long tail on their vendor portals for another quarter. This is the single largest saving available and it costs you almost nothing operationally, because the brands you exclude are usually the ones with the fewest chargers.
Keep your existing payment processor. Rebuilding the payment relationship at the same time as the platform doubles the number of things that can go wrong on launch weekend, and processors are genuinely interchangeable later.
Defer roaming. If under a tenth of your sessions arrive through a partner app, the interoperability layer can wait for phase two, and hub onboarding runs on the hub's calendar rather than yours so it can proceed in parallel with the build instead of blocking it.
Take manual quarterly compliance reporting for the first two quarters. It is a day of somebody's time twice, against a five figure line item, and by the second quarter you will know exactly which fields the state actually asks for.
Then sequence the release itself. Ingestion and the operations console first, because that stops the six tabs problem before any money moves through the system. Rating, payment and reconciliation second, run in shadow mode against your existing invoicing for two weeks before cutover.
Which should you choose, by operator size and stage?
Under 50 chargers, one or two brands, public tariffs, no roaming, no funded sites: buy. Revisit when a third brand arrives or a fleet contract needs a rate your platform cannot express.
Operator whose only complaint is visibility across vendor portals: build the read only dashboard at $20,000 to $40,000, or price your existing vendor's reporting tier against it. Be clear that it will not survive a second brand, and treat it as a stopgap you have chosen rather than a platform you have bought.
Around 300 chargers on three or more brands with real fault volume: build the focused first release at roughly $118,000, keep the payment processor, defer roaming and compliance reporting. This is the clearest case in the category and it usually crosses over against a subscription inside two to three years.
Operators with federally funded sites: build the remediation loop before the reporting. Hitting a 97 per cent uptime minimum is an operations problem and measuring it is a reporting problem, and you need both, but only one of them earns the reimbursement.
Operators with several fast chargers behind one transformer: build, and put site level load management in scope early. A demand peak set by four simultaneous sessions can erase a site's margin, and generic throttling either leaves capacity unsold or fails to protect the peak.
Anyone signing fleet or business to business contracts with negotiated rates: build the rating engine, because those rules have to sit alongside your public tariffs so a partner session rates and reconciles exactly like a direct one.
If you want a second opinion before signing anything, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
Frequently asked questions
What does it cost to migrate off AMPECO or Driivz without downtime?
Budget it as a real phase rather than a cutover weekend. The pattern that works is repointing a subset of chargers at the new endpoint, verifying that sessions, billing and faults match the incumbent, then moving sites in waves, which means running both platforms in parallel for a period.
The two cost drivers are historical charge detail record import, which keeps reporting continuous, and the parallel subscription you keep paying while the waves complete. Neither is large next to the build, and neither is zero.
What happens if our CPMS vendor raises per charger pricing?
Model it at the charger count you expect in three years rather than today, because the per charger model is exactly what scales against you as you grow. Add the transaction component and anything billed separately for roaming, extra users or reporting.
Set that against build plus 15 to 20 per cent annual running cost. A $118,000 first release typically crosses over inside two to three years at 300 chargers, and the gap widens because your own platform does not scale with charger count the same way.
How long does the first release take?
Twelve to sixteen weeks for a release the operations team uses daily, with two to three weeks of discovery in front of it. Weeks one to eight cover ingestion and the operations console, weeks nine to sixteen cover rating, payment and reconciliation.
The schedule risk usually sits outside engineering. Getting sample protocol traffic from every brand and access to test units at a live site is a scheduling problem with your own operations team, and it is worth starting before kickoff.
Is Monta enough if we run 80 chargers on two brands?
Probably, and the question is tariffs rather than charger count at that size. Standard public pricing on two brands with no roaming settlement is exactly the shape those products were built for, and you should keep the money.
The case changes when a fleet contract needs an idle fee grace rule or a demand charge pass through the rating model cannot express, or when a third brand arrives and you are back to reconciling exports by hand.
Why does each additional charger manufacturer cost so much?
Because protocol conformance is not uniformity. One vendor reports energy in watt hours and another in kilowatt hours, one sends a fault with a manufacturer specific code and another simply stops sending heartbeats.
Each brand needs an adapter mapping its states, units and error codes into your canonical model, plus field testing against real units. Budget roughly $8,000 per additional brand, and expect fast chargers to cost more to profile than slower units because their fault surface is larger.
Can we phase the spend instead of funding the whole platform?
Yes, and phasing is the normal shape here. Release one is ingestion plus the operations console, which stops the six vendor tabs problem before any money moves through the system. Release two is rating, payment and reconciliation, run in shadow mode against your existing invoicing for two weeks before cutover.
Roaming, smart charging and compliance reporting should be scoped after three months of your own data, because operators routinely reprioritise once they can see which sites actually carry demand charge exposure.
What does roaming add, and can it wait?
It means exposing interoperability endpoints for locations, sessions, charge detail records, tariffs and tokens, publishing your tariffs, authorising partner tokens and settling inbound records through the same rating engine as your direct sessions. As a scope block it belongs in the upper band rather than the first release.
The part buyers underestimate is commercial onboarding with a hub such as Hubject or Gireve, which runs on their timeline. Start that conversation before the engineering, not after.
Do we own the code and the session data if an agency builds this?
You should own the source code, the database schema and the infrastructure accounts, agreed in writing before kickoff. At Digital Heroes the client owns it from the first commit.
That ownership is the structural difference from a subscription platform, where your session history and your roadmap both sit with the vendor. Your charge detail records are the record behind every invoice you have issued, so treat access to them as a contract term rather than an assumption.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Eleanor.
Senior Partnerships Manager · New-york · 5 posts on the site
Published · Last updated .
