An off-the-shelf mailing system from an external vendor runs on a subscription model, where the fee is charged for the size of the contact database or the number of messages sent, while the address list itself is stored on the vendor's servers. The entry threshold tends to be low, which makes the decision seem cheap and reversible. Over a horizon of several years, however, the math looks different: the cost grows with every contact added to the database, regardless of whether the company actually writes to them, and as the list grows, the fee rises disproportionately to actual use.
The analysis below is based on the current pricing of popular mailing systems — the Polish GetResponse and the international Mailchimp, ActiveCampaign, and Brevo — as of June 2026. It shows what off-the-shelf mailing really costs in PLN and USD, where the cost invisible in the price list shows up, and what alternative a mailing system built as a company-owned tool represents. The thesis of the whole piece is this: for a B2B company growing its own recipient base, a long-term commitment to subscription mailing is a costly decision that is hard to reverse, because the fee is charged simply for holding contacts, not for the value communication brings to the company.
How a subscription mailing system works and what it charges for
Subscription mailing is software delivered as SaaS — the company doesn't buy the system but rents access to it, paying a recurring fee that depends on the size of the database or the volume of sends. The system runs in the vendor's cloud, and the address list, recipient activity history, and automation scenarios are stored on its infrastructure.
This model produces three constant traits that recur in the pricing of leading systems — Polish and foreign alike. The billing unit is a contact or a sent message, so the total cost depends directly on the size of the database or the number of sends, not on the effect of the communication. Advanced features, such as multi-step automation or dynamic personalization, are split across package tiers and require upgrading to a more expensive plan. The address list, together with its entire activity history, stays with the vendor, and sender reputation — which determines deliverability — is built on the vendor's shared infrastructure. Each of these traits sounds neutral on its own. Combined and multiplied by time and the pace at which the database grows, they produce a bill that rarely resembles the original offer.
What off-the-shelf mailing really costs in 2026
The real cost of off-the-shelf mailing for a B2B company on a working plan doesn't depend on a single number, but on the billing unit the vendor has adopted and the currency it bills in. The table below compares five systems as of June 2026 — the amounts are net prices and change over time.
| System |
Billing model |
Working B2B plan |
At a larger database |
Billing currency |
| GetResponse (PL) |
per contact + plan |
Marketer from ~PLN 239/mo (~USD 65) |
~PLN 2,499/mo (~USD 685) at 50,000 contacts |
PLN — no currency risk |
| MailerLite (PL/Vercom) |
per contact |
~PLN 149/mo (~USD 41) at 5,000 contacts |
grows with the database |
PLN — no currency risk |
| Mailchimp |
per contact (including unsubscribed) |
Standard ~USD 100–135 at 5,000–10,000 (~PLN 365–490) |
USD 270 (~PLN 985) at 25,000 contacts |
USD — currency risk |
| ActiveCampaign |
per contact |
Plus from ~USD 49 (~PLN 180) / Pro from ~USD 79–99 |
~USD 1,000 (~PLN 3,650) at 50,000 contacts |
USD — currency risk |
| Brevo |
per send (unlimited contacts) |
~USD 19 (~PLN 70) for 20,000 sends |
grows with sends, not the database |
EUR/USD — currency risk |
Net prices, as of June 2026. Currency conversion at a rate of approx. PLN 3.68/USD — exchange rates fluctuate, so with vendors billing in USD or EUR, the PLN cost also moves independently of the company.
GetResponse. This Polish platform with global reach bills in PLN and provides support in Polish. The entry-level Email Marketing plan starts at PLN 59 per month for a thousand contacts, but the real working plan for a B2B company is Marketer, from PLN 239, or about USD 65, which is the plan that actually opens up access to automation and sales funnels. The price grows with the database: at fifty thousand contacts, the pricing calculator shows PLN 2,499 per month. The fee is charged per contact, including a case where the same address ends up on two lists and gets counted twice. The model here is identical to that of foreign vendors — what differs is the billing currency, not the rental logic itself.
Mailchimp. This system bills in USD, based on the number of contacts in the database and the selected plan. Essentials starts at about USD 13 per month for 500 contacts, but lacks multi-step automation, so the real working plan is Standard — from about USD 20 at the smallest database size, about USD 60 at 2,500 contacts, and about USD 100–135, or PLN 365–490, at 5,000–10,000. The send limit is ten times the number of contacts. The fee is charged for all addresses in the account, including inactive and unsubscribed people, until they're manually archived, which means the bill can run ten to twenty percent higher than the actual number of recipients the company writes to. In 2026, the vendor changed its terms twice: in January it lowered the free plan's limits, and in April it raised prices on some accounts by eleven to thirteen percent.
ActiveCampaign. This system also bills per contact, in USD. The Starter plan starts at about USD 15 for a thousand contacts, but limits the number of actions in a single automation, so the real choice for a B2B company is Plus from about USD 49 (about PLN 180) or Pro from USD 79–99, also at a thousand contacts. The price rises steeply above five to ten thousand contacts: a plan that costs several dozen dollars at a thousand contacts reaches about a thousand dollars a month at fifty thousand, or more than PLN 3,600. On top of that come paid add-ons — the CRM module, SMS, reporting, and additional users — which push the real bill thirty to fifty percent above the list price.
Brevo. This system uses a different model: it charges for the number of messages sent, not for the size of the database. The number of contacts is unlimited, and plans are priced according to monthly send volume — about USD 9 for 5,000 messages, USD 19 (about PLN 70) for 20,000, USD 29 for 40,000, and USD 69 for 100,000. For a company with a large database and a moderate communication frequency, this model can be many times cheaper than per-contact billing. Comparing it with the other systems reveals something more important than the amount itself: in the subscription model, the size of the bill depends not on the value of the communication, but on the vendor's arbitrarily chosen billing unit.
The scale of the cost only becomes clear once the per-contact model is projected onto a database that grows along with the company. A list of 2,500 addresses today reaches 10,000–25,000 after a few years of B2B marketing and sales activity. On the Mailchimp Standard plan, that means the annual cost rising from about PLN 2,600 (USD 720) to nearly PLN 12,000 (USD 3,240) — for the same number of campaigns and the same content. The company pays more not because it communicates more intensively, but because its database has grown.
| Number of contacts |
Mailchimp Standard (annual cost) |
| 500 |
PLN 876 (~USD 240) |
| 2,500 |
PLN 2,628 (~USD 720) |
| 5,000 |
PLN 4,380 (~USD 1,200) |
| 10,000 |
PLN 5,913 (~USD 1,620) |
| 25,000 |
PLN 11,826 (~USD 3,240) |
Chart caption: the cost grows with the size of the database, not with the number of campaigns sent or the effect of the communication. Mailchimp bills in USD, so the PLN cost also fluctuates with the exchange rate. Standard plan license only, annual billing; converted at approx. PLN 3.68/USD, as of June 2026.
What the company pays for, and what it can't use
The per-contact model has a trait invisible in the price list: the company also pays for addresses it doesn't write to, and can no longer write to. Mailchimp charges for all contacts in the account, including people who have unsubscribed or stopped responding long ago, until they're manually archived. GetResponse charges for the same contact twice if it appears on two lists. The older the database, the heavier its ballast — inactive, duplicated, and unsubscribed addresses push up the price threshold without adding any value.
A cost emerges for simply storing data that's already useless to the company, and its scale grows over time. The address database naturally expands, but the share of recipients who actually respond to a send tends to shrink. Under a per-contact billing model, these two trends work together against the company: the bill grows with the entire list, while the real value of the communication concentrates in an ever-smaller, active part of it.
A Polish vendor removes currency risk, not the rental model
Choosing a Polish vendor is sometimes presented as the answer to the shortcomings of foreign platforms. In reality it solves only part of the problem. GetResponse and MailerLite bill in PLN, so the bill doesn't move with the dollar or euro exchange rate. That's a real benefit, because Mailchimp, ActiveCampaign, and some other vendors bill Polish customers in a foreign currency — so on top of the cost growing with the database, there's exchange-rate fluctuation the company has no influence over at all. PLN billing removes that one factor.
The other traits of the model, however, stay the same. The fee is charged per contact and grows with the database, the list and activity history are stored on the vendor's infrastructure, and advanced features require a more expensive package. The system's Polish origin doesn't change the fact that the company is renting access to someone else's software and handing over its own database to it.
A vendor's domestic address doesn't protect against its decisions, either. The fate of FreshMail shows this — a Polish mailing platform that companies across the country relied on for years. After merging with MailerLite, its application was shut down at the end of February 2025, and all customers faced the need to migrate their database to another tool by a set deadline or lose their data. The new tool ran on separate infrastructure, so existing plans and configurations couldn't be carried over unchanged. Companies that kept their database and communication processes in the rented system didn't choose that migration — they carried it out because the platform owner's decision forced it on them.
The same risk applies to every subscription vendor, regardless of country of origin. As long as the database and communication logic sit in someone else's system, decisions about its future — a pricing change, a feature being dropped, a merger, a service shutdown — become the company's problem and the company's timeline to execute. An in-house system doesn't eliminate this risk entirely, but it shifts control over it to the company: it decides on maintenance, any migration, and the direction of development.
The cost you don't see in the price list
The most serious cost of off-the-shelf mailing never appears on the invoice. It's dependence on a single platform and the lack of full control over the company's own database and sender reputation. It's this layer that turns a pricing decision into a strategic one.
The address list, segments, templates, and automation scenarios are created within a structure imposed by the vendor and run on its infrastructure. Sender reputation — which determines whether messages land in the inbox — is built on the vendor's shared IP addresses and stays outside the company's control. Migrating to another system carries over the address list itself, but not the automation scenarios, recipient activity history, or the reputation built up over time, which means a separate technical project carrying the risk of losing part of what's been built. This difficulty of exit is a feature of the model, not a side effect of it: the more of its communication process a company places in the system, the higher the cost of switching, and the more locked in it becomes.
The result is a situation where the recipient database and its activity history — an asset that constitutes a real advantage in B2B communication — remains stored on an external party's infrastructure, under terms the vendor imposes. The company has no full control over where this data is stored, nor over the reputation that determines the effectiveness of every send.
Data as a strategic asset in the age of AI
The subscriber database, together with the history of their behavior — which links they clicked, when they opened messages, what they responded to — is fuel for a company's own AI tools: content personalization, segmentation, and predicting the response to the next send. The longer this data is collected, and the closer it reaches to purchase decisions, the more accurately the models built on it perform. This advantage can't be bought or copied — it only grows inside the company's own infrastructure, and belongs to it throughout that entire time.
Seen this way, the decision about where recipient data is stored stops being a technical question. Entrusting it to an external vendor's servers means that an asset of growing strategic importance stays outside the company's control, on the terms of a party whose business model depends on maintaining that dependency.
The conclusion for a company planning its growth concerns direction, not a specific form. Recipient data is worth treating as an asset that should stay independent of external vendors and sit on infrastructure the company controls. The goal isn't to abandon AI tools in communication. The goal is to build them around the company's own data, instead of handing over data in exchange for access to someone else's tools.
What changed the math: a lower barrier to building software
The case for building an in-house mailing system would have sounded irrational just two years ago. Building a dedicated tool from scratch meant a long development project, a high cost for the development team, and a timeline measured in months. For most B2B companies, renting off-the-shelf mailing was the only sensible answer back then, and the subscription was the price for avoiding that risk.
AI tools that support software development have changed this math. Coding assistants built on large language models shorten application build times many times over, shifting a large share of the work from manual coding to design, validation, and integration. An area that used to require a multi-person team and a multi-month schedule is now delivered by a smaller team in a fraction of that time. The barrier to building a dedicated mailing system — matched to the company's actual communication process, not to a ready-made platform's framework — has dropped enough that, for a growing number of businesses, it has stopped being an obstacle.
This shift has a second layer. The same AI tools that speed up building the system also become a built-in feature of it. A dedicated mailing system gets built faster thanks to AI used as a development tool, and at the same time it contains AI running in day-to-day operation — for instance in recipient segmentation, content selection, and picking the right moment to send. As a result, the cost-and-time argument that spoke against building an in-house system for years has, in large part, stopped holding true.
The alternative: a mailing system the company owns
The alternative to a subscription is a dedicated mailing system built as a company-owned tool, matched to the company's way of communicating and running on its own infrastructure. The address list, segments, and automation scenarios belong to the company and integrate with its other data and tools. The actual sending goes through a specialized mail-delivery service, billed for messages actually sent, at a cost close to the technical one, rather than for the number of contacts stored. A built-in AI layer handles segmentation, content selection, and analysis of recipient responses.
The difference is structural, not cosmetic. Under the subscription model, the company bears a cost that grows with the entire database, regardless of whether a given contact is active or whether the communication has any effect. Under the dedicated model, the company bears the cost of building a system that then belongs to it — with no fee for stored contacts and no bill that grows with the size of the list. The first model is renting someone else's copy of your own database. The second is an investment in an asset that stays with the company.
Fairness requires stating this plainly: a dedicated system isn't free. It comes with a build cost, ongoing maintenance, and a fee for the sending infrastructure, billed per message sent. The point of this decision isn't that the company stops paying, but what it pays for and what it gets in return. Instead of a growing fee for merely storing contacts in someone else's system, the company funds the creation of its own tool, one whose cost doesn't grow with the size of the database and whose data, list, and logic stay under its control. That such a system can be built is demonstrated by working web applications created this way — dedicated tools with their own back end, maintained as company systems rather than extensions of off-the-shelf platforms.
When off-the-shelf mailing is enough, and when your own system pays off
An off-the-shelf mailing system is a rational choice under specific conditions, and this article doesn't claim otherwise. It works well when the database is small and stable, when needs are limited to simple campaigns that fit within a ready-made framework, when a fast start without a build phase matters, and when the company doesn't treat where its database is stored or control over sender reputation as a strategic issue. For an organization like that, a subscription can be the simplest and sufficient answer, and a Polish vendor billing in PLN is a sensible choice in that scenario.
The math reverses when at least one of the following conditions is met. The database is growing, so the per-contact model starts working against the company, and an ever-larger share of the bill consists of inactive addresses. Communication requires unusual scenarios whose accommodation means constantly working around a ready-made tool's limitations. Recipient data is sensitive material, and where it's stored is subject to legal requirements or security policy. The system needs to be integrated with the CRM, sales data, and the company's other tools as part of a coherent ecosystem. The decision horizon spans several years, and the cost summed over that time exceeds the cost of building an in-house solution. In these situations, a dedicated mailing system stops being the more expensive option and becomes the cheaper and safer one over the long run.
Don't rent the channel that belongs to you
Subscription mailing — regardless of whether the vendor is Polish or foreign — tempts with a low entry threshold, but over a horizon of several years it reveals three costs: a fee that grows with the database and is also charged for inactive and unsubscribed contacts, features split across ever more expensive packages, and dependence on a platform where the company's list and sender reputation get locked in. Choosing a Polish system like GetResponse removes the currency risk present with vendors billing in USD or EUR, but leaves the rental model itself untouched. The most serious cost concerns data: in an age of AI's growing role, the recipient database and its behavioral history remain a valuable company asset, and the subscription model keeps them outside the company's control while basing its revenue on the difficulty of leaving. For a B2B company whose database is growing, the sum of these costs turns a seemingly cheap decision into a costly commitment that's hard to reverse.
A dedicated mailing system built as a company-owned tool reverses this logic. The build cost replaces a fee that grows with the database, the list and recipient data stay on the company's infrastructure, and the system mirrors its real way of communicating instead of forcing it to fit someone else's framework. A full description of this approach and the other dedicated web applications is available at artechconsult.com/solutions. The starting point for a conversation about an in-house system is a free consultation.
The prices cited in this article come from official vendor price lists and independent pricing analyses as of June 2026; they are net prices and change over time. Billing models differ in unit — contact or message sent — so a direct comparison of amounts requires reference to a specific database size and send volume. Amounts are given in each vendor's billing currency, with the PLN equivalent converted at approx. PLN 3.68/USD; for vendors billing in USD or EUR, the PLN cost additionally depends on the current exchange rate. The FreshMail example refers to that platform's shutdown at the end of February 2025 following its merger with MailerLite.
