Viramos
A multi-role regatta operating system connecting sailors, judges, clubs and associations across Latin America.
2025
Role
Product Designer
Duration
11 months
Team
Product Owner, Scrum Master (part-time), Designer (me), Engineering team, QC
Viramos is a regatta management SaaS operative system used by sailing clubs and championship organizers across multiple countries.
After launching an initial no-code MVP, it became clear that the system architecture could not support the operational complexity of large-scale championships.
The project evolved into a full platform rebuild designed for scalability, supporting multi-stage competitions, regulatory workflows, and role-based operations.
My Responsibilities
Product architecture
Defined the championship lifecycle model, domain structure, and scalable interaction patterns.
Workflow re-architecture
Re-structured complex competition flows into modular, role-aware systems.
Role & permission model
Designed flexible role-based access layers to support overlapping operational responsibilities.
Complete UI system
Redesigned core screens and evolved the UI component system aligned with engineering constraints.
Field research & domain immersion
Conducted on-site research during live championship events to validate operational realities.
Structural rebuild strategy
Played a key role in transitioning from MVP limitations to a scalable system architecture.
Product architecture
Defined the championship lifecycle model, domain structure, and scalable interaction patterns.
Workflow re-architecture
Re-structured complex competition flows into modular, role-aware systems.
Role & permission model
Designed flexible role-based access layers to support overlapping operational responsibilities.
Complete UI system
Redesigned core screens and evolved the UI component system aligned with engineering constraints.
Field research & domain immersion
Conducted on-site research during live championship events to validate operational realities.
Structural rebuild strategy
Played a key role in transitioning from MVP limitations to a scalable system architecture.
The Opportunity
Regattas in Latin America relied on disconnected systems and manual coordination, leading to operational inefficiencies and inconsistent user experiences. The opportunity was to build a regatta operating system — a unified digital layer supporting the entire championship lifecycle, from inscription to results.
Early validation (No-code phase)
Testing the operating model
Viramos began as a no-code MVP (Bubble), validating inscriptions, payments, requests, and results.
Signal for re-architecture
Adoption confirmed value, but scale demanded a structural rebuild.
Context immersion — SIVI (Brazil)
SIVI, the largest sailing championship in Latin America, became a live stress test for the product at scale. On-site immersion by traveling to Brazil and being part of the tournament exposed the operational realities that remote interviews alone could not surface.
Mobile-first reality
Sailors relied entirely on mobile access while moving between docks and race areas. This confirmed that desktop assumptions were irrelevant for this user role.
Formal regulatory workflows
Judges operated within strict procedural frameworks. Protests, hearings, and rulings followed defined regulatory steps that required structured information, traceability, and clear communication between parties.
Real-time operational pressure
Administrative teams managed time-sensitive tasks like inscriptions, updates, and communications while the competition was ongoing. Speed, clarity, and information hierarchy became critical.
Role definition under real conditions
SIVI exposed the full range of operational roles involved in a championship. Each role carried distinct permissions and decision-making authority. Understanding these boundaries — and how roles intersected during live competition — reshaped the system architecture.
Inflection Point
Product–market fit was validated. The architecture was not. The no-code foundation could not sustain the scale, role complexity, and performance demands of large championships. Viramos needed to evolve into dependable operational infrastructure.
Re-architecting for scale
We rebuilt Viramos in Next.js with a system-first approach focused on clarity, scalability, and operational reliability.
Role-based architecture
Roles were redefined as permission layers rather than user types. Interactions were mapped to explicit authority and visibility rules.
Modular championship engine
Forms became the system core. Inscriptions, disputes, and results were structured as reusable modules to support multiple championship configurations.
Mobile-first redesign
Primary sailor workflows were optimized for dock-side usage, improving hierarchy, speed, and accessibility.
Design system aligned with development
A shadcn-based design system ensured parity between UI components and frontend implementation, reducing friction and accelerating delivery.
Championship configuration (Clubs)
Structured form architecture enables consistent setup across categories while reducing administrative errors.
- Modular championship creation aligned with regulatory requirements
- Centralized management of participants, requests, and results
- Permission-based access for internal club roles
Protest & hearing flow (Judges)
Regulatory workflows formalized into traceable, structured interactions aligned with real-world procedures.
- Guided protest submission with structured data inputs
- Searchable participant references (name or sail number)
- Traceable rulings with controlled visibility across roles
Dock-side mobile experience (Sailors)
Mobile-first interface designed for real-time usage during competition.
- Simplified access to results, notices, and updates
- Reduced navigation depth for high-attention moments
- Responsive layouts optimized for on-the-move usage
Impact
Viramos evolved from MVP to operational infrastructure adopted by leading clubs across Latin America.
Viramos operates today as the digital backbone for competitive sailing championships in the region.
2025 metrics
