Your business didn’t grow 40%.
Your customers didn’t grow 40%.
Your revenue didn’t grow 40%.
But your bot traffic did.
And if your bot defense contract is priced on total traffic, your bill can grow right along with it. That’s the uncomfortable reality hiding inside a lot of security pricing models. The customer gets attacked harder, the security platform inspects more traffic, and the invoice goes up. Nobody designed the model to reward abuse. But in an AI-driven threat environment, that’s increasingly what the meter does.
AI is making this harder to ignore. Attackers can now generate credential stuffing, fake account creation, scraping, API abuse, transaction fraud, and agent-driven automation at a scale that has almost no relationship to a customer’s actual business growth. The marginal cost of creating bad traffic is collapsing. The volume of abuse is rising. And the old assumption behind traffic-based pricing is starting to break.
That assumption was simple. More traffic usually meant more business value. For a long time, that was reasonable enough. If an ecommerce site, a bank, a travel platform, a marketplace, or a media company had more traffic, it usually meant more customers, more usage, more revenue, and more value to protect. Total traffic wasn’t a perfect proxy, but it was easy to measure and easy to explain.
AI-driven abuse breaks that math. Traffic is no longer a clean proxy for business scale. It’s a messy blend of legitimate customers, automated attackers, partner integrations, crawlers, bots, scripts, and increasingly autonomous agents. Some of it is valuable. Some of it is hostile. Some of it is just noise. Too many security contracts still treat all of it as the same billable unit.
That creates two problems at once. The first is the attack penalty: customers pay more when they’re abused more. The second is the success penalty: when the security product works and suppresses the bad traffic, the bill can shrink, making the product look smaller at renewal even though it delivered exactly what the customer bought.
Both are symptoms of the same thing. The meter is no longer aligned to the value.
The Attack Penalty
Picture a retailer heading into a major promotion. Real customer demand is steady. Revenue is in line with forecast. But attackers launch a credential-stuffing campaign against the login flow, scrape product pages, hammer inventory APIs, and test stolen payment credentials at scale.
The security platform does what it’s supposed to do. It inspects the traffic, challenges suspicious behavior, blocks abuse, and keeps the site usable for real customers. Then the bill goes up.
From the customer’s point of view, that’s hard to defend internally. The business didn’t become 30% more valuable. The site wasn’t suddenly serving 30% more legitimate customers. The risk increased. The abuse increased. And the customer is now paying more because attackers chose to aim more automation at them.
This isn’t bad-faith pricing. It’s a model built for a different environment. When traffic growth broadly tracked business growth, the model was easy to live with. When bad traffic can scale independently from business value, the model starts to punish the wrong party. The CFO sees a bigger invoice. Procurement sees a contract that’s harder to forecast. The CISO has to explain why a successful defense against hostile automation produced a larger bill. That’s not a great renewal conversation.
The success penalty
The other side of the same meter shows up later, and it’s just as broken. A strong bot defense program should reduce abuse over time. It should make attacks less effective and force attackers to spend more, move elsewhere, or give up. Ideally, the worst traffic never reaches the customer at all. That’s the outcome the customer paid for.
But on a total-traffic meter, that success makes the product look smaller. Less bad traffic reaches the inspection layer. The billable number falls. The customer is safer, and the commercial signal points in the wrong direction.
At renewal time, both sides can end up arguing over the wrong evidence. The customer sees lower volume and asks why spend should stay the same. The vendor points to lower abuse and argues that the product worked. That argument might be true, but it isn’t always easy to prove when the meter is still built around inspected traffic.
This is the success penalty. The better the product gets at suppressing abuse, the less visible the abuse becomes in the number everyone is using to discuss value. The customer benefits operationally. The renewal conversation gets harder. And both sides end up debating the wrong question.
The question usually is, “How much traffic did we inspect?” The better question is, “How much legitimate business did we protect, and how much abuse did we prevent?”
This is Not a Procurement Problem
It’s tempting to treat this as a contract argument, something to negotiate after the technical evaluation is done. That misses the point. Pricing shapes behavior. It determines what gets measured, what gets optimized, and what both sides show up prepared to defend at renewal. If the contract is built around total traffic, the customer naturally wants that number to be lower. The vendor is forced to defend value through a number that rises with volume. Neither side is wrong, but both sides are now anchored to a metric that has very little to do with the business outcome.
Customers don’t buy bot defense because they want more traffic inspected. They buy it because they want real customers to get through, fake users to get stopped, account takeovers to fall, scraping to become uneconomical, fraud to be reduced, and APIs to stay available. The billable unit should move closer to those outcomes.
What a Better Meter Actually Looks Like
The obvious answer is to say security pricing should be based on value, not noise. That’s directionally correct, but it isn’t enough on its own.
“Value-based pricing” can become vendor-speak for “trust us, we helped.” Security buyers shouldn’t accept that, and most won’t. A real value-aligned meter has to clear a higher bar than a slogan. It has to be auditable, so both sides understand what’s being counted and why. It has to be predictable, so customers can budget without worrying that an attacker can blow up the bill. It has to connect to real outcomes, like protected legitimate usage, prevented abuse, or governed activity. It has to be resistant to manipulation in both directions, so neither party benefits from inflating meaningless volume. And it has to be specific to the product, because API security, bot defense, and AI agent governance don’t create value in the same way.
That last point matters. There isn’t one universal pricing model for security. The right meter depends on the job the product is hired to do.
How Cequence thinks about pricing
At Cequence, we believe security pricing should bill for value, not noise. That principle is already visible across our portfolio.
API Security is priced by the number of endpoints, which is the actual surface a customer is asking us to protect. AI Gateway is priced on tool-calls and users, the actual agent activity a customer is asking us to govern. In both cases, the meter tracks what the customer came to buy, not the unrelated volume that happens to pass through the system along the way.
Bot defense is where the legacy traffic meter still dominates the industry, and it’s where the success penalty has been hiding longest. It’s also where AI-driven automation is putting the most pressure on the old model. We apply the same value-pricing philosophy to how we think about bot defense that we apply everywhere else in our portfolio. The shape of that work won’t look identical across products, because bots, agents, and APIs are different problems with different value structures. But the principle is the same. Bill for the protection delivered, not for the noise inspected along the way.
The Renewal Question
If you’re responsible for a security renewal this year, the first question isn’t whether your price went up or down. The better question is whether the meter still matches the outcome you’re buying. Are you paying for legitimate business protected? Are you paying for abuse prevented? Are you paying for the surface that actually needs to be secured? Or are you paying for every piece of hostile automation attackers decide to throw at you? That distinction used to be easy to ignore. AI is making it harder to ignore.
The next generation of security pricing won’t be judged only by the dollar amount on the contract, it will be judged by whether the model aligns customer value with vendor incentives, in an environment where bad traffic is cheap, automated, and growing faster than legitimate demand.
At your next renewal, ask the uncomfortable question first: Are you paying for the business you want to protect, or the abuse you’re trying to stop?
