GTM platform engineering · Kai Karlstrom
Platform engineering for GTM engineers.
I run the internal platform a team of GTM engineers builds client systems on. The problems on it are the ones software platform teams have already named, and they have known answers. This page is those answers, applied, and what each one does.
THE CLAIM What limits a GTM engineer's output isn't their skill. It's everything under their work: each client's environment, credentials, scheduled jobs and model choices. That layer is a platform, and platform engineering is what lets a team of GTM engineers scale.
self-healing
16apps held to their declared state: five always running, eleven started only when a job is due
heartbeats
52scheduled jobs checked against their own schedules every morning
deploy gate
3,070tests that must pass before anything deploys
model gateway
10 + 1model routes cleared by evals on our own data, plus one on trial
Read from the live system on 19 October 2026
The rest
is the build.
Where the platform sits, why it's a platform, what engineers use, the seven practices, the control point, the LinkedIn loops, what it's done and what's next.
Open the page
Every system, diagram and number.
The rest of this page is how the platform is built and run: each practice with its diagram, and what it does.
Got a link from me? Open it and the page unlocks.