TRAVEL COMPANY
From Checklist to Audit Trail: Reinventing Release Management with Claude Code
Cutting Release Admin by 80%
Kablamo uses Claude Code to cut release times by 80% for a travel company, replacing four disconnected manual systems with a purpose-built Release Agent that automates everything safe to automate while keeping a human in the loop for everything that isn't.
The Challenge
The travel company's core sales product generates bespoke travel itineraries for end customers, so release quality ties directly to revenue. Every release meant manually updating four disconnected systems:
- Confluence checklists
- Jira fix-version linking and ticket transitions
- GitHub release notes
- Rollback-image preparation
A single missed step in that process could go unnoticed until it surfaced downstream, and a rollback needed to be ready before it was needed, not assembled after the fact.
The Approach
Kablamo built its Claude Code Release Agent to bring speed and rigour to release management, then applied and customised it for the travel company's systems and workflows. It runs every release check that's safe to automate, guides the team through the parts that aren't, tags versions across tickets and commits, and drafts fully cross-linked release documentation as the release happens. It integrates via MCP with Atlassian and GitHub, using local markdown files as its working memory across handoffs.
Deployment triggers and product-owner sign-off remain with a person by design: the agent surfaces what it can't decide rather than treating silence as approval. Built as a reusable capability rather than a one-off, the Release Agent is now Kablamo's standard approach to release management across engagements.
The Results
The impact showed up in three ways.
Speed. The Release Agent cut release admin from hours to minutes, an 80%+ reduction. That time was reinvested, not eliminated: automated checks per release scaled from 26 on a smaller release to 34 on a larger one, so releases now carry more rigour than the manual process ever did. That's what makes running releases around fifteen times a year practical, without trading pace for quality.
Quality. The Release Agent is now the standard way releases are executed for the travel company, tuned to their specific systems and continuing to be refined as the engagement evolves.
Governance. Release documentation is now produced during the release, not reconstructed after it. On one release, the agent held back a change pending its ticket while confirming a further eleven tickets out of scope. On another, its pre-flight checklist caught a partial outage in a third-party CI tool before it caused a problem, invisible even on that tool's own status page. What used to be reconstructed after the fact is now a living record of every release.
Looking Forward
The Release Agent is built as a reusable capability, not a one-off, and is now Kablamo's standard approach to release management across engagements. As it's applied and tuned to each client's systems, the same speed, quality, and governance gains scale with it, rather than depending on manual effort keeping pace.
The underlying pattern, automating everything safe to automate while keeping a human in the loop for judgement calls, extends well beyond release management, to any repeatable but high-stakes process that would benefit from consistent rigour without adding headcount.
