A developer awarded a two-building envelope package: cladding and roof, delivered in fifteen months. Before it was even closed out, the same client awarded the adjacent lot — three buildings, a larger scope including windows and balcony doors.
Repeat awards are won or lost on the first project’s delivery data. The second lot had more buildings, more scope, and a shorter window: eleven months, overlapping with two other live sites.
Industrialise what the first lot had taught: same crews, same measured-quantity certification rhythm, pricing from a single transparent offer sheet the client could interrogate line by line.
Monthly progress certification against the offer BOQ; interfaces with the developer’s other trades resolved at site level within days, not escalated; access equipment and supervision shared across the concurrent sites to keep the eleven-month plan credible.
First lot completed on plan; second lot — 50% more buildings — delivered in eleven months against the fifteen of the first. The client’s delivery risk on lot two was priced by evidence, not promises.
- The most reliable delivery metric a board can ask for is simple: does the client hand this team the next site?
- A learning curve only materialises if crews, systems and certification rhythm carry over — continuity is a contract decision, not an accident.
Serial delivery converts execution history into pricing power — for both sides of the contract.