Locations
How many restaurants are included in the first rollout and how they are grouped.
Pilot pricing
Start with a scoped pilot. Expand when it works.
We price the first rollout around the locations, team roles, guest feedback workflow, and review scope involved. You see the scope before you commit.
The first rollout
A working reputation system, not a long software evaluation.
The pilot should be large enough to test the real operating workflow and small enough to fix quickly with the team using it.
See how groups roll it outIncluded in scope
Restaurant group pilot
- A defined group of restaurant locations
- Branded, location-linked guest feedback flow
- Alert routing and named follow-up owners
- Head-office and location-level operating views
- A working review-management scope agreed before launch
- Pilot review with the team before any expansion
What shapes the price
Four practical variables. No mystery package.
The proposal should be easy to read because the rollout itself should be easy to understand.
Team structure
The head-office, regional, and location roles that need access and alerts.
Feedback workflow
The guest touchpoints, escalation rules, and follow-up process being configured.
Review scope
The public review sources, approval process, and response workflow included in the pilot.
The decision path
Know the scope before the invoice.
Map the current process
Locations, team roles, guest touchpoints, review sources, and where follow-up breaks today.
Define the pilot
A written location and feature scope, the people involved, and what the team will evaluate.
Agree the commercial terms
The price and pilot review point are settled before configuration starts.
Pricing questions
Plain answers while the product is in pilot.
Why is there no fixed public price yet?+
Breeze is in a focused pilot stage. The cost depends on the number of locations and the workflow being configured. We agree the scope and price before any work starts.
Does a pilot require every location?+
No. The better first step is usually a representative set of locations with a team that can use the workflow and give clear feedback.
Is there a long-term commitment?+
The pilot has an agreed scope and review point. Expansion is a separate decision based on whether the workflow is useful to the restaurant group.
What do we need to prepare?+
A location list, the people who own guest follow-up, and a short view of the current feedback and review process are enough for the first discussion.
Get a real scope
Tell us how your group works. We will price the first rollout.
No generic package or forced estate-wide commitment. Just the locations and workflow needed to test Breeze properly.
Discuss your pilot