Most indie studios don't know their build pipeline is broken until it blocks a release. Here's how I systematically find the bottlenecks in 20 minutes flat.

Start with the logs

The first thing I look at is your CI logs from the last 10 runs. Not the build output — the timing data. Most CI systems expose per-step timing. Sort by duration descending. The top 3 steps are where you're losing time.

In nearly every Unity project I've audited, the top culprit isn't compilation. It's asset processing. Unity's asset pipeline is single-threaded by default, and most teams never configure the accelerator.

Check your branching strategy

If your team is merging into main and hoping CI catches breakage, you're already in trouble. The correct pattern for Unity projects: every PR runs a fast incremental build, main runs the full platform build.

The bus factor test

Here's a question I ask every lead: "If your build engineer quit tomorrow, could anyone else ship a build within 24 hours?" If the answer is no — and it almost always is — you don't have a pipeline. You have a person-shaped bottleneck.

In the full audit, I look at 12 dimensions: asset pipeline, code compilation, platform-specific builds, addressables configuration, caching strategy, artifact storage, deployment path, monitoring, alert routing, rollback capability, documentation, and onboarding time for a new team member to ship a build.

If you're interested in a pipeline audit, book a call and we'll talk through your current setup.