Software That Charges You for Doing Nothing

Almost everything else on this site is about what you lose when you stop paying. This page is the inverse: the documented cases where not doing anything costs you money.

There are fewer of them than the internet's general paranoia suggests, and the ones that exist are published plainly. What makes them worth a page is that the windows are short and the notifications go to one person.

The five-day one

monday.com is the sharpest example, and it is not a trial at all.

If an account goes over the seat limit of its plan:

1. It stays on the current plan until renewal.
2. If the overage continues, the account owner receives three notification emails.
3. After five days, the account is automatically upgraded to the seat bucket covering its active seats.

Nothing here is hidden, and locking a growing team out of its own workspace mid-week would be worse behaviour, not better.

The problem is structural rather than ethical. Five days is short, and the emails go to the account owner — who in most organisations is whoever happened to sign up two years ago. Frequently someone in another team. Occasionally someone who has left.

The person who added the three new starters is almost never the person who gets the warning. The full detail is here.

The card-on-file one

Pipedrive states that a trial with billing details added converts to a paying account when the trial ends, and you are invoiced when the paid cycle starts. Without billing details, access is restricted instead and the data is deleted "shortly after".

So the card is the switch. There is no separate "would you like to continue?" step at the end — the conversion is the default once payment details exist.

Which makes adding a card mid-trial a purchase decision rather than an administrative one. People add them to unlock a feature for an afternoon, or because the signup flow asked and declining felt like friction.

Worth deciding deliberately on day one which kind of trial you are running: the two outcomes are documented and they are very different.

The one that keeps billing after you downgrade

ClickUp: "Add-ons are independent of your plan. You must manually add and remove them."

This is the quietest of the three because nothing happens at all. You downgrade the plan, the plan changes, and the add-on carries on billing for a subscription tier you no longer have.

There is no notification, because from the system's point of view nothing went wrong.

Check the invoice after the next cycle, not just the plan page before it. If the bill did not fall as far as you expected, this is almost always the reason.

The shape they share

Look at all three and the common factor is not greed. It is that the default behaviour favours continuity, and continuity costs money.

That is defensible. A team that outgrows its seats would rather be upgraded than locked out. A business mid-evaluation would rather keep working than lose access on day fifteen. An add-on should not vanish because someone touched the plan.

But the consequence is consistent: doing nothing is never the neutral option. It is a choice with a price, and the warning about it arrives by email to a single inbox.

The four things that prevent all of this

1. Know who the account owner is on every tool you use. Not the admin — the owner, the one who receives billing mail. If that person has left, fix it today.
2. Make sure billing email is not filtered. Notifications from software vendors are exactly the category people route into a folder they never open.
3. Diarise renewal dates as operational deadlines. Annual plans are the expensive ones to miss, because the next chance to change anything is a year away.
4. Check the invoice after any plan change, once, at the following cycle. Five minutes, and it catches the add-on problem.

If it already happened

Refunds exist and have deadlines.

FreshBooks requires refund or dispute requests to reach Support within 90 days, with a 5 business day grace period on recent payments. 37signals says it will consider refunding someone who has not used their account in months or who has just started a new billing cycle.

Both require asking, and asking promptly. A charge you notice in month four is a harder conversation than one you notice in week one, which is an argument for reading invoices rather than filing them.

The related failure — where a payment does not go through at all — behaves differently again, and is covered in what happens when your card fails.