Asking price and market value are two different things in every Michigan submarket we work in, and the gap between them tends to be widest exactly where an exchange deadline is putting the most pressure on an investor to move fast, which is precisely when a defensible number matters most.
Why One Statewide Number Never Tells the Whole Story
A cap rate that looks reasonable for a Southfield office building says very little about whether it is reasonable for a Traverse City retail property or a Kalamazoo industrial building. Michigan's regional variation is wide enough that a single statewide average is close to useless for pricing any one deal. We build comparisons at the submarket level, pulling sale and lease data from the specific corridor or city the replacement candidate sits in, whether that is the Ann Arbor medical office cluster or a Lansing government-adjacent office node.
We have seen investors walk into a Grand Rapids negotiation with pricing expectations formed entirely from a Detroit-metro deal they closed the year before, and the two numbers simply do not translate. Tenant credit, corridor demand, and even typical lease structure can differ enough between those two markets that a Detroit-based instinct is closer to a starting guess than a reliable benchmark.
What Goes Into a Comparable Set
A defensible comparison relies on more than a handful of headline sales.
- closed sale comparables from the same or a genuinely similar submarket
- lease comparables tied to actual signed terms, not asking rents
- cap rate observations adjusted for tenant credit and remaining lease term
- capital expenditure history that affects true net income
- liquidity context for smaller markets where few transactions occur in any given year
The Small-Market Problem
Submarkets like Traverse City or smaller mid-Michigan towns simply do not generate enough transaction volume to build a large comparable set the way Southeast Michigan does. In those cases we widen the geographic net carefully, prioritizing property type and use similarity over strict proximity, and we are explicit with investors about where the comparable data is thinner so expectations stay realistic rather than falsely precise. A Traverse City retail comparable set might reasonably pull from other northern Michigan resort towns before it pulls from a Detroit suburb, even though the suburb is geographically closer, simply because the demand drivers are closer in kind.
Separating Outliers From the Real Trend
Every submarket has at least one sale that does not fit the pattern, whether from a related-party transaction, an unusually motivated seller, or a property with hidden issues that depressed the price. We flag those outliers rather than letting them pull an average in a misleading direction, since an investor pricing a replacement property against a skewed comparable set can end up either overpaying or walking away from a fair deal. In smaller Michigan submarkets, where the total comparable pool might only be four or five sales, one outlier can swing the average more than in a deep market like Southeast Michigan where it simply gets absorbed.
Turning the Analysis Into Something Usable
The final output is a short pricing narrative alongside the comparable table itself, written so the investor and their advisor can see both the numbers and the reasoning behind which comparables were included and why. That narrative is what actually gets used in negotiation, not the raw data set on its own, and it is usually what a broker or seller's agent responds to more directly than a spreadsheet full of unexplained figures.
Common 1031 Exchange Questions
Does a statewide Michigan cap rate average help price a specific property?
Not much. Cap rates vary widely by submarket and tenant quality across the state, so we build comparisons at the local level rather than relying on a broad statewide figure.
How do you handle thin comparable data in smaller Michigan markets?
We widen the search by property type and use rather than strict distance, and we are upfront with investors about where the comparable set is thinner, particularly in smaller up-north or mid-Michigan submarkets.
Are asking prices treated the same as closed sale comparables?
No, asking prices are not closed-market evidence and can overstate value, so our comparable sets prioritize actual closed transactions and signed lease terms wherever they are available.
What happens when a comparable sale looks like an outlier?
We flag it and generally exclude it from the core average, since a single unusual transaction, whether from a related-party deal or a distressed seller, can distort the pricing picture if it is treated as typical.
Can pricing experience from Detroit-metro carry over to a Grand Rapids or Traverse City deal?
Not directly. Tenant credit, corridor demand, and typical lease structure vary enough between Michigan submarkets that a pricing instinct formed in one region is better treated as a starting guess than a reliable benchmark elsewhere.
How many comparable sales are enough to support a pricing narrative?
There is no fixed number, but we generally look for enough closed, genuinely similar transactions to show a defensible range rather than a single point estimate, adjusting the target count down in thinner submarkets where that volume simply is not available.
Does market comparable analysis factor in exchange timing pressure?
We keep pricing analysis and timing pressure as separate considerations, since a defensible price should not shift just because an exchange deadline is close, even though that pressure is clearly part of the real decision an investor is making.
