What a clinic website really costs in 2026: four tiers and what you actually buy

You open your inbox and find three offers for a new clinic website. The first costs 3,000 PLN from a freelancer, the second 14,000 PLN from an agency, the third 42,000 PLN from a software house. Each one uses the same words: responsive, GDPR, SEO, fast. You try to compare them and nothing lines up.

The situation repeats itself often enough that it's worth breaking down. Not to argue that the cheap offer is bad. To see exactly what you're buying at each price tier and at what clinic scale each option pays back the fastest.

This text is for the practice owner, the director of a 5-30 person clinic and the marketing manager at a larger group. I write specifically about what each tier costs in Poland in 2026, why the cheapest solutions usually end with a second rebuild after a year, and what actually increases bookings.

The price doesn't come from the number of subpages or whether someone uses WordPress or Next.js. It comes from eight things that the client rarely sees, because they aren't spelled out in the offer.

1. Content. A clinic typically has 8-15 specialties, each doctor has a profile, each location has its own subpage. Writing these texts so that Google understands who's on your team and a patient sees what they're looking for in three seconds is work that the freelancer for 3,000 PLN won't do. The receptionist will do it in their spare time, which means never.

2. Local SEO and schema.org. The phrase “dr Kowalska cardiologist Warsaw” leads the patient straight to you, if the clinic and doctor profile have the right structured data (MedicalBusiness, Physician, MedicalSpecialty). Without this, Google doesn't know that dr Kowalska is a doctor or that your clinic is a cardiology clinic. You drop 20-30 positions in the results.

3. Online booking system. 24/7 appointments, two-way sync with the reception calendar, email and SMS confirmations, cancellations and rescheduling, integration with EHR (Mediporta, KSWeb, Eskulap). Each element is a separate module. Either you buy ready-made (ZnanyLekarz, Booksy: per-visit commission plus loss of control over your patient base), or you build your own (higher upfront cost, your own database, no commission).

4. Compliance. GDPR-by-design (encryption at rest, retention, form audit logs, DPIA), WCAG 2.1 AA (the harmonised standard EN 301 549 v3.2.1, the legal benchmark of the European Accessibility Act, in force since 28 June 2025; we treat WCAG 2.2 as the recommended industry standard), a cookie policy with granular consent and a decision log for a Data Protection Authority audit. These aren't badges. They're architecture.

5. Doctor profiles with Google reviews. Each doctor has their own page, reviews are pulled from the Google Business Profile, and after a visit the patient gets a gentle email asking for a review. Three months of this process change the clinic's visibility in Google Maps.

6. Hosting and backups. A clinic website where appointments are booked can't go down on a Friday evening. Daily backups with restore tests (the mere existence of a backup means nothing if it's never been restored), SSL certificates, automatic updates. This is an operating cost, not a one-off.

7. Uptime monitoring and incident response. Monitoring isn't somebody checking once a week whether the site responds. It's 24/7 alerts (uptime, SSL certificate before expiry, 5xx errors, response-time spikes), someone who actually receives them, and a response procedure written in advance. In a clinic context: if the site goes down on Friday at 8 PM and patients can't book on Saturday, by Monday your calendar is empty.

8. Post-launch support and iteration. A website doesn't end on the day of launch. The first three months show what works (where patients click, where they get lost, what questions they search for), and that's where the biggest quick wins usually sit. If the offer has no defined post-launch budget or a model for working together after launch, you're left alone with analytics nobody reads.

In Poland in 2026 a clinic website realistically falls into four tiers. I'll show what you buy in each and who it's for.

A quick comparison of the four tiers, if you prefer everything on one screen:

A single-page business card. Hero, about-the-practice section, services list, contact with map, inquiry form. For a solo practice (1 doctor, 1 dentist, 1 cosmetologist, 1 physiotherapist) this is enough to start. Key point: a patient searching in Google finds your practice and sees who they'll see.

