Product requirements package
A prioritized set of customer, system and interface requirements that engineering, sales and delivery teams can use.
Product leadership for technically complex energy-storage decisions
The work is designed for BESS manufacturers, system integrators, project developers, PCS and EMS vendors, and industrial energy companies. It is most useful when the organization has strong engineering capability but needs a clearer connection between customer demand, product scope, commercial priorities and execution.
Typical triggers include a new market or application, an overloaded roadmap, conflicting stakeholder requirements, an RFP that exposes product gaps, or a pilot that needs objective success criteria. The goal is not to add another layer of process; it is to make the decisions, ownership and evidence visible.
What the engagement produces
Scope is tailored to the decision, but every deliverable is designed to be used by a real team after the engagement ends.
Product and portfolio roadmap
A sequenced roadmap connecting market opportunities, grid requirements, technical dependencies and commercial value.
RFP and market evaluation
A structured comparison of applications, buyer requirements, competitors, gaps and product implications.
MVP or pilot definition
A testable first release with assumptions, success criteria, data requirements and a clear go/no-go decision.
Cross-functional alignment
Decision records and operating cadence for product, hardware, software, controls, sales, EPC and service stakeholders.
Launch and feedback plan
A practical route from design validation to customer deployment, evidence collection and roadmap iteration.
From ambiguity to an executable product plan
Frame the decision
Review customer evidence, technical constraints, current architecture, competitors, commercial assumptions and stakeholder expectations. Define the decision, gaps and success measures.
Evaluate options
Build and compare product options. Resolve requirement conflicts, identify dependencies and test the most consequential assumptions with customers, partners or project data.
Commit to execution
Deliver the prioritized roadmap, requirements, decision record, owners, validation plan and launch or pilot sequence. Align the operating cadence for ongoing decisions.
The actual timeline depends on product maturity, stakeholder access and the amount of technical or market validation required.
Built around hardware, software and field execution
Sergey Syrvachev brings 14+ years of product-management experience across energy storage, industrial hardware, software and AI/ML. The work includes utility-scale MV-skid development, high-rate lithium batteries for data-center UPS applications and anomaly detection for energy-storage systems.
Before we start
Can you work under an NDA?
Yes. Public case studies can stay at an NDA-safe level, and confidential project material does not need to become website content.
Is the work limited to one geography?
No. Engagements can be remote and international. Grid codes, incentives and commercial assumptions are handled in the context of the target market.
Do you replace the engineering team?
No. Product management connects customer, commercial and engineering decisions. Final designs and approvals remain with qualified project engineers and responsible organizations.
Can the engagement focus on one decision?
Yes. A focused requirements review, RFP evaluation, roadmap workshop or MVP definition can be more useful than a broad transformation program.
Bring a specific BESS product decision
Describe the product, market, decision and current constraint. I will respond at sergey@data-panda.com.
