<- BACK TO WORK DIRECTORY
● IN FLIGHT
New Project

CueSphere

A SaaS platform for billiards and gaming cafes — session billing, customer records, and payments in one dashboard.

Next.jsReactNode.jsMongoDBPayment Integration
arch://cuesphere
billed by the minute
built for the counter
01 // ORIGIN & CONTEXT

The Backstory

Why this system was engineered, what existed previously, and the core operational bottlenecks it solves.

CueSphere is a SaaS app built for billiards and gaming cafe businesses — helping owners run day-to-day operations: tracking table/session usage, managing customer records, and handling payments, all in one platform.

Gaming cafes run on razor-thin per-minute margins, so the product had to make the most time-sensitive job — starting, tracking, and billing a table session — as close to zero-friction as possible.

02 // HUD.TELEMETRY & BENCHMARKS100% PRODUCTION VERIFIED
● ACTIVE
In Build
Current Phase
● ACTIVE
Automated
Session Billing
● ACTIVE
Integrated
Payments
● ACTIVE
Centralized
Customer Records
03 // PROBLEM SPACE & ARCHITECTURAL REMEDIATION
[DEFECTS & BOTTLENECKS]

The Challenge

  • 01.Cafe owners were tracking table time, customer records, and payments manually or across disconnected tools.
  • 02.No easy way to see business performance (usage, revenue) at a glance.
  • 03.Payment collection and session billing needed to be fast and accurate during busy hours.
[ENGINEERED REMEDIATION]

The Solution

  • 01.Building a session-tracking system for tables/games with start/stop timers and automatic billing.
  • 02.Centralizing customer and business records in one dashboard.
  • 03.Integrating payments so billing and collection happen in the same flow as session tracking.
04 // SYSTEM ARCHITECTURE

Modular Capabilities

MODULE 01
Auto time-based billing

Session Tracking

Start/stop a table and the bill calculates itself.

MODULE 02
Centralized management

Customer Records

Repeat customers and their history, in one place.

MODULE 03
Collect in-flow

Payment Integration

Close a session and take payment without switching apps.

MODULE 04
Day-to-day operations view

Owner Dashboard

Tables, revenue, and activity at a glance.

MODULE 05
Track several sessions at once

Multi-Table Support

Built for cafes running multiple tables in parallel.

MODULE 06
Usage and revenue at a glance

Business Snapshot

Daily/weekly performance without manual tallying.

05 // ENGINEERING SPEC

Technical Deep Dive

~/architecture/spec.ts
TYPESCRIPT 5.x
01.

Session timers are server-authoritative (not just a client-side clock), so a closed browser tab or dropped connection doesn't lose billing accuracy — the server tracks elapsed time independently.

02.

Billing rates are configurable per table/game type, since a cafe might charge differently for a pool table versus a console station, without needing separate systems for each.

03.

Payment collection is built to close a session and settle payment in the same action, minimizing the steps between "game over" and "paid" during busy hours when speed at the counter matters most.

06 // INTERFACE SCHEMATICS

Project Gallery

07 // VERIFIED IMPACT

Business & Velocity Value

Direct outcomes, architecture speedups, and developer feedback delivered in production.

Built for the counter, not the back office.
08 // ENGINEERING LESSONS

Post-Mortem Takeaways

TAKEAWAY 01

Speed at the Counter

Time-based billing needs to be dead simple and fast during peak hours.

TAKEAWAY 02

Design for Owners

Non-technical owner audience means a minimal interface, not a feature-heavy one.

TAKEAWAY 03

One Flow, Not Three Tools

Bundling records, sessions, and payments removes the app-switching owners were doing before.

🔒
Access Note

In progress — client SaaS project. Links are placeholders pending clearance to share once available.

● OPEN FOR ENGINEERING PROJECTS

Have a similar project in mind?

Let's build a scalable, high-performance solution from architecture to deployment.