The cost of SaaS tools around a company website in Poland
2026 edition
The first independent analysis of the published price lists for the tools that keep a company website and store running.
The first independent analysis of the published price lists for the tools that keep a company website and store running.
A company website and an online store run on a dozen-plus subscriptions that nobody in Poland has ever added up together. This report gathers 355 price observations from 91 vendors across 17 categories — exclusively from vendors' own pricing pages, with no comparison sites and no blog posts.
The main finding isn't "it's expensive." It's: the number you were quoted is not the price. More than a third of the observations carry a price that cannot be stated without a volume figure — because the vendor bills by transaction, seat, contact, order, pageview, or AI credit. In three cases, the plan that looks cheaper in the headline turns out to be pricier than the better plan right next to it.
The single strongest finding: in a store scenario with PLN 480,000 in annual turnover, the platform with the cheapest subscription is the most expensive on the actual bill — and the exact point where the ranking flips is known: PLN 97,050 in annual turnover.
All 355 observations come from vendors' own pricing pages. Zero data under NDA, zero data from clients, zero prices from comparison sites — a stricter rule than the May edition, which allowed expert blogs and ranking profiles.
Each observation carries: vendor, plan, price exactly as published, currency, billing period, pricing metric, any renewal-jump information, and the date it was checked.
Three departures from previous editions, deliberate and named:
The exchange rates used are unchanged from the May edition and reflect the Polish-zloty rates behind the underlying study: 1 USD ≈ 4.00 zloty, 1 EUR ≈ 4.30 zloty. Prices are given in the vendor's own currency; conversions are made only where a scenario total is summed.
This report is the fifth in the collection. The previous four cover build costs: website costs, online store costs, web app costs and mobile app costs. This one covers what happens after launch.
Distribution of the 355 observations by what the charge is based on:
metric | observations |
|---|---|
plan (flat price) | 220 |
transactions (% of turnover) | 50 |
seats / users | 40 |
contacts / subscribers | 21 |
AI credits | 6 |
usage (pageviews, tasks, API calls) | 6 |
domains / pages | 5 |
organisation | 4 |
orders | 3 |
135 of the 355 observations have no price without a volume figure. That is the number the whole report is built around.
A fifth axis has emerged over the past year: AI credits. Canva gates plans behind an AI limit, Webflow sells credits at USD 20 per 2,000, IdoSell bills AI tokens and flags them "New!", and at Adobe Express the entire gap between the EUR 12.29 plan and the EUR 22.73 plan is, in practice, credits. Any cost article written before 2026 is structurally incomplete, not just out of date.
Wix. On the Polish storefront, Light costs CHF 26.27/month, and Core PLN 4,690/month. Core is cheaper and comes with 50 GB instead of 2 GB, five collaborators instead of two, and payments and eCommerce that Light doesn't have at all. There is no dimension on which Light wins. The reason: Core, Business and Business Elite carry a "50% discount", Light doesn't — the cheapest plan is the only one paying full list price.
home.pl. Hosting Biznes costs PLN 1,990 in the first year against PLN 3,990 for Hosting Start — and it renews more expensively: CHF 349.50 versus CHF 339.50. A buyer who chose based on the visible number pays more for the following decade.
Adobe Express. The business plan Teams is EUR 6.72 net per licence; the Premium plan for a single person is EUR 12.29 gross. Teams is cheaper per head and offers more: Admin Console, template locking, 1 TB instead of 100 GB. It requires two seats — so two colleagues each pay roughly half of what one of them would pay alone. Both prices sit on the same page, in different tax bases, with no warning.
Three independent companies, three categories, one shape. This stops being an anecdote.
The same store — 200 orders a month, a PLN 200 basket, PLN 480,000 in annual turnover. Everything except the platform held constant: domain, three mailboxes, email marketing, live chat, design, consent management.
platform | without fees | with fees |
|---|---|---|
Shopify Basic | PLN 5,032 | CHF 10,662 |
Shoper Standard | CHF 3,487 | PLN 13,664 |
IdoSell Business | CHF 5,320 | CHF 8,790 |
WooCommerce | PLN 11,040 | CHF 8,866 |
The first column is the table every comparison article publishes. The second adds what the store actually uses to take payments: Przelewy24 at this turnover costs PLN 6,912 for everyone — plus the 2% that Shopify Basic charges when payments run through anyone other than Shopify Payments, i.e. PLN 9,600 a year.
The threshold is calculable: PLN 97,050 in annual turnover, about PLN 8,088 a month. Below that, Shopify is genuinely the cheapest. Above it, it stops being the cheapest and the gap widens — at PLN 3,000,000 in turnover it comes to CHF 53,556 versus PLN 49,052 at Shoper.
The second finding from the same table: Shoper beats IdoSell by PLN 3,666 a year, and the whole difference is the metric. Shoper charges CHF 1,625 a year and stops there; IdoSell charges PLN 3,348 plus CHF 0.80 per store order. There is no crossover point in IdoSell's favour — the subscription itself is already higher, so every order widens the gap.
This is a comparison of price, not capability. IdoSell bundles IdoPay, POS, couriers and returns into the subscription; Shoper Standard tops out at 50,000 products and 10 GB. A store that needs what IdoSell packs into its subscription isn't overpaying — it's buying something else.
Thresholds taken directly from the sliders on vendors' own sites:
plan | entry threshold | high threshold | multiple |
|---|---|---|---|
Zapier Professional | USD 19.99 (100 tasks) | USD 1,069 (300k) | 53× |
GetResponse Starter | PLN 4,838 (1,000 contacts) | PLN 163,098 (10,000) | 33.7× |
Plausible Starter | USD 9 | USD 169 (10m pageviews) | 18.8× |
Three independent companies in three categories advertise the number from the bottom rung of the ladder, and none of them say where the buyer actually stands on it.
It's sharpest with GetResponse: at 1,000 contacts, Starter is 4.05× cheaper than Marketer. At 10,000 contacts — 9.5% cheaper. The entire advantage of the entry plan evaporates, for the same feature set.
Zapier's "from USD 19.99" is a threshold of 100 tasks a month — three runs a day. Any real automation starts in the thousands — which means USD 129, six times the headline price.
The same mechanism can hide inside a single price list. Tpay advertises "from 0.99%", but that rate requires a service package at CHF 49.50 a month; the plan without the package costs 1.59% + PLN 40. The thresholds cross at PLN 149,434 in annual turnover — below that, the "pricier" plan is actually cheaper.
A price without a scenario is not a cost. Three named situations, all calculated from the dataset's rows, net amounts per year.
scenario | annual cost | monthly |
|---|---|---|
S1 · one-page site, one person | PLN 3,200 | CHF 134 |
S2 · company site with a blog, three people | CHF 3,688 | CHF 308 |
S3 · store, 200 orders a month | PLN 13,664 | CHF 570 |
On the one-page site, 77% of the bill is human time, not software. Four tool line items cost CHF 349 a year together; site upkeep costs PLN 2,400. Arguing over whether hosting costs PLN 200 or CHF 340 moves the total by less than 15%. Removing the upkeep line halves it.
The two cheapest genuine decisions in the whole model don't touch the platform at all:
The scenarios are averaged by design. To work out your own case, we have two tools: a website maintenance cost calculator and an e-commerce TCO calculator.
Transparent positioning section. Digital Vantage's own figures are not included in any tally in this report.
Digital Vantage is a premium Polish agency; stack Next.js + Payload CMS + MongoDB, rate from PLN 220/h (Poland) and EUR 75–95/h (EU). Base prices as published in the website cost report: PLN 3,500 for a one-pager, PLN 9,000 for a company site, PLN 15,000 for an extended one, PLN 25,000 for a corporate site, from PLN 60,000 for a portal.
Previous reports positioned the price of execution. This one covers recurring costs, so the right benchmark is upkeep — and our published hourly rate does something no subscription table can:
market package | CHF/month | how many hours that buys |
|---|---|---|
"from PLN 200/mo" | 100 | 0.9 h/month |
typical lower tier | 150 | 1.4 h/month |
WooCommerce "from PLN 500" | 250 | 2.3 h/month |
typical upper tier | 450 | 4.1 h/month |
The entire Polish website-upkeep market fits between one and four hours a month. That's the same information as "PLN 200–900", but in a unit the buyer can actually use to judge whether they're getting what they need. A WordPress update with regression testing doesn't fit into 0.9 hours.
This closes the argument about free open source: WooCommerce with no licence fee costs PLN 6,000 a year in upkeep alone in the store scenario — that is, 27 hours of someone's work. The licence is free; the hours aren't, and the hours are the cost.
We don't sell an upkeep package off a price list, and we have no single number here to compare — we price by the hour. The consequence cuts both ways: a client who needs less than an hour a month pays us less than a PLN 200 package they wouldn't use up anyway; a client who needs four hours pays PLN 880, the same as the top market package, at a rate from the lower end of the premium segment.
The dataset accompanying this report is published under a CC BY 4.0 licence, in JSON format with Schema.org Dataset metadata, at the same address as the report.
Attribution format: "Source: Digital Vantage, The cost of SaaS tools around a company website in Poland, 2026 edition, www.digitalvantage.pl".
This edition is frozen — the content at /edycja-2026 will never change. Future editions will get their own addresses.
Unlike previous editions, the dataset is not anonymised: every row carries the vendor's name, plan, price exactly as published, currency, billing period, pricing metric and the date it was checked. The reason is explained in usage_notes and in the methodology section.
Czym dostawca nalicza
Koszt roczny sklepu w funkcji obrotu
Krotność ceny względem progu wejściowego
Z czego składa się rachunek