Quick answer

Use the free plan to prove one complete path: landing page → form or order step → follow-up email. Keep the first workflow simple and confirm the current automation allowance in your account; the supplied capture is not a guarantee of today’s limits.

Starting planFree ($0)
First assetOne funnel
Email choiceVisual or classic editor
Automation budget1 rule

Best for: A solo operator validating a small offer, lead magnet, or course funnel.

Think twice if: You need to migrate a complex production stack or handle live payments without a full test plan.

Key limit: This walkthrough intentionally stops before payment setup, sending to real contacts, or publishing a live domain.

Plan evidence update · September 6, 2026

The supplied screen shows one Free automation rule and paid-plan funnel caps. The current official pricing FAQ instead describes unlimited funnels on paid plans and does not confirm that automation-rule limit. Treat the captured allowances below as a dated record, not confirmed current restrictions. Check the official plan details before upgrading for a limit.

01

1. Define one outcome and create its funnel steps

Choose a single outcome, such as collecting a permissioned lead or explaining one product. Create only the steps needed for that route.

EvidenceWhich step should come next in the first funnel?
systeme.io funnel step type selector with sales and checkout-related options
The builder separates sales pages, order forms, upsells, downsells, and thank-you pages. English UI · supplied capture reviewed Sep 6, 2026.
02

2. Build the page around one action

The page editor combines elements and reusable blocks. Keep the first page focused on one action and preview it at mobile width before using it with real traffic.

EvidenceCan the page be edited visually without separate design software?
systeme.io visual page editor with text, media, and column elements next to a page canvas
The visual editor exposes elements and blocks alongside the live page canvas. English UI · supplied capture reviewed Sep 6, 2026.
03

3. Choose an email editing mode

Select the visual editor when layout matters or the classic editor for a simpler message. Treat templates as starting structures and replace all sample brands, copy, links, and images before any send.

EvidenceWhat editing choice appears before writing the newsletter?
systeme.io newsletter setup showing visual and classic editor choices with template thumbnails
Template selection is evidence for the editor choice; sample template content is not a user endorsement. English UI · supplied capture reviewed Sep 6, 2026.
04

4. Spend the single free automation rule carefully

Choose the event that matters most, then the smallest useful action. For a first funnel, that may be a form subscription followed by adding a tag or subscribing the contact to a campaign.

EvidenceWhich user event can start an automation?
systeme.io automation trigger menu with tag, form, campaign, and webinar events
Available trigger types include tag changes and several form-submission events. English UI · supplied capture reviewed Sep 6, 2026.
EvidenceWhat can happen after the trigger?
systeme.io automation action menu with campaign, tag, email, and course actions
The action list includes campaign subscription, tags, email, and course access changes. English UI · supplied capture reviewed Sep 6, 2026.
05

Pros and limitations

What works

  • One account covers the first funnel, page, email, and rule
  • The visual editor makes the page structure visible
  • Free limits encourage a small first experiment

What to watch

  • Sample templates require careful cleanup
  • The broad interface can invite scope creep
  • Current automation allowances need account verification
06

Who this route fits—and who should skip it

Good fit

You can test one offer end to end

You are comfortable keeping the first automation simple

You will verify consent, links, and mobile layout before any real send

Probably not

You need a high-risk production migration

You want several workflows on the free tier

You need specialist functionality beyond an all-in-one starter stack

Sources and scope

Assessment of English UI captures supplied for this project, reviewed on September 6, 2026. A visible control establishes interface availability, not completed end-to-end performance. Screenshots were reviewed for visible names, email addresses, account identifiers, domains, and other account-specific information before use.

Editorial scope: no purchase, live campaign send, payment setup, domain publication, or external posting was performed for this guide.