What software stack should a Battery & Energy Storage business run in 2027?

What it is and why it matters

The term "software stack" for a storage business covers more ground than a typical software business because storage sits at the intersection of hardware, safety-critical monitoring, and long-duration service contracts. A residential or commercial battery installer, a community storage developer, or a utility-scale operator all need the same five functional layers, even though the specific vendors and configurations differ by segment.

The first layer is customer relationship management (CRM) and quoting — capturing leads, running site-specific sizing and payback calculations, and generating proposals that account for utility rate structures, demand charges, and incentive stacking. The second layer is project and asset management, which tracks a project from signed contract through permitting, procurement, installation, and commissioning — the physical build-out that a pure-software business never has to manage. The third layer, and the one unique to this industry, is the energy management system (EMS) or SCADA layer that ingests real-time telemetry from the battery management system (BMS), inverters, and site controllers. This layer is not optional: it is how the business detects thermal anomalies, state-of-charge drift, cell imbalance, and communication faults before they become safety incidents or warranty claims. The fourth layer is a traditional ERP for accounting, inventory, and procurement of cells, enclosures, inverters, and balance-of-system hardware. The fifth is field service and ticketing software that turns a monitoring alert into a dispatched technician visit with parts, labor, and warranty tracking attached.

Why this matters for a battery and storage business specifically: unlike a SaaS company where "software" and "the business" are the same thing, here the software exists to manage a physical, safety-critical asset with a 10-20 year service life. A gap between any two layers — for example, telemetry data that never reaches the CRM, or a service ticket that never links back to the original warranty terms in the ERP — creates real financial and safety exposure. The businesses that scale past the first 50-100 installed systems are the ones that treated this integration as core infrastructure from day one, not an afterthought bolted on after growth created chaos.

The step-by-step process

The software stack is best understood as a pipeline that follows the physical project lifecycle, with data flowing forward at every stage and telemetry flowing back once the system is live. A lead enters through the CRM, gets sized and quoted, moves into contracted project management, goes through procurement and installation, gets commissioned into the monitoring platform, and then enters a permanent monitoring-and-service loop that can last well over a decade.

Each handoff in that chain is a place where businesses either integrate cleanly or create a manual workaround that eventually breaks. The CRM-to-project-management handoff needs the signed contract's system size, battery chemistry, and site conditions to carry forward automatically, because re-keying that data introduces sizing errors. The procurement-to-installation handoff needs serial-number-level tracking of cells and enclosures, since warranty claims years later depend on knowing exactly which battery pack and firmware version shipped to which site. The installation-to-monitoring handoff is the most safety-critical: a system that goes live without its BMS telemetry correctly mapped into the EMS is a system nobody is watching for over-temperature or over-voltage events. And the monitoring-to-service loop needs to close automatically — an alert that requires a human to notice it in a dashboard and manually open a ticket in a separate system will eventually get missed, and a missed thermal alert on a lithium-ion system is not a minor operational miss.

Costs, timelines, and typical ranges

Budgeting for this stack depends heavily on business size and segment (residential/small commercial versus commercial-and-industrial versus utility-scale), but some general ranges hold across the industry. A CRM and quoting platform suited to solar-plus-storage sales typically runs from roughly $50 to $150 per user per month for off-the-shelf tools, or can climb into six figures annually if the business builds custom sizing and incentive-calculation logic on top of a platform like Salesforce or HubSpot. Project management and field service tools for install-heavy businesses commonly run $30-$100 per user per month, though enterprise field-service suites with routing, inventory, and mobile work-order support can run considerably higher once implementation and integration costs are included.

The EMS/SCADA layer is where cost varies most by segment. A small commercial or residential storage business will often use the EMS bundled by its inverter or BMS manufacturer at little or no direct software cost, accepting less flexibility in exchange. A business managing many sites or multiple hardware vendors typically needs a vendor-agnostic monitoring platform, and licensing for that tends to scale per monitored site or per kilowatt of managed capacity rather than per user — meaning costs grow directly with the fleet, not with headcount. ERP costs for a growing storage business commonly land in the range of $20,000-$150,000 per year depending on whether the business needs manufacturing/inventory modules, multi-entity accounting, and integration middleware, or just core financials.

Timelines matter as much as cost. Standing up CRM and quoting is usually the fastest piece, often achievable in 4-8 weeks. Project management and ERP implementations commonly take 2-4 months when configured carefully against real workflows rather than generic templates. The EMS/telemetry integration is typically the longest pole in the tent — mapping BMS and inverter data points correctly, validating alert thresholds against manufacturer specifications, and testing failover behavior can take 3-6 months per hardware platform supported, and multiplies for businesses that install multiple battery chemistries or brands. A realistic full-stack rollout for a business scaling from a handful of installed systems to fleet-level operations should budget 6-12 months of iterative build-out, not a single go-live date.

Where teams get it wrong

The most common and most damaging mistake is treating the EMS/monitoring layer as an afterthought that lives entirely inside the hardware vendor's proprietary app, disconnected from the CRM, the warranty database, and the service-ticketing tool. This works fine for the first dozen installed systems and becomes untenable past a few hundred, because technicians end up manually cross-referencing three or four separate logins to answer a basic question like "which sites are showing cell-imbalance warnings and are they still under warranty."

A second frequent error is under-investing in interconnection and permitting tracking. Utility interconnection queues, permit status, and inspection scheduling are treated as spreadsheet work by many early-stage storage businesses, and that spreadsheet becomes a bottleneck the moment project volume exceeds what one operations person can track manually — missed interconnection deadlines directly delay revenue recognition.

