Epilot

Name: Epilot
Brand: Epilot

The cloud platform for utilities, grid operators and solution providers. Become a pioneer of the energy transition🚀

Est 2017|Raised $10.8M|89 Ref Customers

LinkedIn 12K|Web traffic 13K|FTEs 127|HQ Cologne, North Rhine-Westphalia, DE

MarketsCRM

Published Oct 15, 2026

01Common complaints

- When independent, third-party customer review volume is a critical procurement requirement; public review footprint is limited - When the organization requires a global, standardized CRM platform spanning multiple non-energy business units (horizontal platforms may better support global standardization) - When SAML/SCIM provisioning is a strict, non-negotiable requirement based on public documentation emphasizing OIDC (confirm identity requirements during procurement) - When the organization requires only basic CRM and ticketing functionality (simpler, lower-cost helpdesk/CRM tools may be more appropriate) - When procurement requires publicly available detailed compliance artifacts (SOC 2, penetration test summaries); the vendor provides some security statements and technical documentation but public audit materials appear limited

Deal disqualifiers

Requirement for publicly available SOC 2 or comparable attestations (unless acceptable via contractual NDA arrangements)
Need for multi-region data residency outside Germany (vendor emphasizes German hosting)
Preference for fully transparent self-serve pricing

Limitations acknowledged or implied by documentation

Audit log capabilities are marketed as an enterprise-tier feature and may not be available in lower tiers.
Some security and compliance attestations (e.g., SOC 2, public penetration test reports) are not publicly documented.

Roadmap / publicly undisclosed items

No detailed public roadmap was found in the reviewed sources. Public communications reference roadmap acceleration and advanced capabilities without committed public release dates.

Scale considerations

No explicit scale limits were found in public documentation. Architecture suggests AWS serverless scalability, but buyers should request specific details including SLA/uptime commitments, API rate limits, and Data Lake usage costs or limits.

Security / compliance gaps (publicly visible)

No SOC 2 report was publicly available in the reviewed sources
No public penetration test disclosure was identified

Possible drivers of customer churn (inferred)

Based on category dynamics and public information:

Enterprise standardization on large horizontal platforms (Salesforce/SAP/Microsoft) could displace a vertical vendor
If contractual assurances for specific third-party attestations are required and cannot be provided, procurement may choose alternative vendors
Perceived opacity in pricing (quote-only models) can be a procurement friction

02Why they buy

Vendor-documented differentiators

- Vertical focus: The vendor provides an energy-specific data model intended for utilities, grid operators, and solution providers. - Portals and partner collaboration: Customer and installer/partner portals are core components of the offering. - Templates/blueprints: Vendor-provided process templates are marketed as a way to accelerate initial configuration and reduce bespoke development effort. - German hosting and ISO 27001 certification: Data residency in Germany and vendor statements regarding ISO 27001 are presented as advantages for EU customers.

Where competitors have advantages

Salesforce: Broader ecosystem, large partner bench, and a wide marketplace of add-ons and SI resources.
Microsoft: Strong integration with Microsoft productivity and cloud tooling for organizations standardized on that stack.

03Field reports

What’s available (and what’s not)

Public review platforms show little to no verified end-user review volume for the vendor:

A Capterra listing was reviewed and showed no verified reviews in the snapshot reviewed.
A G2 review page was not located in the searches performed.

This limited presence reduces the ability to form a consensus view of product quality from standard review aggregators.

Vendor-published testimonials and claims

The vendor website includes customer quotes and outcome metrics reported in case studies and marketing materials, for example: - Reported reductions in cost-to-serve for utilities (vendor-attributed) - Statements about rapid process launches and portal deployments in customer examples - Operational metrics such as reported application volumes and number of process variants implemented Critical note: These are vendor-published case study statements; underlying methodology, baselines, and measurement definitions are not disclosed publicly.

Public negative signals

Mainstream SaaS review coverage is scarce. A publicly visible negative signal was found in employee feedback on employer review sites indicating periods of high workload during growth phases. Such signals can be relevant to delivery or support risk but do not directly measure customer outcomes.

Why customers cited the vendor (in published references)

From vendor case pages and sector reporting:

A need for end-to-end digitization spanning customer inquiry → order → partner/installer coordination → ongoing service
Requirements to digitize grid connection and regulatory processes via portals
Interest in replacing spreadsheets/legacy CRM and long IT programs
Use of sector-specific data models and templates (vendor-provided blueprints)

Vendor case library

The vendor publishes a case library and downloadable case studies (some gated behind contact forms). Published quotes and metrics reference deployments for grid operator portals and digitizing PV/DER registration processes.

Independent / third-party case evidence

Industry reporting documents a migration milestone where a grid/network operator migrated contract management for generation plants to the vendor as part of a broader digitization initiative.

Evaluation of reported metrics

Many operational metrics in case studies are vendor-published without disclosed baselines, control groups, or independent audits.
Buyers should request detailed definitions for reported before/after metrics, volume definitions (e.g., what counts as an "application"), and support metrics during rollout.

04Best fit

Company sizes

Most consistent fit appears to be mid-market to enterprise utilities and grid operators, plus solution providers managing substantial inquiry and installation volumes.

Industries / verticals

Energy suppliers, municipal utilities (Stadtwerke)
Grid operators
Energy solution providers (PV, heat pumps, EV charging)

Roles and personas

Decision makers: Head of Sales/Service, CIO/IT leadership, Head of Grid/Network operations, digital transformation leads
End users: Customer service agents, sales teams, partner management teams, grid connection processing teams

Pain points addressed

Manual, fragmented tooling and processes
Need for customer and installer portals
Complex product and pricing logic
Managing new energy product types (DERs, electrification)

05The pitch

What the product does (core value proposition)

Epilot is a vertical, cloud-based platform described by the vendor as an "energy XRM" (extended relationship management) solution designed to digitize and automate end-to-end sales, service, and grid/operator processes for energy-sector organizations. In practice, it combines: - Relationship management with energy-specific objects (products, prices, processes, partners/installers) - No-/low-code process configuration and templates (referred to by the vendor as "blueprints") - Customer and partner/installer portals - APIs/webhooks and an "epilot Data Lake" for analytics The vendor positions the product as an alternative to multiple point solutions (spreadsheets, legacy CRM, point solutions) and reports that it can reduce time required to launch new energy products and processes.

Target market and market positioning

Primary target segments (vendor positioning):

Energy suppliers & municipal utilities
Grid operators
Solution providers (e.g., PV/solar, heat pumps, EV charging)

Epilot is presented by the vendor as a sector-specific alternative to generic CRM/workflow platforms (for example, Salesforce or Microsoft) and as an option for organizations seeking prebuilt energy workflows and portals rather than building them from a horizontal CRM.

Get a comprehensive analysis of Epilot including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →