All offers
Assessment
Platform Engineering
Platform Engineering Maturity Assessment
Three weeks to learn what your developer platform truly costs, where it lets your engineers down, and which fixes come first.
Duration
3 weeks
Usual next step
IDP Foundation Sprint
The problem
Most platform initiatives do not fail on technology. They fail because nobody has an honest, evidence-based picture of the current state. Teams build portals nobody adopts, standardize on tools that solve last year’s problem, and discover the real bottleneck (a two-week environment request, an approval chain, an undocumented golden path) only after eighteen months of investment.
You probably already suspect where the friction is. What you are missing is the evidence to prove it, quantify it, and get it funded.
What the assessment gives you
A measured baseline of your delivery flow: lead time for change, deployment frequency, change failure rate, time to restore, and provisioning lead time for the environments and services developers request most often
A cognitive load analysis for your platform and stream-aligned teams, showing where responsibility is misplaced
A capability map of your current platform against a reference architecture: self-service, golden paths, observability, security and policy, runtime, developer portal, and the AI workload path
A named list of the top friction points, each with an estimated cost in engineering time
A prioritized 12-month roadmap with effort estimates, sequenced so that the first improvement lands within one quarter
A build-versus-buy-versus-adopt recommendation for each capability gap, with no vendor lock-in agenda: we recommend open source where open source wins and commercial products where they win
How it runs
Week | Focus |
|---|---|
1 | Kickoff, data access, stakeholder interviews, telemetry review |
2 | Developer survey and workshops, hands-on review of pipelines, cluster configuration, and platform code |
3 | Synthesis, roadmap workshop, findings presentation to engineering leadership |
Roughly 8 to 12 hours of your team’s time per week, spread across interviews and two workshops. We do the rest.
Who it is for
Engineering organizations with 50 or more developers who have either started a platform initiative and want to know whether it is working, or are about to start one and want to avoid rebuilding it in two years.
What happens next
You own the report and the roadmap whether or not you continue with us. If you decide to act on it, the usual next step is an IDP Foundation Sprint, which turns the first phase of the roadmap into a running platform in eight weeks.
Frequently asked questions
Do we need to prepare anything before the assessment starts?
Access to your delivery telemetry (pipelines, ticketing, repositories) and a list of interview candidates is enough. We send a short preparation checklist after kickoff; most teams spend less than a day on it.
Will this disrupt our teams’ delivery work?
No. The assessment is designed to run alongside normal delivery: interviews and workshops take roughly 8 to 12 hours per week across the whole organization, and we work read-only — nothing in your environment is changed.
What if we already track our own DORA metrics?
Even better. We validate your existing numbers, fill the gaps — provisioning lead time and cognitive load are usually missing — and concentrate on the interpretation: what the numbers say about where your platform investment should go next.
Interested?
Tell us where you are and what you are trying to decide. We will come back with a scope, a price, and an honest view of whether this is the right offer for you.