Off-the-shelf Israeli booking system or custom build: five criteria - what you own, what you cannot change, your data on exit, cost shape, what a build buys.
Key takeaways
- Israeli products such as Tiffulit, Clickynder and SimpleTor cover the core: online booking, reminders, card processing and deposits.
- The criterion that actually decides it is not the feature list but the ability to change a rule the product never anticipated.
- None of the three publishes public developer API documentation. Tiffulit mentions a developer interface, with no specification available.
- On the day you leave, what matters is the customer list and the history. Ask about export before you sign up, not after.
- A custom build buys you one booking rule that has no name in any product. Without such a rule, you are buying maintenance.
The choice between an off-the-shelf Israeli booking system and a custom build turns on five criteria: what you own, what you cannot change, what happens to your data the day you leave, how the cost behaves over time, and what a build actually buys that a product does not. Most businesses should not build.
What the three Israeli systems cover
According to what each company presents on its own site:
- Tiffulit targets beauty salons, clinics and hairdressers, and presents a booking calendar, automatic reminders and attendance confirmations over WhatsApp and SMS, WhatsApp automations, a till with card processing and online deposit collection, a branded booking app, digital forms with online signatures, and staff management.
- Clickynder presents round-the-clock online booking, group classes, a smart waiting list, recurring appointments, card processing and deposits, cancellation-policy enforcement, coupons, intake forms with digital signature, multi-location support and native mobile apps.
- SimpleTor presents a branded business page, automatic customer messages, a customer management panel, card processing with receipts and invoices, calendar sync, waiting lists and deposit collection.
The overlap between them is larger than the difference, and that is itself a data point: core appointment management is a solved problem in the Israeli market. Choosing between the three is a question of sector fit and usability, not of whether the capability exists.
The five criteria that decide it
| Criterion | Off-the-shelf Israeli system | Custom build |
|---|---|---|
| What you own | An account and the data inside it, subject to the terms | The code, the database and the server |
| What you cannot change | Booking rules the product does not support, the field model, anything beyond branding-level appearance | Nothing. Which is also the problem |
| What happens to your data when you leave | Depends on an export capability you must establish in advance | All of it is yours, including responsibility for the backup |
| Cost shape | A fixed monthly fee growing with users and locations | A large one-off build cost plus ongoing maintenance |
| What it buys | Time. You are live within a day | A booking rule that exists in no product |
| When it starts working | Immediately | Weeks to months later |
| Who handles it breaking on a Saturday | The vendor | You |
Row five is the only one worth arguing about. Everything else is knowable in advance, and checkable in one conversation with the vendor.
Who owns the customer list, and how do you get it out?
The customer list is the asset. The calendar is not an asset - it empties every month - but names, phone numbers and visit history are what remain after five years.
Across the three systems, I found no public documentation of a data export or an API for any of them. Tiffulit mentions an open developer interface on its site, but I found no available specification. Clickynder presents enterprise-level customisation without public documentation. SimpleTor mentions no API, webhook or export at all.
That does not mean the capability is absent. It means you have to ask, and get a clear answer before signing up:
- In what format the full customer list comes out: CSV, spreadsheet, or programmatic access.
- Whether the history comes with it, or only the current list.
- How long an export takes to obtain, and who performs it.
- What happens to the data after you stop paying, and how quickly.
- Whether a recurring export is possible, rather than one export on the way out.
That check costs five minutes at the start, and it is the difference between a system migration and a system migration that begins with retyping thousands of customers.
What does a custom build actually buy you?
It buys one rule that has no name in an off-the-shelf product. That is the only criterion that justifies building, and it is worth stating in a single sentence before budgeting anything.
Four examples of rules products generally do not cover:
- A dependency between two different resources. An appointment needing both a practitioner and a piece of equipment kept elsewhere, so the slot is valid only when both are free.
- Pricing derived from the combination. A price varying by which practitioner, by actual duration and by booking source, rather than by treatment type alone.
- An appointment that is part of a course. A series with minimum and maximum gaps, where cancelling one shifts all the rest.
- A booking conditional on data in another system. An eligibility approval or a remaining quota that lives in a CRM.
If you read those four and did not recognise your business, a custom build will mainly buy you maintenance. If you did recognise it, that is the reason. The subject is broken down in how to build a booking system and in self-hosted booking versus Calendly.
Cost shape, not price
I am not quoting prices here, because SaaS pricing moves and the number would be stale before you read it. What does not move is the shape of the cost.
- Off-the-shelf: low starting cost, ongoing cost that grows with users, locations and sometimes message volume. It never ends, and the vendor controls it.
- Custom build: high starting cost, lower ongoing cost but never zero - hosting, a messaging channel, security updates and fixes. You control that cost, and you also own it.
- Messages are a separate cost line either way. SMS and WhatsApp are charged by usage on both routes, so message volume is a variable rather than a constant.
The real break-even is not a number in a spreadsheet. It is the question of how many years the system will serve you without a fundamental change. A business that knows its model will change within a year should not be building.
When each one is clearly the right call
- Off-the-shelf is clearly right when your process is practitioner, time, treatment and payment; when you need to be live this month; and when nobody on the team will maintain code.
- A build is clearly right when there is a booking rule you can state in one sentence that no product satisfies, when appointments must live inside a larger system you already run, or when the data has to stay with you.
- The hybrid usually wins in practice: the product runs the appointments, and a thin layer on your side pulls data from it into reports and workflows. It leans on an agreed export, which is exactly why the export question is the first one and not the last.
Related: what it costs to build a booking app, leading appointment scheduling software.
Sources
Frequently asked questions
Do the Israeli booking systems have an API?
I found no public developer API documentation for Tiffulit, Clickynder or SimpleTor. Tiffulit mentions a developer interface on its site, but published no specification I could locate. So anyone needing a programmatic connection should request a specification and a sample call from the vendor before committing to a schedule.
When is it worth building a booking system instead of buying one?
When a booking rule exists that you can state in a single sentence and no product satisfies it, when appointments need to sit inside a larger system you already run, or when the data must stay with you. Without one of those three reasons, a build mostly buys ongoing maintenance cost.
What happens to my customer list if I leave a booking system?
That depends entirely on that vendor's export capability, and it is a question to ask before signing up rather than after. Establish what format the list comes out in, whether visit history comes with it, how long it takes, and what happens to the data once payment stops.
Can I combine an off-the-shelf system with my own development?
Yes, and it is usually the most practical route. The product runs appointments and messaging, and a layer on your side pulls data from it into reports or a CRM. That combination stands or falls on a stable export capability, which is why it is the first thing to check.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build. I reply within 24 business hours with a few targeted questions, then we walk through it on a free 30-minute call, with no commitment. You come away with a scope, a timeline and a fixed price - or a straight answer that it isn't worth building.