This is an opinion piece. It sets out the view of NerdBible's editors; the facts it relies on are sourced below.
Our view is simple: when an AI sales agent is billed per contact, the pricing page should also show what a booked meeting is expected to cost, and it should publish the price and rollover rules for its volume plans. A per-contact price is a unit cost. Buyers are not shopping for contacts. They are shopping for conversations that turn into sales calls.
What changed on the page
The trigger is a pricing reset at AiSDR, one of the vendors in the AI sales agent category. According to the independent pricing analysts at Usage Pricing, in October 2026 AiSDR retired its Solo ($250 a month), Explore ($900) and Scale ($2,500) contact-allowance tiers and moved to a straight per-person rate. The same analysis says its pricing has changed three times in under two and a half years.
The vendor's own pricing page now leads with $1.50 per person prospected on a self-serve pay-as-you-go plan. It says this is charged daily, can be stopped at any time, and covers research, lists and writing at no extra cost. Teams contacting 1,000 or more people a month are sent to a sales-led Team plan.
There is a good deal to like here. A buyer can sign up without a sales call, and the FAQ says the paywall appears only when the buyer is ready to launch a campaign. We are not alleging that AiSDR has broken any rule. This piece is about what a pricing page should help a buyer do, and AiSDR's page is a recent, public example.
The arithmetic the buyer is left to do
The same page gives a rule of thumb: one to three booked meetings for every 100 contacts, which it calls a directional benchmark based on the historical performance of teams using AiSDR, varying with market fit and offer strength. The page does not turn that into a cost per meeting, so here is the arithmetic. At $1.50 a person, 100 contacts cost $150. One to three meetings from that spend implies roughly $50 to $150 per meeting in platform charges at the self-serve rate. That is our calculation from the vendor's figures, not a number the vendor publishes, and it leaves out add-ons such as the $33 warmed-up mailbox.
A buyer who sees only "$1.50" has to find that benchmark in the FAQ, divide it, and hope the benchmark applies to their market. A buyer who sees "$50 to $150 per meeting at the vendor's own benchmark, lower or higher depending on your market" can compare it with a human SDR, an agency or a competitor's seat price in seconds.
Where the page leaves gaps
- Volume plans have no price. The page says Team plan prices fall by up to 40% per contact as volume rises, but it gives no starting figure. Pricing is based on your volume, so the buyer has to talk to sales to learn it.
- Rollover is explained by sales, not the page. Asked what happens to unused allowance, the FAQ says rollover rules depend on the subscription and that the sales team will explain what carries over and when it expires before sign-up.
- Small inconsistencies. The page gives a minimum campaign of $7.50 in one place and, in another FAQ answer, says campaigns start from as little as $3. Usage Pricing flags the same mismatch. The FAQ also still describes monthly, quarterly and annual terms, with annual 20% cheaper than quarterly, alongside the new self-serve rate.
None of these is dramatic. Together they mean that the cheapest reading of the page and the likeliest reading are different, and the buyer finds out which is which only by asking.
The strongest counter-argument
The fair objection is that a vendor cannot honestly promise meetings. Outcomes depend on the buyer's offer, list, market and follow-up, and the vendor's own page says as much. Per-contact pricing is arguably the more honest meter: the buyer pays for work done, can stop within a day, and risks as little as a few dollars to test. Pricing per meeting also raises its own problems, such as who decides what counts as a meeting, and it can reward a vendor for chasing easy bookings over good ones.
We accept most of that. We are not asking for a guarantee or for per-meeting billing. We are asking for a clearly labelled range, built from the vendor's own benchmark and stated as a benchmark, placed next to the per-contact price. A vendor that is confident in its 1 to 3% figure loses nothing by showing what it implies. A buyer who reads it still pays $1.50 a contact, but now knows what that tends to buy and can judge whether the benchmark looks plausible for their market.
Why a plain range is the minimum
When the FTC launched its Operation AI Comply sweep in 2024, its then chair said that there is no AI exemption from the laws on the books. That statement was about deceptive conduct in several unrelated cases, and it says nothing about any vendor in this piece. It does underline a basic expectation: claims about what AI tools deliver should be backed by evidence and presented clearly. A benchmark that sits in an FAQ while the headline shows only the unit price leaves the buyer to assemble the clearer picture alone.
For small businesses the stakes are practical. Because pay-as-you-go is charged daily, spend runs for as long as a campaign does, and an outreach list is only worth what it converts. A pricing page that states the unit price, the benchmark outcome, the volume price and the rollover terms lets a buyer set a budget before launching rather than after.
What we would like to see
- A cost-per-meeting range beside the per-contact price, labelled as a benchmark with its source and caveats.
- A published starting price for volume plans, even if it is a "from" price.
- Rollover and expiry rules on the page, not only on a sales call.
- One minimum-campaign figure, used everywhere the page mentions it.
Per-contact billing is a reasonable model. It becomes a fair comparison only when the page also says what the contacts are expected to produce.
