We worked with a San Fran-based tech firm with 3 million subscribers and $1.5 billion revenue, that was undergoing rapid growth.
The growth was causing two headaches…
- As they increased the number of tech teams, the rate of product delivery was not increasing as fast.
- #cloudcosts were growing faster than revenue, causing margin erosion.
The #CTO made two great changes to the culture and technology to fix this:
1. Provided visibility and ownership to all the engineering teams on their costs and performance.
Once teams could see this, they took ownership of their costs and performance.
2. Brought about a cultural change on using shared services.
The engineering teams were used to working independently. To build more efficiently, the CTO put in place common approaches for monitoring, logging & CI/CD pipelines.
This meant that teams could focus on product innovation rather than spending their time supporting different toolchains.
Often, non-scalable cloud costs are symptoms of underlying inefficiencies and poor working practices.
An underlying principle here is great tech performance = less capacity = less cost = highly performing teams.
What approaches have you used to #scale your tech teams?
Schedule a Cloud Opportunity and Risk Assessment Call
View Free, Relevant Capacitas Insights
Whether you’re looking to optimise costs, improve agility or drive value creation, our expert insights can help you. Ready to start?
About the author
Team Capacitas
FinOps and AI: Building the Financial Discipline for the Next Wave of Enterprise Intelligence
AI FinOps represents an evolution rather than a replacement of traditional FinOps. It extends the model into a domain where financial, technical, and product decisions are tightly interconnected.
Confidence Under Load: How We Verified AKS Readiness for Peak
How Capacitas verified AKS readiness for peak demand by validating workload performance, autoscaling, cluster capacity, monitoring, and incident response.
Building Cloud Resilience: Lessons from the AWS Outage
Learning from the Latest Outage. Events like this week’s AWS disruption highlight one clear truth: resilience must be designed, not assumed.
Bringing Order to Chaos: A Practical Guide to Chaos Testing in the Cloud
In today’s cloud-native environments, resilience is not optional—it’s critical. Chaos testing has emerged as a key practice for validating system behaviour under failure conditions.