CONSULTING PROBLEM

We need to decide which product to build.

Connect customer requirements, technical fit and product economics before the architecture hardens.

A focused problem,
structured for action.

Typical clients

  • Startups
  • CTOs and technical leaders
  • R&D teams
  • Product teams
  • Investors reviewing technical claims

Typical symptoms

  • Low efficiency
  • Unstable operation
  • Capacity fade
  • Poor repeatability
  • Lower-than-expected current density
  • System underperformance

Relevant areas

  • Troubleshooting
  • R&D and testing
  • Systems and product development
  • Scale-up and due diligence

Typical engagement

  • Focused review
  • Diagnostic assessment
  • Workshop + analysis
  • Development roadmap
01

Electrochemistry

Kinetics, transport, state of charge or degradation may be limiting the result.

02

Materials / formulation

Material selection, compatibility or formulation can shift both performance and lifetime.

03

Membrane / separator

Crossover, resistance, water transport or stability can create system-level effects.

04

Cell / stack design

Architecture, compression, flow or interfaces can constrain the operating window.

05

Balance of plant / controls

Hydraulics, thermal behavior, control logic or auxiliaries can mask the core issue.

06

Testing / data / validation

The test plan, controls or data quality may not isolate the variable that matters.

Make the next
technical move clearer.

  1. 01Why is efficiency below target?
  2. 02What is limiting performance?
  3. 03Is the issue chemistry, architecture or operation?
  4. 04Are we testing the right variables?
  5. 05Which experiment or analysis should happen next?
  6. 06Are the current claims technically credible?
  7. 07What is the most likely root-cause path?
  8. 08What is the fastest way to reduce uncertainty?
01

Root-cause hypothesis map

02

Evidence-gap assessment

03

Prioritized next tests

04

Trade-off analysis

05

Technical risk list

06

Recommended action plan

If performance is under target, the important question is what to test or change next.

Discuss this problem ↗