A third mistake is choosing an ERP built for a pure-services or pure-retail business rather than one that handles serialized inventory, because battery packs, inverters, and enclosures need serial-number and firmware-version tracking all the way through to field service, not just at the point of sale. Businesses that skip this find themselves unable to answer basic questions during a recall or a warranty dispute.

A fourth mistake is under-provisioning for data retention and alerting fatigue on the monitoring side. Storage systems generate continuous telemetry, and if every minor voltage fluctuation triggers a notification, technicians start ignoring alerts altogether — a phenomenon that has caused real safety incidents across the broader battery industry when genuine thermal events got lost in noise. The fix is tiered alerting: informational logs, actionable warnings, and true emergency escalation, each routed differently and each reviewed on a different cadence.

Finally, many storage businesses under-integrate financial software with monitoring data, which matters increasingly as revenue models shift toward performance-based contracts, demand-response participation, and capacity payments. If the ERP cannot ingest actual delivered performance from the EMS, the business cannot accurately bill, forecast, or defend its numbers to financiers and insurers.

Decision framework: when to choose what

The right stack depends heavily on three variables: business segment (residential/small commercial, commercial-and-industrial, or utility-scale), fleet size, and whether the business installs a single hardware platform or multiple. A small residential-focused installer can often run lean — an off-the-shelf CRM, the inverter manufacturer's bundled monitoring app, and a lightweight field-service tool — because integration complexity is lower and volume per site is smaller. A commercial-and-industrial business juggling multiple customer contracts, demand-charge calculations, and multi-year service agreements typically needs a dedicated project management and ERP layer earlier, because contract complexity outpaces what a CRM alone can track. A utility-scale or multi-site fleet operator almost always needs a vendor-agnostic EMS/SCADA platform from the outset, because relying on a single hardware vendor's app becomes a liability the moment the fleet includes more than one battery chemistry or inverter brand.

The build-versus-buy question follows a similar logic: businesses under roughly 100 installed systems are almost always better served by configuring existing CRM, ERP, and monitoring platforms than building custom software, because the integration and maintenance burden of custom tools outweighs the benefit at that scale. Past several hundred systems, particularly for fleet operators with performance-based revenue, custom middleware that unifies telemetry, financial, and service data increasingly pays for itself, because off-the-shelf tools rarely model storage-specific revenue streams like capacity payments or ancillary-services participation out of the box.

Related questions

Does a storage business need a dedicated EMS, or can it rely on the inverter manufacturer's app?

For a handful of sites with one hardware vendor, the bundled app is often adequate. Past a few dozen sites, or with multiple vendors, a vendor-agnostic EMS becomes necessary to avoid fragmented monitoring and alerting.

How is this different from a solar-only software stack?

Storage adds a safety-critical, continuous telemetry layer (BMS state-of-charge, temperature, cell balance) that solar-only businesses don't need to monitor with the same urgency, plus more complex warranty and serialized-inventory tracking.

Should the CRM and ERP be the same platform?

Not usually early on — CRM tools are optimized for sales workflows and ERPs for financial and inventory control. Integration between two best-of-breed tools generally beats a single generalist platform until the business is large enough to justify a unified enterprise suite.

What's the biggest hidden cost in this stack?

Integration and data-mapping work between the EMS/telemetry layer and everything else — CRM, ERP, and service ticketing — is consistently underestimated in both time and dollars.

FAQ

What's the minimum viable software stack for a new battery and storage business? A CRM for quoting, a lightweight project management tool for installs, and the monitoring app bundled with the chosen inverter/BMS hardware. This covers a business through its first year or so before fleet size demands dedicated EMS and ERP tools.

Does the software stack differ if the business also does solar installation? Mostly the same core layers apply, with additional quoting logic for combined solar-plus-storage sizing and incentive stacking, and monitoring that correlates solar production with battery charge/discharge behavior.

How important is mobile access for field technicians? Very important — technicians need mobile access to work orders, site history, and warranty status in the field, since desk-bound tools create delays that directly extend outage and repair times on safety-relevant equipment.

Can a small storage business get by without a dedicated ERP? Briefly, yes, using accounting software plus spreadsheets, but serialized battery and inverter inventory tracking becomes error-prone quickly, and most businesses outgrow this within their first 100-200 installed systems.

Who typically owns the decision on monitoring software — the sales team or operations? It should be a joint decision, since sales needs monitoring data for the customer-facing performance guarantees baked into contracts, while operations needs it for safety alerting and service dispatch. Choosing it in a silo is a common failure mode.

Does the stack need to change as storage business models shift toward performance-based revenue? Yes — businesses moving toward demand-response, capacity payments, or performance guarantees need their EMS telemetry to flow directly into ERP billing and reporting, which off-the-shelf tools often don't support without custom integration.

Sources

• https://www.nrel.gov/
• https://www.energy.gov/
• https://www.eia.gov/
• https://www.iea.org/
• https://www.batteryuniversity.com/
• https://www.salesforce.com/
• https://www.hubspot.com/
• https://www.gartner.com/
• https://cleanpower.org/

Related on PULSE

• What CRM setup works best for solar-plus-storage sales teams?
• How should a commercial storage operator structure field service and warranty tracking?
• What KPIs matter most for a utility-scale battery fleet operator?
• How do demand-response and capacity payment contracts change revenue operations?
• What ERP features matter most for hardware businesses with serialized inventory?