Per-send vs per-seat pricing for cold-email tools

Most cold-email and outbound tooling is priced one of two ways: per seat (a flat monthly fee per user, usually with a send-volume cap bundled in) or per send / usage-based (you pay for what you actually send, and adding a teammate is free). The right model depends entirely on your shape of usage — not on which one sounds cheaper on a pricing page.

Per-seat: predictable, but it punishes team growth and light usage

• Cost scales with headcount, not with output — a 10-person team pays 10x even if only two people run campaigns.
• Volume is usually capped per seat, so a single power-user account often gets throttled while unused seats sit idle.
• Predictable line item for finance, which is genuinely valuable at a certain company size.
• Tends to reward vendors for adding "seats" as a growth lever, which does not always track the value you are getting.

Per-send: scales with output, but takes discipline to forecast

• You pay for what you send — a small team blasting high volume pays more; a large team sending selectively pays less.
• Adding teammates, or letting an AI agent send through an API/MCP integration, does not multiply the bill.
• Costs can spike unexpectedly if a campaign runs away from you — worth checking whether the vendor has hard caps or alerts.
• Usually the better fit for API-first or agent-driven sending, where "seats" is not even a meaningful concept.

A rough way to decide

If your bottleneck is people (many users, each sending a modest, steady volume), per-seat pricing is often cheaper in practice. If your bottleneck is volume (a lean team or an automated pipeline sending a lot, or sending in bursts), per-send pricing usually wins — because you are not paying for idle seats, and you are not capped by a per-user ceiling that has nothing to do with your actual constraint.

For a look at how specific tools price and where CogniLead fits among them, see /alternatives.