Every leasing website has a page where the decision actually happens. It isn’t the homepage. It isn’t the amenities gallery, however good the photography is. It’s the floor plan page. The moment a renter stops browsing a building and starts pricing a specific home for themselves.
Most floor plan pages are built for exactly one kind of renter. That used to be fine. It isn’t anymore.
two products, one page.
More properties now lease two ways at once. Conventional apartments priced by the unit sit alongside furnished suites priced by the bedroom. Co-living plans share a page with three-bedroom penthouses. By-the-bed leasing, once the preserve of student housing, keeps turning up in conventional multifamily.
Most leasing platforms haven’t caught up. They assume one pricing model and one shopper, so the property picks a lane and hopes. Show full-unit rates and the renter shopping a single furnished bedroom sees a number four times what they’d actually pay. Show per-bed rates and the family pricing a three-bedroom sees a figure that doesn’t cover their household.
Here’s the part that makes this expensive: the renter who sees the wrong number doesn’t ask a question. There is no form fill that says “this price confused me.” They leave, and the property never finds out why. It shows up in your analytics as an ordinary bounce, indistinguishable from someone who was never going to lease.
what we did at 626 on the park.
626 On The Park opened in Chicago’s South Loop with 16 floor plans and two leasing structures under one roof. Studios, two-bedrooms, and three-bedroom penthouses leased conventionally by the unit, plus fully furnished four-bedroom suites leased by the private bedroom. Three audiences to serve at once: young professionals, families, and students. And no prior-year traffic to learn from, because the building was brand new.
Three decisions shaped the page.
Segment the way renters think, not the way the rent roll is organized. The filters read Studio, 2 Bed, 3 Bed Penthouse, and 4 Bed (Per Bed). That last one names the leasing model in the filter itself, so a renter self-sorts before they ever see a price.
Show each plan’s price in its native format. Conventional homes show full-unit rates. Co-living suites show per-bedroom rates. No conversion math, no asterisk, no “starting at” that quietly means something different two rows down.
Put the action on the plan. Every floor plan carries its own Schedule a Tour and Lease Now. A renter who has found their home never has to back out to a generic contact form and re-explain what they already told you by clicking.
the results tell us it worked.
The floor plan pages carried the traffic. The six most-viewed layouts drew more than 3,000 views between them.
The mix is the part worth sitting with. Four conventional layouts and one per-bed co-living plan all landed in the top five. Both products found their audience on the same page, in the same reporting period, and neither one buried the other.
Downstream, that engagement produced 1,068 guest cards, 215 account creations, 159 completed applications, 100 click-to-calls, and 58 tour requests from 47,859 new users, 75% of whom arrived on a phone. The property is 44% pre-leased with lease-up still in motion.
3 questions for your own floor-plan page.
1. Does the filter name your leasing model? If any part of your building leases by the bed, the words “per bed” belong in the filter, not in a footnote under the price.
2. Can a renter tell whose price they’re looking at in under two seconds? Read your own page as someone who wants one bedroom. Then read it again as a family of four. If either has to do arithmetic, you are losing them.
3. How far is the action from the decision? Count the clicks between “this is my apartment” and a form. Every one of them is a place to lose a lease.
what we’re getting at is…
A floor plan page is the conversion point of the entire property. On mobile, where three-quarters of this audience arrived, it is often the only page that gets read properly at all.
If your building leases more than one way, a template that assumes otherwise isn’t a design compromise. It’s a leak.
Click to read the full 626 On The Park case study →
