“Launch in 4-6 weeks” is the headline claim behind most white-label EV charging platforms, CarChargeOS included - and it's reasonable to want to know what that actually means before you sign a contract. Here's the real week-by-week path from kickoff to a live, branded network, and - just as importantly - what pushes a deployment past six weeks.
One clarification up front: 4-6 weeks describes a typical timeline for a standard deployment under normal circumstances, not a contractual guarantee. It assumes OCPP-compliant chargers already in the field, a merchant account or payment provider you can onboard quickly, and branding assets ready to go. Scope beyond that - custom integrations, hardware certification, on-premise infrastructure - extends the timeline, and any serious vendor should tell you that plainly rather than let the number do the selling.
What “launch” actually means
Launch isn't just “the software exists.” It means: your branded iOS and Android apps are live in the app stores, your first stations are onboarded and reporting real-time status, tariffs and payment methods are configured and tested, your team can see and operate the network from the console, and drivers can actually find a charger, start a session and pay for it under your name.
A typical six-week path
| Week | What happens |
|---|---|
| Week 1 | Kickoff, scoping and branding handoff - logo, colors, app name and store listing details; confirm charger inventory and payment provider. |
| Week 2 | Chargers connected to the platform and verified over OCPP; payment gateway / merchant account integration started; tariff structure defined. |
| Weeks 3-4 | Branded app build and review; tariffs, promotions and invoicing/VAT rules configured and tested against real session data; operator console access and roles set up for your team. |
| Week 5 | User acceptance testing on live stations, staff training on the operator console, and a pilot group of chargers goes live under your brand. |
| Week 6 | App store submission and release, remaining stations brought online, full rollout. |
What actually stretches the timeline
Most delays don't come from the platform - they come from dependencies outside it:
- Payment and merchant account approval. Bank and payment-processor underwriting can take longer than any part of the technical setup, and it's on their timeline, not the platform vendor's.
- App store review. Apple and Google review times vary, and a first-time developer account or a name/branding conflict can add review cycles.
- Chargers that aren't OCPP-compliant yet. Hardware that needs a firmware update - or replacement - to speak OCPP 1.6J/2.0.1 pushes the connectivity step out until that's resolved.
- Custom integrations. ERP, CRM or identity (SSO) integrations beyond the standard API/webhook set add a scoping and build phase of their own.
- On-premise or bring-your-own-cloud deployment. Provisioning your own infrastructure takes longer than a managed-cloud launch - see how deployment model affects launch speed.
- Migrating off an existing CSMS in parallel. Running a cutover from a live network adds data-migration and dual-running steps on top of a greenfield launch - see the migration guide for that path specifically.
What to have ready on your side
The fastest launches are the ones where these are settled before kickoff, not during it:
- Brand assets - logo, colors, app name and app store developer accounts.
- A payment provider relationship already in progress, or a clear decision on which one to use.
- An accurate list of existing chargers, their manufacturer/model, and current firmware.
- A first-pass tariff and pricing strategy - it can change later, but a starting point avoids stalling on it mid-build.
- Legal entity and tax details needed for invoicing (VAT/e-invoicing requirements vary by market).
Full suite means CSMS, sessions and tariffs, billing, and the branded driver app all launch together as one deployment - not four separate vendor timelines stacked end to end. See how those pieces fit together on the platform page, or the full comparison of build vs. buy vs. white-label timelines.
Frequently asked questions
Is 4-6 weeks guaranteed?
No - it's the typical range for a standard deployment under normal circumstances: OCPP-compliant chargers, a straightforward payment integration, and no custom scope. It's a planning benchmark, not an SLA; actual timelines are confirmed during scoping.
Can a pilot go live faster than the full rollout?
Often yes. A small pilot group of already-connected chargers can go live as soon as branding, tariffs and payments are configured - sometimes inside three weeks - while the app store release and remaining stations catch up on the standard timeline.
What's the single biggest thing that delays a launch?
Payment provider / merchant account approval, in most cases - it's a third-party underwriting process outside the platform vendor's control, so starting it in week one rather than waiting on it matters more than almost anything else on this list.