Customer evidence · Kokusai Kogyo
Understand what customers used, how it fitted their workflow and what they reported. These examples are a starting point for evaluating your own requirements.
Enegaeru’s published adoption figures cover more than 700 organizations across the series. Named customer stories show different ways to use the foundation: battery-sales simulation at Anker Innovations Japan and tariff-related calculations within Panasonic’s home EV charging service.
Use these examples to assess workflow fit, then validate your own representative case. Standardize the assumptions and calculations your team uses across channels; select the products and APIs that match your scope.
Series-wide adoption source (Japanese). Adoption does not mean every customer uses every product.
In a customer interview published on August 29, 2025, Anker’s Japanese business described replacing spreadsheet-based work with Enegaeru ASP for residential battery proposals. A small sales and customer-support team reported running nearly 300 simulations a month and presenting multiple equipment configurations.
For international market-entry teams, the relevant question is operational: can a local team produce consistent, explainable comparisons across different regions and households? This case illustrates that workflow; it does not establish that Enegaeru caused the company’s market entry or guarantees another company the same outcome.
The published Panasonic case describes Enegaeru API adoption for its home EV charging service. It shows how electricity tariff calculations can form part of a branded digital experience.
For a platform or automotive team, use the case to frame your own requirements: what data the user provides, what calculation the application needs, and how the result informs charging or tariff choices. Confirm the endpoints and integration scope for your own service.
See the product scope behind household solar and battery proposals.
Explore this service →Explore how calculation capabilities fit your own systems.
Explore this service →Browse all published customer stories (Japanese) →
Customer names identify published use cases, not a commitment to introduce customers, share their data or endorse a new partner. Results remain specific to the customer and publication date.
Tell us what you want to launch in Japan, who will use it, and where the work is getting stuck. We can discuss the right combination of software, APIs, data and specialist support.