What doesn't fit here: an online booking system, more than one location, team profiles, a blog, bilingual content. If someone sells you a 10-person clinic website for 4,000 PLN, they'll either use a ready-made template (and you'll look like a 5-minute version of your competitor), or they'll cut corners on compliance, or both.

A full clinic website, 8-25 subpages. Doctor profiles with Google reviews, local SEO, medical schema.org, blog, optional bilingual content. GDPR-by-design in the advanced variant, WCAG 2.1 AA with a conformance report (harmonised standard EN 301 549, the operational EAA requirement; WCAG 2.2 as the recommended forward direction). Hosting included for 12 months.

What doesn't fit here: a 24/7 online booking system, SMS reminders, EHR integration. That's left for phase two.

Who it's for: a 5-30 person clinic, the receptionist handles the phone, but the website has stopped selling. No Google reviews, no local SEO, doctors don't show up in searches by name.

A clinic website plus the full patient acquisition machine. 24/7 online booking, automatic SMS and email reminders (24 hours and 2 hours before the visit), automatic Google review request flow after the visit, integration with your existing EHR (one connector included), payment gateway (deposit at booking), an audit log of every access to patient data.

Who it's for: a clinic where reception is drowning in phone calls. No-shows pull 20-30 percent off the schedule, patients ask for online booking, doctors want to see their calendar in one place.

ROI in this category: no-show reduction of 30-50 percent (systematic reviews of SMS reminders in healthcare, including Gurol-Urganci et al., Cochrane Database 2013), additional patients from local SEO and Google reviews: 10-25 percent. For a clinic with 200 visits per week and an average visit value of 350-400 PLN (around 3.5-4 million PLN annual revenue), the investment typically pays back in 4-8 months. Provided you count margin from extra visits, not gross revenue.

Clinic networks, hospitals, organisations of 50+ people with HIS. Multi-branch operation, data isolation between branches, integration with a central EHR (Eskulap, AMMS, KS-SOMED, CGM CliniNet), DPIA at the organisational level, 24/7 SLA, audit logs at scale.

This isn't a price for a website. It's a project for a patient-handling platform, in which the website is the presentation layer.

Typical scope at this tier: integration with the existing HIS (most often AMMS, Eskulap, KS-SOMED), separate permissions and views per branch, single sign-on with the hospital system, two-stage DPIA (organisation + patient journey), audit logs aligned with internal policy, an SLA with penalty clauses and an on-call team on the vendor side. Each project is priced individually because the scope depends less on “the website” and more on the state of existing IT infrastructure, and how much of it needs to be worked around versus connected to.

The question I'll hear after this text is published: “but we have a 3,000 PLN website and it works”. It usually works until it stops.

Compliance. The European Accessibility Act has been in force since 28 June 2025. The EAA does not formally cover healthcare services as such, but it does cover e-commerce services. If your clinic offers online booking with payments (deposits, prepay, prepaid packages), the website becomes an e-commerce service under the EAA, and WCAG 2.1 AA (the harmonised standard EN 301 549 v3.2.1) is a real legal requirement. A business-card site without online payments sits in a grey area, but accessibility is still worth treating as a baseline, especially given senior patients and patients with disabilities. On top of that, GDPR-by-design for patient data and the link to NIS2 under the health-sector classification. A 3,000 PLN website usually has none of these. The first regulatory inspection and the rebuild becomes mandatory.

The micro-enterprise exemption. The EAA exempts micro-enterprises (under 10 employees and turnover up to EUR 2M) from parts of the service-provision obligations. Solo practices and 1-9 person clinics often fall into this category. That doesn't mean accessibility doesn't matter for you (it does, especially given senior patients and patients with disabilities, who are a significant share of private healthcare's audience), only that the formal regulatory risk is lower. Larger entities don't get this exemption and must hold full EAA and EN 301 549 conformance.

Patient base scale. The clinic grows. After a year it turns out that the website that handled 200 visits per day handles 2,000. Sites built on a rigid 2018 template don't scale. You have to build from scratch.

No code ownership. A cheap site usually uses ready-made plugins (WordPress plus a bookings plugin) or is built on a platform whose vendor holds your DNS and patient database. When you want to switch vendors, it turns out the data is in a closed format. Migration costs more than a second rebuild.

No EHR integration. Online booking that doesn't sync with the reception calendar means more work for reception, not less. After two months reception switches off booking themselves, “because it gets in my way more than it helps”. The website remains, the function dies.

The mechanics are simple: a booking system without EHR coupling is an open-loop system. Reception compensates for the missing information by hand, which means re-typing bookings, calling to confirm, manually catching schedule conflicts, correcting when a doctor cancels at the last minute. At 50 visits per week, that still works. At 300 visits per week, the operating cost of that compensation (two receptionists instead of one, a rising number of complaints about “something being booked wrong”) is larger than the cost of closing the loop with a proper integration. A cheap site shifts the cost from the IT budget to the HR budget. The director usually only notices when they have to hire a third person.

No Google review process. A clinic with 30 reviews and a 4.7 average earns more than a clinic with 3 reviews and a 5.0 average. Without an automatic post-visit process (email or SMS asking for a review with a direct link to the Google Business Profile), reviews don't grow. Without reviews Google Maps doesn't lift you in local results.

The point isn't that a cheap website is bad in itself. The point is that if you buy a clinic website for 3,000 PLN, you're buying it for a year or two. After that the cycle repeats. Three years, three implementations, totalling 12-15 thousand PLN for solutions that replace each other. You can invest right away in one implementation of 12-18 thousand that will last 5 years.

Four elements whose absence is the biggest cause of patient loss in private medicine in Poland in 2026.

1. 24/7 online booking. A patient who wants to book in the evening won't call in the morning. Either they book somewhere else, or they forget. ZnanyLekarz and Booksy collect 20-50 PLN from each booked visit plus a margin for promoted slots. Your own system pays back at 80-150 visits per month.

2. Automatic SMS and email reminders. No-shows in private medicine typically run at 15-30 percent (industry data; there isn't a single nationwide Polish study for the private sector). An SMS reminder 24 hours and 2 hours before the visit reduces no-shows by 30-50 percent (systematic reviews including Gurol-Urganci et al., Cochrane Database 2013). For a clinic with 200 visits per week that's 12-30 additional visits per week. At an average visit value of 250 PLN, that's 3-7 thousand PLN of extra revenue per week.

3. Automatic Google review requests after the visit. A patient who has just left satisfied is ready to write a review if you remind them. A patient who left three days ago has already forgotten. Automatic process: email or SMS within 6 hours after the visit, link straight to the Google Business Profile, short text. A clinic that consistently collects reviews for 6 months moves up in Google Maps from positions 7-10 to 1-3.

4. Local SEO with medical markup. For the clinic as an institution use MedicalBusiness plus MedicalSpecialty and AggregateRating. For individual doctor profiles use Physician (still in use, although in many implementations combined with MedicalBusiness as the primary class for the whole institution). Plus entries on the Google Business Profile, opening hours, photos. A patient searching for “cardiologist Mokotów” sees you on Google Maps with reviews and hours.

In order of impact on the number of bookings: online booking, then SMS reminders, then Google reviews, then local SEO. GDPR, WCAG, security certificates are the foundation whose absence costs you (inspection, fine, exclusion from tenders). Without the acquisition machine described above, the foundation doesn't generate revenue.

Eight questions worth asking before signing a contract.

If a vendor answers “yes” to every question without pause, ask for details. If they answer “well, in fact we can build that in”, it means it's not included. If they answer “we don't know, we've never done that”, that's also useful information, better to have it before signing.

A clinic website costs what it costs because eight things have to go into it: content, local SEO, booking system, compliance (GDPR plus WCAG), doctor profiles with reviews, hosting and backups, uptime monitoring, post-launch support. A cheap offer usually has one or two of those eight. The rest turns up as a gap later, when the clinic grows or when the first inspection asks for documents.

The most sensible tier for a 5-30 person clinic is 12-28 thousand PLN for a full website without online booking, plus 38-60 thousand for a full acquisition machine with booking, SMS reminders and Google reviews. Those numbers pay back in 4-8 months for a clinic with 150+ visits per week, provided you count margin from the extra visits, not gross revenue.

If you don't know which tier fits your clinic, you have two paths. A free automatic scan in 48 hours flags the main gaps: WCAG, GDPR, performance, schema.org. It's a short PDF with the most important red flags, a lead magnet, not a full analysis. A paid audit at 4,900 PLN is something different: a report in two weeks, manual business/SEO/compliance/UX analysis, a remediation plan with pricing for the next steps, an hour-long call with the author. The audit fee is fully credited toward the package price if you decide to continue with us within 60 days.