How to Find Multifamily Roofs Due for Replacement (A Roofer's Targeting Playbook)

Most roofers who say they "do commercial" are really waiting for commercial to come to them. A property manager calls about a leak, somebody bids it, and that's the pipeline. Meanwhile the apartment complex two exits down has a 24-year-old modified bitumen roof that took 1.75-inch hail eleven months ago, the owner is an LLC registered in another state, and nobody has knocked on that door because nobody knows it's there.

Finding multifamily roofs that are actually due for replacement is a research problem before it is a sales problem. You are stacking three independent signals — who owns the building, how old the roof is, and what weather it has lived through — and the addresses where all three line up are your route. Get the targeting right and a two-person sales team can run a metro of 4,000 apartment communities without ever cold-walking a strip mall. Get it wrong and you burn six months knocking on roofs that have eight good years left.

What follows is the full workflow I'd hand a new commercial rep: how to build a list of multifamily properties, how to read roof age and remaining life off aerial imagery, how to layer storm exposure so the wind- and hail-worn roofs float to the top, how to find and reach the human who can actually sign, and how to document a roof so that the owner has a clean, accurate estimate to take to whoever pays for it. There is a lot here. Skim the section headers, take what fits your market, and build the rest into a repeatable system.

Why Multifamily Is a Different Animal Than Retail Roofing

Before the workflow, understand what makes this property class worth the extra research, because the differences drive every targeting decision downstream.

The roofs are big and the decision-makers are concentrated. A single garden-style apartment community might have 14 to 30 separate buildings, each with its own roof, adding up to 80,000 to 250,000 square feet of roofing under one owner. One signed contract can equal forty residential jobs. And one regional owner often controls a dozen communities, so a single relationship compounds.

Ownership is layered and deliberately opaque. Multifamily is almost never owned by a person named on the mailbox. It's an LLC, often a single-purpose entity that owns exactly one property, frequently managed by a third-party property management company, sometimes wrapped inside a syndication or a REIT. The person who answers the leasing office phone cannot approve a roof. Figuring out who can is half the job.

Roof types are mixed and the failure curves differ. A 1990s garden complex might be steep-slope asphalt shingle. A 1970s three-story walk-up might be low-slope built-up roofing (BUR) or modified bitumen. A newer mid-rise might be TPO or PVC single-ply. Each ages differently, fails differently, and shows different tells from the air. Your age estimate has to account for the assembly, not only the calendar years.

Capital is budgeted, not impulsive. Owners run these as financial assets. Re-roofs get planned into capital expenditure schedules, reserve studies, and refinance events. That cuts both ways: the buying cycle is slower, but a roof that's genuinely at end of life is a known liability the owner is often already worried about. Your job is to show up with documentation at the moment the asset crosses from "maintain" to "replace."

There's real money in being early and organized. Because so few roofers prospect this segment methodically, the competitive bar is low. A rep with a clean target list, accurate roof-age reads, and a professional documentation package looks like a different species than the contractor who left a flyer at the leasing desk.

The Three-Signal Model: Age, Storm, Owner

Everything in the rest of this piece rolls up to one mental model. A multifamily roof becomes a real opportunity when three signals overlap:

Any one signal alone is noise. A 25-year-old roof owned by a phantom LLC you can't reach is a dead end. A severe hail swath over a building you can't date is a guess. An easy-to-reach owner with a six-year-old roof is a waste of a conversation. The route you want is the intersection. Build each signal as its own layer, then find where they stack.

The sections below build those layers in order, then combine them.

Step 1: Build the Multifamily Property Universe for Your Market

You can't target what you haven't listed. Start by assembling every multifamily property in your service radius, then enrich it. This is grunt work the first time and a maintained asset forever after.

Define your geographic and size filters

Decide the box before you collect. A typical commercial re-roof program filters on:

• Radius / drive time: usually 45 to 90 minutes from your shop, or specific counties.
• Unit count: many crews start at 8+ units (smaller than that and the economics look residential). Garden-style 50 to 300 unit communities are the sweet spot for most.
• Property class: apartments, condominiums (HOA-owned roofs), senior living, student housing, and sometimes townhome associations.
• Construction era: you'll often pre-filter to buildings built before a cutoff year, because a roof on a 2019 building isn't due yet.

Source the raw list

Four reliable starting points, roughly in order of effort:

1. County assessor / parcel data. Nearly every county publishes a property tax assessment roll, and most now have a GIS parcel viewer. Filter by land-use code (multifamily codes vary by county but are usually in the "apartment" / "residential 5+ units" family). This gives you parcel ID, owner of record, mailing address, year built, building square footage, and often number of units. This is your backbone dataset.
2. The Census as a sanity layer. The U.S. Census Bureau's American Community Survey reports units-in-structure by tract, so you can see which neighborhoods actually have dense multifamily stock and where to concentrate. It won't give you addresses, but it tells you where the inventory is.
3. Commercial property platforms. Subscription data providers compile multifamily inventory with unit counts, ownership, and sometimes management company. Useful as a cross-check and for ownership, though coverage and freshness vary.
4. Drive-and-pin / aerial scan. For pockets the data misses, you can scan aerial imagery over a corridor and pin the obvious garden complexes by their roof footprints, then back into the parcel record. Tedious, but it catches recently re-parceled or oddly-coded properties.

The minimum useful record

For each property, you want a row that eventually holds:

Property name | Address | Parcel ID | Year built | # buildings | Approx roof SF
Roof type (est) | Owner of record (LLC) | Mailing address | Mgmt company
Secretary-of-state principal / agent | Best contact | Last storm date | Hail size | Wind gust
Roof age estimate (range) | Last permit date | Priority score | Status

Don't try to fill every column on day one. Get name, address, parcel, year built, and owner-of-record first across the whole market. Then enrich the top-priority rows deeply. Enriching all 4,000 to the same depth up front is how people quit.

Step 2: Estimate Roof Age and Remaining Life

This is the signal most roofers skip, and it's the one that separates a targeted route from a spray of door knocks. "Year built" is not roof age — a 1985 building may be on its second or third roof. You're trying to answer: when was the current roof last replaced, and how much service life is left? You will rarely get an exact date, and you should not pretend to. You're building a range and a probability, and that's enough to prioritize.

Method A: Permit history (the closest thing to ground truth)

Most jurisdictions require a permit for a commercial re-roof, and many publish permit records online or release them on request. A re-roof permit from 2008 on a building means that roof is roughly 16 to 18 years old today — and if it's an asphalt or modified-bitumen system, it's entering the replacement conversation.

How to work permits:

• Search the jurisdiction's permit portal by address or parcel for permit types like "reroof," "roof," "roofing," or "commercial alteration."
• Record the most recent roofing permit date — that resets the roof-age clock.
• Note the scope if listed (full tear-off vs. recover vs. repair). A 2015 "roof repair" permit does not reset the clock the way a full replacement does.
• Where there's no permit on record at all for a 30-year-old building, the original roof may still be up there — or the work was done without a permit. Either way it flags an old assembly worth a closer look.

Permits are gold, but coverage is uneven: small jobs go unpermitted, older records may not be digitized, and some jurisdictions are slow to release. Treat permits as your strongest single input and fill the gaps with the methods below.

Method B: Reading roof age from aerial imagery

When you don't have a permit date, the roof tells on itself from above. Historical aerial imagery is the key tool — being able to scroll back through years of overhead images of the same building lets you spot the year the roof changed color or texture, which brackets the replacement.

Tells to look for, by roof type:

Asphalt shingle (steep-slope garden buildings):

• Color and granule loss: a fresh shingle roof reads dark and uniform; an aging one looks faded, blotchy, and lighter as granules wash off and expose mat.
• Streaking and biological growth: dark streaks (often algae) and green patches read as years of exposure.
• Surface texture: cupping and curling can show up as a rougher, less-flat texture in high-resolution imagery and oblique views.
• The replacement event: scroll historical imagery; the year the whole roof jumps from light/streaked to dark/uniform is the re-roof. The roof's age is "current year minus that event."

Low-slope BUR / modified bitumen (flat-ish older mid-rises):

• Surfacing condition: gravel-surfaced BUR shows bald spots where ballast has migrated; smooth or cap-sheet systems show alligatoring and discoloration.
• Ponding stains: persistent dark rings where water sits after rain — a sign of slope and drainage problems and an aging membrane.
• Patch density: lots of visible patches, especially around penetrations and seams, signals a roof being nursed past its life.

Single-ply (TPO/PVC on newer flat roofs):

• Brightness: bright white and clean reads newer; chalky, dirt-streaked, gray reads aged.
• Seam and flashing shadows: lifted seams and billowing membrane can throw shadows visible in oblique imagery.
• Mechanical clutter changes: new rooftop units or solar added in a given year sometimes coincide with a re-roof.

A worked example: you pull a 1994 garden complex. County says no recent roofing permit. You scroll historical aerial imagery: 2009 image shows light, streaked shingles; 2010 image shows dark, uniform shingles across all buildings. That brackets a re-roof to roughly 2009-2010. So the current roof is about 15 to 16 years old. For an architectural asphalt shingle in a sun-and-storm climate, that's mid-to-late life — a legitimate target, especially if storm exposure stacks on top (next section).

Two practical cautions when reading imagery. First, watch for partial re-roofs: on a multi-building community, some buildings may have been replaced after a localized event while others weren't, so date each building, not the whole property — your route may be "buildings 3, 7, and 12," not the entire complex. Second, beware image-capture artifacts: low sun angle, cloud shadow, wet roofs after rain, and different imagery vendors all change how a roof reads. Cross-check at least two capture dates before you commit to an age bracket, and flag low-confidence reads so a rep verifies them on site rather than pitching off a bad guess.

Method C: Visible condition + a confidence range

Combine what you see with what you know about the assembly to produce a remaining-life range, not a false-precision number. Rough service-life reference points (real-world, not warranty fiction) for planning:

These ranges are planning aids, not promises — install quality, ventilation, slope, foot traffic, and climate swing them hard. Use them to convert a roof-age estimate into a "how due is it" bucket:

• Past service life (age > top of range): replacement-ready. Top priority.
• Late life (within ~5 years of top of range): replacement conversation now, especially with any storm exposure.
• Mid life: maintenance and relationship-building; not a re-roof pitch yet.
• Early life: leave it alone; revisit in a few years.

Write the estimate as a range with a confidence note, e.g. "Roof age est. 15-17 yrs (aerial bracket 2009-2010, no permit found) — late life." That honesty protects you in the sales conversation and keeps your data trustworthy.

Step 3: Layer Storm Exposure So Worn Roofs Float to the Top

Age tells you which roofs are aging out. Storm history tells you which roofs got worn out — and which ones may have damage the owner doesn't know about. Layering storm exposure over your age-ranked list is what turns a generic "old roofs" list into a prioritized one, because hail and wind do not hit every roof equally.

Where to get real storm data

Use authoritative weather sources, not a vague "big storm last spring":

• NOAA's Storm Prediction Center (SPC) publishes storm reports, including hail and wind reports with sizes, dates, and locations.
• NOAA's Storm Events Database is the searchable archive of severe weather events by county and date, with magnitudes (hail diameter, measured/estimated wind gusts).
• The National Weather Service issues and archives severe thunderstorm and tornado warnings and local storm reports.
• The Insurance Institute for Business & Home Safety (IBHS) publishes research on hail and wind impacts to roofing assemblies — useful for understanding what a given hail size actually does to a given roof type.

What sizes matter

Not every hailstorm is a re-roof event. As a rough field heuristic for asphalt and softer membranes:

• 1" (quarter) hail: bruising and granule loss possible, often cosmetic on newer roofs; meaningful on aged roofs.
• 1.25"-1.5" (half dollar to ping-pong): functional damage gets likely, especially on older or thinner assemblies.
• 1.75"+ (golf ball and up): functional damage probable across most asphalt and many single-ply roofs.
• High wind (roughly 58+ mph severe-criteria gusts, higher for real uplift damage): edge metal, flashing, and shingle/membrane uplift, especially on roofs already at end of life.

These are guides for prioritization, not a substitute for inspection. A storm map tells you where to look harder; the roof tells you what's actually true.

Stacking storm over age

The move is to cross your age-ranked property list against storm swaths:

1. Pull the significant hail/wind events over your market for the last few years from SPC / Storm Events.
2. Map the swaths (date, size footprint).
3. Flag every property in your universe that sits under a meaningful swath, recording the date and size.
4. Bump priority where late-life or past-life roofs sit under a 1.5"+ hail swath or a high-wind event — that's a roof that was already due and just got accelerated.

A late-life modified-bitumen roof under a 2-inch hail swath from last June is a far better knock than a same-age roof that's seen calm weather. Same age, very different probability of an active replacement conversation.

How RoofPredict does the age-plus-storm layer for you

The two hardest, most time-consuming layers above — estimating roof age from imagery across thousands of properties, and modeling storm exposure per individual roof — are exactly what RoofPredict automates for contractors. Rather than reading aerial tells one building at a time and hand-mapping storm swaths, RoofPredict scores a contractor's market house-by-house (and building-by-building) and returns, per address:

• a roof-age range estimated from aerial imagery (a range, never a precise install date — the imagery brackets it, it doesn't certify it), and
• a per-roof storm exposure model that accounts for the actual hail and wind that specific roof has lived through, expressed as the odds a roof was affected, not proof that it was.

It then ranks doors, routes, and lists so the roofs that are aging out and the roofs the storm wore out rise to the top — and it can enrich a contractor's own property list or CRM with those roof-age and storm signals, so your existing multifamily universe gets the age and storm layers attached automatically instead of by hand. To be straight about the limits: a roof-age range is an estimate, a storm model gives probabilities, and neither replaces climbing the roof and documenting it. What it does replace is the weeks of manual research that otherwise stand between you and a prioritized list — so a small team can actually work a whole metro of multifamily instead of whichever ten complexes they happened to drive past. (More on how the modeling is framed at the close.)

Step 4: Identify the Owner Behind the LLC

Now the part that stops most roofers cold. You've got a prioritized list of due, storm-worn multifamily roofs. The owner of record is "Maple Ridge Holdings LLC" with a mailing address that's a UPS Store box. Here's how you get to a human.

Start with the assessor record

The county assessment roll gives you the owner of record and a mailing address. Sometimes that mailing address is the management company or even the principal's home or office — useful immediately. Often it's a registered-agent box. Either way, the legal entity name is your key into the next step.

Run the entity through the Secretary of State

Every LLC is registered with a state's business filing office (usually the Secretary of State), and most states publish a free business entity search. Look up the exact entity name and you'll typically find:

• Registered agent name and address (often a law firm or service — not your target, but a thread).
• Principal office address (frequently the real operating address).
• Members / managers / officers (in states that disclose them — this can be the actual decision-maker's name).
• Related entities (the same principals often register many single-purpose LLCs; finding one opens up a whole portfolio).

This single search often converts "Maple Ridge Holdings LLC" into "Maple Ridge Holdings LLC, managed by Davidson Property Group, principal Mark Davidson, operating address in your metro."

Identify the management company

Many multifamily properties are run day-to-day by a third-party property manager who handles maintenance vendors — and who often influences or controls roofing decisions on smaller jobs. Find them via:

• The leasing office (call and ask who manages the property and who handles capital maintenance).
• The property's website footer or resident portal branding.
• Signage on site.
• Apartment listing sites that name the management company.

Know the split: the management company often controls maintenance and emergency repairs; the ownership entity controls capital projects like a full re-roof. For a replacement you usually need to reach the owner/asset manager, but the property manager is frequently the gatekeeper who routes you there — and a manager who trusts you will hand you the owner's contact.

Skip trace to a phone and email

Once you have a principal's name and a company, skip tracing fills in contact details. Approaches, cleanest first:

1. Company website / LinkedIn: asset managers and owners of any scale usually have a findable professional presence. Title clues: "Asset Manager," "Director of Capital Projects," "VP of Operations," "Principal," "Managing Member."
2. Business filings and licenses: registered-agent and principal addresses, professional licenses, and any DBA filings.
3. Skip-tracing / B2B contact tools: paid services that resolve a name + company to direct phone and email. Standard in commercial prospecting.
4. The front door: when all else fails, calling the leasing office and politely asking "who at the ownership group handles roofing capital projects, and how would I reach them?" works more often than reps expect.

Keep your outreach compliant with telemarketing and email rules (the FTC's Telemarketing Sales Rule and CAN-SPAM for email) — honor opt-outs, identify yourself and your company, and don't pretend to be something you're not. B2B doesn't exempt you from basic honesty and do-not-contact hygiene.

What the first touch should actually say

When you reach the asset manager, lead with the specific roof and the data, not a generic pitch. The difference between "we do apartment roofs, can we bid yours" and a researched opener is the difference between a hang-up and a meeting. A tight, honest first message for a storm-worn, late-life property looks like this:

"Hi [name] — I work with multifamily owners on roofing capital planning. Your community at [address] looks to be on a roof from roughly [year range], which puts it in the late part of its service life for that assembly, and the property sat under a hail event on [date] with reported [size] hail per NOAA's records. I'd like to climb it, document the current condition building by building, and give you an itemized estimate for your reserve planning and your files — no obligation. Worth 20 minutes?"

Notice what that does and doesn't claim. It states a roof-age range (not a certified date), cites the public storm record (not an insurance outcome), and offers documentation and an estimate (not claim handling or a promised payout). It speaks the owner's language — service life, reserves, capital planning — because that's how they actually think about the asset. Save the storm-only urgency pitch for door-knocking residential; multifamily owners respond to a roofing partner who understands their budgeting cycle.

A note on portfolios

The highest-leverage discovery is that one principal owns several properties. When the Secretary of State search shows the same members across "Maple Ridge Holdings," "Cedar Point Holdings," and "Stonegate Holdings," you've found a portfolio. Cross-reference those entities back to your property universe and you may turn one due roof into a five-property relationship. Track related entities in your CRM as a linked group.

Step 5: Score and Sequence — Build the Route, Not Only a List

A list is not a plan. Convert your enriched universe into a priority score so your reps work the best roofs first. A simple, transparent score beats a fancy black box because your team will actually trust and use it.

A worked scoring model

Score each property 0-100 by summing weighted factors. Tune the weights to your market, but here's a sane default:

A property that's past service life (35), under a recent 2" hail swath (25), with a direct asset-manager contact (15), large roof area (10), part of a five-property portfolio (10), and visible patching (5) scores 100 — that's a call you make today. A mid-life roof with no storm exposure and a dead-end LLC scores maybe 10 — leave it in the database and revisit.

Sequence into routes

Once scored, group the top tier geographically so a rep can document several properties in a day without crossing the metro twice. Storm-driven campaigns especially reward geographic clustering: when a swath hits, you may have 60 due-and-worn roofs in one quadrant. Work the quadrant.

Maintain the system

This dataset decays. Roofs get replaced (by you or a competitor), owners sell, new storms hit. Plan to:

• Re-pull permit and storm data quarterly.
• Re-score after every significant storm event in your market.
• Mark status honestly: prospected, contacted, documented, bid, won, lost, re-roofed-by-other (dead for a decade), revisit-date.
• Recheck ownership annually; multifamily trades hands constantly and a sale is often a re-roof trigger (new owner, fresh capital plan, reserve study).

Step 6: Document the Roof and Build an Accurate Estimate

You've reached the owner of a due, storm-worn multifamily roof. Now the work shifts from research to documentation — and this is where many roofers either underdeliver or wander into territory they shouldn't. The whole value you bring an owner here is a thorough, accurate, defensible record of the roof's condition and a clean repair/replacement estimate. That's it. That's the deliverable.

What a professional documentation package contains

• Safe, complete access plan: multifamily roofs mean ladders, multiple buildings, and occupied units below. Follow OSHA fall-protection requirements for low-slope and steep-slope work; document your safety setup. A rep who's casual about fall protection on an occupied apartment building is a liability you don't want.
• Overview and orientation: address, building IDs, roof areas, slopes, assembly type, number of layers if known.
• Condition photos, systematically: wide shots of each roof plane, then close-ups of every issue — granule loss, mat exposure, blisters, splits, seam failures, flashing separation, ponding, damaged edge metal, penetrations, and any impact marks. Photograph in a consistent order per building so the package is easy to follow.
• Storm correlation, stated as fact only: "Property is located under the path of a hail event on [date] with reported hail of [size] per NOAA Storm Events Database," plus dated photos of impact-consistent marks. State what you observed and what the public record says. Do not opine on whether it's "covered."
• Measurements: accurate roof area, by building, with penetrations and details counted. Aerial measurement reports speed this up; verify on the roof.
• Scope and estimate: a clear, itemized repair or replacement scope.

A practical organizing tip: number your buildings on a site map and structure the whole package the same way every time — site overview, then per-building (overview photo, then planes, then close-ups of distress), then measurements, then scope. On a 14-building community that's a lot of photos; a consistent, labeled order is what makes a 200-image package readable to a busy asset manager instead of an undifferentiated dump. Date- and geo-stamp images where your camera or app supports it. The owner should be able to open the file a year later, during a refinance or a reserve study, and instantly understand the roof's condition building by building.

Writing an estimate that holds up

For commercial and multifamily work, your estimate should be itemized and aligned to recognized line-item pricing so it reads as professional and reproducible. Many restoration-track contractors write estimates in Xactimate because it's the line-item standard the insurance ecosystem reads fluently, but the principle holds in any estimating platform: tie scope to defined line items, real quantities, and real unit costs. Build the estimate to reflect your actual scope of work to repair or replace the roof — tear-off, decking repair, underlayment, the roofing system, flashing, edge metal, penetrations, accessories, disposal, and the labor to do it right.

Reference recognized installation standards in your scope so it's clear you're quoting a code- and manufacturer-compliant job: the International Building Code / International Residential Code as adopted locally, NRCA installation guidance, and manufacturer specifications for the chosen system. "We will install per IBC and manufacturer spec" is a stronger, more defensible line than a vague allowance.

The compliance line you do not cross

This matters enough to be blunt, because storm-driven multifamily work pulls people toward insurance, and there's a bright legal line. As a roofing contractor you may:

• Inspect and thoroughly document the roof's condition.
• State factual observations and the public storm record.
• Prepare an accurate, itemized estimate for the work you would perform.
• Hand that documentation and estimate to the property owner.

You may not, for a fee, do the things that are unlicensed public adjusting:

• Negotiate, adjust, or "handle" an insurance claim on the owner's behalf.
• Interpret the owner's policy or tell them what is or isn't covered.
• Promise a specific payout, approval, or outcome.
• Promise that a deductible will be waived, absorbed, or made to disappear.
• Advertise a "free roof."
• Represent the owner against their insurer.

The clean framework: you document thoroughly and write an accurate estimate; the owner files whatever they choose to file; the insurer decides coverage. You are the roofing expert who produced a precise record and a real estimate — not the claims handler. Teaching this distinction to your reps protects your license and your reputation, and frankly it builds more trust with sophisticated multifamily owners than the "we'll get it all paid for" pitch ever does. Owners who run buildings as financial assets can smell that pitch, and it reads as either naive or shady. A tight estimate and an honest scope reads as a professional they can hand a 200,000 SF project.

A do-not-say cheat sheet for reps

Laminate this and put it in every truck:

Common Mistakes Roofers Make Targeting Multifamily

Learn these from other people's wasted quarters instead of your own.

Treating "year built" as roof age. A 1980 building on its third roof is not a 44-year-old roof. Always reset the clock with the most recent permit or the aerial replacement event.

Knocking the leasing office and calling it prospecting. The leasing agent can't sign a re-roof and usually can't even route you well. You'll feel busy and accomplish nothing. Reach the owner/asset manager.

Chasing storms without age data. A fresh roof under a big hail swath is usually a fresh roof afterward. Storm plus old roof is the opportunity; storm alone scatters your effort across roofs with years left.

Over-promising on insurance. Beyond the legal exposure, sophisticated owners discount you instantly when you promise outcomes you can't control. Document and estimate; don't adjust.

No system, all hustle. Reps who keep targets in their heads and their trucks produce streaky, unrepeatable results. The contractors who win multifamily run a maintained database, a transparent score, and routes — boring, durable, compounding.

Ignoring portfolios. Closing one roof for an owner who has eight properties and not asking about the other seven is leaving the entire reason you did the research on the table.

Skipping fall protection on occupied buildings. Beyond the human cost, an OSHA incident on a multifamily roof in front of residents ends relationships and contracts. Document safety like you document condition.

A 30-Day Plan to Stand This Up

If you're starting from zero, here's a realistic sequence.

Week 1 — Build the universe. Pull the assessor/parcel multifamily list for your target counties. Filter to your size and era box. Get name, address, parcel, year built, and owner of record into a sheet or CRM. Don't enrich yet — just get the backbone for the whole market.

Week 2 — Add age and storm layers to the top. Take your largest and oldest 150-200 properties. Pull permit history where available; bracket roof-replacement years from historical aerial imagery for the rest; assign a roof-age range and a life bucket. Pull the last 24-36 months of significant hail/wind events from SPC / Storm Events and flag which of those properties sit under a swath.

Week 3 — Find the humans. For your top ~60 scored properties, run the ownership entities through the Secretary of State, identify management companies, and skip trace to a direct contact for the decision-maker. Note portfolios. Now you have a real call list.

Week 4 — Document and sequence. Build geographic routes from the top tier. Start reaching out and scheduling documentation visits. Build your photo/estimate template (and the do-not-say cheat sheet) so every package looks the same and reads professionally. Begin logging status honestly in the CRM.

After 30 days you have a maintained, scored, contactable multifamily pipeline — and a system you re-run quarterly and re-score after every storm, instead of a stack of guesses.

Where Software Earns Its Keep — and Where It Doesn't

The research-heavy layers — roof age from imagery and storm exposure per roof, across thousands of buildings — are where tooling pays off, because they're the parts that don't scale by hand. This is the gap RoofPredict is built for: it estimates a roof-age range per address from aerial imagery and models storm exposure per individual roof as odds, then ranks the doors, routes, and lists so the roofs that aged out and the roofs a storm wore out surface first. Point it at your multifamily universe and it enriches your own list with those age and storm signals, so the prioritization in Step 5 mostly builds itself.

Be honest with yourself about what it is and isn't. A roof-age estimate is a range, not a certified install date — the imagery brackets the roof's age, it doesn't notarize it. A storm model gives you odds a roof was affected, not proof — proof comes from climbing the roof and documenting it. The owner research, the relationship, the safe and thorough inspection, the accurate estimate, and the clean compliance line are still yours to own. What you get back is your reps' time: instead of spending weeks reading imagery and hand-mapping storms, they spend that time on roofs and in front of owners, working a list that's already ranked by which multifamily roofs are genuinely due.

The way to think about any tool here — whether it's RoofPredict, your CRM, an aerial measurement service, or a skip-tracing platform — is that each one collapses a slow manual layer into a fast one, but none of them close a roof. The wins compound where the data feeds a disciplined process: a ranked list is only worth as much as the rep who works it in order, documents honestly, and writes a clean estimate. Buy tools to remove research drudgery and to scale your reach across a whole metro, not to replace the judgment of someone standing on the roof. The roofers who pull ahead in multifamily are the ones who pair good data with that discipline, then keep both running quarter after quarter while their competitors wait for the phone to ring.

Find the due roofs, reach the right human, document honestly, estimate accurately, and stay on the right side of the claims line. Do that as a maintained system rather than a hustle, and multifamily stops being the segment you wait for and becomes the one you own.

FAQ

How do I find out who actually owns an apartment complex when it's listed under an LLC?

Start with the county assessor record for the owner of record and mailing address, then run the exact LLC name through that state's Secretary of State business entity search. That typically reveals the registered agent, principal office address, and in many states the members or managers — i.e., the real people. From there, identify any third-party management company (call the leasing office or check the property's website) and skip trace the principal's name to a direct phone and email. The same principals often register many single-purpose LLCs, so finding one can open up a whole portfolio.

Can I really estimate a roof's age from aerial imagery, and how accurate is it?

Yes, within a range. Historical aerial imagery lets you scroll back through years of overhead images of the same building and spot the year the roof changed from faded/streaked to dark/uniform (shingle) or from patched/discolored to clean (membrane) — that brackets the replacement. You won't get an exact install date; you get a range like '15-17 years.' Combine it with permit records where available for a tighter estimate. Always record it as a range with a confidence note, never as false precision.

What roof age makes a multifamily roof worth pursuing for replacement?

Compare the estimated roof age to the assembly's typical service life. Architectural asphalt shingle runs roughly 20-30 years, 3-tab 15-20, modified bitumen 15-25, BUR 20-30, TPO 15-25, PVC and EPDM 20-30. A roof past the top of its range is replacement-ready; within about five years of the top is a strong conversation, especially with storm exposure. Mid-life is for maintenance and relationship-building, not a re-roof pitch. These ranges are planning aids — install quality, slope, ventilation, and climate move them significantly.

Where do I get reliable storm data to know which roofs took hail or wind?

Use authoritative public sources: NOAA's Storm Prediction Center for hail and wind reports, NOAA's Storm Events Database for a searchable archive of events by county and date with magnitudes, and the National Weather Service for warnings and local storm reports. The Insurance Institute for Business & Home Safety publishes research on how specific hail sizes affect roofing assemblies. Map the significant swaths over the last 24-36 months and flag which properties in your list sit under them, recording the date and hail size or wind gust.

What hail size actually causes functional roof damage?

As a prioritization heuristic for asphalt and softer membranes: 1-inch hail can cause bruising and granule loss (often cosmetic on newer roofs, meaningful on aged ones); 1.25-1.5 inch makes functional damage likely, especially on older or thinner assemblies; 1.75 inch and up makes functional damage probable across most asphalt and many single-ply roofs. High winds in the severe range can lift edge metal, flashing, and shingles or membrane on roofs already at end of life. These are guides for where to look harder — the actual condition is confirmed by inspecting the roof, not by the map.

How is targeting multifamily roofs different from residential storm canvassing?

The roofs are far larger (one complex can equal dozens of houses), ownership is layered behind LLCs and management companies, decisions are budgeted capital projects rather than impulse buys, and the same owner often controls multiple properties. That means more research up front — owner discovery, roof-age estimation, storm layering — but each closed relationship is worth many residential jobs and can compound across a portfolio. The buying cycle is slower, but the competitive field is thinner because few roofers prospect it methodically.

Can I tell a property owner that insurance will cover their roof replacement?

No. Promising coverage, a payout, an approval, or that a deductible will be waived crosses into unlicensed public adjusting in most states and is also a credibility-killer with sophisticated owners. What you can do as a roofing contractor: inspect and thoroughly document the roof, state factual observations and the public storm record, prepare an accurate itemized estimate for the work you would perform, and hand that to the owner. The owner files whatever they choose, and the insurer decides coverage. Document and estimate — don't adjust or interpret policy.

Should I write commercial multifamily estimates in Xactimate?

It helps for restoration-track work because Xactimate is the line-item standard the insurance ecosystem reads fluently, but the real principle is broader: tie your scope to defined line items, real quantities, and real unit costs in whatever platform you use. Build the estimate to reflect your actual scope — tear-off, decking, underlayment, the roofing system, flashing, edge metal, penetrations, accessories, disposal, and labor — and reference the locally adopted IBC/IRC, NRCA guidance, and manufacturer specifications so it reads as a code- and spec-compliant job. An itemized, reproducible estimate beats a vague allowance every time.

How does RoofPredict fit into finding due multifamily roofs?

RoofPredict automates the two most time-consuming research layers: it estimates a roof-age range per address from aerial imagery and models storm exposure per individual roof as odds, then ranks doors, routes, and lists so the roofs that aged out and the roofs a storm wore out surface first. It can enrich your own property list or CRM with those age and storm signals. The honest limits: a roof-age range is an estimate not a certified date, and a storm model gives probabilities not proof — you still confirm condition by inspecting the roof. What it replaces is the weeks of manual imagery reading and storm mapping, so a small team can work a whole metro of multifamily.

How often should I refresh my multifamily target list?

Treat it as a living dataset. Re-pull permit and storm data quarterly, re-score the whole list after every significant storm event in your market, and recheck ownership annually because multifamily trades hands constantly and a sale often triggers a re-roof. Mark status honestly — prospected, contacted, documented, bid, won, lost, re-roofed-by-other, revisit-date — so you don't re-knock a roof a competitor just replaced or skip one that flipped to a new owner with fresh capital.