Simple Energy's Rs 1,750 Crore Raise and a New Plant: The Insurance Build for an EV Two-Wheeler Maker Scaling Up

In late September 2026, Inc42 reported that Simple Energy had raised about $180 million (Rs 1,750 crore) in an all-equity Series C led by the Dr. Arokiaswamy Velumani Family Office. The round takes the Bengaluru-based electric two-wheeler maker's total funding to about $264 million (Rs 2,530 crore), and the company has earmarked the money for a new manufacturing plant, higher output, distribution and R&D. Entrackr's quarterly tally, published on 1 October, ranked the $182 million Series C as the largest deal of Q3 2026, in a quarter when EV funding totalled $583 million.

The pace matters as much as the size. Startup Researcher noted that the round arrived roughly three months after a Rs 250 crore Series B, and that Simple Energy plans to grow from 80 sales outlets across 60 cities to 160-170 outlets by March 2027. That is a doubling of the retail and service footprint inside about six months, running in parallel with a new plant.

For an insurance buyer, this is the point where the risk profile changes category. An R&D-stage EV maker is mostly insuring prototypes, a pilot line, test equipment and a few founders' personal liability. A maker scaling to mass production is insuring a warehouse full of lithium-ion cells, an installed base of vehicles on Indian roads, a firmware stack that controls every battery pack in that base, and a dealer network acting in its name.

A note on scope: this post uses Simple Energy's announced plans as the example. We have no knowledge of the company's actual insurance programme, and nothing here describes or comments on it. The structure applies to any EV two-wheeler OEM moving from pilot to volume production.

The clearest recent illustration of mass-production risk comes from South Korea. On 16 August 2026, the Kyunghyang Shinmun reported that an analysis by the Seoul fire authority led to recalls of more than 6,000 electric two-wheelers from two companies. The investigators traced the issue to battery management systems that lacked adequate criteria for inter-cell voltage deviation, and to a possible lack of safety margin in the BMS protection parameters.

The insurance lesson is in the nature of the defect. As reported, it was not a bad batch of cells or a single assembly fault. It lay in the criteria and protection thresholds the BMS used, which means every unit carrying that BMS design shared the same exposure. A design or firmware decision made once in the R&D phase becomes a common-mode defect the moment production volumes ramp up.

Why this matters for an Indian OEM's programme

For an Indian maker, three consequences follow:

• The recall is sized to the installed base running the affected firmware, not to the number of fires that have actually occurred.
• An over-the-air fix may resolve the defect cheaply, but if the BMS hardware cannot support the corrected parameters, the campaign becomes a physical pack or board replacement.
• The root-cause finding (a parameter choice) sits squarely in design, which is where a product liability claimant will look first.

Whichever manufacturers were involved, it is the scenario an underwriter will have in mind when an Indian OEM asks for recall cover on a fast-growing fleet.

A new plant is first insured during construction and commissioning, usually under an erection all risks or contractors all risks policy that covers the works, plant and machinery being installed, and often the contractor's interests. That cover is written to end at a defined point: handover, provisional acceptance, or the completion of testing and commissioning. On the day it ends, the operational fire and property programme has to take over, and the transition is where gaps open up.

The common failure points in EV plant handovers are predictable:

1. Partial handover. Battery pack assembly may go live while the paint shop or vehicle line is still under testing. If the EAR policy ends for the whole site on one date, or the fire policy only attaches once the whole site is complete, a section of live production can sit uninsured.
2. Stock arriving before the policy attaches. Cells, modules and finished packs often arrive during trial production. EAR wordings typically cover the works, not trading stock, so inventory needs operational cover from the first delivery.
3. Testing exclusions. Hot testing of battery formation, charge-discharge cycling and end-of-line checks are exactly where thermal events happen. The EAR testing period and any extension need to cover them explicitly.
4. Machinery breakdown and business interruption. These are rarely bought at the construction stage, so machinery breakdown and business interruption cover must be placed to start with operations, not months later at the next renewal.

The detailed mechanics of the handover are covered in our piece on the construction-to-operational handover gap. The specific point for an EV maker is that the highest-hazard material on site, lithium-ion cells, tends to arrive during the handover window.

Once a plant is at volume, the largest single property exposure is usually not the building. It is the concentration of cells, modules and finished packs in raw-material stores, work-in-progress areas, finished-goods yards and the transit legs between them. A fire in one store can destroy weeks of supply and the finished vehicles parked next to it, as the Bengaluru EV yard fire showed for parked fleets.

Why a single fire policy is often the wrong tool

