/// Emerging & Frontier
Mobile EV Charging
Bring the electrons to the vehicle. Route economics decide whether it works.
What the workspace runs
The ERP is not five pages. Every mobile ev charging workspace inherits the operating spine and adds what this industry actually needs.
Records the ERP keeps
- Service unit record: capacity, state of charge, availability
- Session record with kilowatt-hours delivered and duration
- Route with sequenced vehicles and time windows
- Fleet contract with availability and response terms
- Energy cost basis and margin per session
Workflows it ships with
- Request intake → route assignment → charging session
- Session metering with kilowatt-hours billed at contract rate
- Fleet depot programs with scheduled overnight service
- Event and emergency roadside charging deployments
Integrations wired first
- Fleet telematics platforms
- Energy suppliers and demand-response programs
- Mapping and routing APIs
- Stripe
The four numbers the owner checks
- Kilowatt-hours delivered per unit-day
- Cost per kilowatt-hour delivered including drive time
- Fleet contract share of revenue
- Unit utilization
Vision layer
Demand prediction and route optimization decide which vehicles to serve in what order to keep cost per kilowatt-hour viable.
/// Underneath every workspace
The part that is the same for everyone
The industry configuration sits on top of a platform that captures what you touch, indexes it without being told how, answers questions about it in plain language, and runs agents against it while you are doing something else. The same index holds the things in your week that are not business at all.
The second brain
Everything you touch gets captured, indexed and recallable in plain language, so remembering stops being a job you do.
- Put it in once
- The index builds itself
- Ask instead of search
- Decisions outlive the chat
- A briefing, not a dashboard
The connectors
Your mail, calendar, phone, files and logged-in accounts feed the same context. Nothing has to be re-entered to count.
- Mail, calendar and drive
- Forward it and forget it
- Your logged-in accounts, connected
- Calls and texts in the same record
- An API you can point anything at
- Bring your own assistantbuilding
The workforce
Agents that keep working when you close the laptop, on models you choose, with every step visible.
- Work that continues without you
- Your context is not one vendor's asset
- You can see what the agent is doing
The business
A CRM remembers people. This books the job, dispatches it, documents it, invoices it and settles it.
- Book it, dispatch it, prove it happened
- Get paid on the same record
- Marketing that reads your own records
- A site and a domain that stay yours
- It arrives already knowing your industry
- Everyone who touched the deal is on the record
The other half of your week
The obligations that are not business are still obligations. They belong in the same index, on the same calendar, out of your head.
- Your documents get the same index
- Nothing with a due date lives in your head
- One workspace, business and personal kept apart
- Hand the recurring parts to an agent
Who it is for
Segments
- Fleet operators without depot charging
- Apartment and workplace parking without infrastructure
- Events, dealerships, and roadside emergency service
What hurts today
- Session pricing that ignores drive time and energy cost basis
- Utilization too low to cover the capital
- No contract structure, so every session is a one-off
How it makes money
On-demand per-session charging
Fleet and depot service contracts
Event deployments and roadside emergency charging
Brand system
Explains kilowatt-hours delivered and cost per session honestly. Does not pretend this is cheaper than a wall charger.
frontiermobileenergeticroute-optimized