How we approach typical engagements in cloud, DevSecOps, security and FinOps: the challenge, the solution and the core metric we would track.
Example scenario. This page describes a typical engagement and how we would approach it. It is not a description of a specific client and it contains no client results. The measures below are what we would track, with targets agreed with you up front.
A European fintech ships often, but every release waits on a slow pipeline and on manual compliance checks that fail late. Here is how we would rebuild the path from commit to production.
Core metric: Deployment lead time, from merge to production, and the share of releases that pass the compliance checks without a manual review. We measure both before and after, against a target agreed up front.
A scaling e-commerce company runs environments on both AWS and Google Cloud, built by hand over time. Here is how we would standardise them on one landing zone.
Core metric: Configuration drift, counted as the differences between environments that should be identical, and the time to roll out a new microservice from first commit to running in production.
A mid-sized company grew its cloud accounts quickly and nobody has a ranked list of what to fix first. Here is how we would review, fix and keep it fixed.
Core metric: Open high-risk findings before and after, and the time from a finding to its fix.
A mid-market SaaS platform on Google Cloud and Azure sees its bill grow faster than its usage. Here is how we would find the leaks and give teams ownership of their spend.
Core metric: Monthly cloud spend per environment and per team, and the share of spend found to be waste, tracked from the first week. A saving only counts once the change is live and stability and performance are unchanged.
