How property tax consultants find owners whose assessed values jumped
Turn county value changes into property tax appeal leads: the owners whose assessment rose sharply, sorted by size of the rise, ready for your team to call.
Part of the guide Workflow automation
The best property tax appeal leads are owners who just saw their assessed value climb by more than they expected, because they are the ones reading their notice and wondering whether to challenge it. Consultants find them by watching the public property records counties publish, keeping only the parcels whose value rose sharply since the last update, and putting the biggest rises at the top of a list the team works through before the appeal window closes.
This article is for property tax consultants, appeal firms and the real estate attorneys who handle assessment cases in the United States. It covers what to look for in county records, how to turn changes into a usable list, a made-up example, the legal and practical traps, and how an AI employee keeps the list filled during appeal season.
What a value change in county records tells you
When a county reassesses, its records change for each parcel: a value before, a value after, sometimes a new tax figure, and the owner's name and mailing address as the county holds them. The Property changes block reads those updates through xMap's property service and passes on each change as an item, with the address, the owner now, the value before and after, and the percentage change.
Three details make a change a lead rather than noise:
- The size of the rise. A small rise rarely justifies the effort of an appeal. Most firms set their own threshold, for example a rise of 15 percent or more, and a Filter keeps only those.
- The kind of property. A commercial building, a block of flats or a portfolio of rentals is usually worth more of your time than a single home, though some firms focus on homeowners on purpose.
- Where the owner lives. When the mailing address differs from the property's, the owner is often an investor or a company, which changes how you approach them.
A made-up example in one county
Picture a three-person appeal firm in Florida that works residential and small commercial cases in Miami-Dade. Last year the partners pulled county files by hand every few weeks and compared them in a spreadsheet, which took most of a Friday. This year they want a Monday list.
In this invented week, the county's updates hold several thousand value changes. The flow keeps those that rose 15 percent or more, sorts them by the size of the rise and by the value after, and drops parcels the firm already represents. The Monday email shows, say, 140 properties: the top line might be a small retail building whose value went from 1.2 million to 1.6 million, owned by a company with a mailing address in another state. The partners split the list by ZIP code and start calling.
Building the weekly list
An AI employee in xMap Flows does the comparison every week and brings only new changes. One way to set it up:
- Schedule: every Monday at 07:00 in the firm's time zone.
- Property changes: changes in your county, kind Value or tax, since the last run, limited to your ZIP codes if you work part of the county.
- Filter: value change of 15 percent or more, or a value after above the size of case you take.
- Match with my table: against your list of current clients, keeping only those not found, so nobody calls an existing client.
- Sort and limit: biggest rise first, keep the first 150.
- xMap LLM: one line per property for the caller, written from its own fields: what kind of property it is, the rise, and whether the owner seems to live elsewhere.
- Email to the team, or a row per property in a shared sheet through Google Sheets.
The emailed list carries each address, the owner as recorded, the value before and after, the change in percent and the caller's line, with a CSV download. Because the block reads changes since the last real run, each change arrives once; an Only new block is only needed if you also run 30-day looks. The properties that sold this week and new homeowners every morning templates use the same block and are quick to adapt.
Mistakes to avoid
- Ignoring the law on contacting owners. Owner names and addresses are public records, but they are not a list of people who agreed to hear from you. Follow the rules on solicitation where the property is, and the opt-out rules if you use Outreach.
- Missing the deadline. Appeal windows are set by each county and are short. Put the deadline in the email's subject so the list is never read too late.
- Trusting every number blindly. A change can reflect a new building, a split lot or a correction. Check the parcel's record before quoting a figure to an owner.
- Reading changes from the wrong period. The first run reads the last seven days. If you start mid-season, run a 30-day look once to catch up, then switch back to since the last run.
Fitting it into the firm's work
The list is the start, not the whole job. Firms usually add a second flow that looks up the owner of each property a client sends in, through the same block's Owner of each incoming place setting, so a new enquiry arrives with its current values attached. For prospecting more broadly, the guide to an AI employee for sales prospecting shows how lists like this one fit a pipeline, and the law and professional services page lists related templates. To check which counties are covered for you, book a call.
Questions
Which counties are covered?
The counties xMap's property service reads; the County setting of the Property changes block lists every county with at least one update, and it grows over time.
Can I see the tax amount, not just the value?
When a county records a change of tax, it comes through as a Value or tax change. Not every county publishes tax figures with each update.
Does it give phone numbers for owners?
No. County records give the owner's name and mailing address. Any further contact details must come from your own research and be used within the law.
Can it cover several counties at once?
Use one Property changes block per county in the same flow, each feeding the same Filter, or one flow per county if different team members cover them.