A developer buys furniture twice: once for the show unit, and once for every unit behind it. The show unit is a decision. The repeat order is a process, and the process is where money leaks. Most developers we work with already know this - what they have not usually worked out is where the process should sit, and who owns it. Still comparing options? everything we make maps everything we make in one page, and How to Get a Custom Furniture Quotation picks up the thread from here.

Twenty years of project work has taught us that the developers who get the best result are not the ones with the biggest budget. They are the ones who decide early how many tiers there are, which pieces are standard and which are bespoke, and who signs off the specification once instead of five times. This guide covers what a developer furniture package actually contains, how to keep a repeat order consistent across buildings and phases, how to phase delivery against a construction programme, and how to keep one contact and one scope from the brief to the last handover. If you are looking at the residential side of the same problem, our bespoke villa furniture service covers the individual owner route.

What a Developer Package Contains

A developer package is not one specification. It is a set of tiers, and the tiering is the whole job. The table below is how a package usually breaks down, and it is worth reading before you ask for a price, because the tiering decides what the price is.

The mistake we see most often is buying the show unit as a one-off and then trying to replicate it later. A show unit is allowed to be bespoke. The forty units behind it are not, and if they are treated the same way, the cost per unit ends up wherever the show unit happened to land. Tier it deliberately and the show unit becomes the top of a range instead of an orphan.

Repeatability Across Buildings and Phases

The question that decides whether a repeat order works is simple: can the factory make the same piece again, two years later, and it will look like it came from the same run? That depends on keeping things you would not normally think to keep. The board reference for the veneer, not just the species. The dye batch for the fabric. The hardware code. The finish recipe and its sheen level. The panel dimensions and edge profile.

Ask any factory to hold those records and to confirm in writing that they will make to the original specification for a stated period. Then keep your own copy. A phase three handover in 2028 should not depend on somebody remembering a conversation from 2025. Our sample and mock-up approval guide covers how the approved piece becomes a written standard that production and inspection both work from.

There is a second side to repeatability that is about people rather than materials. If phase one is approved by the design team and phase two by a different person with different expectations, the variation does not come from the factory. Fix the approval group once and keep it the same across phases, and write down who can approve a change.

Phasing Delivery Against a Construction Programme

A development has a programme, and the furniture has to follow it. Units are fitted in blocks, blocks are released in a planned order, and the loose furniture goes in at the end. Deliver to a block that is not released and you are storing furniture on site in the rain, waiting for a fit-out date, and hoping.

The practical part is scheduling against the site rather than against the factory. That means agreeing which block is released on which date, and delivering in the order the blocks are ready rather than in the order the containers arrive. The shipping and customs clearance guide covers the container side of that.

Our own practice is to build the delivery sequence into the production schedule rather than sorting it out at the end, so each item has a production slot, a packing slot and a delivery window against a named block. You get one sequence to plan around instead of a series of separate promises.

One Contact, One Scope

On a project that runs across buildings and phases, the number of people making decisions is the thing that usually goes wrong. Every extra approver adds a week. Every informal approval adds a version.

The arrangement that works is a single scope document that states what is being made, to what drawings, with what materials, and what is excluded. One named decision maker signs it. Changes go through that person and are recorded as a revision with a date. We do not need to be in every meeting - we need the scope to be current.

And keep one channel for the commercial and one for the technical. When a price question and a drawing question land in the same email thread, both get answered slowly. When they are separated, each moves at its own speed.

faq