What is the difference compared with Mews, Booking.com, Resengo or a similar SaaS?
Mews, Apaleo, Cloudbeds (hospitality), Booking.com (marketplace), Resengo, TheFork (restaurants), Salonized, Treatwell, Eversports (beauty / fitness) and similar platforms are good at general mechanics. They hit their limits in four areas. First, industry- or concept-specific logic: a hotel chain that wants to combine rooms and spa in a single booking, or a fitness concept that links personal-trainer slots to childcare. Second, integrations with unusual PMS, POS or CDP stacks, where adapter work becomes expensive and fragile. Third, commission and fee structures that make your best channel more expensive the better it performs. Fourth, ownership of customer data: on a marketplace the guest remains their customer, not yours. We will also tell you honestly when a SaaS solution is enough: for a standard booking flow without exotic integrations, it can be a perfectly good first step.
Native or cross-platform: what do you recommend?
It depends on the mechanics and your internal capacity. For standard booking flows (slot selection, payment, reminders, loyalty), Flutter or React Native works very well and delivers a simultaneous release on iOS and Android from a single codebase. For apps that make heavy use of hardware (Apple Wallet for passes, advanced push segmentation via OS features, NFC check-in at the desk, complex animations that carry the brand feel), we increasingly choose native: Swift for iOS, Kotlin for Android. We advise case by case. We can deliver both, and do both well. For the web version of the app that you open in the browser (for example from a Google search result), we build a Progressive Web App that shares the same booking engine.
How do you handle PMS and POS integration?
We integrate with all common PMS and POS systems in the Benelux: Mews, Apaleo, Cloudbeds, Opera, Protel, RoomRaccoon and in-house PMS via custom middleware, plus the common POS systems (Lightspeed, Untill, Tally Pay, Toast, Storyous, Vectron, MplusKASSA, Square, Adyen POS stacks). The integration works in both directions: reading availability (in real time or via a cache with invalidation on change) and pushing in bookings (atomic, with retry logic on timeouts so that double bookings are ruled out). For industry-specific systems (Salonized, Treatwell, Mindbody, Eversports, Trainin, Resengo, Salonkee), we build the adapters so that migrating existing bookings does not have to happen as a big bang.
How do you handle payments, PSD2 and SCA?
Payments run through Mollie or Stripe as standard, and for larger volumes through a
dedicated payment platform. We comply with PSD2 and Strong Customer Authentication (SCA) through 3D Secure 2.0 for card transactions, a native flow for iDEAL and Bancontact, and a frictionless flow where the PSP supports it. For recurring payments (subscriptions, no-show fees, repeat deposits), we use mandates with the right SCA exemption. Refund flows are covered by automated tests, because a refund error damages a customer relationship faster than an ordinary booking error.
How do you set up no-show fees so they stay customer-friendly?
No-show fees solve a real operational problem but can damage the customer relationship if they go wrong. We build in three mechanisms. First, a grace period with an automatic reminder beforehand, so the customer can still cancel or reschedule. Second, a transparent policy in the booking flow: the terms are visible before the customer pays, not hidden in the general terms and conditions. Third, a reasonable appeals process, so staff can reverse a no-show fee if the customer comes forward with a good reason. Customers experience a fair system, and you keep operational occupancy under control.
How do you handle GDPR and customer data?
Booking data is sensitive by definition: names, contact details, payment details and, in healthcare, medical context too. We build a GDPR-compliant opt-in flow for marketing communication, a granular consent model (you can book without receiving personalised offers), retention policies for customer and transaction data, and a data vault setup in which sensitive attributes are kept separate from operational data. For healthcare practices we add NEN 7510 measures (encryption at rest, an audit log for every record access, pseudonymisation where possible, role-based access based on BIG registration). We include a DPIA as standard in larger CDP projects. ePrivacy also plays a part for push notifications, which have a separate consent step.
What about the EAA and WCAG accessibility?
From 28 June 2025, a booking app falls under the European Accessibility Act (EAA), which sets WCAG 2.1 level AA as the minimum. We build for accessibility from the start: correct contrast ratios, visible focus states, screen reader labels on interactive elements, inventory selection that works with keyboard navigation, and a booking flow that doesn't rely on timeout buttons. For sector-specific requirements (healthcare, government), we go beyond AA where needed. We run an accessibility audit at the end of the project and deliver an accessibility statement that you can publish on your site.
How do we prevent double bookings on the same slot?
Double bookings almost always come from a race condition: two customers book the last available slot at exactly the same moment, and the back end accepts both. We solve this with atomic booking transactions on the database (Postgres advisory locks or row-level locking), combined with a queue mechanism for peak moments such as a popular group class or a sought-after dinner time. The booking engine guarantees that a slot can be taken at most once, no matter how many customers press the "confirm" button at the same time. Automated tests cover these edge cases so that regressions never reach production.
What about gift vouchers and the Dutch Gift Voucher Act?
If you issue gift vouchers for bookings (dinner vouchers, spa vouchers, escape room gifts, fitness punch cards), specific rules apply in the Netherlands around validity (a minimum of two years since 2023), the duty to provide information, stating the remaining balance, and what happens in case of loss or expiry. We make sure the redemption flow complies with these rules, and for larger programmes we explicitly arrange a legal check with a specialist, so there are no surprises later in a first discussion with a regulator.
Does the app work offline?
For viewing confirmations, calendar items and wallet passes, working offline is generally not critical, because the booking is made on the customer's side, where they have internet. For staff tooling at the front desk or in a meeting room without coverage, we have built offline-friendly flows: the staff app caches booked slots locally, guests can be checked in without a connection, and changes sync as soon as the network is back. This matters in old buildings, basement locations or hospitality venues with thick walls where wifi is patchy.
How do you measure whether the app works commercially?
We set up reporting on occupancy per location and resource, revenue per slot category, no-show rate, conversion through the funnel (from app open to confirmation), customer LTV per segment, and commission savings if you migrate from a marketplace. For more mature programmes, we also build in A/B tests on price points, slot presentation and upsell flows, so you know not only whether the app works but also which variant performs best for which segment. Reporting goes to your BI tool if you already use one, or is available as a dashboard in the app's own admin.
Who owns the code, customer data and booking history?
You. We hand over the complete source code, schemas, build pipelines and deploy scripts. The data lives in your cloud (GCP, AWS, Azure) or with a hosting provider of your choice. If you later want to continue with another agency, or take it in-house, you can. There's no technical lock-in, no hidden API keys and no subscription for something you no longer want. We earn our money from good work that lasts, not from clients who are stuck with us.
What determines the cost of a booking app?
The biggest cost drivers are the complexity of the booking mechanics (single-resource versus multi-resource with capacity and waitlist), the number of integrations (PMS, POS, calendar, CDP, marketing automation, ERP, finance), the degree of personalisation and revenue management (static prices versus a dynamic pricing engine), the number of locations and languages, and whether native or cross-platform is the right choice for your brand. Industry-specific compliance requirements (healthcare, finance) also play a role. We work in sprints with fixed sprint budgets, so there are no surprises and you can steer the scope sprint by sprint.
How long until we can go live?
A first working version with slot selection, payment and confirmation can be on TestFlight and the Google Play internal track within a few sprints. For a full platform with multi-resource booking, waitlist, no-show fees, dynamic pricing, loyalty and multi-location integration, we plan a project of several sprints. We often roll out in phases, so a single pilot location can start while we keep building. We feed that feedback straight into the wider launch.