Leaving a tool that charges for contacts you never emailed

The decision

Your marketing or CRM bill rose after a pricing change tied to contacts stored, subscribers synced, or profiles kept—whether or not you messaged them. People online will tell you to cancel today. Others will say switching costs more than the increase. Both can be true. Walk the for and against with your own numbers.

For staying (or renegotiating)

• The list is doing work. If automations, segments, and deliverability depend on this vendor, a price hike may still be cheaper than a broken welcome series in peak season.
• You can delete your way down. Many tools charge on contacts stored. Archiving or suppressing cold addresses—lawfully—can drop you a tier without a migration.
• Sales might meet you. A written usage summary (active 90-day contacts vs total stored) is a better renegotiation packet than a vague threat to leave.
• One vendor holds the sending reputation. Moving domains and warm-up mid-campaign is real work; staying buys time to plan.

Staying is rational when you price active contacts, clean the list, and get the increase in writing with a review date—not when you simply avoid the export.

For leaving

• The metric trains bad habits. Billing on hoarded contacts rewards never deleting. That is the opposite of good list hygiene.
• You already pay elsewhere. If the same people live in your store, support tool, and ads manager, paying again to store them idle is optional.
• Export is healthier now than in a panic. Quiet weeks are when you test CSV/API export, field mapping, and a sample campaign on a new tool.
• Automations are portable if you inventory them. A one-page list of triggers and messages (see scope automation before you buy) turns "we can't leave" into a project with an end.

Leaving is rational when the math on contacts you actually message no longer works, and you have a tested landing place—not when a social thread dared you.

Against both extremes

Against "cancel tonight": you may lose segments, consent records, and sending history you need for compliance. Against "never leave": you may fund a list of people who have not opened a message in years. The adult move is a third path—clean, measure, decide—on a calendar.

Use an exit scorecard mindset from vendor exit readiness: ownership of data, export completeness, replacement timed before cancel. Add one commerce-specific column: cost per contacted-in-90-days profile, not cost per row stored.

A sample worksheet for the meeting

Bring one page to the decision meeting—not a slide novel:

• Contacts stored versus contacted in the last 90 days versus unsubscribed versus never messaged.
• Current monthly bill and the announced bill after the change.
• Cost per contacted-in-90-days profile now and after the hike.
• Alternative quote calculated the same way.
• Automations that would break (welcome, abandoned browse, renewal, support surveys).
• Export test result: fields present, special characters intact, consent timestamps readable.
• Parallel-run plan: dates, who sends what, when the old account becomes read-only.

If the room cannot fill that page, you are not ready to cancel or to renew casually. Fill it once; reuse it at each pricing anniversary.

Compliance sits beside cost. Consent records, suppression lists, and regional rules must survive the move. A cheaper tool that loses lawful-basis documentation is not cheaper. Involve whoever owns privacy in the export review, not after the first complaint.

Vendors sometimes offer a temporary discount to pause a leave. Treat that as buying time to finish the worksheet—not as proof the contact metric is fair. Put a calendar reminder on the discount end date so the problem does not quietly return.

Also price your team's hours. A migration that consumes two weeks of a marketer and an engineer has a cost even if the new SaaS invoice looks friendly. Write those hours on the same page as the subscription math so leadership sees the whole trade.

How to decide this week

1. Export a full contacts dump and open it. Are consent and source fields present?
2. Count contacts messaged or active in the last 90 days versus total stored.
3. Divide the new monthly bill by active contacts. Compare to an alternative quote the same way.
4. List every automation that would break on Monday after cancel.
5. If you stay, schedule a list-clean and a renegotiation note. If you leave, schedule a parallel-run week before you kill the old account.

We help teams redesign business process automation around lists and handoffs they own. If your bill is growing faster than your sends, talk to us.

There is also a softer cost: team attention. Every week you spend arguing about the bill is a week you are not improving the welcome series or the offer. Set a decision date. On that date, stay with a clean list and a written renegotiation, or leave with a parallel run. Open-ended frustration is the most expensive option because it never shows up as a line item.

If you stay, schedule a quarterly contact hygiene review the same way you schedule security reviews. If you leave, keep the old account read-only long enough to confirm deliverability and consent trails on the new tool—then cancel deliberately, not in a mood.

Watch for double billing during parallel run: two tools charging for overlapping contacts while you test. Negotiate a short overlap credit or keep the old account in a free/paused tier if offered. Accidental double pay is a common migration tax.

Share the worksheet with finance before marketing alone decides. Contact-based SaaS spend often sits in a marketing budget while deliverability and compliance sit elsewhere. A shared decision prevents one team from optimizing invoice optics while another inherits risk.

Price the contacts you use, not the contacts you hoarded.

Price the contacts you use, not the contacts you hoarded. That line is the filter for every renegotiation and every migration pitch you will hear this year.

When the decision is stay, put the clean-list tasks in the same sprint calendar as campaigns—not "someday hygiene." When the decision is leave, freeze new automation builds on the old tool so you do not polish a platform you are exiting. Either path beats another month of complaining about the invoice in chat.

Related work: Howcast.