How SolarWinds replaced ad hoc account tracking with a shared customer health framework, a modernized CRM foundation, and its first systematic feedback programs.
SolarWinds was growing a SaaS customer base without a shared system of record for how those customers were actually doing. Account health lived in individual reps' heads rather than in a system anyone else could see, escalate against, or plan around.
As Project Manager, CRM & Lifecycle Operations, Justin T. Neal owned the CRM platform and the lifecycle programs built on top of it — turning fragmented account knowledge into a shared, systemized view of customer health.
As SolarWinds' subscription customer base grew, the tools tracking that growth hadn't caught up. CRM usage was inconsistent across teams, customer feedback arrived informally and rarely made it back to product or go-to-market decisions, and there was no structured way to flag an at-risk account before renewal was already in jeopardy.
The gap wasn't a missing tool — SolarWinds already had Salesforce. The gap was a missing system: no consistent workflows, no shared definition of customer health, and no repeatable way for customer feedback to reach the teams who could act on it.
Lifecycle programs are only as good as the system underneath them. Fix the platform and the data foundation first, then build the frameworks and feedback loops on top of it.
Took ownership of the Salesforce CRM environment — integrations, workflows, and reporting — so customer support activity, product usage, and subscription health could be tracked in one place instead of scattered across teams.
Built a health scoring model that combined account signals into a single, shared view of churn risk — giving Customer Success a consistent way to prioritize attention instead of relying on individual judgment alone.
Launched NPS and QBR programs that turned customer feedback into a repeatable input — structured enough to inform product and go-to-market decisions, not just logged in account notes.
Led data migrations and platform enhancements to support scale and data integrity, so the health scores and lifecycle reporting built on top of the CRM could actually be trusted.
Partnered cross-functionally so systems, workflows, and lifecycle execution stayed aligned across teams — rather than each function maintaining its own version of the customer.
This case study reflects foundational CRM and lifecycle-operations work led at SolarWinds between 2015 and 2017 — early in what became a decade of enterprise SaaS transformation work.
Every scalable lifecycle program sits on top of a system someone had to own first. Before you can operationalize customer health, feedback, or retention strategy, someone has to build the CRM foundation those programs actually run on.
Let's fix the foundation before scaling the process on top of it.