Where the delivery margin goes

The production estimate covers the build. Clarification and reconciliation still need a budget.

Illustrative scenario. The situation and arithmetic below explain a delivery pattern. They are not a reported interview or a client result.

The ticket has reopened.

The component has passed its layout review, but a new comment asks which record should supply the price, another asks what happens when that record is empty, and the release lead is waiting for an answer.

The layout matches the design.

Distributed delivery had a purpose.

Bringing in an external production team can provide specialist capacity and keep a project moving while the agency’s own people concentrate on the account, creative direction and decisions that depend on their knowledge of the client.

The arrangement can work well.

The people are carrying the context.

The producer translates the client’s answer into a ticket because they attended the meeting, while the developer waits for a rule they cannot safely invent and the designer checks that the resulting state remains usable.

Each person is doing necessary work.

The estimate counted only part of it.

Consider an illustrative batch of 20 tickets: if each needs 45 minutes of clarification and 30 minutes of additional review, the batch adds 25 hours across the team beyond the implementation time already allowed in the estimate.

The extra work is measurable.

Distance can add friction.

Different working hours, late client changes and unfamiliar source records can extend the exchange, particularly when a decision reaches production after the person who can explain it has finished their day or moved to another account.

Location can affect the delay.

The missing input crosses every border.

If the brief specifies the visible component but leaves its source record, exceptional states and acceptance decision unresolved, moving production closer changes the conversation’s speed while leaving the same decisions for someone to make during delivery.

The original estimate excluded operating decisions that the build still requires.