# Forecasting demand and dynamic pricingdynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.View full definition → in real estate markets
At large multifamily operators, rents are not set once a year by a leasing manager with a spreadsheet. They are recalculated every night. Software ingests yesterday's leasing activity, competitor asking rents, and how many units expire next month, then recommends a new price for every available floor plan. A two-bedroom facing the courtyard might tick up 1.2 percent while an identical unit facing the parking lot drops 0.8 percent. This is revenue management, and it is one of the most mature uses of AI in real estate.
Companies like AvalonBay and other large REITs (Real Estate Investment Trusts, publicly traded firms that own income-producing property) have used revenue management platforms for years. The math borrows directly from how airlines and hotels price perishable inventory. An empty apartment tonight is revenue you can never recover, just like an empty airline seat.
The core insight: a vacant unit earns zero, and that loss is permanent. So the pricing question is never just "what is this unit worth?" It is "what price fills it fast enough without leaving money on the table?"
That tradeoff has a name: absorption. Absorption is the rate at which available units get leased over a period. If you have 40 vacant units and lease 10 per week, your absorption rate implies a roughly four-week runway.
Pricing changes absorption. Cut rent and units lease faster (higher absorption, lower rent per unit). Raise rent and they lease slower. The model's job is to find the price that maximizes total revenue over time, accounting for how long units sit and what future demand looks like.
Hotels track RevPAR (revenue per available room). Multifamily operators think similarly: revenue per available unit across the whole property. A model that pushes rents too high wins on headline rent but loses on occupancy, and total revenue falls. The optimization target is the product, not the price alone.
A demand forecast for a single property blends several signal categories.
Internal pipeline signals
Seasonality
Leasing demand is highly seasonal in most US markets. Spring and summer see far more moves; December is slow. A model that ignores this will overprice in January and underprice in June. Seasonality is usually the single strongest pattern in the data.
Submarket signals
A submarket is a defined geographic slice of a metro (for example, a specific set of neighborhoods or ZIP codes). Signals include local job growth, new supply coming online (a competitor delivering 300 units nearby suppresses your pricing power), and comparable asking rents.
Macro context
Interest rates, for-sale housing affordability (when buying is expensive, more people rent), and regional migration trends.
Here is the kind of tabular data a pricing model consumes, one row per unit per day:
# Conceptual feature layout for a nightly repricing model
features = {
"floor_plan": "2BR-B",
"days_vacant": 14,
"expirations_next_30d": 6, # supply pressure
"weekly_leads": 22, # demand signal
"lead_to_lease_rate": 0.11,
"comp_asking_rent": 2450, # scraped competitor set
"week_of_year": 24, # seasonality
"submarket_new_supply_90d": 180, # units delivering nearby
}
# Model predicts absorption probability at candidate prices,
# then picks the price that maximizes expected revenue over horizon.Note what is NOT here: the resident's name, demographic data, or anything that could introduce discrimination risk. That exclusion is deliberate, and we will return to why.
The forecast estimates demand. The pricing engine turns that into a number.
A common approach: for each candidate price, the model estimates the probability the unit leases within a target window. Multiply expected occupancy by rent across a time horizon, and you get expected revenue for each price. Pick the price that maximizes it.
In practice, operators layer in business rules on top of the model:
The human still approves. Most systems recommend; a revenue manager reviews exceptions. Full autopilot is rare because a bad feed (a competitor mistakenly listed a unit at half price) can poison the model.
🎬 [VIDEO: "How Revenue Management Works in Multifamily" — youtube.com — a plain-language walkthrough of automated rent pricing for apartments]
You cannot teach this topic honestly in 2026 without the legal context. RealPage, the dominant revenue management vendor, became the subject of a US Department of Justice antitrust lawsuit alleging its software helped landlords coordinate rents by pooling competitors' nonpublic data. Several cities and states have passed or proposed restrictions on algorithmic rent-setting software.
The legal question is not "is dynamic pricingdynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.View full definition → bad?" It is narrower: does software that ingests competitors' private data and nudges many landlords toward similar prices function as a coordination mechanism? Using public asking rents is standard practice. Sharing confidential future pricing across competitors is where regulators focus.
You can follow the case through the DOJ Antitrust Division's public case documents. The takeaway for operators: know what data your vendor uses, and whether it is public or shared confidentially.
The US Fair Housing Act prohibits housing discrimination based on protected characteristics (race, national origin, familial status, disability, and others). A pricing model that uses ZIP code or other proxies can produce disparate impact: a neutral-looking variable that correlates with a protected class and produces discriminatory outcomes.
This is why serious operators exclude demographic features and audit models for proxy effects. "The algorithm did it" is not a legal defense.
Knowledge check
1. Why is a vacant apartment unit described as a 'perishable good' in revenue management?
2. A revenue management model recommends raising a unit's rent. What tradeoff is it implicitly weighing?
3. Why can pushing headline rents as high as possible actually reduce a property's total revenue?
4. Select ALL correct answers about the concept of absorption in multifamily pricing.
Select all the correct answers.
5. Select ALL correct answers about how real estate revenue management borrows from airlines and hotels.
Select all the correct answers.
Imagine a 200-unit property. It is late May (peak season, week 22). You have 12 vacant two-bedroom units and 18 expirations coming in the next 45 days. Weekly leads are strong at 25, conversion is running 12 percent, so you expect roughly 3 leases per week from that traffic.
Current asking rent is 2,400 dollars. The model sees strong seasonal demand and low competitor availability nearby. It estimates that at 2,475 dollars, absorption slows only slightly (you still lease in about five weeks) while capturing 75 more dollars per unit per month across a 12-month lease.
The recommendation: raise to 2,475. The revenue manager checks that no competitor just dropped a large block of units and approves.
Now flip it to January (week 3). Same property, but leads fall to 10 per week and you still have 12 vacant units. Holding at 2,400 means units sit for months, and each empty month costs a full 2,400. The model recommends dropping to 2,325 to accelerate absorption. Losing 75 dollars per month hurts less than losing an entire month of rent.
That asymmetry (vacancy loss versus rent optimization) is the heart of the discipline.
Thin data. A single small property does not generate enough leases to train a robust model. Vendors pool data across many properties, which is exactly what creates the antitrust scrutiny. The value and the legal risk share a root cause.
Regime shifts. Models trained on stable years fail when conditions break. A sudden wave of new supply, a local employer layoff, or a rate shock can invalidate historical patterns. Human oversight matters most precisely when the model is least reliable.
Feedback loops. If every operator in a submarket uses similar software reading similar signals, prices can move together even without explicit coordination. Regulators and researchers are actively studying whether this alone raises rents.