Illustrative business case · researched 16 November 2026. This independent study uses public SACRA prices to make the example tangible. It is not commissioned work, a forecast for SACRA or evidence that SACRA uses Fresha. Its existing Flyby booking route should be retained unless a review supports a change. No client relationship or measured result is implied.
A guest finishes a relaxing visit and wants to come back next month. They already know where they want to go. Does that repeat booking need a new app—or simply a clear link to the booking system the spa already uses?
The answer starts with a small but expensive misunderstanding: moving a returning guest away from a discovery marketplace does not necessarily save a commission. If the fee was paid once, at the first visit, there may be nothing left to save on the next one.
Discovery and repeat booking do different jobs
A marketplace can help unfamiliar guests discover a venue, compare services and reviews, and book with more confidence. Those are useful acquisition and trust benefits. The spa still delivers the treatment, schedules staff, manages capacity, handles guest needs and resolves service issues. A marketplace is not a replacement for those operations.
Fresha’s published pricing distinguishes new-client acquisition from returning bookings. Its pricing surface showed 20% acquisition commission, but currencies and payment rates varied by region during research. Those are not a verified UAE merchant quote. The model below uses editable planning assumptions; confirm local subscriptions, transaction charges, minimums, caps and negotiated terms before a decision. Accessed 16 November 2026.
Its fee guidance says the acquisition charge is one-time, excludes returning clients, and follows the original discovery route—even if someone later books through the business website. The initial booked value matters; later checkout additions are excluded. It also says unlisting disables Fresha online booking channels. A direct link is not a way to erase an acquisition fee already earned. Accessed 16 November 2026.
| Approach | What you gain | What you take on |
|---|---|---|
| Marketplace-led | Discovery, reviews, familiar booking experience | Acquisition charges and platform conditions; service delivery remains yours |
| Branded web + existing booking SaaS | A clear direct journey with less build scope | Your own audience-building and content; check vendor charges and limits |
| Standalone branded app | Potential repeat tasks in one place, if guests need them | Build, updates, stores, support, integrations and acquisition |
| Hybrid | Discovery alongside a direct repeat journey | Attribution, permissions and consistent capacity across channels |
Start with a real price, not an invented app uplift
SACRA’s public price page lists three-hour general admission at AED 450 Monday–Thursday and AED 500 Friday–Sunday, plus an Oriental Hammam Ritual at AED 550 (accessed 16 November 2026). For illustration, assume 50% weekday admissions, 30% weekend admissions and 20% hammam appointments: an average AED 485. These are separate visit types, not an admission-plus-treatment package. Eligibility, inclusions and final prices need confirmation.
Assume those prices include 5% VAT, the business is VAT-registered and input VAT on eligible costs is recoverable. Revenue is then AED 461.90 per visit, not AED 485. This is a modelling assumption, not a tax determination. All costs below are VAT-exclusive where recoverable; irrecoverable VAT must be added. The fee calculation uses gross booked value by default; switching it to net value changes the result. Confirm the actual invoice base, caps and tax treatment.
| Input | Editable planning assumption |
|---|---|
| Average guest receipt / revenue excluding VAT | AED 485 / AED 461.90 |
| Variable fulfilment | AED 220: variable labour180, supplies25, utilities/laundry15 |
| Payment | 3% of gross + AED1 per completed visit, same on both channels |
| Direct-only extras | Rewards2% of net; unrecovered refunds/cancellations1% of net; handling AED5 |
| Acquisition fee for lost new marketplace guests | 20% of gross, minimumAED22, no cap modelled; NOT verified UAE terms |
| Moved visits | Returning visits only: no recurring acquisition fee to avoid |
| Mature monthly volumes low/base/high | Moved20/80/180; genuinely additional direct5/30/80 |
| Opportunity costs in each scenario | 5 new marketplace guests lost + 5 displaced/misattributed existing direct visits |
| Available capacity | 120 spare visits/month at relevant times; must validate staffing/slots |
After these costs, an additional direct visit contributes about AED 207.50. An existing returning marketplace visit contributes AED 226.35 under the equal-payment assumption. Moving it direct changes contribution by minus AED 18.86, because the scenario adds rewards, reserves and handling. With identical costs on both channels, migration alone contributes zero. Do not count the whole receipt as a saving.
What a smaller web journey and a custom app really cost
The following are public planning allowances, not Select Creatives quotes or private rates. Both options retain AED600/month for the existing booking vendor, AED100 CRM/email, AED100 messaging, AED1,000 campaign labour and AED1,000 acquisition/creative. No old fee is assumed cancelled. Message spend might fund roughly500 messages at an assumedAED0.20 each; actual Meta, provider and email charges vary. Do not add separate card fees when a vendor’s rate is already all-in.
| Cost | Branded web pilot | Custom app + Care |
|---|---|---|
| Frontend/configuration | 10,000 | 50,000 |
| Backend build | 0 | 20,000 |
| Integration | 5,000 | 15,000 |
| QA/security/acceptance | 2,000 | 10,000 |
| Launch/training/creative | 3,000 | 5,000 |
| Initial account provision | 0 | 457 |
| Prelaunch period + overhead | 1month ×500 | 3months ×500 |
| Total kickoff funding | 20,500 | 101,957 |
| Care + hosting + backend/month | 500 +100 +0 | 1,500 +300 +200 |
| All fixed costs/month | 3,400 | 4,800 |
| Annual account renewal from launch month13 | 0 | 365 |
A realistic ad hoc app-maintenance allowance of AED1,000/month reduces spending by AED500, rather than making upkeep free. It offers no assumed Care response commitment. Large repairs, store-rule changes and security incidents can exceed that allowance. Account provisions are estimates, not verified current store tariffs. The pilot must validate the booking supplier’s integration price and permission before committing.
The base case does not repay the investment
Adoption starts at 25%,35%,45%,55%,65%,75%,85%,90%, then100% for months9–12 and thereafter. The same demand is used for web and app: there is no app-specific uplift. Costs start at launch; prelaunch overhead is included in funding. Monthly benefits include moved-visit contribution changes, genuinely additional contribution, lost discovery and displaced direct trade. “First year” below means twelve months after launch, after initial funding. Payback is the first nonnegative cumulative month, without discounting.
| Option/scenario | Mature net/month AED | First-year net cash AED | Payback launch / kickoff |
|---|---|---|---|
| web / low | -4,424 | -70,259 | None≤120mo / None≤120mo |
| web / base | -368 | -34,769 | None≤120mo / None≤120mo |
| web / high | 8,121 | 39,511 | 7 / 8 |
| app / low | -5,854 | -168,516 | None≤120mo / None≤120mo |
| app / base | -1,798 | -133,026 | None≤120mo / None≤120mo |
| app / high | 6,691 | -58,746 | 21 / 24 |
| adhoc / low | -5,354 | -162,516 | None≤120mo / None≤120mo |
| adhoc / base | -1,298 | -127,026 | None≤120mo / None≤120mo |
| adhoc / high | 7,191 | -52,746 | 20 / 23 |
At base demand the custom app loses about AED1,798/month at maturity, and the web option loses about AED368. Neither pays back while those conditions persist. In the high case, the app recovers around month21 after launch, or month24 from kickoff; the web pilot around month7/8. These are conditional illustrations, not expected outcomes. High volumes need evidence and usable capacity.
What would have to be true?
Holding base migration and opportunity costs constant, the app needs about 39 additional direct visits per month at maturity to cover operating costs. To recover funding, the required mature additional visits are:
| Recovery horizon | From launch | From kickoff |
|---|---|---|
| 12 | 104 | 138 |
| 18 | 78 | 87 |
| 24 | 66 | 71 |
The 12-month kickoff target exceeds the assumed spare capacity after displacement, so it is not operationally feasible without changing capacity or economics. Each extra AED50 of variable fulfilment cost reduces contribution on incremental visits; it also changes the contribution of lost visits. Each10 additional direct visits adds roughlyAED2,075 before fixed costs at the default assumptions. AnotherAED1,000/month of operating cost needs roughly5 more incremental visits. If no new marketplace demand is lost, the base case improves by aboutAED647/month, not a recurring commission on every customer. A tax-exclusive commission base reduces the loss deduction; a vendor cap changes it again. Use the editable model, not rounded prose, for decisions.
Try the assumptions yourself
Change the volumes, costs and fee assumptions below. These are scenarios, not recommended terms. “Moved” means returning visits; use the controls to test equal costs and see why migration has no automatic fee saving. No information is submitted or stored by this calculator.
Spa direct-channel planner
Edit all model inputs
Option costs: AED except lead months
Own the relationship without creating another admin job
A guest could choose a service on your website, complete the existing booking flow, then receive a clear confirmation and an optional invitation to hear about relevant future visits. Keep service updates separate from marketing permission. A contact record does not grant unlimited promotional access, and it does not give you historical identities from another marketplace.
Useful segments might be service interests, last visit and stated preferences—not speculative health profiles. Test one helpful rebooking email or permissioned WhatsApp message. Budget the staff work, creative and delivery charges. App notifications need permission and repeated usefulness. Measure completed additional visits and net contribution, after campaign costs; do not assign an invented asset value to a list of names.
Fresha documents permission-controlled client exports, while card information cannot be exported. Its Data Connector is a one-way reporting integration, not evidence of an appointment-writing API. Get explicit supplier approval for booking changes, shared availability and identity matching. Accessed16November2026.
Keep the existing booking engine until the case says otherwise
SACRA’s current site already links to Flyby for booking and describes memberships, suites and services. No marketplace use or Flyby merchant fee is established here. A sensible review would begin with that working route and the operator’s own capacity and repeat-booking figures.
For comparison, Soloist advertises a branded booking page fromAED99/month under limited launch pricing and all-in online payments of4.5%; its page also shows regular pricing and team options. These are advertised vendor terms, not a validated fit for a bath club. Keep payment-on-site card costs in the budget even where the SaaS booking fee is zero. Existing-SaaS or branded-web options deserve a fit check before a custom build. Accessed16November2026.
Pilot one service-to-booking journey for four weeks, with the current supplier and a named operations owner. Confirm permitted integrations, usable appointment slots, refunds, staff scheduling, data access and support ownership. Measure completion, genuinely additional visits, cannibalisation, staff effort and permissioned rebooking. Do not move guests simply to make a migration chart look better.
A custom app is unsuitable when repeat tasks are rare, current booking tools work well, spare capacity is limited or demand cannot support the fixed costs. Ask Select Creatives for a business-case assessment. We can review the existing journey and compare a smaller web improvement with a custom build before you commit.
Model formulas, boundaries and refresh date
Modelv1,16November2026. Net revenue=gross/(1+VAT). Payment=gross×rate+fixed. Repeat marketplace contribution=net−variable fulfilment−payment. First marketplace contribution=repeat−acquisition fee, with editable gross/net base,min and cap. Direct contribution=repeat−net×(reward+reserve)−handling. Monthly contribution change=moved×(direct−repeat)+additional×direct−lost-new-marketplace×first−displaced×direct, all multiplied by adoption ramp. Net cash=contribution change−all fixed costs−account renewals. Cumulative starts negative by initial build/integration/QA/launch/accounts/prelaunch funding. Recovery targets solve for mature additional direct visits using cumulative ramp sums. All build, fulfilment, demand, subscription and marketing numbers are planning assumptions unless expressly attributed to public prices. No historic client identities, vendor discounts or cancelled fees assumed. No capacity expansion capex, financing, corporate tax, working-capital timing or terminal value; settlement delays, deposits, chargebacks and refunds require a fuller cash schedule. Reserve is an unrecovered loss allowance; do not also count the same loss in fulfilled visits. Volumes are completed visits; no-shows are excluded. Discounts must reduce realised basket value before modelling; actual acquisition invoice may follow initial booked amount. No marketplace commission is saved on returning visits under this model. App and web use identical demand. Refresh terms before a proposal and by14February2027 at latest. No confidential client rates or private margins used.


