Engineering Intelligence Assessment
“Where does our delivery actually get stuck — and what are the three changes worth making?”
4 weeks
Four weeks of work, kickoff to readout, starting once data access is in place.
CHF 18–25k (estimate)
An indicative estimate. The final figure depends on the number of teams and repositories in scope, and is agreed with you before we start.
30–300 engineers
Organisations large enough that delivery performance has become a question nobody can answer from memory.
“I can't answer how fast we ship, or where it gets stuck.”
If you can already answer that with data you trust, you do not need this.
Four weeks, in the open.
Four things, all of them yours.
A delivery-performance baseline you can re-run — the number you measure against next quarter, not a slide.
Where the time actually goes, with the queue and wait time separated from the work.
A working dashboard your team keeps and maintains after I leave. No dependency on me to see your own numbers.
Prioritised, with effort and impact estimated for each. Enough detail that your team can start on Monday.
What this is not.
- Implementation. The assessment ends with a prioritised plan; building it is a separate engagement, and you are free to do it yourselves or with anyone else.
- A tooling procurement exercise. If the finding is that your tools are fine and your review process is not, that is what the readout will say.
- A team performance review. This measures the delivery system, not individuals, and the readout names no names.
- A compliance audit. Supply chain controls come up, but this is not an ISO or regulatory assessment.
Worth a conversation?
Thirty minutes is usually enough to tell whether an assessment would find anything you don't already know. If it wouldn't, I'll say so.