Turning a Finished Solar Project Into the Next One

A system running below its expected output for a sustained stretch is the earliest, most objective retention signal an EPC has, well ahead of anything a developer says on a call. Track that against each system's own baseline rather than a fleet-wide average, since site conditions vary enough that comparing a shaded urban rooftop system to an open-field array tells you very little. A developer who sees underperformance flagged and explained proactively, with a clear plan to address it, reads that very differently than one who finds out from their own utility bill months later that something has been wrong the whole time.

The O&M contract is closer to a subscription: a recurring service fee, a defined scope of monitoring and maintenance, and a renewal date. The next-project relationship is closer to the general contractor problem: no ongoing product, just a developer deciding whether to trust you with the next site based on how the last one performed. Treating both as one undifferentiated client relationship means the O&M renewal risk and the next-project pipeline can both go unmanaged at the same time, because nobody owns either one specifically.

For a firm with a growing portfolio of O&M contracts and a lean asset management team, ChurnZero's lighter setup can trigger a client check-in when the system's monitoring shows a performance issue or when a maintenance visit gets delayed, without needing a dedicated customer success hire to run it. That's most of the value for a firm whose O&M book is still small enough to track without a full account hierarchy, and small enough that one asset manager can reasonably keep every system's status in view.

Flag an O&M client for a check-in when:

• The system's monitoring shows output running below its own baseline for a sustained stretch.
• A scheduled maintenance visit gets delayed, even if the invoice is still being paid.
• The system underperforms for months without a proactive explanation from your team.

Once a developer is running a portfolio of sites with you and has separate people managing acquisitions, asset management and operations, Gainsight's account model becomes the more natural fit: one roof-level view of every site you maintain for that developer, so an underperforming system at one location surfaces to the account owner before it becomes the reason the developer's next site goes to a competitor.

Technology sales teams, a world away from solar EPC bidding, post a win rate on deals with existing customers that clearly outpaces their win rate on cold pitches to brand-new prospects¹. That figure was measured in software sales, not developer relationships, so treat it as a directional pattern rather than a claim about EPC win rates specifically. It still lines up with what most O&M account managers already sense: a developer who has seen your crews maintain their existing sites well is a far easier close on the next site than a developer evaluating your firm cold. Say your firm is deciding between hiring another business development rep to chase new developers or investing in a dedicated O&M account manager; that pattern argues for protecting and growing the relationships you already have before adding headcount aimed purely at net-new logos.

Salesforce is where developer relationships, project history and O&M contract terms should live in one place, so a change in account manager doesn't mean losing the history of every site built for that developer. Gong is worth adding once O&M renewal and next-project pitch calls with developers are frequent enough that a business development team can't reliably remember what was promised on a call from earlier in the quarter.

A firm with a handful of O&M contracts and one or two active developer relationships doesn't need either platform yet; a shared tracker reviewed monthly by the person who owns those relationships covers the need. The calculation changes once you're managing dozens of systems across multiple developers, each with its own performance baseline and renewal date, because that's the point where relying on memory and a spreadsheet starts quietly dropping systems that need attention. Evaluate ChurnZero first if your book is mostly O&M with modest per-developer complexity, and only look seriously at Gainsight once multi-site developer accounts with separate acquisitions, asset management and operations contacts make up a real share of your revenue.