Hands-on setup test · Free plan
Systeme.io free plan: what we could actually build
The free account is enough to try a simple page and a contact pipeline. Our test does not yet establish that it can run your complete enquiry-to-client workflow.
For a solo consultant or small service business, the useful question is whether an enquiry can reach the right next step with little extra administration. A long list of features cannot answer that on its own. We opened a free account and tested a deliberately small part of that job on 27 September 2026.
Our verdict: a reasonable candidate for a small, no-payment setup trial. Keep your existing process until you have tested sender setup, permission-based contact capture and follow-up with your own requirements. Do not buy a larger plan just to reproduce the page and pipeline we built.
What we tested, and what we did not
| Check | Observed result | Limit of the finding |
|---|---|---|
| Free account | The account displayed Free as its current plan. | No paid subscription or payment-card setup was needed for our test. |
| Page builder | Created a custom funnel, added an information-page step, dragged in a text block, edited it and saved. | A minimal text page, not a designed sales funnel or a form test. |
| Public page | The saved text loaded on the supplied systeme.io subdomain. | Save made this page accessible by URL. Do not assume a saved example is private. |
| Narrow screen | At a 375-pixel viewport, the text wrapped without horizontal overflow. | One simple page and viewport, not a full accessibility or device audit. |
| Contact pipeline | Created and reopened six named stages. | No actual client or deal moved through those stages. |
| Fictional contact | The form rejected an address on the reserved .example domain because it lacked a valid MX or A DNS record. | The record was not saved. We did not import real customer data to get around this check. |
| Email campaign setup | The campaign form required a sender; our sender list was empty. Email settings also showed no verified email addresses. | Campaign not created. No sending, inbox-placement or delivery-speed test. |
The interface in our account was Russian-language, and page text was English. A setting label or displayed currency can depend on account context. It does not prove what every visitor will see or which currency their bank will receive.
The free limits we saw in the account
These are the limits displayed in our account on the test date, not promises that the limits will never change. We did not deliberately fill each allowance to test enforcement.
| Feature | Displayed Free allowance | Why it matters |
|---|---|---|
| Contacts | 2,000 | Check how your audience and existing records count before importing. |
| Funnels and steps | 3 funnels, 15 steps | A small prototype can fit; several distinct service journeys may use the allowance faster. |
| Email campaigns | 1 | Plan which sequence belongs in that campaign before building several independent journeys. |
| Automation rules / workflows | 1 rule / 1 workflow | Separate limits, not an unlimited automation allowance. We have not tested execution. |
| Contact pipelines | 1 | We could create six stages inside the one pipeline. |
| Custom domains | 1 | Our test used the included subdomain; custom-domain setup was not part of it. |
| Course students | 500 | Relevant if your service later includes a course. Course delivery was not tested. |
We also found inconsistencies between broad wording in the public pricing-page FAQ and its detailed table. For these figures we used the specific account allowances. Check your account and the current official pricing table before committing to a workflow or purchase.
The page-building test
We started with a custom funnel rather than importing a ready-made sales template. Its information-page step contained one text block describing a fictional consultation and clearly stated that no service, form, payment or mailing list was connected.
The basic sequence worked: create the funnel, add a step, open Configuration, choose Edit page, drag a text element into the canvas, edit it and save. In the narrow dashboard layout we had to open Configuration explicitly to reveal the page settings. We verified the saved result by opening its public address.
That establishes a working route from an empty page to a public text example. It does not establish that a multi-step form, a checkout, a booking calendar or a thank-you redirect works correctly. Those deserve separate tests before inviting real customers.
The pipeline is contact-based in the flow we used
We named the stages New inquiry, Contacted, Proposal sent, Negotiation, Won and Lost. The saved board offered Add contact in each stage. Creating a new contact required an email address; an intentionally non-deliverable example was rejected.
We did not establish whether the product can represent your full deal model, such as several opportunities per client, forecast values, separate owners or a detailed activity history. If these are essential, test them directly. A six-column board alone is not evidence that all of those needs are covered.
Email needs its own setup and test
Opening an account did not give our campaign form a verified sender. The sender dropdown was empty, and email settings listed no authenticated domains or verified email addresses. We stopped before creating a campaign or sending any message.
This is an unfinished account setup step, not a finding that the free plan cannot send email. Before relying on it, verify your sender, review domain authentication and test with an address whose owner has agreed to receive the test. Confirm subscription and unsubscribe behaviour as part of that workflow. We have no delivery-rate, spam-folder, open-rate or conversion results to report.
Who should try it first
- A solo service provider exploring one simple journey: start with a clearly labelled example page and a small pipeline. Check the limits against that job.
- A business with an existing customer process: trial the required steps alongside it before moving contacts, a live domain or payments.
- A team needing several separate pipelines or campaigns: the Free allowances above are a reason to map the workflow carefully before investing time.
A free subscription can still cost time: sender and domain setup, consent wording, page design, testing and later migration. Our test did not measure those costs or establish a return on investment.
A sensible next test before you buy
- Write down one enquiry journey and the fields you actually need.
- Build a clearly labelled page; check whether its URL is public after saving.
- Verify a sender and test a permitted signup with a consenting recipient.
- Check the form, confirmation, next-step page and unsubscribe path on phone and desktop.
- Test your one required automation, keeping payment actions out of the trial.
- Check export and deletion before importing a customer list.
We completed the page and pipeline setup checks described above. The remaining steps are a checklist for a further trial, not claimed test results.
Sources and scope
- Our authenticated Free-plan page, page editor, contact-pipeline flow, campaign form and email settings, observed 27 September 2026.
- Official pricing, consulted on the same date; account allowances are distinguished above.
- Terms and conditions and provider privacy policy.
This is a limited hands-on setup report, assisted by AI for browser operation, drafting and structure. It is not a long-term use review, performance benchmark, security audit or claim of increased sales. No star rating has been assigned.