HEVGAVTalk to HEVGAV

How We Work

Know exactly what will be delivered before Go-Live — and what support comes after

HEVGAV starts with how your restaurant actually works, then agrees what will be delivered, how it will run, what your restaurant needs to prepare and who is responsible for what before implementation begins. After Go-Live, support, maintenance and new work remain clearly separated. You deal directly with the person responsible for the technical delivery.

  1. 01Understand
  2. 02Choose
  3. 03Agree
  4. 04Deploy
  5. 05Enable
  6. 06Support

  1. 01 Understand

    Start with how your restaurant actually works

    We look at how the restaurant operates today — or, for a new venue, how it is intended to operate — before recommending the system or delivery path.

    • How you serve guests
    • What systems you use today
    • How tables and orders move through the restaurant
    • How the kitchen or preparation flow works
    • What infrastructure is already in place
    • Where the operation slows down or becomes difficult
    • What you want to improve

  2. 02 Choose

    Choose the right path before implementation starts

    If your needs fit HEVGAV Platform, we keep the project focused around the standard product. If they do not, we recommend Restaurant Systems Engineering rather than stretching the Platform beyond what it was designed to do.

  3. What we’re delivering
    How it will run
    Who is responsible for what
    What your restaurant needs to have ready
    What needs a separate agreement

    03 Agree

    Agree exactly what will be delivered

    Before implementation, we agree what the system will cover, how it will run, who is responsible for what, what your restaurant needs to have ready and what requires a separate agreement.

    Clear scope means you know what is included, what is separate and who is responsible before implementation begins.

  4. 04 Deploy

    Prepare and deploy for the agreed restaurant setup

    We configure and deploy the agreed system for your restaurant. Standard HEVGAV Platform deployments use Local Resilience or Private Hosted. Non-standard setups are assessed separately through Restaurant Systems Engineering.

  5. 05 Enable

    Prepare your team to operate the system

    We prepare the staff covered by the agreed onboarding scope to use the system confidently in the restaurant’s real operating flow. What training and enablement are included is defined before Go-Live.

  6. 06 Support

    Go live with the support period already defined

    The standard HEVGAV Platform includes a 60-Day Limited Post-Go-Live Support period beginning on signed Go-Live Acceptance. Maintenance is separate from the 60-day support period, so the two are not presented as the same service.

Know what is support, what is maintenance and what counts as new work

Support

Help using, configuring or diagnosing the delivered system within the agreed support terms.

Maintenance

Covered software maintenance, security and compatibility updates for the supported version under the applicable entitlement or plan.

Change Request

New work that changes what the delivered system was originally agreed to do — such as a workflow, report, design, integration or scope change.

Keeping these boundaries separate makes it easier to see what is included after Go-Live and what needs a separate agreement.

Tell us how your restaurant works. We’ll help you choose the right path.

Tell us what is working today, where the operation becomes difficult and what you want to improve. We’ll first determine whether HEVGAV Platform fits your restaurant or whether Restaurant Systems Engineering is the better route.

Talk to HEVGAV