Skip to content

IZI Club Launch Checklist: 30 Steps to Your First Session

Published: · Updated: (12 days ago)· IZI Team

IZI Club Launch Checklist: 30 Steps to Your First Session

Section titled “IZI Club Launch Checklist: 30 Steps to Your First Session”

This document is a route from an empty account to a hall running live sessions. Thirty steps are grouped into four phases: registration, setup, staff, and first shift. Each step is one concrete action; detailed CRM instructions are linked.

Completing all steps from scratch takes 5–7 working days for a small hall. A large hall — allow two weeks, most of the time goes to installing agents on each computer.


  • An IZI owner account (created in step 1)
  • A list of computers: how many machines, in which zones, their specs
  • A basic pricing decision: hourly rate, whether you need a night tariff
  • One or two staff members for the first shifts
  • Access to hall computers for installing the IZI client

Phase 1 — Registration and structure creation

Section titled “Phase 1 — Registration and structure creation”

Phase 2 — Hall setup: zones, devices, tariffs

Section titled “Phase 2 — Hall setup: zones, devices, tariffs”

Zones → devices → tariffs — strictly in this order. Tariffs are tied to zones; devices are assigned to zones.

  • Step 7. Decide on your zone structure: how you’ll divide the hall (VIP / Pro / Standard or custom names) → Devices, zones, and tariffs: key concepts
  • Step 8. Create zones in the CRM via Club Settings → ZonesZone setup
  • Step 9. Review zone layout: are machines correctly distributed, are zone names clear to the administrator → Zones overview
  • Step 10. Install the IZI client on the first hall computer using the IZI client installer — the agent that connects the machine to the CRM → Connecting your first PC
  • Step 11. Link the device to the club via UUID — the machine appears in the hall as a clickable tile → Connecting your first device
  • Step 12. Enable Wake-on-LAN for remote PC power-on without leaving the front desk → How to add a device
  • Step 13. Install the IZI client on all remaining computers — repeat steps 10–12 for each
  • Step 14. Assign each device to the correct zone — the hall should look like a real floor plan
  • Step 15. Add non-standard equipment manually: consoles, VR, simulators — managed from the CRM separately
  • Step 16. Create a basic hourly tariff for each zone — the minimum starter set → How to create your first tariff
  • Step 17. Add a discounted night tariff for low-load hours (if needed at launch)
  • Step 18. Set up a multipass — a prepaid hour package at a discount (can be added later)
  • Step 19. Review tariff schedules: when each tariff is active, no overlapping windows

  • Step 20. Review IZI’s role model: the only built-in staff role is Administrator. All other staff profiles — cashier, equipment manager, barista, etc. — are custom roles you create by choosing a name and selecting the exact permissions → Owner and administrator: permission differences
  • Step 21. Create custom roles for each staff profile in your club — e.g. a cashier with payment access only, or a barista with bar-only access → How to configure a custom role
  • Step 22. Invite your first administrator by email, assign a role and club → Inviting staff
  • Step 23. Add remaining employees — each with their own role and no excess permissions → Adding staff
  • Step 24. Verify each role has no excess permissions: someone handling only payments should not be able to change tariffs
  • Step 25. Create a starter bar catalog: water, energy drinks, snacks — minimum for day one → How to add products to the catalog
  • Step 26. Set up product categories and prices — full inventory can be completed later when you see real demand

Migration (if switching from another system)

Section titled “Migration (if switching from another system)”

  • Step 28. Run a test shift with no guests: open a shift under an admin account, start a test session on one computer, add a mock balance, ring up a bar item, close the shift → How to open and close a shift
  • Step 29. Train your staff: show the administrator how to start a session, accept payment, ring up the bar, and move a player to another computer — one hour on an empty hall is enough
  • Step 30. Open the first real shift — stay nearby on day one to quickly fix anything you didn’t anticipate: prices, tariff schedules, receipt text

After closing all 30 steps, the club is operationally ready. The next level is working with data:

After 1–2 weeks of real operation you’ll have enough data to:

Frequently asked questions

How long does it take to complete all 30 steps?

Basic setup (steps 1–20) takes several hours of focused work. Full cycle to first shift with staff — 5–7 working days. This depends on hall size and team count: connecting 50 machines takes longer than 10.

Must the steps be done strictly in order?

Phases are strictly sequential: you can't create a tariff without zones, you can't connect a device without a club. Within a phase, some steps can be done in parallel — for example, devices and tariffs are configured independently.

Can I skip the test shift?

Not recommended. A test shift on an empty hall takes less than an hour and surfaces typical issues: wrong zones, tariff without a schedule, role with too many or too few permissions. A mistake on the first real guest costs more.

What if the club was already running on another system?

See step 26 — data import. If you're migrating from Langame, there's a dedicated guide with the sequence for transferring clients and balances. Run IZI in parallel with the old system for at least one shift before fully switching.

Do I need to create all tariffs right away?

No. Minimum: 1–2 hourly tariffs per zone. Add others (night, multipass, promo) after the first weeks, when you see real demand.

What if there are multiple clubs in one organization?

Organization and roles are shared across the entire network. Run through the device, zone, and tariff steps separately for each club. Roles and employees need to be configured once and can be reused.

When should I connect the player mobile app?

After the first two weeks of real operation. The app makes sense when players already have history, balances, and reasons to return. Earlier is not a priority.

What if a device doesn't appear in the system after installing the IZI client?

Check: the computer is on the same network as the server, the IZI client is installed and running, and the device UUID is entered correctly. If that doesn't help — contact support with client logs.