A standard fire policy written with a declared sum insured per location struggles with stock that moves. Values swing with production schedules and seasonal demand, and stock passes through supplier sites, inland transit, the plant, regional warehouses and dealer premises. If declared values lag actual values at the time of loss, the average clause reduces the payout proportionally.

A stock throughput policy addresses this by following the goods from the point the OEM takes risk until delivery to the dealer or customer, covering storage and transit under one wording and one limit. For an EV maker, the structure should include:

• Per-location limits sized to the peak value of cells and packs at each site, not the annual average.
• A transit limit per conveyance that reflects the value of a full truckload of packs or vehicles.
• Declaration or adjustment provisions so values can be reported monthly as output ramps.
• Clear treatment of lithium-ion batteries as a named class, since some wordings carve out batteries or apply higher deductibles to them.

Insurers will ask about cell storage practice before they quote: segregation distances, state-of-charge limits for stored cells, thermal detection and suppression, and quarantine areas for damaged or returned packs. The answers drive both the rate and the size of the deductible.

Product liability cover for a two-wheeler maker responds to third-party bodily injury and property damage caused by a defective vehicle. Under the Consumer Protection Act, 2019, that liability sits with the manufacturer regardless of the rider's own motor insurance. A battery fire in a home parking area, spreading to other vehicles and the building, is the scenario that sets the limit.

Recall cover is separate and usually narrower. It pays defined first-party costs of withdrawing or fixing affected products: customer notification, logistics, replacement parts and labour, temporary storage, and sometimes forensic investigation. Many wordings exclude the cost of the replacement product itself, loss of market share and price rebates, so each head should be read against the OEM's own recall plan.

How to size the limits

The Korean case gives a practical way to frame the recall limit. Take the number of units likely to share a firmware or pack design at any point, and estimate the per-unit cost of the worst plausible fix (a physical BMS or pack replacement, not an OTA update). Add notification, logistics and investigation. That number, not last year's warranty spend, is the recall sub-limit to aim for. It should be revisited each time annual output steps up.

For product liability, the limit has to grow with the installed base, the share of vehicles parked and charged indoors, and the export plans, if any. Startups that bought a modest limit at Series A often find it inadequate after two years of volume growth. Our earlier guide on electric two-wheeler OEM insurance sets out the base product liability and recall structure in more detail.

Doubling the outlet count from about 80 to 160-170 changes the liability picture as much as the plant does. Every new showroom and service point adds premises where customers' vehicles are charged, stored and repaired, and where battery packs may be swapped or held for return. Whether those premises are company-owned or franchised, claimants and consumer forums often name the OEM alongside the dealer.

The programme should address three questions directly:

1. Whose public liability responds at a dealer site after a battery fire? The dealer agreement should require dealers to hold their own public liability and fire cover, name the OEM as an additional insured where possible, and deliver certificates before the outlet opens.
2. Who holds returned and faulty packs, and under which property policy? Damaged packs awaiting return are a higher hazard than new stock and are often stored informally at service points.
3. How are warranty costs funded? Routine warranty claims are a balance-sheet provision, not an insurable event. A spike from a common-mode defect is closer to a recall, and the boundary between the warranty reserve and the recall policy should be agreed with the insurer in advance.

Company-owned experience centres also need their own fire, burglary and employee cover. These are small individually but numerous, and a schedule that is updated only at renewal will lag a network that is adding outlets every month.

For any EV two-wheeler OEM raising growth capital to build a plant and expand distribution, the programme review should happen before the plant's first cell delivery, not at the next annual renewal. A practical sequence:

1. Map the EAR expiry, testing period and handover dates against the delivery schedule for cells and packs, and close any gap with an early attachment of the operational fire policy.
2. Place a stock throughput policy covering suppliers, transit, plant, warehouses and dealer stock, with peak-value limits and monthly declarations.
3. Add machinery breakdown and business interruption cover for the new lines, with an indemnity period that reflects the lead time for replacing specialised battery assembly equipment.
4. Reset product liability and recall limits against the projected installed base for the next two years, with recall wording that clearly covers software-parameter defects.
5. Rewrite dealer agreements to require insurance, additional-insured status and storage rules for returned packs.
6. Review directors and officers cover, since new institutional investors and a larger board raise the governance exposure.

Present the underwriter with BMS validation records, cell storage procedures and the recall plan together. An OEM that can show how it would find and fix a firmware defect across its fleet is a better risk than one that cannot, and the terms will reflect it.

Funding rounds are announced as growth stories. For the risk manager, each one is also a list of new exposures that need to be insured from the day they start, not from the day someone notices.