About The Runbook
Why This Exists
Most operations content is written by people who have never shipped a system into production. They write about tools in theory. They write about AI like it exists in isolation from the messy data, legacy infrastructure, and fragile automations underneath it. The Runbook exists because that gap has real consequences. When your Pipedrive schema doesn't match your Airtable base, your automation fires wrong. When your data layer is inconsistent, your RAG pipeline hallucinates. The problem was never the AI — it was the architecture underneath it.
Who's Behind It
The Runbook was founded by a practitioner with experience across every layer of this stack. Big 4 consulting at KPMG, diagnosing why large organizations' information systems weren't producing trustworthy outputs. Solutions architecture at MongoDB, designing the database layer that everything else depends on. Implementation engineering at Forethought, watching AI fail in production when the data wasn't clean. Workflow development at Ave Workflow, building the automation logic that connects it all. That background isn't academic. It's operational. Every guide published here has been stress-tested against real systems, real constraints, and real failure modes.
What We Don't Do
We don't publish vendor-sponsored content. We don't write about tools we haven't used in production. We don't use the words “revolutionize,” “game-changer,” or “seamless.” If a system doesn't work with a limited budget, messy data, and a stack built by three different people over three years — we won't tell you it does. And we don't collapse seven distinct stack layers into one vague category called “AI ops.” Pipedrive gets its own guides. Airtable gets its own guides. So does Zapier, ActiveCampaign, MongoDB, and every RAG pipeline that failed in production because nobody cleaned the data first.
The best place to start is the newsletter.