Pilot access
Start with the right scope
There is no one-size-fits-all price list yet. A Hallify pilot starts with the workflows a venue needs to run first, then expands once the operating loop is proven.
Three ways to start
Three deliberate ways to start
Begin with live service, connect the whole operation, or plan a coordinated group rollout. Every path uses product capabilities available today.
01 · One venue
Service Core
For one venue that wants the guest journey and live service working as one.
- Reservations, waitlist, and guest context
- Floor, tables, and service sessions
- Orders, payments, and corrections
- Kitchen queue, courses, and ready signals
02 · Whole operation
Recommended
Connected Operations
For teams ready to connect service, kitchen, stock, people, and decisions in one operating loop.
- Everything in Service Core
- Menu, recipes, variants, and station routing
- Ingredients, stock, suppliers, and purchasing
- Staff, schedules, time, tips, and roles
- Analytics and operational attention
03 · Tailored rollout
Group Rollout
For multi-venue teams or complex openings that need a rollout built around how they actually work.
- Shared operating standards for each venue
- Roles, access, and accountability model
- Phased setup, data migration, and team onboarding
- Rollout partnership shaped around your sequence
Scope, not fine print
What shapes a Hallify pilot
Each package is a starting architecture. Final scope follows the workflows, setup work, and rollout sequence your team actually needs.
- 01
Implemented product areas
Every path is grounded in product areas available today: service, kitchen, menu, inventory, staff, analytics, and role-safe access.
- 02
Clear rollout boundaries
Integrations, hardware, partner work, and tailored rollout needs are discussed directly instead of being hidden behind broad promises.
- 03
Expansion after proof
Start with the workflows that matter now. Expand only after the team can run the first operating loop with confidence.
Before the pilot starts
Straight answers on scope, data migration, hardware, and what happens before a pilot begins.
Are these final prices?
No. These are early-access packages. Final pricing will be set after pilots prove the operating scope and rollout model.
What is included in a pilot?
A pilot should include the smallest complete workflow that can survive a real shift: service, permissions, kitchen or POS, and manager review.
Can existing data be moved in?
Pilot setup can include venue structure, menu, recipes, roles, stock categories, suppliers, and staff basics depending on scope.
Do you provide hardware?
The product is browser-based. Hardware planning can be part of the pilot if a venue wants tablets, cashier devices, or kitchen screens.