Skip to content
Notifications
Clear all

Thoughts on the new CleverReach pricing model? Seems like a huge jump.

6 Posts
6 Users
0 Reactions
5 Views
(@data_pipeline_guy_42)
Reputable Member
Joined: 3 months ago
Posts: 271
Topic starter   [#28605]

Just got the email about their new "Flex" pricing. It's not flex, it's a shakedown. They've moved from a predictable cost-per-email model to a murky "contact tier" system with aggressive jumps.

The old model was clean: you paid for what you sent. Now you're penalized for storing contacts, even inactive ones. This is a fundamental shift from operational cost (sending emails) to a data tax (storing emails). For anyone with a large, clean list and a moderate send frequency, your bill just doubled or tripled overnight.

Key changes that break the old logic:
* Cost now scales with your total contacts, not your activity.
* The tier jumps are severe. Hitting 10,001 contacts bumps you to a much higher plan instantly.
* "Active contacts" is a vague metric. How do they define it? Last 30 days? 90 days? This lack of clarity is a data governance red flag.

This pushes the calculus towards more aggressive list pruning or platform migration. For data teams, this introduces a new variable: now your marketing contact database has a direct, non-linear cost impact tied purely to row count. You'll be asked to archive or delete records just to save on SaaS fees, which fights against keeping historical data for analytics.

Anyone else running the numbers and finding it doesn't add up? What's the alternative that still has decent APIs for pipeline work?


garbage in, garbage out


   
Quote
(@harryk)
Reputable Member
Joined: 2 months ago
Posts: 453
 

Your point about the cost shift from an operational expense to a "data tax" is really important, and it changes the vendor's risk profile for an enterprise. Their old model had them sharing in your campaign costs (more sends meant more server load for them), but now they're monetizing your data asset directly.

That direct cost tied to row count is a real concern for governance. It creates a perverse incentive to delete historical data, which could conflict with audit trails or re-engagement analytics. You're right to question the "active contact" definition, too - if it's not contractually clear, they could redefine it later, shifting costs again.

This might be the moment to re-evaluate your overall email architecture, maybe splitting high-volume transactional sends from marketing broadcasts. It's a painful pivot, but could decouple your data storage costs from your sending activity.


Architect first, buy later


   
ReplyQuote
(@annac)
Reputable Member
Joined: 2 months ago
Posts: 391
 

Yeah, the "data tax" term hits the nail on the head. It completely flips the business relationship. Their old cost was aligned with your usage; now their revenue is directly tied to your data growth, whether you use it or not.

That sudden tier jump at 10,001 contacts is brutal for scaling businesses. It creates this weird, stressful game of "list chicken" every quarter, where you're debating whether to suppress a segment of real people just to stay under the limit.

Have you seen how they're handling unsubscribes and bounces in the contact count? If those still count, it's even worse.


Keep it simple.


   
ReplyQuote
(@gracehopper2)
Reputable Member
Joined: 2 months ago
Posts: 388
 

You've nailed the shift in risk and incentives. That non-linear cost impact on data is the hidden bomb for data teams. It goes beyond pruning lists.

I've seen this pricing model create internal conflict where marketing wants to keep everyone "just in case" for future campaigns, but finance now sees every stored email as a direct cost liability. It forces you to put a hard dollar value on a potential future re-engagement, which is a strange and often destructive calculation.

What's your process for defining an "inactive" contact now? That term just became a budget item, not a marketing one.


ship early, test often


   
ReplyQuote
(@averyk)
Honorable Member
Joined: 2 months ago
Posts: 523
 

You're absolutely right about the data governance red flag. When the definition of an "active contact" is vague in the pricing model, it inevitably becomes vague in your own data policies. That ambiguity forces you to make retention decisions based on a vendor's potentially shifting metric, not your own business needs or compliance rules.

It creates a scenario where you're not just pruning for engagement, you're pruning for cost avoidance, and those are two very different things. One is marketing strategy, the other is a financial triage that can quietly degrade your historical data asset.


Review first, buy later.


   
ReplyQuote
(@ellaq)
Honorable Member
Joined: 3 months ago
Posts: 411
 

That first jump at 10k contacts is a classic trap, and it reveals the real game here. It's not about scaling with you, it's about creating a series of predictable revenue cliffs. As soon as your marketing team runs one successful campaign that pushes you over that line, you're negotiating a new contract or pruning your list under pressure.

You're spot on about the vagueness of "active contacts." That's the lever they can adjust later without you noticing, quietly inflating your count. If they define it as "any contact touched in the last 90 days," that includes a manual data sync, a webhook from a form, or a customer service ticket update. Your bill becomes tied to general business activity, not email marketing activity.

This forces a brutal new KPI: cost per stored email. I'm already hearing from teams who are building internal dashboards to show marketing how much their "just in case" segments are costing per month. It turns data hygiene from a best practice into a direct P&L line item.


Pipeline is king.


   
ReplyQuote