Why the advertised price is rarely the real price

You're comparing different kinds of numbers without realizing it

When you put two chatbot vendors side by side, it's tempting to treat their advertised prices as directly comparable: plug both into a spreadsheet, go with whichever number is lower. But two "prices" on two different pages are often not measuring the same thing at all. One might be a real, all-in monthly rate. Another might be an annual-only rate, a per-seat rate, or not a real price at all, just a placeholder that gets replaced once you talk to sales.

These aren't rare edge cases. They're common enough that comparing sticker prices alone, without checking what kind of number each one actually is, tells you very little about what you'd actually pay. Three patterns show up again and again.

Pattern 1: "Contact us for pricing"

Some vendors publish no real number at all, just a "starting at $X" teaser, or nothing more than "contact us." The real price only comes out after a sales call, by which point you've already spent real time in their funnel: a demo scheduled, a call taken, momentum already built toward saying yes.

The time you've already invested makes you less likely to walk away, whatever the real number turns out to be. That's worth noticing on its own: the number you found up front wasn't the price, it was the opening move in a longer conversation.

Pattern 2: the annual number looks better than the monthly number

A vendor advertises a price that only applies if you commit to a full year upfront and pay it in one lump sum. Month-to-month pricing, if it's listed at all, tends to run noticeably higher per month, sometimes considerably so. The marketing leads with the annual number because it's the lower, more impressive one at a glance.

This matters because most teams want month-to-month flexibility, especially early on. You might not know whether a support tool actually fits your workflow until you've lived with it for a few weeks. An annual prepay removes that option. A prospect comparing prices will often anchor to the lower annual number and only discover the real monthly cost after they've already decided on the vendor.

The way to catch this: always check what month-to-month costs specifically, not just the annual rate. If a vendor makes that number hard to find, that's worth noticing on its own.

Pattern 3: per-seat pricing that multiplies with your team

A price is quoted per seat or per agent. The advertised number might be some amount per seat per month, which sounds small, until you count your actual team: a few people in support, a couple more in customer success, maybe a founder who also needs access. A small per-seat number, multiplied across a real team, adds up fast, and the advertised price typically reflects a single seat, not a real team's headcount.

You: Does the per-seat price include our whole support team?

Sales rep: The price shown is per seat. You'd add a seat for each team member who needs access.

This is especially common in tools built around shared, collaborative features. Seeing the same ticket history your teammates see is exactly the kind of feature that requires paying for every person who needs it. A solo user sees the small per-seat number and assumes that's the bill. A team of ten does the multiplication and finds a very different number.

Always do that multiplication for your actual team size before comparing tools. A published "price per seat" is the one-seat price, not a representative cost for a real team.

How we handle this

We charge a single flat price: $49 a month. There's no setup fee. There's no annual commitment, it's month to month and you can cancel any time. The price applies no matter how many people on your team use the agent. One number, no tiers, no per-seat multiplier, no lower annual rate that makes the honest monthly price look bad by comparison, and nothing gated behind a "contact us" form.

That price is posted on our homepage itself, not something you have to request a demo to find out.