VenueIQ

The business problem

What was going wrong

A venue generates data in half a dozen places — the gaming system, the point of sale, the rostering tool, the compliance folder — and none of it meets. Managers spend the first hour of the day rebuilding yesterday by hand, and the patterns that matter (a quiet Tuesday that correlates with weather, a late-night trend, a compliance task nobody closed out) are invisible until somebody goes looking.

The solution

What we proposed

VenueIQ ingests those feeds into a single tenant-scoped platform and presents them as dashboards a duty manager can read in thirty seconds. An on-premises edge collector handles the systems that cannot reach the cloud directly, buffering locally when the connection drops. A rules engine correlates the feeds and surfaces suggested actions with a confidence score, so the platform explains its reasoning rather than issuing verdicts.

Technology

What it is built on

• Next.js 16 App Router
• React 19
• TypeScript
• PostgreSQL with Prisma
• Auth.js v5 with RBAC
• Zod validation
• Node.js edge collector service
• Recharts

1. 01

   Discover

   Mapped the systems a venue already runs and what each one can export.

2. 02

   Plan

   Modelled a multi-tenant schema with strict per-venue separation.

3. 03

   Design

   Designed dashboards around the duty manager's first ten minutes of a shift.

4. 04

   Build

   Built the cloud application and the edge ingestion service in parallel.

5. 05

   Test

   Ongoing testing of ingestion resilience, permissions and tenant isolation.