CUEFIELDS · FOUNDER CASE STUDY
Building the product system behind competitive cue sports.
CueFields is a full-stack SaaS product for snooker and pool. I conceived the vision and built the connected foundation behind matches, scoring, progression, analytics, subscriptions and venue experiences.
01 — PRODUCT THESIS
A match should become more than a score that disappears when players leave the table.
Players lacked a persistent performance history, a shared progression model and a consistent digital experience across clubs. Scores existed in the moment but rarely became useful evidence of improvement.
I designed CueFields to connect the full journey: capture a real match accurately, turn it into trusted performance data, translate that data into rankings and insight, then give the player a reason to return.
02 — HOW THE PRODUCT WORKS
Every experience begins with one source of truth: the match.
Create, score and validate
Players move from invitation to frame-by-frame scoring and a traceable final result.
Turn events into insight
Match history powers performance ratings, matchup analysis and personal patterns.
Make improvement visible
Leagues, rankings, reports and achievements create a continuous competitive journey.
03 — THREE STRUCTURING DECISIONS
The choices that made CueFields a product system rather than a scoring app.
MODEL THE SPORT FIRST
Match → Frame → Break as the domain backbone.
I avoided building scoring as screen-level calculations. Match states, frame resolution, breaks, fouls and result validation were modeled as deterministic domain behavior.
Result: UX, APIs and analytics derive from the same rules instead of recreating the sport differently in every module.MAKE PROGRESSION MEANINGFUL
Rank performance, not participation alone.
I designed Bronze-to-Platinum progression with inputs such as opponent level, match difficulty, result and scoring patterns, supported by anti-boosting constraints.
Result: rankings can communicate competitive legitimacy while giving players visible milestones.MONETIZATION AS PRODUCT BEHAVIOR
Capabilities belong to plans—not just prices.
Free, Basic, Premium and Ultimate are defined through capability matrices governing match features, analytics, limits, eligibility and lifecycle actions.
Result: subscriptions remain consistent across UX, permissions, backend behavior and notifications.04 — THE PRODUCT EXPERIENCE
From arranging a match to understanding what it changed.
Fast when play is happening
Mobile-first flows reduce friction across invitations, scoring, edits and result validation.
Clear after the match ends
The result feeds ranking, league position, best breaks, reports and achievement progress.
Controlled when disputes occur
Administrative experiences support player oversight, league management and disputed-result review.
05 — PERFORMANCE, RETENTION & MONETIZATION
Use the same match data to create insight, motivation and a viable product model.
Performance rating
A proprietary signal summarizing player skill and consistency across valid match evidence.
Matchup intelligence
Wins, losses, historic sequences, dominance and opponent-specific patterns.
Personal insight
Nemesis, favorite opponent, victory margin, consistency and pressure-response signals.
06 — PLATFORM & TECHNICAL DEPTH
I stayed accountable from domain model to deployment.
Definition
Vision, roadmap, journeys, business rules, monetization and go-to-market.
Interaction
Mobile-first match flows, progressive disclosure, premium gating and admin UX.
Architecture
Domain states, real-time APIs, caching, background jobs and event-driven behavior.
Operations
Quality, releases, CI/CD, infrastructure, monitoring and continuous refinement.
Technical deep diveMatch and scoring engine+
The engine models creation, invitations, Pending → Active → Completed → Disputed states, edit constraints, plan restrictions, conflict scenarios, fouls, break calculation, frame and match resolution, best-break tracking and result validation.
Technical deep diveNotifications and cross-module events+
A unified event model connects invitations, responses, results, plan activation, upgrade validation and progression. Each event retains the context required to return the user to the relevant match, player, plan or state.
Technical deep diveTechnology foundation+
NestJS, Node.js, PostgreSQL, Prisma, Redis and BullMQ support the backend foundation; React, Next.js, TypeScript and Chakra UI support product experiences; Docker, Nginx, CI/CD, VPS deployment, monitoring and logging support delivery.
07 — OWNERSHIP & STATUS
A founder case study grounded in what has actually been built.
I owned the product vision, domain and functional architecture, UX logic, business rules, engineering delivery, quality, releases, reliability, branding and go-to-market preparation.
One domain model connecting scoring, competition, analytics, plans and engagement.
A real product foundation across player experience, admin control and venue integrations.
Retention and monetization designed into the same product behavior.
The CueFields core platform, rules and product flows have been designed and built. Broader commercial and national rollout remains in progress; future extensions are product direction rather than delivered outcomes.
08 — WHAT I TOOK FORWARD
Great products become simpler to use because their internal rules are explicit.
CueFields strengthened my ability to move between vision, detailed domain logic, user experience and technical delivery without treating them as separate responsibilities.
- Model the domain before designing isolated screens.
- Use deterministic rules to create trust and engineering clarity.
- Connect engagement mechanics to genuine user value.
- Design monetization as part of product architecture.
- Build foundations that can evolve without losing coherence.
WORK WITH ME
Need to turn a complex domain into one coherent product?
Let’s discuss the rules, experiences and systems that will make it work.
Start a conversation ↗