Free Sample Chapter - EXTENDED EDITION
Still struggling to justify your platform investment to leadership? Or just want to see the technical depth before you buy?
We heard both. So the free sample now covers both.
Platform engineers are technical experts — but selling a platform to a CFO or VP Engineering requires a completely different skill. And before you invest in a book, you want to know it goes beyond theory.
The extended free sample includes two chapters from The Comprehensive Guide to Platform Engineering in 2026:
Chapter 19 of Gives you a concrete framework for calculating platform ROI, structuring the business case, and presenting it in a way that actually lands with decision-makers.
Chapter 26 Gives you a complete, annotated AWS reference architecture — eight functional layers, real configuration code, and the reasoning behind every component choice, specific enough to use as the starting point for your own implementation.
Chapter 30 follows a fintech platform team scaling from 50 to 500 engineers on that same AWS stack — the sequencing decisions, the wrong turns, and what a platform build looks like under timeline pressure.
What's in the sample
—Chapter 19: How to calculate toil cost and frame it in language finance understands
—Chapter 19: A repeatable ROI model you can adapt to your org's numbers
—Chapter 19: How to structure the narrative — from problem to ask
—Chapter 26: A complete AWS cloud-native platform reference architecture across all eight layers — with real Terraform, YAML, and the reasoning behind every component choice
—Chapter 30: A fintech case study scaling from 50 to 500 engineers — including the decisions that were right, and the one that nearly took down payment processing
Jordan Dinsdale
Senior Director of Platform Engineering at TransUnion.
The views, opinions, and insights expressed in this book and on this website are entirely my own. This work is independent and does not represent the views, endorsement, or affiliation of any current or former employer