The unit mix is the business plan.
Who This Matters To (And Why)
Critical: Developer (unit mix is the revenue model, not a design variable), Architect (you're executing a financial decision, not making a product decision), Banker (unit mix determines rent roll stability and underwriting risk).
Important: GC (unit mix drives repetition, cost per unit, and prefabrication opportunity), Broker (mix determines your target renter demographic and absorption rate).
Context: Engineer, Interior Design, City.
Highest typology impact: Multifamily (obviously), Mixed Use (residential component), Hotel (room type mix is the same thesis). Lower impact: Office (floor plate drives program more than room mix), Industrial (minimal).
A unit mix document is a pro forma in disguise. The developer who treats it as an architectural input is making a financial decision without knowing it.
How It Shapes Development
Unit mix is typically presented to architects as a program: "We want 30% studios, 50% one-bedrooms, 20% two-bedrooms." That feels like a design brief. It's actually an income projection. Each unit type carries a different rent per square foot, a different absorption rate in the market, and a different construction cost per unit. The mix is an optimization across those variables. The developer — or their market analyst — ran those numbers before the program landed on anyone's desk.
Studios rent at a higher rate per square foot than two-bedrooms, usually. In most urban markets, a 450 SF studio at $2,800 rents at $6.22/SF. A 950 SF two-bedroom at $4,200 rents at $4.42/SF. More studios, more revenue per square foot of building. But studios have higher turnover, higher operational cost per unit, and attract a demographic that may or may not match the submarket. Two-bedrooms attract longer-term residents, stronger credit profiles, lower turnover. The mix is a bet on which trade-off produces the best stabilized NOI over the loan term.
Construction cost cuts the other direction. Studios and one-bedrooms share walls, plumbing stacks, and mechanical runs more efficiently than large units — up to a point. But higher unit counts mean more doors, more bathroom fixtures, more MEP connections, more FF&E, more management complexity. A building with 300 studios costs more to manage than a building with 200 one-bedrooms at equivalent square footage. The developer's asset management assumptions affect the mix as much as the rent projections do.
Zoning enters here too. Many jurisdictions cap density by unit count rather than FAR or height. A floor plate that could hold 30 units might hold 22 under a density restriction. That constraint pushes unit sizes up — which changes the mix — which changes the revenue model. The architect working through unit mix optimization is simultaneously solving a zoning problem and a financial problem. The tools they need are pro forma math and zoning analysis, not floor plan aesthetics.
The practical consequence: architects who can run a unit mix pro forma before presenting schematic layouts are in a fundamentally different position than those who cannot. They can propose a mix shift — "moving from 50% to 40% one-bedrooms and replacing with additional studios adds $180K in annual NOI at current market rents" — and have that be the design conversation. That's an architect who's in the deal. The alternative is presenting a floor plan and getting told the mix is wrong after three weeks of layout work.
Quick Wins: Connect This Applet To
- Applet #3 (Cap Rates): Show how unit mix affects stabilized value at a given exit cap. Change the one-bedroom percentage, watch the NOI update, watch the exit valuation update. Three linked fields, no code beyond arithmetic.
- Applet #37 (Unit Depth / Daylight): Mix slider linked to floor plate. When studio percentage rises, show how floor plate depth requirement changes. One slider, one updated floor plate diagram.
- Applet #68 (Pro Forma): Full sensitivity: unit mix across rows, rent per SF assumptions across columns. Grid showing NOI outcomes. Twelve cells, static calculation.
For Other Professions (24-Hour Builds)
- City Planner: Add "workforce housing unit count" derived from mix. If city requires 15% affordable at 80% AMI, show how that requirement changes the revenue mix. One percentage input, one updated NOI output.
- Investor: Add LP return sensitivity by mix. Show how a 10% shift from studios to two-bedrooms affects equity IRR. Two mix scenarios, one IRR comparison readout.