Skip to main content

Pricing

Pricing follows your deployment, not a fixed tier.

The factors below shape what a ChargeControl deployment actually involves, which is why pricing is confirmed directly rather than published as a flat rate.

ChargeControl finance overview for charging activity
Financial controlCosts, allocation and exports

How pricing actually gets confirmed

A short scoping conversation covers the factors below before any number is discussed.

  1. Confirm your charging domains

    Home, public, workplace, and depot charging each bring different data and policy needs into scope.

  2. Confirm scale

    Site count, driver count, and vehicle count shape what a deployment actually involves.

  3. Review integration needs

    CRM, ERP, billing, and reporting connections affect setup and ongoing scope.

  4. A tailored proposal

    Once scope is clear, you receive a proposal that reflects your actual deployment rather than a generic tier.

What to have ready before that conversation

These details let a specialist scope pricing accurately on the first call.

  • Your domain mix

    Which combination of home, public, workplace, and depot charging is involved.

  • Rollout scale

    An approximate number of sites, drivers, or vehicles, even as a range.

  • Reimbursement needs

    Whether ChargeBack settlement across home or workplace charging is part of the scope.

Talk pricing directly

A demo is the fastest way to connect these factors to your actual deployment, and a callback works if you have questions first.

Why there is no rate card on this page

ChargeControl does not publish prices, tiers, or discounts, because charging deployments vary too much for a flat number to mean anything useful. What actually shapes cost is your mix of charging domains, the scale of sites, drivers, and vehicles involved, the integrations you need into CRM, ERP, or billing systems, and whether reimbursement and settlement across home or workplace charging is part of the scope.

Confirming pricing means walking through those factors directly so a proposal reflects your deployment rather than a generic tier. A demo is the most efficient way to connect the platform to your specific setup, and a callback works well if you have scoping questions before booking time.