Looty Pool

Overview

Looty Pool is a production web application for people who want to play lottery pools together without managing the process in spreadsheets, group chats, or informal side agreements. The product is part of the Looty Ecosystem and sits on the community side of that portfolio.

Live site: lootypool.com.

The Problem

Group lottery play is simple in conversation and messy in practice. Someone has to collect money, keep a list of members, buy tickets, record what was purchased, and communicate before each drawing. When that work lives in texts and shared docs, it is easy to lose track of who is in, what was bought, and what happens next.

The product problem was not “make a lottery more exciting.” It was: make group play easier to organize, easier to inspect, and easier to repeat.

The Product Vision

The vision was a centralized platform where members can join available pools or participate in private pools with friends, family, or coworkers. Upcoming drawings, ticket information, and pool activity should be visible from one place instead of being reconstructed after the fact.

My Role

I founded and built Looty Pool as a full-stack product. That includes product strategy, architecture, development, security, operations, and ongoing growth. The same pattern shows up across Looty: I stay close to both the user problem and the systems that have to keep working after launch.

Architecture & Technology

Looty Pool is a web application built with Next.js, React, Tailwind CSS, Node.js, and Firebase. That stack supports a product that needs authenticated users, persistent pool data, and workflows that change around drawings and purchases.

Key Product Capabilities

• Public and private lottery pools
• Real-time pool and drawing management
• Secure payment and purchase workflows
• Centralized ticket and pool activity access

Engineering / Product Challenges

The hard parts are operational, not decorative. Public and private pools have different membership rules. Drawings introduce time-sensitive state. Payments have to be trustworthy. Ticket records have to remain inspectable after the purchase moment has passed. Those constraints shaped the product more than any visual treatment.

Security, Scalability & Reliability

Because the platform handles membership, purchases, and pool records, security is part of the product design: authentication, payment workflows, and access to activity that members should be able to review. Reliability matters for the same reason — a pool that cannot be trusted at drawing time is not a product people will use twice.

What I Learned / How the Product Evolved

Building Looty Pool reinforced a lesson from enterprise work: people will forgive a missing flourish, but they will not forgive ambiguity around money, membership, or records. The product evolved toward clearer pool states and a more centralized view of activity rather than adding novelty for its own sake.

Current Direction

Looty Pool remains the community product in the ecosystem. The direction is to keep group play organized and transparent, and to stay connected to the broader Looty family — including the charitable side represented by Looty Foundation. More of that portfolio is on the ecosystem overview and in other case studies.