Case Study: Digital Ecosystem for Future Beach Volleyball School
From product and UI design to an automated ERP with role-based access.
Maksim Ermilov
WAPP founder · product & architecture
Nastya
Project manager
Zhenya
QA engineer
Dima
Full-stack & backend developer
Gosha
Designer
About the Project
Future is a network of beach volleyball schools in Moscow. The goal was a deeply customized service that automates the full customer journey—from the first ad click to the receipt for the 10th membership package.
Tech stack: Laravel + Filament (backend/admin), React + Tailwind (portal frontends).
Effort: ~500 person-hours, including multiple iterations, refactors, and feature expansion.
1. Product and UI/UX Design
We started with business logic and UX, not code. The interface had to work equally well for a parent enrolling a child and for a coach on the sand.
Design and Retouching:
We ran a full graphics cycle, including deep retouching of coach and venue photos. Details matter: custom ball icons, strict typography, and a clean UI.
Copy and Tone:
Landing copy drops clichés. Only facts: three branches, coach credentials, and transparent pricing.
2. Personal Portals: Three Sides of One System
We built three independent React interfaces that talk seamlessly to the Laravel-backed database.
Student & Parent Portal:
Digital attendance diary with remaining sessions, payment history, and progress. Includes “freezes” and quick notifications.
Coach Portal:
Mobile-first UI for coaches: one-tap attendance, schedules for their groups, and parent contacts for emergencies.
Admin (Filament):
Owner control room: role models (who sees what), tariff editing, and new branches.
3. Financial Core and 54-FZ Automation
We built a resilient payments stack—no more manual reconciliations or spreadsheets.
Payments:
YuKassa integration with modern payment methods.
Fiscalization:
Automatic receipts via Atol Online cloud cash register.
Reporting:
Data flows to Kontur OFD and is mirrored for tax reporting.
Email:
After payment, clients get confirmation and the fiscal receipt—on-brand for the school.
4. Architecture and Scaling
The system is designed to stay solid for years.
No Hard Ceiling:
Current architecture can absorb 10, 50, or 100 new branches without a rewrite. Students and coaches scale with server capacity—which is easy to grow.
Flexible Rules:
We split sessions between “sand” and “strength work at CSKA” with different pricing and accounting logic.
5. Behind the Scenes: Depth and Refactoring
This project stood out for the volume of invisible but critical work.
Iterative Delivery:
We reworked portal flows multiple times at no extra charge to nail the logic—for example, membership rules when attendance policies changed.
Technical Rigor:
Frontends are Tailwind-first for clean markup and fast loads on mobile.
Full Handover:
We didn’t just ship code: corporate mail, staff training, and stable wiring for all external services.
Results in Numbers
~500
hours of development and polish
3
autonomous branches managed from one console
100%
automation of receipts and reporting
0
lost payments or attendances
Need a similar ecosystem—booking, payments, reporting, and roles? Let’s shape the architecture for your case.