back_office_ops · saas · workflow
Spotify's background coding agent (Honk) generates 1,500+ merged pull requests across the codebase
Spotify's Fleet Management system handled simple, repeatable code transformations well but could not solve complex migrations. Defining source-to-source transformations programmatically required deep specialized expertise, and the complexity caused one migration script alone to grow to over 20,000 lines of code, limiting advanced use to a small number of teams.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Engineer defines task in natural language
Engineers define and run fleet-wide changes using natural language prompts.
Tools used
Fleet ManagementMCPGCPMLflowLLMs
Outcome
Spotify's AI coding agents have generated more than 1,500 pull requests merged into production, achieving a time saving of 60–90% compared to writing code by hand, while enabling complex migrations that were previously out of reach for most teams.
Results
Time saved60–90%
Volumemore than 1,500
Running sinceLast February
Grounding & classification
Source type: technical build writeup
29 fields verified against source quotes.
agentic workflowai agentcode generationmulti agent workflowcode diff prbuilder submittedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwareemployee productivitythroughput increasetime savedtechnical build writeupback office opsagentic task executionai draft human approval