Read the Pricing Model as an Incentive Document

Every vendor's pricing page is also a confession. It tells you exactly what behaviour makes them money, and therefore exactly what they will optimise as long as you are their customer.

Per-seat pricing pays the vendor when more of your people log in. Usage-credit pricing pays them when you consume, whether or not the consumption produced anything. Cost-per-lead pricing pays them when a usable lead lands in your hands.

None of these is dishonest. But only one of them points the vendor's roadmap at the same target as your pipeline.

What Seats Actually Charge For

The seat model was built for software whose value is a person using an interface: a design tool, an inbox. Demand tooling kept the model out of habit, and the habit costs buyers in two ways.

First, the seat tax on collaboration. The moment a rep, a marketer, and an operations person all need to touch the same account record, the price triples, so teams ration access to data that should be ambient. Second, the decoupling of price from output. A seat costs the same in a month where the tool produced two hundred sales-ready leads and a month where it produced nothing. The vendor's revenue is protected from your results, which is precisely the arrangement an incentive-minded buyer should notice.

Watch what seat-priced vendors build: engagement features. Dashboards, notifications, reasons to log in. Login frequency defends renewals. It is rational, and it is aimed at a metric that is not your pipeline.

What CPL Puts on the Line

Cost-per-lead pricing inverts the exposure. The vendor invoices per enriched, usable lead delivered. No seats, no minimum platform fee; the invoice scales with output.

Follow the incentives through that model. Match rate becomes the vendor's revenue problem: an account they cannot enrich is an account they cannot bill. Quality becomes their retention problem: a delivered lead that a rep cannot work gets disputed, and a client who disputes leads churns. Infrastructure efficiency becomes their margin problem: at a fixed price per lead, every failure and retry in their pipeline comes out of their side of the table, not yours.

A CPL vendor who is bad at enrichment goes out of business. That is the guarantee no feature list can offer.

The Objections, Taken Seriously

CPL invites two fair challenges, and both are really questions about definitions.

"Does the vendor stuff volume?" Only if a "lead" is defined loosely. The fix is contractual: a lead is an account from YOUR target list, enriched to an agreed depth, with a verified contact. When the list is yours, the vendor cannot manufacture volume; they can only improve their hit rate on accounts you chose.

"Is the unit price high?" Per unit, a properly enriched lead costs more than a database row, because it should: it replaces the row plus the hours of research the row demands. The honest comparison is not CPL against a data subscription; it is CPL against seats plus the salary time your team spends turning rows into something workable. Run that arithmetic on your own numbers before deciding which model is expensive.

The Alignment Test for Any Vendor

Strip the analysis to one question you can ask across a table: describe the month where we fail and you still get paid.

A seat vendor has a long answer, because the scenario is routine: you paid for seats, results did not come, the invoice stands. A CPL vendor has a short answer, because the scenario barely exists: no usable leads, no bill. The length of that answer is the alignment gap between you and them.

Why We Price This Way

Relish Demand prices per enriched lead because the pipeline is the product. Upload a target account list; pay for the accounts that come back enriched, scored, and matched to a personalised page. The economics that make this survivable on our side (a single automated pipeline from list to delivery, with no manual stitching between stages) are the same economics described in The Consolidation Imperative. Pricing is downstream of architecture: vendors sell the model their infrastructure can afford.

If the incentive argument holds for your situation, the pricing page has the numbers, and a demo runs the pipeline against your own list so you can judge the unit of value before paying for one.