Self-Service Release Build · price and payback
What your release work costs, and what fixing it costs
Enter the numbers for the release flows you want automated.
Prices in
Step 1 of 3
What your releases cost today
Count everyone who touches a release: engineers, release managers, ops, approvers.
A release flow is one path from merge to production: one pipeline and one way of deploying. Count each path once, however many services use it. A web app and its API deployed by one pipeline are one flow; an iOS app shipped through the App Store is another.
flows
For one typical flow
If your flows differ, use the average.
releases
Time people spend on it, all combined, including watching steps run
hours
Reruns, broken runners, manual fixes, environment setup
h / week
Releases that needed a rollback, hotfix or manual repair. At most the releases per month
releases
All people combined
hours
For all flows
Salary plus employer costs and overhead. Use your finance team's number if you have one
EUR / h
Hands-on hours a year0
Cost a year0
Step 2 of 3
What the Build removes
How does a release run today? Pick the closest description. It sets the share of hands-on hours the Build removes.
Hours returned a year0
Value a year0
Step 3 of 3
Build scope
The first team is included
teams
Starting point
Where it runs
Included in every Build
- Status messages in chat or the ticket for every release
- A change record for every production release: approval, author, commit and deploy
- A tested rollback, a runbook and 30 days of support
- Signed artifacts, a software bill of materials for every release, and an audit export
Add-ons
How the numbers work
Cost a year is the hands-on hours from step 1 times your hourly cost. Value a year is the part of that cost the Build removes, based on your choice in step 2. Payback is how long that value takes to cover the Build price.