The cost of SaaS tools around a business website in Poland
2026 edition
The first independent analysis of the published price lists for the tools that keep a business website and store running.
The first independent analysis of the published price lists for the tools that keep a business website and store running.
A company website and an online store rest on more than a dozen subscriptions that nobody in Poland has ever added up together. This report collects 355 price observations from 91 providers across 17 categories — sourced 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 figure you were quoted is not the price. More than a third of the observations carry a price that cannot be stated without knowing the volume — because the provider bills by transaction, seat, contact, order, page view, or AI credit. In three cases, the plan that looks cheaper in the headline turns out to be more expensive than the better plan right next to it.
The single strongest finding: in a store scenario with PLN 480,000 in annual revenue, the platform with the cheapest subscription is the most expensive on the bill — and the exact line where this flips is known: PLN 97,050 in annual revenue.
All 355 observations come from providers' own pricing pages. Zero data under NDA, zero data from clients, zero prices from comparison sites — a stricter rule than in the May edition, which allowed expert blogs and ranking profiles.
Each observation carries: the provider, the plan, the price exactly as published, the currency, the billing period, the pricing metric, information about a renewal jump, and the date checked.
Three departures from previous editions, deliberate and named:
Exchange rates applied, the same as in the May edition: 1 USD = 4.00 PLN, 1 EUR = 4.30 PLN. Prices are given in the provider's own currency; conversions are made only where we total up a scenario.
This report is the fifth in the collection. The four earlier ones cover the cost of delivery: website costs, online store costs, web application costs, and mobile application costs. This one covers what happens after launch.
Breakdown of the 355 observations by what the charge is based on:
metric | observations |
|---|---|
plan (flat price) | 220 |
transactions (% of revenue) | 50 |
seats / users | 40 |
contacts / subscribers | 21 |
AI credits | 6 |
usage (page views, tasks, API) | 6 |
domains / pages | 5 |
organization | 4 |
orders | 3 |
135 of the 355 observations have no price without volume. That's the number this entire report is built around.
A fifth axis 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 difference between the plan at EUR 12.29 and EUR 22.73 comes down, in practice, to credits. Any cost article written before 2026 is structurally incomplete, not just outdated.
Wix. On the Polish storefront, Light costs PLN 52.53/mo and Core costs PLN 46.90/mo. Core is cheaper and comes with 50 GB instead of 2 GB, five collaborators instead of two, payments and eCommerce that Light doesn't have at all. There's no dimension where Light wins. The reason: Core, Business, and Business Elite carry a "50% discount," Light doesn't — the cheapest plan is the only one paying list price.
home.pl. The Biznes hosting plan costs PLN 19.90 in the first year against PLN 39.90 for the Start hosting plan — and it renews more expensively: PLN 698.99 versus PLN 678.99. A buyer who chose based on the visible number pays more for the next decade.
Adobe Express. The business plan Teams costs EUR 6.72 net per license; the Premium plan for a single person costs EUR 12.29 gross. Teams is cheaper per head and includes 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 pattern. This stops being an anecdote.
The same store — 200 orders a month, a PLN 200 basket, PLN 480,000 in annual revenue. Everything except the platform held constant: domain, three mailboxes, email marketing, live chat, graphic design, consent management.
platform | without fees | with fees |
|---|---|---|
Shopify Basic | 5,032 | 21,323 |
Shoper Standard | 6,973 | 13,664 |
IdoSell Business | 10,639 | 17,579 |
WooCommerce | 11,040 | 17,731 |
The first column is the table every comparison article publishes. The second adds what the store actually uses to take payments: Przelewy24 at this revenue level 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 revenue, about PLN 8,088 a month. Below it, Shopify is genuinely the cheapest. Above it, it stops being the cheapest and the gap widens — at PLN 3,000,000 in revenue it's PLN 107,111 versus PLN 49,052 at Shoper.
The second finding from the same table: Shoper beats IdoSell by PLN 3,666 a year, and the entire difference is the metric. Shoper charges PLN 3,249 a year and that's it; IdoSell charges PLN 3,348 plus PLN 1.59 per store order. There's no crossover point in IdoSell's favor — the subscription itself is 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 different.
Thresholds taken directly from the sliders on providers' websites:
plan | entry threshold | high threshold | multiple |
|---|---|---|---|
Zapier Professional | USD 19.99 (100 tasks) | USD 1,069 (300k) | 53× |
GetResponse Starter | PLN 48.38 (1,000 contacts) | PLN 1,630.98 (10,000) | 33.7× |
Plausible Starter | USD 9 | USD 169 (10M page views) | 18.8× |
Three independent companies in three categories advertise the number at the low end of the ladder, and none of them say where the buyer actually stands on it.
With GetResponse it's sharpest: 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, with the same feature set.
Zapier's "from USD 19.99" is a threshold of 100 tasks a month, i.e. three runs a day. Any real automation starts in the thousands — i.e. at USD 129, six times the headline price.
The same mechanism sometimes hides inside a single price list. Tpay advertises "from 0.99%," but that rate requires a service package at PLN 99 a month; the plan without the package costs 1.59% + PLN 0.39. The thresholds cross at PLN 149,434 in annual revenue — below that, the "more expensive" plan is actually cheaper.
A price without a scenario isn't a cost. Three named situations, all calculated from the dataset's rows, net amounts per year.
scenario | annual cost | monthly |
|---|---|---|
S1 · single-page site, one person | PLN 3,200 | PLN 267 |
S2 · business site with a blog, three people | PLN 7,375 | PLN 615 |
S3 · store, 200 orders a month | PLN 13,664 | PLN 1,139 |
In a single-page site, 77% of the bill is human time, not software. Four tool line items cost PLN 697 a year combined; site care costs PLN 2,400. Whether hosting costs PLN 199 or PLN 679 moves the total by less than 15%. Removing the care line halves it.
Two of the cheapest real decisions in the whole model have nothing to do with the platform:
Scenarios are averaged by design. To calculate your own case, we have two tools: website maintenance cost calculator and e-commerce TCO calculator.
A transparent-positioning section. Digital Vantage's figures are not included in any tally in this report.
Digital Vantage is a premium Polish agency; a Next.js + Payload CMS + MongoDB stack, rates from PLN 220/h (Poland) and EUR 75–95/h (EU). Base prices published in the website cost report: PLN 3,500 for a single-page site, PLN 9,000 for a business site, PLN 15,000 for an expanded site, PLN 25,000 for a corporate site, from PLN 60,000 for a portal.
The earlier reports positioned the price of delivery. This one covers recurring costs, so the right benchmark is care — and our published hourly rate does something no subscription-plan table can:
market package | PLN/mo | how many hours that is |
|---|---|---|
"from PLN 200/mo" | 200 | 0.9 h/mo |
typical low end | 300 | 1.4 h/mo |
WooCommerce "from PLN 500" | 500 | 2.3 h/mo |
typical high end | 900 | 4.1 h/mo |
The entire Polish website-care market fits between one and four hours a month. That's the same information as "PLN 200–900," but in a unit where the buyer can judge whether they're getting what they need. A WordPress update with regression testing doesn't fit in 0.9 hours.
This closes the argument about free open source: WooCommerce with no license fee costs, in the store scenario, PLN 6,000 a year in care alone — that's 27 hours of someone's work. The license is free; the hours aren't, and the hours are the cost.
We don't sell a care subscription off a price list, and we don't have a 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 will pay us less than for the PLN 200 package they wouldn't use anyway; a client who needs four hours will pay 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 license, 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 Business Website in Poland, 2026 edition, www.digitalvantage.pl".
The 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 anonymized: every row carries the provider's name, the plan, the price exactly as published, the currency, the billing period, the pricing metric, and the date checked. The reason is described 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