How to Score and Qualify Leads by Estimated Home Value

Not every valid address is worth the same follow-up. A verified address on a $250,000 starter home and one on a $900,000 house are both real, but if you sell solar, roofing, remodeling, insurance, or any high-ticket home service, they are not equally valuable leads. Estimated home value turns an address into a rough proxy for buying power, which makes it one of the most useful signals you can add to lead scoring. This guide shows how to pull an estimated home value from an address with a single API call and turn it into a lead score your team can act on.

Why home value is a lead-scoring signal

Home value is not a credit check, but it is a strong and cheap first-pass filter. The value of the property behind a lead correlates with the budget available for exactly the kinds of purchases that get sold at the door or over the phone: a new roof, a solar install, a kitchen remodel, a higher insurance tier. When you can see that number the moment a lead comes in, you can prioritize the outreach that is most likely to convert and spend less time on the outreach that is not.

It pairs naturally with property type. A lead is worth pursuing when the address is a residence you can actually sell to, and it is worth pursuing first when that residence sits in the value band you do best in. If you have not read it yet, classifying property type from an address covers the first half of that decision.

Getting an estimated value from an address

You do not need a separate property-data vendor to get a value. The same call that validates the address returns the estimated value alongside the property type:

curl -X POST 'https://api.addressverify.io/service/lookup/address' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{ "address": "20 Marie St, Iberia, MO 65486" }'

{
  "address": "20 Marie St, Iberia, MO 65486",
  "addressValid": true,
  "homeType": "SINGLE_FAMILY",
  "homeValue": 371000
}

One request, and you have the three things a score needs: whether the address is real, whether it is a residence, and what it is worth.

Turning value into a score

A useful score does two things. First it rejects anything that is not a valid residential address, because a value on a bad or non-residential address is meaningless. Then it tiers the survivors by value band. The bands are yours to set based on your economics, but the shape looks like this:

const RESIDENTIAL = ['SINGLE_FAMILY', 'TOWNHOUSE', 'CONDO', 'MULTI_FAMILY', 'MANUFACTURED'];

function scoreLead(result) {
  // Reject anything that is not a valid residential address.
  if (!result.addressValid || !RESIDENTIAL.includes(result.homeType)) {
    return { tier: 'reject', reason: 'not a valid residential address' };
  }

  // Tier by estimated value. Set the bands to match your ideal customer.
  const value = result.homeValue ?? 0;
  if (value >= 600000) return { tier: 'A', value };
  if (value >= 350000) return { tier: 'B', value };
  return { tier: 'C', value };
}

Now every inbound lead lands in your CRM already tagged. Tier A goes to your best rep or your fastest follow-up. Tier C can go to a nurture sequence instead of a phone call. Leads that fail validation never waste anyone's time. The logic is the same in any language, because the response is plain JSON.

Sharpen it with expanded data

When a single value band is too blunt, add ?expanded=true to the request. The response then includes the tax assessed value, year built, living area, and lot size, which let you segment more precisely, for example separating a large older home that needs work from a small newer one:

{
  "homeValue": 371000,
  "propertyInfo": { "bedrooms": 4, "bathrooms": 2, "livingArea": 2072, "yearBuilt": 2001 },
  "taxAssessment": { "taxAssessedValue": 150210, "taxAssessmentYear": "2024" }
}

Year built alone is a strong signal for roofing, HVAC, and window replacement, where the age of the home predicts the need. Combine it with the value band and your score gets a lot smarter without a second API.

Treat the value as an estimate, not an appraisal

Be honest with yourself about what the number is. An estimated home value is an automated estimate, useful for prioritization and segmentation, not a formal appraisal and not a basis for underwriting or a firm offer. Use it to decide who to call first and how to route a lead, and combine it with your other signals rather than treating any single value as ground truth. Used that way, it is one of the highest-leverage fields you can add to a lead record.

Where the score goes

The score is most valuable the moment the lead is created, so compute it in the same request that captures the address. Write the tier and value to the lead record, route Tier A to immediate follow-up, suppress rejects before they reach a rep, and use the value bands for direct-mail and ad-audience targeting. If you are doing this at the point of capture, the real-time address verification guide covers the request path, and filtering PO boxes and non-residential addresses covers the reject step in more detail.

Try it on your own leads

Paste a few of your own addresses into the free address verifier tool to see the value and property type come back, then wire the same call into your funnel using the API documentation. Pricing is pay-as-you-go with 50 free lookups a month, so you can score a test batch before you commit. For the value and property-type mix behind real traffic, see The State of Address Data.