Free Plan or Paid Plan? Decide Whether to Upgrade Your Email Tool With Evidence
About Alex: a pen name. There is no shop behind it, and no results are claimed. This is arithmetic, official pages and opinion, and I'll mark which is which.
In short
Upgrade only when a limit you can name has cost you more, over the same period, than the next plan costs, and the plan you are looking at is shown to lift that limit. Everything else is "stay" or "keep counting". (That rule is my judgement, not a standard.)
What you get from reading it:
- A hit log that separates a full row from a limit that actually cost you something
- A one-page sheet that prices stay, upgrade and switch per month and per year
- A decision, an early-review trigger and a review date
The Upgrade button is easy to keep in view, and a monthly price comes round twelve times a year. When the list crosses a round number, the button can start to feel like a small accusation. A feeling that you ought to upgrade is not evidence. Neither is the opposite feeling, that you refuse to pay for one more tool. Both are worth a sheet of paper.
This guide is for the moment after you started. You already send email from a free plan, and you want to know if a paid one is worth it. Two neighbouring guides cover the rest, so I won't repeat them:
- Choosing whether to open a free systeme.io account at all: systeme.io's Free Plan: What You Get, What You Don't.
- A tool-agnostic test for any purchase: Five Questions to Ask Before You Buy Another Paid Tool.
Here the work is narrower: what to log, what a hit on a limit looks like, and how to compare staying, upgrading and switching.
Who this is for. A seller with an email list on a free plan. If you have no list yet, a plan decision is premature; the sign-up page comes first, and Build Your First Email Signup Page and Welcome Email on systeme.io's Free Plan is the hands-on guide for it.
What it costs. Nothing, and about 45 minutes the first time (my estimate), plus a few minutes a week of logging.
Three imaginary sellers carry the numbers: Amara (printable wall calendars), Leo (spreadsheet templates) and Sam (a brand-new list). None is real; every number and account response attached to them is invented.
Staying free is a full answer. Of the three cases below, two end without a payment.
Step 1: Build a limits ledger from the plan page
A ledger has one line per limit you care about: what the plan allows, what you use now, how full that is. The plan side must come from your tool's own pricing page, with the date you read it written down. I'd not use a review site for this.
For systeme.io, I read the pricing page FAQ lines on 25 October 2026. The comparison table on that page did not load as text (every cell came back empty), so this list may be incomplete. Its FAQ says:
| Free | Startup | Webinar | Unlimited | |
|---|---|---|---|---|
| Price per month | $0 | $17 | $47 | $97 |
| Price x 12 (my arithmetic) | $0 | $204 | $564 | $1,164 |
| Contacts | 2,000 | 5,000 | 10,000 | unlimited |
| Sales funnels | 3 | 10 | 50 | unlimited |
| Automation rules | 1 | not read | not read | unlimited |
| Email campaigns | 1 | not read | not read | not read |
Emails sent are unlimited on every plan, according to the same FAQ, which also says other free-plan features have lower limits, and names 1 automation rule, 1 email campaign and 500 students as examples. The gaps matter: the Startup rule count and any campaign limit are what a rule-limited seller needs, and I could not read them.
The page also shows an annual billing option labelled "2 months free", but the annual price did not load. If that label means ten months charged, Startup would be 10 x $17 = $170; that is an inference, so read the real figure before using it.
The same FAQ gives its own sizing advice: under 2,000 contacts, free; 2,000 to 5,000, Startup. That is the vendor describing its own product. I'd treat it as a pointer to what to check, not a reason to pay.
Now your own ledger. Your dashboard may show contacts, funnels, rules and campaigns somewhere; I could not check where, so look for those words in the account or its help.
LIMITS LEDGER plan: ____
price page read on: ____
Limit | Allows | I use | Used %
Contacts | | |
Funnels | | |
Rules | | |
Campaigns | | |
At the contact limit the tool
does: ____ (source: ____)
What counts as a contact: ____
Write a number you read or counted. Write 0 only if you checked and it was zero, not measured if nothing counts it, and unknown if a counter exists but you cannot find it. For contacts, my sources say neither what counts as one nor what happens at the cap, so fill both from your account's help.
Amara and Leo, side by side (imaginary):
| Limit | Allows (free) | Amara uses | Amara % | Leo uses | Leo % |
|---|---|---|---|---|---|
| Contacts | 2,000 | 1,640 | 82% | 900 | 45% |
| Funnels | 3 | 2 | 67% | 3 | 100% |
| Rules | 1 | 1 | 100% | 1 | 100% |
| Campaigns | 1 | 1 | 100% | 1 | 100% |
Several rows read 100%. Step 2 asks which of them cost anything.
Step 2: Log hits, not full rows
A full row is not a cost. Amara's rules row reads 100%, but she has no second automation waiting to be built. So I use a stricter word. A limit is hit only if, in the last 30 days, one of these happened:
- Blocked: you tried to do something and the plan refused.
- Workaround: you did extra manual work, or accepted a worse result, because the plan would not let you do it the way you wanted.
Keep the log as you go, one line per event. Reconstructing a month from memory is where the numbers go soft.
HIT LOG
Date | I tried to | What happened
| (exact words on screen)
| Workaround | Minutes | People
A third state is projected: not hit yet, but your own counts say it will be. For contacts:
per month = added in 90 days / 3
months left = room / per month
With under 90 days of history, write not enough history. A projection sets your review date. It is not a reason to pay today.
A wrong first attempt (imaginary)
Amara sees contacts at 82%, rules at 100%, campaign at 100% and writes "upgrade, probably". Then she asks the two questions. Anything blocked in 30 days? No. Any manual workaround? No. The full rows are full because she has one rule and one campaign and wants nothing more. Contacts: 105 added in 90 days is 35 a month; room is 2,000 - 1,640 = 360; 360 / 35 = 10.3 months.
She crosses out "upgrade, probably" and writes "none yet", with the projection beside it. Paying now would have bought room she would not touch for about ten months.
Try the free ways round before you call it a hit
A hit is confirmed when the obvious free ways round have failed for a reason you can write down. My sources do not say whether one rule can serve several forms, or whether one campaign can hold a long series, so test or ask rather than assume. Write the answer and its source on the sheet.
Leo (imaginary, including every response of his account). He has three sign-up pages. His one rule is attached to the first page only. In 30 days, 140 people joined through pages two and three, got no welcome email, and he sent each the first email by hand. That is a workaround. He tries the free options:
- A second rule. The account refuses it with a message that the free plan allows one (an invented message). That matches the FAQ.
- One rule for all three pages. He asks support; the invented reply is no, one form per rule. A real seller must ask and write down the real answer.
- Merge the pages into one. He decides against it, because he wants sign-ups per page.
Only now is "automation rules" his confirmed hit. His other full rows are not hits. Had support said yes, he would have no hit and would stay free. Write a limit on the sheet only if you can state it in one sentence as blocked or workaround and name what you tried. If all you have is a vague annoyance, write "none yet".
Step 3: Count what the limit cost in 30 days
The decision compares two amounts, so the cost has to become a number, with its source beside it.
People: how many sign-ups got less than planned (no welcome email, say)? Count from your contact list's sign-up dates or your sent-mail folder.
Hours: workaround count times minutes each. Leo: 140 x 3 = 420 minutes = 7 hours.
Write beside each figure whether it was counted or estimated. A guess is allowed if you call it one; write a range and use the lower end against a price. If you did not log, rebuild from sent mail and dates, or write not measured.
Putting money on hours (optional). You need your own value for an hour; this guide has none. Leo names $15 (invented).
Break-even for the $17 plan is 17 / 15 = 1.13 hours, about 68 minutes, which at 3 minutes per person is about 23 people a month. Check the edge: 22 people cost 66 minutes, 1.1 hours x $15 = $16.50, under $17; 23 people cost 69 minutes, 1.15 hours x $15 = $17.25, over it.
Step 4: Price the three options per month and per year
A monthly price looks small. Multiplying by 12 shows the commitment and lets you compare with a switch that has a one-off cost.
A stay: $0 + (hours x $/hour)
= ___/month x 12 = ___
B upgrade: plan ___ $__/month x 12
= ___ (+ workaround left)
C switch: $__/month x 12 = ___
+ one-off hours x $/hour
year 1 ___ ; later ___
A. Stay. Hours per month times your hourly value. The yearly figure assumes the last 30 days repeat, which you do not know.
B. Upgrade. Take the smallest plan whose row actually lifts the limit you named, and read that row.
For systeme.io, Startup's contact, funnel and course rows are readable; its rule and campaign rows are not in what I read. So if your hit is rules or campaigns, the number comes from the live page or from the vendor in writing, before you pay.
C. Switch. Write the other tool's price, page address and date, plus the one-off hours from Step 5. I list no other tool's prices or features: I fetched no other vendor's page, and a number from a review site would not be good evidence.
Leo (imaginary).
- A: 7 h x $15 = $105 a month, 105 x 12 = $1,260 a year if every month looks like the last.
- B: $17 a month, 17 x 12 = $204 a year, and he expects the hand work to stop. That assumes the Startup row for rules reads at least 3 on the live page (imaginary here; unread by me).
- C: he has read no other price, so he works out what a move would need. At 10 hours the one-off is 10 x $15 = $150. Year one beats $204 only if 12 x price + 150 < 204, so price < 54 / 12 = $4.50 a month. Later years, under $17.
If Startup's rule row turns out to be below 3, the only plan I could read that lifts rules is Unlimited at $97: break-even is 97 / 15 = 6.5 hours, about 130 people a month (129.3 rounded up). Leo's 140 barely clears that, and his halved count (70 people, $52.50) does not. His decision would become "too thin".
Amara (imaginary). A: $0. B: $17 a month, $204 a year; about ten months of room left, so paying now is about 10 x $17 = $170 for room unused in that time. C: not priced, because nothing was hit.
If no plan lifts your limit, write "no plan found" and treat B as unavailable. If a price is missing, write unknown and fill it from the vendor.
Step 5: Fill in the switch-cost checklist
Option C needs a one-off cost in hours, and that is the part a friendly new price hides. Moving a list is several small jobs. This checklist names jobs, not any tool's screens. Where systeme.io's help is quoted, it is an example only.
| # | Job | What it involves | Hours |
|---|---|---|---|
| 1 | Export with a consent record | Download contacts. Ask whether the export carries sign-up date, form or page, and subscribed or unsubscribed status. Keep a dated copy of the sign-up wording people saw. | |
| 2 | Opt-outs | Move the list of people who left, so nobody who left gets mail from the new tool. | |
| 3 | Sender and domain | systeme.io's help says an @gmail.com sender address has been refused since 16 July 2024 and recommends your own domain [S17]; it also says the sending address should be tied to a domain with an active homepage, with SPF, DKIM and DMARC records [S20]. Another tool may differ. | |
| 4 | Forms, pages and links | Rebuild each one, then change every place that points to the old one: Pin links, bio links, anything published. | |
| 5 | Emails, rules, tests | Copy text; rebuild and test triggers and delays; decide where people mid-series go. | |
| 6 | Overlap and learning | Keep the old account until the new one passes a test, and keep the export file safe. Add time to learn the screens. |
Add the hours column, and multiply by your hourly value if you use one. If you are unsure, use the top of a range, because under-counting makes a switch look cheap. Rules about consent and unsubscribing depend on where you and your readers are, and I checked no law for this guide; read the rules that apply to you.
Leo's invented hours by row are 2, 1, 2, 2, 2 and 1, which is 10 hours, the 10 in his Step 4. Amara leaves the checklist blank, because she is not pricing a move.
One more fact from the pricing FAQ, relevant to leaving a paid plan later: you keep the paid plan until the next billing date, then the account reverts to the free plan. To downgrade to a lower paid plan, support can convert remaining days, or you cancel and re-upgrade after the revert. Read your tool's version before paying.
Step 6: Decide, test for thin evidence, set a date
Write one decision and a review date. The evidence is too thin if any of these is true:
- Short window. Under 30 days of counting, or you could not reconstruct 30 days.
- One-off. The whole cost came from a single event, such as a launch week.
- It flips. Halve your count, redo the comparison; if the answer changes, you cannot trust the count. Leo's count halved is 70 people: 70 x 3 = 210 minutes = 3.5 hours x $15 = $52.50, still above $17. His decision holds.
If too thin, write "too thin", stay by default, start a tally, put the review 30 days out and write the line that would move it earlier. Before you stay by default, compare one more month of staying (X hours at your hourly value) with the plan's $17, and say which you prefer and why.
If firm, use this rule (my judgement):
- No hit and none projected before the next two reviews: stay.
- A hit, a counted cost above the plan's price for the same period, and a plan row that lifts it: upgrade.
- A hit, but no plan of your tool lifts it, or the price is not worth it: compare C. Switch only if year one, with the one-off hours, beats B, or if your tool has no plan that does the job.
- A limit projected, not hit: stay, and move the review date earlier to a line you set, such as 90% of contacts.
Rule 4 is the one some readers will argue with. I'd still stay: paying early buys months of room you are not using, and the review date exists to catch the moment that stops being true.
Other reasons are allowed, if you label them. Free systeme.io emails carry a "Sent with systeme.io" line, which free users cannot remove; the help lists Startup, Webinar and Unlimited as plans that can [S18]. If you would not put that line under your name, write it on the sheet as a preference with its monthly price.
That is a legitimate reason to pay, but not a counted cost, so keep it on its own line.
Review date. A calendar date, not "later". Thirty days matches the evidence window. On it, redo Steps 1 to 4; if you upgraded, check the counted cost dropped. The weekly review guide is a good place to park the date.
Three finished sheets, all imaginary.
Case 1: Amara stays free.
UPGRADE-EVIDENCE SHEET Amara
(imaginary) Free read 25 Oct 2026
Hit: none yet
Projected: 1,640/2,000 = 82%;
360/35 = 10.3 months
Cost 30d: 0 people, 0 hours
A stay $0/mo, $0/yr
B Startup $17/mo, $204/yr
now = about $170 unused
C switch not priced (no hit)
Test: 30 days, not one-off,
nothing to flip. Firm.
DECISION: Stay free
REVIEW: 25 Nov 2026, or sooner
at 1,800 contacts (90%)
Open: what happens at 2,000
Case 2: Leo has an imaginary, confirmed reason to upgrade.
UPGRADE-EVIDENCE SHEET Leo
(imaginary) Free read 25 Oct 2026
Hit: rules (1 allowed);
pages 2, 3 have none
Tried: 2nd rule refused; one
rule for 3 pages: no
(invented reply); merge
rejected
Cost 30d: 140 people, 420 min = 7 h
Hour: $15 (his figure)
break-even about 23 people
A stay $105/mo, $1,260/yr
B Startup $17/mo, $204/yr
rules row on live page:
3 or more (invented)
C switch 10 h x $15 = $150;
yr 1 wins only under
$4.50/mo
Test: halved: 3.5 h = $52.50 >
$17. Holds.
DECISION: Upgrade
REVIEW: 30 days after upgrade;
hand-sent count back to 0
Open: cancel and downgrade terms
His decision rests on four things: a confirmed hit, a counted cost above break-even, a plan row that exists at a price the counted cost beats, and a result that survives halving. Remove any one and the sheet says "check first".
Case 3, in brief: Sam, too thin. Sam's list is three weeks old with 62 contacts, 62 / 2,000 = 3.1%, and no workaround notes. His sheet reads: hit none yet; cost not measured; decision "too thin: stay, start a tally"; review in 30 days.
If you want to upgrade although the test says "too thin", that is your call. Write what you are paying for, the monthly price and a review date. The sheet does not forbid a payment. It shows what the payment rests on.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| You cannot tell what counts as a contact | My sources do not define it | Write what your account shows; find the definition in its help |
| The plan row for your limit is blank | The page or table does not say | Ask the vendor in writing before paying |
| Nothing counted for 30 days | You were not logging | Mark not measured, decide "too thin", start the hit log |
Frequently asked questions
Is staying on the free plan a real answer? Yes. If no limit has cost you anything you can count, "stay free" is what the evidence gives.
Will a paid plan bring more subscribers or sales? Nothing in the pricing text says so; plans differ in limits and features. If your real question is where visitors come from, see Why Your Shop Isn't Growing.
Should I price a yearly plan? If the page shows a yearly price, use it and say so. I could not read it.
Your next step
Fill in the ledger and start the hit log today, even if the answer will be "none yet". If Step 4 stalled because you do not know what an hour or a sale is worth, Price Your Digital Product So It Actually Leaves Profit walks through profit per sale. For any other tool you are tempted by, run the five questions first.
Sources and checks
What I read, and when. On 25 October 2026 I read these systeme.io pages as saved text: the pricing page FAQ lines (S11), the email-footer help page (S18, updated 1 June 2026), the personal sender address help page (S17) and the deliverability guidelines (S20). The comparison table did not load as text, so the limits may be incomplete.
The Startup rule and campaign counts are unread. I did not log in to any account and tested nothing.
No other vendor. I fetched no other tool's page, so this guide states no other tool's price, feature or export behaviour.
Opinion, not fact. The decision rule, the word "hit", the "too thin" tests, the stay-while-projected view and the 90% line are my judgement. All arithmetic was recomputed with Python on 26 October 2026.
Unverified. What happens at 2,000 contacts; what counts as a contact; whether one rule or campaign can serve several pages; the Startup rule count; the annual price; whether anyone else has used the sheet.
- V01 The plan numbers in Step 1 match the live pricing page on the day a reader checks, including the comparison table whose numbers did not load as text (automation rules on Startup, any per-campaign limit, what happens at 2,000 contacts) [PENDING]
- V02 At least three real sellers on a free plan fill in the sheet from their own account and report which numbers they could not find [PENDING]
- V03 The switch-cost checklist is checked against the help pages of at least two other tools, including whether each exports sign-up date, source form and status [PENDING]
What this guide does not claim
That any plan is worth buying, that the plan limits will stay as read, that a paid plan raises sales, or that Amara, Leo or Sam exist or that their numbers are typical.