In real estate development, “vertically integrated” gets used loosely. At its tightest, it means the same firm sources and underwrites the opportunity, oversees the construction, and manages the asset through stabilization — one team, accountable from start to finish.
That’s a different posture than the more common alternative: a fee developer that hands a project to a construction manager, then to a third-party operator, and steps away once the building is full.
The three legs of vertical integration
A vertically integrated developer carries three functions in-house:
Development. Identifying the site, underwriting the deal, navigating entitlements, structuring the capital stack, and signing the loan. This is the function that decides what gets built and on what economics.
Construction oversight. Managing the general contractor, the budget, and the schedule from groundbreaking through certificate of occupancy. The team that does this work is not the contractor — the general contractor is hired — but the developer’s representative who holds the contractor accountable to the design, the budget, and the timeline that the development team committed to.
Asset management. Running the community from lease-up through stabilization, working with property management on rent strategy, expense control, capital reserves, and the long-run health of the asset. Asset management is where the actual financial performance of the deal is realized; before this stage, everything is a forecast.
A vertically integrated developer carries all three. A fee developer carries the first, hires out the second, and may have no role in the third at all.
Where the handoff risk lives
The most expensive mistakes in development tend to happen at handoffs. A budget assumption that made sense at underwriting gets quietly missed in construction. A design choice that looks fine on a drawing creates an operational problem nobody notices until residents move in. A vendor decision made under deadline pressure during construction creates a maintenance line item that haunts the asset for a decade.
When the same team carries the project across all three phases, those handoffs disappear. The person who underwrote the rent assumption is in the room when the construction-cost surprise forces a value-engineering decision. The person who will operate the building is in the room when the design team considers a finish choice that affects make-ready costs. The person who signed the loan is the same person whose reputation is tied to whether lease-up holds the underwritten pace.
That is not just an organizational preference. It changes the decisions that get made.
How alignment shows up day-to-day
Vertical integration is, in part, a story about incentives. A fee developer’s economics are largely realized at closing or at lease-up — once the building is full and stabilized, the fees stop. A vertically integrated sponsor, by contrast, continues to share in the performance of the asset over time, often alongside the same investor partners whose capital funded the project.
The day-to-day result is that decisions get evaluated against long-run performance, not short-run delivery cost. A specification choice that costs slightly more to install but saves meaningfully on operating expense over the life of the asset is a different conversation when the team making the decision will also operate the asset for years.
The trade-offs
Vertical integration is not the right model for every developer. Carrying all three functions requires scale — enough deal flow to keep a construction team busy, enough stabilized assets to justify in-house asset management, and the operational infrastructure to support both. It also tends to slow geographic expansion: moving into a new metro means standing up a real local presence, not just signing up new vendors.
A fee development model can move faster across markets, with a lighter operational footprint and lower fixed overhead. For developers prioritizing breadth and deal velocity, that model has its own logic. The trade is that the depth of accountability — the alignment that comes from one team carrying the project through stabilization — is harder to maintain when each function is handed to a different party.
A philosophy, not a tactic
Vertical integration is best understood as a philosophy about how a sponsor relates to its assets and its investors, not as an organizational chart. The point isn’t that every project benefits from in-house everything — it’s that the alignment between the team making the decisions and the team that lives with the outcomes is, in our view, what produces a better outcome over the long run.
That alignment is the model we run at Alder, and it’s the lens we use to evaluate every decision a project asks of us.