Guide · ~26 min read
Own systems instead of SaaS.
A complete 2026 guide.
In brief
An own business system is a dedicated application that replaces vertical SaaS (Booksy, Booking, Restaumatic, ZnanyLekarz, Calendly, eRejestracja). Instead of 130-500 PLN/month + booking commissions, you pay once at deployment and use it for years. Data on your server, zero vendor lock-in, zero commissions. Economics: pays back in 12-36 months for most small businesses, saves 30-60k PLN over 5 years for mid-size ones.
- Price: Booking widget from 699 PLN / Mini 3 999 PLN / Standard 5 999 PLN / Pro 7 999 PLN / Custom from 9 999 PLN
- Timeline: 2 days (widget) to 8 weeks (custom multi-location system)
- 4 ready-made systems: bookings (lodging/restaurants/fitness), customer records (beauty/medical), auto workshop, construction
- When NOT worth it: small scale (Booksy x1 = 130 PLN/month, an own system pays off in year 4), no settled process (fix the workflow first), pure B2B with Allegro/Empik (leave what works)
Table of contents
- 1. What's wrong with SaaS in 2026?
- 2. When it's worth moving to an own system, and when it isn't
- 3. Real ROI math, 4 industries, 5 years
- 4. The 4 types of systems I offer
- 5. Deployment process, from brief to launch
- 6. Migrating from SaaS, step by step
- 7. The 7 most common mistakes
- 8. FAQ, 12 questions
- 9. Related articles
1. What's wrong with SaaS in 2026?
Vertical SaaS (Booksy, Booking, Restaumatic, ZnanyLekarz, eRejestracja, Versum) was a breakthrough for small businesses between 2015 and 2022. Cheap entry, everything ready, "click and it works". But in 2026 the model has broken down for 4 reasons.
1.1. Commissions go up, your data is held hostage
Booking launched in 2008 with a 12% commission. In 2026 it's 17-22% depending on region and category. Booksy was 79 PLN/month in 2018, 130 PLN/month in 2026. ZnanyLekarz went from 99 PLN to 200+ PLN. Restaumatic went from free to 300 PLN/month. This is how every SaaS behaves: first acquire users cheaply, then start milking them.
Why not just leave? Because the data (customers, bookings, photos, treatment history) is locked inside the SaaS. CSV exports are often limited. You put 5 years of data in, you are a hostage. Full article: Why SaaS holds you hostage.
1.2. GDPR, whose customer data is it really?
Your company is the data controller for customer data (GDPR). The SaaS is only the processor. But the data physically sits on the SaaS provider's servers (often in the US. Booking on AWS, Booksy on AWS). What that means:
- The SaaS can analyse, aggregate, anonymise and sell the data (per TOS).
- A breach at the SaaS = your fine from the data protection authority (as the controller). You answer to the customer.
- You have no physical control over who accessed what and when.
- A customer requests deletion (right to erasure)? You have to trust that the SaaS actually deletes it. If they don't. Your liability.
Full overview: GDPR and SaaS, whose data is it really.
1.3. The SaaS algorithm shows your competitors
Booking, Booksy and ZnanyLekarz are not neutral tools. Their business is converting your customer into a competitor's customer. Your customer lands on your restaurant's Restaumatic profile? They see "Similar venues nearby". Your customer on your salon's Booksy profile? They see "Other salons nearby with open slots".
You do not control this. The customer you acquired through ads, reviews or a 360 tour is being actively cannibalised by the SaaS you pay a subscription to.
1.4. AI has flipped the economics of building your own systems
Until 2024 an own booking system meant a software house, 30-100k PLN, 3-6 months. Unreachable for a small business. SaaS was the only option.
Since 2025 with AI (Claude by Anthropic, GPT) one freelancer ships in 1-4 weeks and 4-15k PLN what used to require a whole team. The economics of an own system have flipped. See: AI and building applications in 2026.
2. When it's worth moving to an own system, and when it isn't
An own system is not always the best call. A simple decision frame:
2.1. When it IS worth it
- You pay 200+ PLN/month for SaaS, break-even at 12-24 months.
- You lose 15%+ in booking commissions. Booking 18% on a guesthouse with 100k PLN annual revenue = 18k PLN. An own system at 6k PLN = payback in 4 months.
- You have your own website and direct traffic, customers come back themselves, not through Booking. In that case the SaaS is just a tax.
- You have a specific workflow the SaaS does not handle (before/after photos for a podiatrist, VIN history for a mechanic, cost estimates for construction).
- Scale of 5+ staff / 2+ locations, subscriptions multiply, an own system = one licence, multi-tenant.
- Customer data value is growing, e.g. a medical office with treatment history, a beauty salon with before/after photos. That data on a US SaaS = risk, on your own server = safety.
2.2. When it is NOT worth it
- Solo + low revenue, one Booksy at 130 PLN/month = 1,560 PLN/year. An own system pays back in year 4. Uneconomical.
- No settled process, if your calendar is chaos today, an own system will not fix it. Fix the workflow first in Excel or Trello.
- Main traffic from marketplaces (Booking, Allegro), if 90% of customers come through Booking, you will not leave entirely. An own system = an add-on for direct traffic, not a replacement.
- You do not want to participate in maintenance, an own system needs a monthly care tier (399 PLN/month for the backend). If you want "set and forget", SaaS is simpler.
- A small business with 1-2 people and no growth plans, a home-visit nurse doing 30 visits a month does not need a custom system. Booksy or Google Calendar will do.
2.3. The decision rule in one sentence
If you pay SaaS 2,000+ PLN per year and have a working process, and you want control over your data and to stop cannibalising your customers to competitors, an own system pays back. Otherwise stay on SaaS.
3. Real ROI math, 4 industries, 5 years
Concrete numbers, not marketing. SaaS rates from 2026.
3.1. Beauty salon (cosmetician, hairdresser, massage), 3 specialists
| Option | Year 1 | 5 years |
|---|---|---|
| Booksy x3 specialists | 3 x 130 PLN x 12 = 4,680 PLN | 23,400 PLN |
| Own Mini system | 3 999 PLN setup + 1 788 PLN care | 12 939 PLN |
5-year saving: ~12,000 PLN. Break-even in year 2. Plus ownership of before/after photos on your server (important for podiatrists, dermatologists). Full article: Booksy alternative 2026.
3.2. Restaurant with table reservations
| Option | Year 1 | 5 years |
|---|---|---|
| Restaumatic Standard | 300 PLN x 12 = 3,600 PLN | 18,000 PLN |
| Own Mini system | 3 999 PLN setup + 1 788 PLN care | 12 939 PLN |
Saving: ~6,600 PLN. Break-even in year 2. Full article: Restaumatic alternative.
3.3. 8-room guesthouse (the strongest case)
Booking takes 18% on every booking. A guesthouse with 100k PLN annual revenue = 18k PLN a year just to Booking.
| Option | Year 1 | 5 years |
|---|---|---|
| Booking 18% on 100k PLN revenue | 18,000 PLN | 90,000 PLN |
| Direct booking 30% (via your own widget) | -5,400 PLN / year less to Booking | -27,000 PLN saving |
| Own Standard system | 5 999 PLN + 4 788 PLN tech care | 29 939 PLN |
Real saving (with 30% direct booking): 11,000 PLN a year, 55,000 PLN over 5 years. Plus no vendor lock-in. Full article: How not to pay Booking commissions.
3.4. Medical office / dermatologist
| Option | Year 1 | 5 years |
|---|---|---|
| ZnanyLekarz / eRejestracja | 200 PLN x 12 = 2,400 PLN | 12,000 PLN |
| Own Standard system | 5 999 PLN + 4 788 PLN | 29 939 PLN |
Financial saving is marginal (~5,000 PLN over 5 years). The real value: treatment history + before/after photos + therapy plan on your server, not at a US SaaS. Critical for GDPR and for company value at sale. Full article: ZnanyLekarz alternative.
Audit your firm's SaaS costs: How much will I save by quitting SaaS.
4. The 4 types of systems I offer
Instead of "custom from zero" for every client, I have 4 ready templates for the 4 most common industries. That cuts deployment from 8 weeks down to 1-2.
4.1. Online booking system (lodging, restaurants, fitness)
Guesthouses, restaurants, event halls, fitness studios, spas. Calendar, availability, online payments (Stripe / Przelewy24), automated SMS/email confirmations, no-show fee.
Price: Widget from 699 PLN (on an existing site), Mini from 3 999 PLN, Standard with payments from 5 999 PLN, Pro multi-location from 7 999 PLN. Dedicated page: /system-rezerwacji-online/.
4.2. Customer records (beauty, medical)
Salons, podiatry and dermatology offices, massage, hairdresser, dog grooming, tattoo. Calendar, customer history, before/after photos, treatment plan, GDPR consent, automated reminders.
Price: from 4 499 PLN setup. Dedicated page: /kartoteka-klientow-online/.
4.3. System for auto workshops
Mechanic, tyre shop, auto detailing, body shop. Repair history by VIN, before/after photos, staff schedules, customer calendar, recurring invoices.
Price: Solo from 4 999 PLN, Pro multi-bay from 7 999 PLN. Dedicated page: /system-dla-warsztatu/.
4.4. System for construction
Remodelling firm, plumber, electrician, roofer, paver. Crew schedules, job tickets, cost estimates with measurements, site photos, customers, invoices, health-and-safety documentation.
Price: Solo from 5 999 PLN, Pro general contractor from 9 999 PLN. Dedicated page: /system-dla-budowlanca/.
4.5. Custom system (non-standard workflow)
CRM for a real estate agency, B2B panel for a wholesaler, pricing calculator for an architecture studio, API integration with Allegro / Empik / IAI, catering order system.
Price: from 9 999 PLN (4-8 weeks delivery). Requires a brief and an individual quote.
5. Deployment process, from brief to launch
Week 0: Brief + quote
A 60-minute call, what you do, your workflow, what does not work for you in SaaS, what you need. Fixed-price quote in 24 hours, decision is yours.
Week 1: Specification + design
A "what I am building" document (5-10 pages), database schema, wireframes of 5-8 screens. Sign-off by you.
Week 2-3: Build + test (Mini/Standard system)
Build on Astro / Next.js + Supabase (database + auth) + Stripe (payments). Tested on my infrastructure. I show a demo every 2-3 days.
Week 3-4: Data migration + production test
CSV export from the SaaS, import into the new system, validation, production test on your side with real data.
Week 4: Go-live + training
Production switch, 301 redirects from old URLs, 2-hour training for you and your team. Manual plus a how-to video.
After go-live: Tech care
Tier 399 PLN/month, daily backup, uptime monitoring, security updates, small changes in 24 hours. No yearly contract.
Full process: How to start your own booking system.
6. Migrating from SaaS, step by step
The most common worry: "you can't export data from Booksy / Booking / Restaumatic". The truth is more nuanced, exports are sometimes limited, but rarely impossible. Concrete strategies:
6.1. CSV / API export
- Booksy, CSV export of customers and bookings in the admin panel (full access).
- Booking. The Channel Manager API allows you to pull historical bookings.
- Restaumatic, CSV export in the panel, limited history (12 months back).
- ZnanyLekarz, CSV export of customers and visits, treatment history is sometimes limited.
- Calendly, full iCal + CSV export.
6.2. Gradual migration (recommended)
Instead of an "overnight switch":
- Week 1-2: the new system runs in parallel with the old one, test bookings.
- Week 3: redirect 50% of bookings to the new one, 50% stay in SaaS.
- Week 4: 100% on the new one, the SaaS in read-only mode.
- Month 2: downgrade the SaaS to its cheapest plan (or remove it).
- Month 3: archive data from the SaaS, cancel the account.
6.3. What about old links and rankings?
A Booksy / Booking profile has SEO value. 301 redirects from the old link to your site pass some authority. Full process: Migrating from SaaS to your own system.
7. The 7 most common mistakes
- Migrating with a chaotic workflow. Fix the process first in Excel or Trello. An own system will only automate what already works.
- "Copy Booksy 1:1". SaaS has dozens of features, you use 5 of them. Build only those 5. The rest is technical baggage.
- Ignoring tech care. A system with a database and auth needs monthly maintenance (399 PLN/month). Without it, after 6 months you have security holes and broken features.
- Migrating too fast. A 1-week switch = mess for customers. A 4-week gradual migration = a professional transition.
- Cutting marketplaces overnight. Booking gives you 50% of your traffic? Don't delete the profile, keep it, but push direct booking alongside. Settle on a 30/70 split: 30% Booking, 70% direct.
- A custom feature for every idea. "I'd also like A/B testing for offers" + "cohort reports" + "Allegro integration", scope creep kills projects. Build the MVP, add features in iterations.
- No plan for "what if the builder leaves". An own system from a solo developer = bus factor risk. Insist on code in GitHub (your account), documentation in the "any next developer can take over in 2 weeks" style, and the option to switch to another developer.
8. FAQ, 12 questions
How long does deploying an own system take?
Widget on an existing site: 2 days. Mini system (booking calendar + customers): 7-10 days. Standard system with payments: 10-14 days. Pro multi-location system: 3-4 weeks. Custom: 4-8 weeks.
What if I want to change the developer in a year?
The code is yours, in your GitHub repo. Technical documentation is written so the next developer can take over in 2 weeks. Stack: Astro / Next.js + Supabase, popular, easy to find a developer for. No vendor lock-in.
What about hosting? Expensive?
No. After deployment you have hosting (from 250 PLN/year with a domain) plus a payment provider fee of around 1.5% (Stripe / Przelewy24). That's on the order of 20-50 PLN a month, instead of 130-300 PLN/month for SaaS.
Will the system still work in 5 years?
Yes, if it has maintenance. The stack (Astro, Supabase, Stripe) is mature tech with large communities, it will stick around. Without maintenance, security holes, outdated libraries. A tech-care tier is mandatory.
Can I accept online payments?
Yes. The Standard package includes Stripe (card) or Przelewy24 (BLIK, transfer). Stripe commission is 1.4-1.9%, Przelewy24 1.5-2.5%. Vertical SaaS usually adds another 5-15% on top.
Do customers have to create an account?
No. Frictionless flow: the customer enters email and phone, gets a magic-login link to their booking panel. No passwords, no frustration. Account optional (auto-invite after 2-3 visits).
And SMS? Expensive?
SMSAPI / Twilio, 0.08-0.12 PLN per SMS. 100 SMS/month = 8-12 PLN. Completely fine for a small business. Plus alternatives: email reminders (0 PLN) + WhatsApp Business API (0.03 PLN/msg). Full article: Bookings, SMS vs email.
Do I stay on Booking in parallel?
I recommend it. Booking provides organic reach you cannot build on your own (Booking for a guesthouse = 30-50% of the first booking). Strategy: 30/70-30% via Booking (you pay the commission), 70% direct through your own system (0% commission). Over time you shift to 20/80, then 10/90.
What about GDPR?
An own system = data on your server (Supabase EU = Frankfurt / Dublin). Full control, no transfer outside the EU, GDPR-compliant by default. Vs SaaS often in the US = you have to document and certify the transfer.
Can I test before a full commitment?
Yes, 2 options. 1) Booking widget from 699 PLN, the cheapest test, 2-day deployment. 2) A 60-minute brief at 0 PLN, you get a quote and a mock-up, decision is yours.
What sets me apart from a software house?
3 things: 1) price (4-15k PLN vs 30-100k PLN), 2) timeline (1-4 weeks vs 3-6 months), 3) communication (directly with the developer vs through an account manager). A software house makes sense for large projects (50+ user roles, integrations with 5+ external systems). For a small business, overkill. See: Software house vs freelancer with Claude Code.
Does AI produce worse code than a human?
No, if the developer stays in control. AI generates boilerplate code (forms, CRUD, validations) faster and without bugs. Architecture, business decisions, edge cases, that's the human. AI is a tool, not a replacement. Full article: AI and building applications in 2026.
9. Related articles
13 posts that expanded specific threads from this guide:
Why SaaS holds you hostage
Read article →
How much will I save by quitting SaaS, the real math
Read article →
GDPR and SaaS, whose data is it really
Read article →
Booksy alternative 2026
Read article →
Restaumatic alternative
Read article →
ZnanyLekarz alternative
Read article →
Calendly alternative
Read article →
How not to pay Booking commissions
Read article →
How to start your own booking system
Read article →
How much an online booking system costs
Read article →
Migrating from SaaS to your own system
Read article →
How to increase restaurant reservations
Read article →
Bookings, SMS vs email
Read article →
Want to escape SaaS?
4 ready-made systems + custom. Start with a free 60-minute brief, fixed-price quote in 24 hours.
Drop me a line and I will tell you what I can do for your business
Website, your own booking system, a 360° tour, ongoing care, separately or together. I will call and tell you straight what makes sense in your case. No obligation.
Leave your number, I will call back within 24h: