15829 W Rosewood Way

Surprise, AZ 85374

$389,900D

3 bd · 3.0 ba · 1,780 sqft · Built 1997 · SingleFamily · Pending · 66 DOM

Cashflow @ list (25.0% down · 7.5%)

• Estimated rent: $2,989/mo
• Mortgage (P&I): −$2,045
• Tax + insurance: −$337
• HOA: −$160
• Vac / Maint / Mgmt: −$628
• Net cashflow: $-181/mo
• Annual: $-2,167/yr
• Cap rate: 5.74%
• Cash-on-cash: -1.99%
• DSCR: 0.91
• 1% rule: 0.77%
• Cash to close: $109,172

Investor read

• This is a 3-bed/3.0-bath single-family listed at $390k.
• At list price, monthly cash flow is $-181 ($-2k/yr) — negative.
• To cash-flow at today's rent, offer at most $358k (8.2% below list).
• To meet the 1% rule (rent ≥ 1% of price), the offer needs to be $299k (23.3% below list).
• It's been on market 66 days — a 6% lower offer ($367k) is reasonable based on typical stale-listing flexibility.
• Recommended offer: $299k (23.3% below list) — sets the bar for 1% rule.
• Local home prices are declining (-3.0%/yr); year-one equity from $3k of loan paydown is wiped out by about $12k of value loss. Plan a longer hold.
• Location reads 74/100 on livability (#19 in AZ, #4,616 nationally) — a middle-class / working-renter tenant base. Strengths: crime A+, housing A+, employment A-; Watch: health & safety D+, amenities D-, commute F.
• Dysart Unified District (4243) (suburban): math 34% / reading 40% proficiency, ranked #73 of 249 in AZ (top 29%) — families likely to look elsewhere, expect single-tenant / working-renter base with shorter leases.
• Market conditions: Rents flat; 399 active listings in the ZIP; 19 comparable units currently listed for rent nearby; rentals lingering (median 44d on market — plan ~5-8 weeks vacancy on turnover, expect pricing pressure); 63% of comp listings sitting > 30 days — soft ceiling on asking rent; solid renter incomes; 36,011 units permitted in Maricopa County in 2024 (12,801 in 5+ unit buildings).
• Maricopa County population projected at +38% by 2050 — long-run rental-demand tailwind backs the buy-and-hold thesis.
• 2 sale attempts with the ask held roughly flat each time — persistent listings suggest the price (not the market) is what's stuck; bring a comps-based counter.
• Current owner paid $140k; list at $390k implies a 179% gain — meaningful room to come down on a strong offer.
• Climate carrying-cost: extreme-heat days projected 7→18/yr by 2055 (HVAC capex compounding) — expect insurance premiums to compound above CPI over the hold.
• Cap rate 5.7% vs local median 3.3% in Surprise — top-decile yield for the area; either an underpriced asset or a hidden risk that comps aren't pricing in. Stress-test before assuming the spread holds.
• This rent runs 44% of the median local income ($81k/yr) — at the standard rent-burdened threshold; future hikes will face affordability resistance.

Questions for listing agent

• What do current leases actually rent for vs. the listed asking? Can we see a recent rent roll and the last 12 months of T-12 income?
• It's been on market 66 days. Have you received any prior offers? Is the seller open to a 23% concession, seller financing, or rate buy-down credit?
• What does the HOA fee cover, when was the last increase, and are there any pending special assessments or reserve-fund shortfalls?
• Why hasn't it sold? Are there any deal-killer items the seller is aware of (foundation, flood, title, zoning, code violations)?
• Is there a deadline driving the sale (1031 exchange, divorce, estate, relocation)? That informs how much negotiation room exists.
• The area grade is low — what's the realistic commute time and amenity access for the typical tenant pool here? Any planned neighborhood developments (good or bad) we should know about?
• What's the average days-on-market for RENTAL listings here right now (not sales)? A rising rental-DOM trend means longer vacancies and softer asking-rent achievability than the comps imply.
• What's the recent tenant-quality profile in this submarket — average credit score on applications, eviction rate, late-payment / NSF rate, and stable-employment percentage? A property-management company in the area should have these aggregated.