The property manager wants a flat annual contract and I want per-job pricing, and I cannot figure out which side of that argument actually benefits me.

Question

A flat annual contract looks stable until the property manager fills their portfolio with problem units. Say the agreement covers 40 turnovers at $180 each, which is $7,200 guaranteed. That sounds clean until month four delivers six units with full estate-level debris because a lease expired and nobody checked on the tenant for six months. Those six jobs cost $420 each to run, and the remaining 34 have to average $94 to break even on the year. Per-job pricing avoids that math entirely, but the property manager trades away predictability and will shop a competitor the moment a slow quarter makes the invoices feel high.

The case for the flat contract is volume certainty and scheduling. If those 40 units come in on a predictable cycle, labor and truck time get optimized in a way that per-job work does not allow, and that efficiency is real money. The case against it is that the contract almost always gets written before you know the actual condition of the portfolio, which means you are pricing off the property manager's best-case description of their worst units.

The clause that matters most is the scope definition. A flat contract without a written definition of what constitutes a standard turnover versus an estate cleanout is just a dispute waiting for the right month to surface. If the contract does not specify cubic yards, floor condition, appliance removal, or pest situation as triggers for a supplemental charge, the property manager will expect standard pricing on a job that runs three times the cost.

What does the property manager's current portfolio actually look like in terms of average tenant tenure and vacancy condition when units turn?

Rena Guide · Answer

The math you laid out is right, and the clause point is the real answer to your own question.

Neither structure is better in the abstract. What determines which one benefits you is the condition variance in that specific portfolio. A portfolio of newer units with six-month leases and active management will have tight variance, meaning actual job costs cluster close to your average. A portfolio of older units with long-tenure tenants and minimal inspection history will have wide variance, meaning some jobs cost two or three times others. Flat-rate contracts reward you when variance is low and punish you when it is high.

So before you negotiate the pricing model, you want two numbers from the property manager: average tenant tenure (how long residents typically stay) and what percentage of recent turnovers required haul-out beyond standard cleaning. Those two things tell you the variance risk better than anything else.

If the property manager will not share that, or does not track it, that is itself useful information.

On the scope clause, you already identified the right move. A flat contract is workable if it defines a standard turnover in measurable terms and names a supplemental rate for anything outside that definition. Cubic yards of debris removed, appliance count, floor category, presence of biohazard or pest evidence are all reasonable triggers. Without that language, you are absorbing the property manager's deferred maintenance costs.

The thing worth knowing before this conversation happens: your archetype skews toward analysis before commitment, which is an asset here. A property manager who resists putting condition triggers in writing is telling you something about how they expect disputes to go.

What do you know so far about the age and management style of this portfolio?

delphine_moreau · Answer

Flat contracts win on volume efficiency; per-job wins when unit condition is unpredictable.

The property manager wants a flat annual contract and I want per-job pricing, and I cannot figure out which side of that argument actually benefits me.

2 replies