Case Study
Climate/ESG SaaS platform. Inherited codebase, zero observability, production instability. In 90 days, the team went from firefighting to operating.
5 days
Assessment completed
2 of 6
Milestones delivered in one quarter
1.8 → 3.3
Maturity improvement
The Situation
The acquiring company merged two complementary SaaS platforms in the climate and ESG space to combine carbon measurement with regulatory compliance reporting. The acquisition brought a functional product serving asset managers and funds, active customers, and proven product-market fit.
It also brought a codebase the current team did not build and did not fully understand. Two products, scattered service ownership, three different data stores, no monitoring, and domain knowledge concentrated in one person who was about to go on leave.
Production was unstable enough that the sales team could not reliably demo the platform. Incidents were discovered by customers, not by systems. During SOC2 preparation and exit planning, the production environment hosting the largest customer experienced a regional infrastructure disruption. No contingency plan existed.
The Assessment
Over the course of one week: codebase access, infrastructure review, developer interviews, documentation analysis, and review of a prior technical due diligence report. The goal was to bring clarity to the inherited platform, quantify risk, and establish a prioritized path to stability.
Maturity Rating
Scale: 1 (critical) to 5 (excellent). Assessed across six dimensions at engagement start and after 90 days.
Key Findings
Platform unreliable enough that sales could not demo confidently. For a product tied to annual compliance reporting cycles, each failed demo during renewal season represented concentrated churn risk.
No monitoring, no alerting, no tracing. Incidents discovered by customers. Mean time to resolution extended because the team had to first understand what was happening before they could fix it.
One team member held the majority of domain knowledge and was about to go on leave. Without immediate knowledge transfer, the team's ability to maintain the platform independently would have dropped significantly.
Production environment hosting the largest customer experienced a regional infrastructure disruption during SOC2 and exit preparation. No contingency plan was in place.
Two products, multiple partially-migrated services, three data stores, unclear ownership. The team was spending most of their time understanding the system rather than improving it.
Business Impact
Production instability was directly impacting pipeline conversion. Sales team unable to demo reliably during renewal cycles. For a platform where revenue is tied to annual compliance deadlines, each quarter of instability represented measurable retention risk.
Zero observability meant every incident consumed 2-3x the engineering hours it should have. With a small team already at capacity, this was the equivalent of losing one engineer's output to reactive firefighting.
Key person dependency was mitigated through a strategic hire and structured industry knowledge sessions covering customer workflows, domain concepts, and compliance requirements. Without that intervention, the team would have lost operational independence on the inherited platform.
Regional infrastructure disruption during exit preparation exposed a gap that could have directly impacted the transaction timeline and valuation discussion.
The Approach
Observability first, then codebase clarity through the most revenue-critical use cases, then architectural decisions based on what was learned. Prioritize by churn risk and revenue impact, not technical elegance. The business model worked in the team's favor: customer usage was periodic, not continuous. Not everything needed to work perfectly all the time. The focus was on the critical paths that drive value.
The Outcome
Tell us about the deal. We'll tell you what we can do and how fast.