Are You Building a Battery Platform or a Very Expensive Prototype?
Most product teams building electrified equipment make their most consequential battery decision early in development, when requirements are least clear, and the consequences of getting it wrong are most unpredictable.
Engineers lock in battery chemistry, voltage, pack configuration, supplier, etc., and design the product around these constraints. The battery determines form factor, thermal management, power electronics, certification pathways, and supply chain dependencies.
Then the product ships, and the battery disappears from active conversation — until it comes back as issues in operations, finance, customer support, and supply chain management much further down the line.
Battery decisions are made in a moment of the highest uncertainty
Conventional battery technology requires organizations to make battery decisions when use cases are still being validated, customer requirements are still being refined, and the regulatory environment may shift. The supply chain hasn't been stress-tested, and real-world duty cycles haven't been observed yet.
Decisions that will shape the product and its roadmap for years are built on these uncertainties. When those decisions turn out to be wrong, the cost of correction is proportional to how far the program has advanced before the error surfaces.
Does your design pass the second-version test?
The second version test is a simple concept. You ask this question before the first version ships: What will the customer ask for in version two? These may include a different duty cycle, a different operating environment, a change in supplier, or new regulatory requirements.
The follow-up question is the same for all the scenarios: can the product accommodate this change without reopening the battery architecture? If the honest answer is no — if any of those scenarios would require a ground-up battery redesign — you haven't built a product platform but a prototype with a purchasing department attached.
The test surfaces assumptions that have been treated as permanent when they're actually contingent.
Beyond the second-version test: Anticipating the future
The second version test isn't a checklist for predicting future requirements. No product team can get them entirely right — markets reveal requirements on their own schedule, customers ask for things nobody anticipated, and supply chains shift in unpredictable ways.
However, the test helps us understand the value of battery architecture flexibility. It gives organizations the ability to respond to market changes and customer demands without reopening decisions that should never have been permanent in the first place.
With a software-defined battery architecture, the second version simply requires a reconfiguration, rather than a redesign.
Output voltage, chemistry tolerance, capacity allocation, and management logic are no longer set in stone. New requirements are met through configuration, supply chain disruptions can be absorbed by switching to an available alternative, and customer requests for different performance profiles are handled without hardware changes.
For instance, Dell manages a relatively small number of physical hardware configurations yet meets the diverse requirements of thousands of enterprise customers because the functionality those customers care about is configured in software, rather than built into the silicon.
Product builders applying this logic to battery systems don't treat the pack as a one-time design decision but as a configurable infrastructure layer.
Is your battery architecture a platform or a constraint?
Product teams that address battery flexibility from the start benefit from a more manageable development process. Changes are absorbed rather than cascaded, customer requirements that would have required a redesign program are handled as configuration updates, and supply chain disruptions that would have stalled production are addressed without fanfare.
More importantly, the product roadmap stays open. A platform architecture allows an organization to continuously respond to market changes and developments, rather than being constrained by decisions made when uncertainty was at its highest. A configurable battery architecture doesn't just support the second version — it makes the third, fourth, and fifth versions possible without starting over.
Companies and engineers have been trained to design their products and processes around the battery, and this mindset must change to drive the next stage of electrification.
>> Tanktwo's Battery Strategy Workshop helps product teams pressure-test their battery architecture decisions and build the flexibility that makes future versions possible without starting over.
