Developer vs builder: why they're almost never the same company

The developer puts up the money and takes the risk; the builder gets paid for what it builds. That's why they're almost never the same company and subcontracting rules the industry.

English · Original discussion in Spanish · Published

Developer vs builder: why they're almost never the same company
Developer and builder: rarely the same company

The question that opens this topic is Construction 101: why are the company that develops a project and the one that builds it almost never the same? The short answer is that they trinc different logics. The developer provides the land and the money, appears in the project and in the LOE (Spain's Building Act) as an agent; the builder executes. And between them sits an award contract, often after a tender or several bids. There is no stable marriage or fixed ratio —that idea of one developer for every five builders doesn't hold up— but a relationship per project.

What each one does and why they split

The developer contributes the capital and assumes the risk of the property business: buys the land, commissions the design, hires the construction and sells the homes. The builder gets paid for what it builds. That's the key that explains the separation: if the development goes bust, the builder has already been paid. Some put it bluntly: large companies have an interest in separating activities to dilute risk, so the property arm takes on the credit and the collapse while the builder pockets the margin with no exposure.

That vertical integration existed and still exists. There was a lot of it before 2008, with builders as subsidiaries of developers to scrape extra margin. After the crash the model shifted to cascading subcontracting by trade: bricklayers, formwork crews, installers, each with their own contract and their own self-employed workers in between. There are also groups that keep both legs, with the developer and the builder under the same corporate umbrella.

The builder that's just a guy with a desk

The real structure of many builders is baffling. Technical team, site managers, administration, tax and legal advisors; the labour, subcontracted. Everything rented —cars, offices, equipment— and charged to each project. The reason, so the argument goes, is that if a crisis hits, it's a clean slate with nothing seized. Hence some builders are little more than a desk and a chair in a rented office, with everything else outsourced.

The result is a chain of contractors and subcontractors where it's sometimes hard to know who answers for what. Is that corruption or simple flexibility? The property business has always had its soap opera, and the figure of the corrupt contractor is a classic even in TV fiction.

Who supplies the bricklayers

Not all builders have bricklayers on their payroll. Some do; others rely on subcontracting, and it's those second-tier companies that employ the skilled workers. The question of whether this should be limited hangs over the issue, but practice is what it is: the actual work is spread across crews that often don't even report directly to whoever signs off the project.

Where the analysis gets stuck

The separation between developer and builder is not a whim or a secret: it's risk engineering. The money and the bricks go down different paths so that one's downfall doesn't drag down the other. What remains unanswered is to what extent that corporate architecture protects the buyer, or only those who design it.

Also available in: Deutsch

Summary of a discussion on Burbuja.info - Foro de economía, actualidad y política., translated from Spanish and reviewed before publication. Read the full discussion (49 replies).

More summaries

All summaries in English →

-
Back