How a Tax Firm's BD Team Won 4 Clients in Its First Month

A PE-backed property-tax rollup screened Texas one county at a time and missed its biggest prospects. AI entity resolution surfaced them, and BD closed 4 in month one.
4 clients
New clients won in the first month
2–4 months
Implementation Time
$25K – $100K
Project Cost

the challenge

The client is a national property-tax consulting firm with about 100 consultants and close to 1,000 clients, one of the largest professional-services rollups in tax consultancy, backed by a Dallas-based middle-market private equity fund. It finds new business in public appraisal rolls, and in Texas those rolls are spread across 254 county appraisal districts, each in its own format. Only four publish electronically. The BD team screened one county at a time against a single-county value threshold. The firm's floor is roughly $5M in business personal property, so a company holding $800K in each of ten counties never showed up anywhere, even though it was an $8M account. Consultant-of-record data is partly redacted, so there was also no clean way to tell which large accounts were unrepresented or had recently switched advisors. The sponsor's first attempt at a fix, running county rollups through ChatGPT by hand, timed out at scale.

what they built

Ingestion pipelines for the four counties that publish electronically (Harris, Dallas, Travis and Hockley), rebuilding each certified roll from the district's exports and normalizing every county into one schema. Open-records petitions, filed by ModernEdge, extended coverage to about 80 public counties. An entity-resolution engine on Claude Sonnet that links company and advisor-firm name variants across counties, so the same taxpayer appears as one account. It runs above 95% precision on the top 100 companies and advisor firms, and anything below the confidence threshold goes to a review queue that the firm's staff clears by hand. A ranked prospect list that flags likely-unrepresented and recently-switched accounts. Clean CSV exports go to the BD team, and a person decides what enters HubSpot.
The work ran as a co-build with the sponsor partner, the firm's CFO, the BD lead and the firm's tech lead, with written progress on Mondays and Wednesdays and a working session every Friday. The team started with the four counties that publish electronically, because the other 250 require an open-records petition with a ten-business-day response window each. ModernEdge filed those petitions itself, so the firm never set a precedent with a county it might later appeal against. Ingestion pipelines rebuilt each roll and normalized it into one schema, then the entity-resolution layer on Claude Sonnet collapsed name variants into single accounts. The four-county pilot alone covered several hundred thousand companies, and tens of thousands of them appeared in more than one county. A review queue sits between the matches and the BD team, so every account is checked before outreach. The pilot was scoped at four to six weeks and BD was working live lists about two months after kickoff. The team then extended by a month for the records petitions and statewide enrichment, added 240 hours, and kept the price where it was.

best fit for

Firms whose prospects only show their true size once records are joined across jurisdictions: property-tax consultants, lien and title services, utility auditors and government-contract sales teams. It pays when that join is the whole competitive edge. If the records you prospect from are already clean and in one place, an off-the-shelf data vendor such as ZoomInfo or Apollo is the better buy. It also needs a human review step between the data and the outreach, because a rep calling the wrong company after two names collide is worse than having no system.
Ai ROLE
Claude Sonnet, through the Anthropic API, runs the matching and inference layer: it resolves company and advisor name variants across county formats and infers consultant-of-record from partially redacted fields. Everything around it is data engineering, and a human review queue checks low-confidence matches before any outreach.

impact

4 new clients

Closed in the first month from accounts the platform surfaced, paying back the build inside that month.

95%+

Entity-resolution precision on the top 100 companies and advisor firms.

4 to ~80 counties

Public county coverage, about 72% of Texas, up from the four that publish electronically.

implementation complexity

Medium: per-county ingestion across inconsistent formats, open-records petitions with ten-day response windows, and entity resolution tuned above 95% precision with a human review queue.
Kevin Malaekeh, ModernEdge AI

Kevin Malaekeh

Co-Founder at ModernEdge AI
ModernEdge AI
Co-founder of ModernEdge AI, a Claude partner that builds custom AI agents, voice systems and document workflows for mid-market and PE-backed companies.
Get an intro
Talk to this team
industry
Professional Services
business organization
Sales & Revenue
AI TYpe
Decision Support & Scoring
value type
Revenue Growth

frequently asked questions

How did a property-tax firm use AI to win new clients from county records?

It normalized Texas county appraisal rolls into one schema and used Claude Sonnet to resolve each taxpayer into one account across counties. BD now works a ranked, reviewed list of right-sized accounts and closed four new clients in its first month on the platform.

What AI was used in the property-tax prospecting platform?

Claude Sonnet through the Anthropic API handles entity resolution and inference at the matching layer. The rest is data engineering: Python ingestion pipelines over county exports and open-records data, a human review queue, and clean CSV exports for the CRM.

What results did the property-tax firm see?

Four new clients closed in the first month from accounts the platform surfaced, enough to pay back the build in that month. Entity resolution runs above 95% precision on the top 100 accounts, and coverage grew from 4 counties to about 80.

How long did the property-tax prospecting build take?

BD was working live lists about two months after kickoff. The team then extended by a month to cover open-records petitions and statewide enrichment.

When is a custom prospecting build like this worth it?

When a buyer's true size only shows after joining records across jurisdictions, as with property-tax consultants, lien and title services, utility auditors and government-contract sales. If your records are already clean and in one place, an off-the-shelf data vendor is the better choice.

Have a similar challenge?

Ask whether this would work for you, or describe what you're trying to solve.
TELL US WHAT YOU'RE EXPLORING