Three Core Layers.
One Intelligence Layer.

Sports Facility Hackers is the operator-growth layer. It gives facility owners and league operators the strategy, implementation sequence, templates, peer community, and accountability needed to modernize a sports business.

The book teaches the revenue moves. The Founders Cohort turns those moves into implementation sprints. Future Operator Academy and certification paths can train front-desk staff, scorers, officials, league teams, sponsor sellers, and facility managers against one operating standard.

• Playbook, calculators, templates, and launch checklists.
• Founders implementation sprints and office hours.
• Operator case reviews and permissioned benchmark learning.
• Staff training, certification, and role-based operating standards.

BALL OS is the verified sports operating system. It coordinates courts, reservations, sessions, leagues, crews, scoring, scoreboards, game records, payments, media surfaces, sponsor inventory, and operational follow-up.

Its deepest advantage is not the number of features. It is the connected event record: one game or court session can link the reservation, participants, officials, scorer actions, scoreboard, statistics, video markers, sponsor delivery, payments, and public updates without creating competing sources of truth.

The migration promise is practical: connect first, prove value, then replace unnecessary tools over time.

BALLNetwork is the public identity and demand layer. It is where players, teams, facilities, leagues, coaches, officials, scorers, providers, families, and fans can discover one another and participate.

Player Passports preserve reusable identity and approved game history. Facility and league profiles act as public storefronts. Discovery, alerts, waitlists, open-gym demand, substitute-player matching, team needs, and BALLCrew opportunities can turn network activity into real bookings, registrations, staffing, and attendance.

BALLNetwork should not become another static directory. Its job is to create trusted identity and measurable demand that BALL OS can serve.

FRIDAY is not a replacement for the three core layers. It is the intelligence layer across them. It reads the playbook, understands permissioned operational data, and helps the authorized user identify the next best action.

• Operator Coach: daily command briefs, implementation guidance, and prioritized next steps.
• Revenue Opportunity Coach: empty court hours, waitlist demand, inactive customers, and unsold sponsor inventory.
• Facility Concierge: a permissioned voice or chat assistant that answers questions, captures leads, and supports booking workflows.
• League Launch Coach: division design, registration, drafting, scheduling, staffing, game day, and season review.
• Team Coach Copilot — future: approved game summaries, player trends, film markers, and development insights without pretending to replace the human coach.

FRIDAY remains private to Francis today except where a specific customer-facing workflow is deliberately released. Any financial, scheduling, messaging, or record-changing action requires authentication, tenancy controls, role permissions, approval rules, idempotency, and an immutable action log.

The verified results return to BALLNetwork, strengthening Player Passports, facility profiles, league history, sponsor proof, and future discovery. The operating lessons return to Sports Facility Hackers, improving the playbook for the next operator. That is the compounding loop.