Release lead · Melbourne
“They spent the first day arguing with our compile cache numbers until we admitted half of them were stale. Awkward, useful, and the only reason the second week’s plan stuck.”
— Mara K., after a build & compile analytics audit
Build guild · Brisbane
“The workshop did not invent new dashboards. It forced us to pick four measures for the cut checklist and retire nine that nobody could defend. I still miss one of the retired charts; the release train does not.”
— Dion R., release metric workshop
Engineering director · Adelaide
“Compile cost review landed a map finance could read. Savings estimates were conservative—maybe too conservative—but the policy changes on night builds were adopted the following sprint.”
— Helen P., compile cost review
Platform owner · Perth
“Clear writers. Slightly stubborn about vanity averages. That stubbornness is why we hired them again for the second application family.”
— Sam T., follow-on audit
A Perth product company saw its compile farm invoice climb for three consecutive quarters. Nightly full rebuilds on long-lived feature branches were the quiet culprit; the team’s “average build time” slide had smoothed the spike into something that looked stable.
During a five-day compile cost review we rebuilt the story from machine-hour exports and branch policy logs. The written map showed that two branch classes accounted for most of the rise. The client changed retention rules for those branches and moved full rebuilds to a narrower overnight window. They did not replace their CI product; they changed the policy the clocks were measuring.
If your story looks similar, start with a briefing request.