Sector — horeca

Run your locations, your reservations, and your public presence from one workspace.

For Dutch horeca operators with multi-location structures and SLA-shaped service obligations: bookings, content marketing, newsletter, GDPR-clean guest data, recurring location compliance — running on one governed workspace, in EN/NL/AR.

What you'll actually run on iSystem

Booking Engine — horeca adapter template

Public reservation flow shaped for table service: party size, time window, location selection (multi-venue), special requests, anti-abuse honeypot + form-start timing. Reservation lifecycle, status history, notifications. Not a Calendly clone — a horeca-shaped flow built into the same workspace.

Multi-location facility structures + SLA tracking

One workspace, multiple venues: each location has its own facility record, recurring tasks (cleaning logs, equipment checks, supplier orders), SLA compliance percentage, location-level breakdown. Operations leads see across the portfolio; venue managers see only their own location via role-gated access.

Content Studio + Newsletter for guest acquisition

Drafts in five narrative styles for menu launches, seasonal events, chef profiles, location-specific stories. Author profiles for chefs and managers with bylines. Newsletter on Resend with audiences segmented by location preference. Workspace popups offer a newsletter signup tied to a discounted-first-visit booking — exit-intent on the menu page works.

Page Builder + EN/NL/AR localization

Constrained visual page builder: hero, location lists, menu blocks, FAQ, contact. Brand-safe — managers can update a seasonal menu or a holiday-hours block without breaking the design. Sticky locale preference for international guests, RTL-clean Arabic surface for MENA visitors.

GDPR + governed AI for guest data

Reservation data and contact lists sit on a GDPR-aware base: workspace-scoped privacy settings, retention windows, anti-abuse logging on every public form. AI credit metering with append-only ledger means menu drafts, chef-bio drafts, and review-response drafts are auditable — and a manager can roll back any AI-suggested edit before it goes live.

Proof — honest about what we have and don't have

There is no published anonymized iSystem horeca case study yet. We don't fabricate proof points. What does exist: the platform is operational, the multi-location facility structures and SLA tracking are shipped capabilities (verifiable in the public dashboard at isystem.ai itself), the booking engine ships with a horeca-specific adapter template, and Hossam can demonstrate the full horeca operator workflow live in a paid €140 online advisory consultation. When a horeca operator deploys and consents to publication, an anonymized case study lands here — same structure as the legal-firm case study below.

See the legal case study →

What this replaces

Replaces: ResDiary or similar reservation system · Mailchimp · WordPress + freelance content writer · TripAdvisor / Google review monitoring done manually · agency retainer for Instagram and content production · spreadsheet-based recurring task tracking across locations.

Pricing

Basic from €2,500–€7,500 setup + €99/month — for single-location operators wanting a structured digital presence and reservations. Pro from €2,500–€7,500 setup + €299–€499/month (metered AI) — for multi-location operators running ongoing content, newsletter, SLA tracking, and Pro booking flows.

Basic vs Pro →

iSystem is not for every horeca operator

  • Single-location cafés that need only a menu and an Instagram link — a one-page site is cheaper
  • High-volume chains with PMS / POS integration as a hard requirement (Lightspeed / Mews / Toast category)
  • Operators wanting full delivery-marketplace integration (Uber Eats / Thuisbezorgd backend)
  • Owners with no interest in publishing public content — the SEO + content moat doesn't apply
Book a paid €140 online advisory consultation with Hossam — we'll walk through how iSystem would run a horeca operator of your shape specifically