Not automatically. EL3AB first checks what your lounge uses and whether a supported connection is available. It may connect to the current system, work alongside it, or define another route in the written scope.
Frequently asked questions
Straight answers before the first meeting.
No separate setup or launch fee is advertised. Initial setup, launch, reasonable data transition, and agreed integration work are included when they appear in the signed scope.
Station count, number of locations, operating complexity, integrations, support coverage, and approved content work affect the ongoing workload. The exact amount is fixed in writing after the free consultation.
These are charges from independent providers, such as online-payment transaction fees, message delivery, domain renewal, extra online capacity, or an existing cafe-management license. EL3AB does not activate a paid provider without written approval.
The cafe remains responsible for its customer relationship and data. Access, processing responsibilities, retention, exports, and deletion are defined in the agreement and configured around operational need.
The production plan includes role-based access, secure sessions, protected admin routes, monitoring, backups, audit evidence, and an incident-response process. Controls are adjusted to the final hosting and integration setup.
Yes. The first release is scoped around a low-cost launch path. Any external service that creates a new fee is identified before activation and requires written approval.
The timeline depends on the current system, data quality, integrations, and staff availability. EL3AB confirms milestones only after discovery, then tests the complete operating flow before go-live.
EL3AB