<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Sergio Barguilla]]></title><description><![CDATA[Sergio Barguilla]]></description><link>https://sergiobarguilla.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 16:26:54 GMT</lastBuildDate><atom:link href="https://sergiobarguilla.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How we normalize per-minute vs per-caller voice AI pricing]]></title><description><![CDATA[If you've tried to pick an AI receptionist or voice-agent platform, you've probably hit the same wall we did: every vendor prices in a different unit…]]></description><link>https://sergiobarguilla.hashnode.dev/how-we-normalize-per-minute-vs-per-caller-voice-ai-pricing</link><guid isPermaLink="true">https://sergiobarguilla.hashnode.dev/how-we-normalize-per-minute-vs-per-caller-voice-ai-pricing</guid><category><![CDATA[AI]]></category><category><![CDATA[Voice]]></category><category><![CDATA[pricing]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Sergio Barguilla]]></dc:creator><pubDate>Tue, 03 Nov 2026 19:52:37 GMT</pubDate><content:encoded><![CDATA[<p>If you've tried to pick an AI receptionist or voice-agent platform, you've probably hit the same wall we did: every vendor prices in a different unit.</p>
<p>Developer platforms like Vapi, Retell and Bland quote a rate per minute. Some receptionist products charge per call or per caller. Others sell a monthly plan with a bucket of included minutes or calls, then charge overage once you go past it. A few combine a platform fee with usage. Put them side by side and the headline numbers are meaningless: $0.07 a minute, $1 a call and $49 a month for 100 minutes aren't the same kind of number.</p>
<p>Business owners don't think in any of those units. They think, "We get about 300 calls a month, and most last three minutes. What will this cost me?" So that's the unit we normalize to: <strong>estimated monthly cost at your call volume and average call length.</strong></p>
<p>The conversion itself is simple arithmetic. Getting it right is the hard part.</p>
<p>A per-minute rate becomes calls × minutes × rate. A per-call price becomes calls × price. A flat plan is the base fee plus overage on whatever goes past the included allowance, and you have to check every plan a vendor offers, because the cheapest plan at 100 calls is often not the cheapest at 1,000. We price every published plan at your volume and keep the lowest, overage included.</p>
<p>Per-minute developer platforms add another wrinkle: their rates aren't all-in. One covers orchestration only, while another bundles speech and telephony. The lowest number is not always the lowest bill. Rather than invent a "true" all-in cost, we show what each rate covers and what it leaves out. Our <a href="https://toolcrew.app/ai-voice-agent-cost-per-minute">per-minute comparison</a> does this at 1,000, 10,000 and 50,000 minutes a month.</p>
<p>All of this is only as good as the input prices, so the data pipeline follows strict rules. Once a day a scraper downloads each vendor's pricing page as plain HTML, without running JavaScript, and a parser written for that vendor reads only numbers printed on the page. When a price appears twice, say on the plan card and again in the FAQ, both copies must agree. If a number is missing or the copies conflict, we don't guess: the vendor's record stays as it was and the failure is logged. A record is only rewritten when a price, plan, allowance or overage rate actually changes, so "last updated" means the last time prices really moved.</p>
<p>Some vendors can't be read this way: their price only appears after JavaScript runs, or there's no public price at all. Those are updated by hand and labeled with their own check date.</p>
<p>Last, the ranking is cheapest first, and vendors we can't estimate go last. We use some affiliate links, but commissions never change the order.</p>
<p>Here's how each conversion works in detail.</p>
<h2>The common unit</h2>
<p>Every estimate starts from two inputs you control: <strong>calls per month</strong> and <strong>average call length in minutes</strong>. Everything else comes from the vendor's published pricing page. The output is one number in USD: estimated monthly cost at that volume. Because every vendor ends up in the same unit, the comparison is finally apples to apples.</p>
<h2>The conversions</h2>
<p>The figures below are illustrative inputs, not quotes from any vendor.</p>
<h3>Per-minute</h3>
<p><code>monthly = calls × avg_minutes × rate_per_minute</code></p>
<p>At 300 calls of 3 minutes, that's 900 minutes. A $0.07/minute rate comes to $63. Minimums and per-minute billing increments are applied where the vendor publishes them.</p>
<h3>Per-call (or per-caller)</h3>
<p><code>monthly = calls × price_per_call</code></p>
<p>Call length doesn't matter here, which is why per-call pricing can look expensive for short calls and cheap for long ones. At 300 calls and $1 per call, you pay $300 no matter how long each call lasts.</p>
<h3>Flat plan plus overage</h3>
<p><code>monthly = base_fee + max(0, usage − included) × overage_rate</code></p>
<p>Usage is measured in whatever unit the plan meters: minutes or calls. A $49 plan with 100 included minutes, priced at 900 minutes, also bills 800 minutes of overage, and that overage usually dominates the total. A plan that doesn't publish an overage rate can't be estimated past its allowance. We mark that plan as not estimable at that volume rather than assume a rate.</p>
<h3>Tiered plans</h3>
<p>Most vendors sell several plans. We run the flat-plus-overage formula for <strong>every published plan</strong> at your volume and keep the lowest result. That's how the "best plan" can change as volume grows: the starter plan wins at 100 calls, and a higher tier with a bigger allowance wins at 1,000. Where pricing is a platform fee plus usage, the fee is added first and usage is priced with the matching formula above.</p>
<h2>The gaps: what per-minute leaves out</h2>
<p>Developer-platform rates aren't directly comparable, even when they share a unit. One rate covers orchestration only. Another bundles speech-to-text, the LLM, text-to-speech and telephony. A third bundles some of those and bills the rest separately.</p>
<p>We don't invent a "true" all-in number by guessing at third-party costs. Instead, the <a href="https://toolcrew.app/ai-voice-agent-cost-per-minute">per-minute comparison</a> labels what each rate includes and what it leaves out, at 1,000, 10,000 and 50,000 minutes a month. If a line says "telephony not included," you know to budget for it. We don't fold in a number we didn't read on the vendor's page.</p>
<h2>The pipeline</h2>
<p>The math is only as trustworthy as its inputs, so the pipeline is built to fail closed:</p>
<ol>
<li><strong>No-JS scrape.</strong> Once a day we fetch each pricing page as plain HTML, without running JavaScript. That gives us exactly what the server publishes, and it's reproducible.</li>
<li><strong>Vendor-specific parsers.</strong> Each vendor has its own parser that reads only numbers printed on the page: prices, allowances and overage rates. No inference, no "typical" values.</li>
<li><strong>Duplicate checks.</strong> When a price appears in more than one place, such as the plan card and the FAQ, all copies must agree.</li>
<li><strong>Fail closed.</strong> If a number is missing or the copies conflict, the vendor's record stays as it was and the failure is logged for review. A bad parse never overwrites good data.</li>
<li><strong>Meaningful timestamps.</strong> A record is rewritten only when a price, plan, allowance or overage rate actually changes, so "last updated" reflects real price movement.</li>
</ol>
<p>Vendors whose prices only render with JavaScript, or who don't publish prices at all, are updated by hand. They're labeled as manual, with their own check date.</p>
<h2>The ranking</h2>
<p>Results are sorted by estimated monthly cost at your volume, <strong>cheapest first</strong>. Vendors we can't estimate, because they have no public price or no overage rate past the allowance, go last instead of getting a made-up number.</p>
<p>Some listings use affiliate links. <strong>Commissions never change the order.</strong> The sort key is the estimate and nothing else. The full policy is on our <a href="https://toolcrew.app/disclosure">disclosure page</a>.</p>
<h2>Try it</h2>
<p>Toolcrew covers US vendors with USD pricing. Enter your monthly calls and average call length at <a href="https://toolcrew.app">toolcrew.app</a> to see every vendor priced in the same unit. If you spot a wrong price or disagree with how we normalize something, tell us. Corrections are the fastest way to make the data better. How we handle affiliate links is laid out at <a href="https://toolcrew.app/disclosure">toolcrew.app/disclosure</a>.</p>
<p><em>Originally published on</em> <a href="https://dev.to/sergio_barguilla_3757e6e7/how-we-normalize-per-minute-vs-per-caller-voice-ai-pricing-2aci"><em>Dev.to</em></a><em>.</em></p>
]]></content:encoded></item></channel></rss>