Help more fleet customers make electric work, and explore how far each deployment could go. TOGL is developing depot flexibility software to reduce charging costs, make better use of existing connections and keep vehicles ready for their shifts. A stronger depot business case could give you more opportunities to sell.
Two ways to grow the opportunity
A small initial order may fit a depot’s supply. The next trucks can expose a costly connection upgrade or an energy bill that holds back the investment. The customer can want your truck and still struggle to justify the project.
The vehicle conversation
Could work
Needs work
Needs work
Needs work
Needs work
Not yet
Where the routes, power and costs line up, a deployment may be straightforward. Other customer opportunities remain difficult to progress.
The vehicle + energy conversation
Could work
Could work
Could work
Could work
Needs work
Not yet
A revised charging plan could improve the economics at some amber sites. That gives you a reason to reopen the conversation with those operators.
Illustrative customer options, not a forecast of sales or conversion rates. Some constraints remain. TOGL cannot provide missing power or make every investment viable.
Grow the opportunity at each depot
Before assuming the next trucks need a larger connection, explore the available charging window. The aim is to fit more vehicles around the same supply and their next shifts.
See how scheduling can make better use of the connection you already have.
Three trucks charge together. The other three bays are empty.
BEFORE / CHARGING ON ARRIVAL
Three trucks charging together use the available connection capacity. Spare bays do not mean spare power at that moment.
AFTER / CHARGING TO A PLAN
Six trucks charge in pairs across the available window. More energy is delivered before departure, with a lower peak on the same connection.
THE CHARGING WINDOW
Readiness shapes the plan.More vehicles can fit only where their energy needs, charging rates and time on site allow.
This is a conceptual comparison, not a pilot result or a capacity assessment. Both states show the same six suitable existing charging bays, depot, grid connection, background site load and available charging window. Before: three trucks charge together at the connection limit, with three bays empty. After: six trucks charge in three successive pairs below that limit. Each truck has the same illustrative energy need and charging rate, so the larger fleet receives twice the energy over three times the active charging period. This is a simplified example, not a claim that scheduling doubles capacity at every depot. Real schedules depend on vehicle energy needs, departure times, charger control, connection capacity and changing site load. No solar generation, storage, export or financial return is assumed.
The conversation now includes when energy is bought, how the connection is used and how charging fits the work. Planned grid flexibility could add value where eligible. It does not need to carry the initial investment case, and does not imply exporting energy from the battery.
Move charging into lower-cost hours where the shift allows.
Share available power as vehicle needs and site demand change.
Adjust eligible charging for potential income, with the next shift taking priority.
PlannedWhy we want to work with your technical team
We want to explore supported API access with you. Vehicle information, combined with the operator’s routes, departure times, tariff and site capacity, helps establish what a useful charging plan could deliver.
Vehicle + depot information
Understand the energy requirement
TOGL charging plan
Work within agreed limits
Pilot evidence
Measure cost and readiness
Vehicle + depot information
Understand the energy requirement
TOGL charging plan
Work within agreed limits
Pilot evidence
Measure cost and readiness
Explore battery state of charge, usable capacity, charging status and energy-use history where available. Agree freshness, permissions and the models covered. Route plans and operating requirements also come from the fleet.
Assess supported start, stop or rate requests through the appropriate vehicle or charging interface. These are control permissions, separate from read access. Availability and behaviour need validation for each integration.
Scope authorisation, operator consent, data handling, command limits and monitoring with your team. Agree tests for lost connectivity, overrides and recovery. Vehicle protections remain constraints of the design.
Proposed technical scope, not a claim that every vehicle exposes these interfaces. eHGV support depends on the interfaces available for the chosen model. Read our security approach.
Start with evidence
Identify a deployment held back by charging or connection costs. Agree what would make the case stronger.
Review the APIs and control paths. Agree a comparison for energy costs, peak demand, readiness and exceptions.
Use the evidence to assess more trucks or further depots. Keep capital benefits, recurring savings and planned income separate.
Current & roadmap
Capability
Status
Notes
Supported passenger vehicle integrations
Supported OEM brands via integration partners. Current list available on request.
Fleet charging intelligence
Built around operational guardrails and charging context
Depot optimisation
Depends on site data, vehicle data, and charging data
Grid connection intelligence
Substation headroom, vehicles supported before upgrade, and how much of that upgrade load management can defer
eHGV support
In active development for depot orchestration. Vehicle data access depends on OEM API availability
Bus support
Depends on OEM API availability and heavy vehicle integration maturity
Flexibility market participation
Depends on market access, asset eligibility, and aggregator relationships
Vehicle-to-grid (bidirectional) flow
Architected for, not sold. Gated on vehicle availability, charger certification, and market access
Bring a vehicle model, a customer scenario and the team that owns API access and charging behaviour. Together we can establish what a pilot would need and what it could demonstrate.
Start a partnership conversationFAQ
TOGL is building depot flexibility software to help manufacturers explore more viable fleet customers and potentially larger deployments. A different charging plan may improve charging costs and connection use while keeping the next shift at the centre of the plan. Depot optimisation and eHGV support can be assessed through scoped pilots. The commercial opportunity must not be treated as a guarantee of additional vehicle sales.
TOGL accesses vehicle data through integration partner APIs rather than by fitting hardware, so what is available for a given model depends on what the manufacturer exposes. Supported passenger vehicle integrations are live and the current brand list is available on request. For electric HGVs, support is assessed through a scoped pilot; bus support is planned. In both cases, vehicle data access depends on manufacturers making an API available for those models.
TOGL sells no vehicles, no charging hardware and no public charging network, and is built to sit underneath a manufacturer's customer relationship rather than alongside it. One of the partnership models TOGL discusses is a white-label or embedded experience, where the orchestration layer sits inside a manufacturer's existing customer digital experience. Where a manufacturer already runs its own energy proposition, the boundary between the two is agreed as part of the partnership rather than assumed.
TOGL starts an OEM engagement with a vehicle model, a relevant customer scenario and a conversation with the team responsible for API access and charging behaviour. The manufacturer, TOGL and fleet operator agree the integration scope, operating limits and measures for the pilot, including charging cost and departure readiness. TOGL responds to enquiries within two working days.
TOGL treats reading vehicle data and requesting charging actions as separate permissions. A proposed eHGV integration needs assessment of the supported interfaces, authorisation, command limits and vehicle protections. Start, stop or rate requests are explored only where supported, with override, connectivity and recovery behaviour agreed and tested as part of the pilot.