Two things to establish before anything else. First, CoreLogic is now Cotality — the company announced a global rebrand in March 2025, so any comparison you read that does not mention it was written before then and may be stale in other ways too. Second, and more useful: if you are here because a quote came back much larger than you expected, the problem is usually not that you were quoted the wrong price. It is that you were quoted the right price for a different product than the one you needed.
Disclosure: Scout Data is our product; treat that section as a maker’s pitch and the rest as our honest read.
What an enterprise property-data contract is actually pricing
Enterprise data is not sold by the record. It is sold as a licence, and the licence prices five things at once. Understanding which of the five is inflating your number tells you whether to negotiate or to leave.
- Scope of the licence. How much of the country, which datasets, and at what depth. Nationwide costs more than a twelve-state footprint, and most buyers scope nationwide out of habit rather than need.
- Permitted use. What you may do with the records once you have them. Internal analytics, customer-facing display, resale and outbound marketing are separately priced permissions, and the last one is often the most restricted.
- Term and minimum. Annual commitments with a floor. If your volume is seasonal — and storm-driven work always is — the minimum, not the rate, is the number that determines whether the contract works.
- Delivery. A bulk file, an API, or a hosted integration are different engineering commitments on both sides and are priced differently. The cheapest line item can be the most expensive once you staff it.
- Seats and downstream users. Who inside your company may touch the data, and whether your own customers count as users. This clause surprises people more than any other.
The unit mismatch
Here is why the enterprise number so often feels wrong to an outbound team. The contract is denominated in access. Your business is denominated in conversations. Nothing in an access licence guarantees that a record resolves to a person you can reach, and nothing in it adjusts when it does not.
| What the contract sells | What an outbound team needs |
|---|---|
| Access to a dataset for a year | A defined count of records this month |
| An annual minimum | Spend that follows the storm season |
| Property attributes at scale | A phone that rings the owner on title |
| Permitted-use language you must comply with | Suppression and DNC handled before delivery |
| A feed you integrate | A file the dialer can load on Monday |
Every row in the right column is work you would be doing yourself on top of the licence fee. That is the real comparison — not licence price against per-record price, but licence price plus the assembly against per-record price. Teams that skip that adjustment conclude the enterprise contract is expensive; teams that make it usually conclude it is expensive and incomplete for their purpose, which is a different and more actionable finding.
Three cases where staying is correct
- You are building a product on top of the data. An AVM, a valuation workflow, an underwriting model, a portfolio analytics tool. You need breadth, history, and a licence that contemplates redistribution. Per-record sourcing cannot do this.
- You are regulated. Lending, insurance and government buyers need documented provenance and defensible methodology as much as they need the data. That documentation is a large part of what the contract buys.
- Your questions are open-ended. If you cannot specify in advance which records you want, you are not a per-record buyer. Per-record pricing rewards buyers who know their filter.
The per-record field, and how it splits
“Alternatives to CoreLogic” is not one market. Once you drop below enterprise licensing, the incumbent’s job breaks into four smaller ones bought from different places:
- Parcel geometry and boundaries. Nationwide, normalised across county formats, licensed as files or an API — Regrid alternatives covers how to evaluate that lane and when you do not need it at all.
- Property research and filtering. Subscription platforms with a published rate card, sold to individuals and small teams rather than negotiated — PropertyRadar pricing is a worked example of how that pricing behaves at volume.
- Data hygiene and append. Address standardisation, identity verification, batch append — the Melissa alternatives field, which overlaps with the enterprise incumbents on hygiene without carrying their property depth.
- Finished homeowner outbound. Records selected by signal and delivered dial-ready. This is the only one of the four denominated in the unit an outbound floor actually consumes.
Most teams who leave an enterprise contract do not replace it with one thing. They replace it with two of these four and discover the other two were never being used.
How to run the comparison honestly
Take one concrete list you would actually buy — a specific geography, a specific filter, a specific month — and price it three ways: under the enterprise quote with the annual minimum amortised across your realistic twelve-month usage; under a subscription platform including its per-contact append overage; and under a per-record quote. Then divide each by the number of records that come back with a working number for the right person, not by the number of records delivered. That last division is where the ranking usually changes, and our skip tracing cost calculator walks the arithmetic. Skip tracing accuracy covers why the delivered count and the dialable count diverge as much as they do.
This page quotes no figures for CoreLogic / Cotality because the company does not publish a rate card; anything you read that does is someone else’s contract. Confirm current terms with the vendor directly, and with our sales team for Scout Data.
Frequently asked questions
Is CoreLogic the same company as Cotality?
Yes. CoreLogic announced a global rebrand to Cotality in March 2025 — same company, new name and identity. If you are comparing quotes or reading a roundup written before then, the two names refer to the same organisation, and a proposal may arrive under either depending on when the template was last updated.
How much does CoreLogic cost?
There is no published rate card, and that is a deliberate part of how enterprise property data is sold. The number you are quoted is an output of licence scope, committed term, permitted use, delivery method and volume — five variables negotiated together, which is why two companies buying “the same” data can be quoted very different figures. The section below covers what moves each one.
Can a small solar or roofing company buy CoreLogic data?
Sometimes, through a reseller or an integrated product rather than directly, and often on terms that restrict what you may do with the records. The gating question is rarely price — it is whether outbound marketing to homeowners is a permitted use under the licence you would be signing. Establish that before you invest weeks in a procurement cycle.
What is the per-record alternative to an enterprise data contract?
Buying the finished output instead of the raw feed: a defined set of records, priced by the record, with contact matched and compliance handled before delivery. You give up the ability to query everything and gain a predictable unit cost with no annual minimum. That trade is right for outbound teams and wrong for anyone building an analytics product.