FUTVIA

Building a platform that streamlines the path from amateur and youth football to professional opportunity

FutVia is a platform designed to help amateur and youth football players move more clearly and credibly toward professional opportunity. It gives players a structured way to present who they are, what they can do, and why they should be considered, while helping clubs, scouts, leagues, and agents identify relevant talent with more context and less noise.

It addresses a structural gap in amateur and youth football. Many players have ambition, discipline, and proof of talent, but no clear way to present themselves beyond scattered videos, informal contacts, and inconsistent opportunities. On the other side, decision-makers often receive fragmented, low-signal information that makes serious evaluation difficult.

FutVia is not a social platform for players. It is a discovery and professionalization layer designed to improve the odds that talent is seen, assessed, and connected to the right opportunity.

02 // My Role

SYSTEM OWNERSHIP ACROSS FUNCTIONS

Scope of ownership

  • Product strategy and ecosystem framing
  • User research and interview synthesis
  • MVP definition and feature prioritization
  • Information architecture and content structure
  • UX writing and profile flow design
  • Trust, consent, and moderation logic
  • Operations model and release thinking
  • Stack selection, implementation direction, and QA

Cross-Functional Scope

In a larger team, this scope would likely be distributed across:

Product Design Research Operations Legal Engineering

03 // Current Stage

LIVE SYSTEM, EARLY STAGE

FutVia is a live early-stage product with functional player onboarding, moderation workflows, visibility controls, and lead intake infrastructure.

This matters because FutVia already behaves like a real operating product: collecting data, supporting workflows, and enabling controlled discovery through live system logic.

At this stage, the product already supports:

  • Player account creation and profile submission
  • Structured player data capture in the database
  • Moderation and publication control for player profiles
  • Structured interest capture from clubs, scouts, agents, and related organizations
  • Automated storage of new users and inbound leads in the database
  • Superadmin control over review, publication, and lead handling

04 // Market and Ecosystem Context

THE MARKET AND ECOSYSTEM CONTEXT

Discovery in amateur and youth football is fragmented, informal, and difficult to trust.

Players and families often hear about opportunities through Facebook, WhatsApp, local contacts, and loosely structured networks, with limited clarity on whether an opportunity is legitimate, safe, serious, or worth the financial and emotional cost. The issue is not a lack of talent. It is a lack of structure, trust, and clear pathways.

On the player side, there is rarely a credible and professional way to present trajectory, readiness, and proof. On the evaluator side, clubs, scouts, leagues, and agents do not simply need more profiles. They need cleaner intake, clearer filtering, stronger signal, and less operational noise.

The real problem is not visibility alone. It is the absence of structured, trustworthy visibility.

For minors, the system becomes even more sensitive. Families are part of the decision process, and they evaluate legitimacy, transport, safety, seriousness, and risk alongside football potential. Any product in this space has to support ambition and trust at the same time.

Product framing

The key question is not how to digitize football discovery end to end, but what product layer can create real value early by improving trust, signal quality, and operational clarity across the discovery process.

05 // Product Thesis

PRODUCT THESIS

My thesis is that FutVia does not need to solve football discovery end to end in order to create value. It only needs to solve one critical layer with enough clarity and discipline to improve how players enter the system, how profiles are reviewed, and how early opportunity signal is captured.

The first version focuses on five things:

  1. helping players create and submit a serious profile
  2. routing profiles through moderation and publication logic
  3. providing a public-safe presentation layer for discovery
  4. capturing structured interest from clubs, scouts, leagues, and agents
  5. supporting operational review, response, and follow-up

That makes FutVia more than a profile builder. It becomes a lightweight operating layer connecting acquisition, onboarding, profile quality, controlled visibility, and early ecosystem demand.

06 // Research Inputs

RESEARCH INPUTS

FutVia is informed by exploratory interviews and synthesis, not by assumptions alone.

On the player side, six amateur players provided highly aligned input about what a serious football profile should include: position, age, height, weight, strengths, weaknesses, videos, and technical or tactical level. They also showed a preference for simple evaluation logic such as low, medium, and high over more abstract rating systems. Just as importantly, they treated WhatsApp as the natural contact layer in the ecosystem.

The same interviews also revealed a discovery environment that is saturated and poorly structured. Visorias were described as mass processes with weak traceability and little proof of individual progress. That helped confirm that the product needs to improve signal quality before it adds marketplace complexity.

Parent and tutor concerns are also important to the product direction, especially around legitimacy, safety, and decision-making for minors. That remains an area for deeper validation in the next research round.

What the research changed

The interviews pushed FutVia away from generic startup logic and toward a more grounded product model.

They made it clear that the MVP needs:

  • a structured player profile
  • simple language and simple evaluation logic
  • moderation and quality control
  • traceability
  • WhatsApp-aware contact logic
  • room for future verification and football-CV layers

They also reinforced an important strategic constraint: the product should structure the ecosystem's existing behavior, not try to replace it all at once.

07 // Defining the MVP

DEFINING THE MVP

The MVP is intentionally narrow.

I do not try to build a full marketplace, content feed, messaging layer, or ranking engine. Instead, the first version focuses on a smaller set of meaningful jobs:

  • player account creation and profile submission
  • structured player profiles designed to be reviewable and manageable from day one
  • moderated visibility and publication control
  • structured interest and lead capture from the ecosystem side
  • superadmin control over review, publication, and follow-up

That decision keeps the product realistic, limits early complexity, and creates value on both sides of the ecosystem without overstating the product’s maturity.

08 // Product Surfaces

PRODUCT SURFACES

FutVia is structured across three connected surfaces.

1. Public surface

The public surface explains the product, builds trust, and captures interest from clubs, scouts, agents, leagues, and related organizations. It works as the entry point for discovery, legitimacy, and ecosystem demand.

2. Player surface

The player surface is where users create accounts and submit a structured profile that presents them in a more serious and credible way than informal channels usually allow. Profiles include core identity and football information such as position, age, height, weight, strengths, weaknesses, technical or tactical level, images, and video links such as YouTube, helping players show both context and proof in one place.

3. Superadmin surface

The superadmin surface is the operational core of the product. It is where submitted player profiles, incoming leads, and related inputs are reviewed, moderated, published, and managed. This layer supports visibility control, lead handling, and day-to-day governance of the system.

A dedicated evaluator-side product for clubs, scouts, leagues, and agents belongs to a later stage, not the current MVP.

09 // Trust, Consent, and Moderation

TRUST, CONSENT, AND MODERATION

Trust in FutVia is not a marketing buzzword. It is built into the product.

That shows up in several ways:

  • profiles go through moderation before publication
  • public visibility is controlled, not automatic
  • minors require tutor authorization
  • legal acceptance is embedded into the user flow
  • consent records are stored as part of the operating model
  • admin controls support approve, reject, hide, and review decisions

The system also includes timestamped acceptance logic for privacy, terms, communications, and tutor consent. That makes accountability part of how the product works, not something buried in a footer.

Legal and governance layer

FutVia includes a legal foundation designed to support privacy, consent, minors safety, and accountability:

  • Privacy Notice
  • Terms & Conditions
  • Minors Safety Policy
  • Tutor Consent for Minors

Designing for minors without making the tutor the main user

One of the most important tensions in FutVia is designing for minors without making the tutor the primary user.

The player remains at the center of the experience. The ambition belongs to the player. But for minors, the tutor is part of the legal, emotional, and operational reality around every decision.

That means the product needs to stay player-centered while still incorporating tutor authorization, consent records, reinforced moderation, and safety-aware handling where needed.

FutVia needs to feel aspirational enough for the player, but serious enough for the family.

10 // Business Decisions

BUSINESS DECISIONS

FutVia is a living early-stage product, but it is also built to become a real business.

That shapes the way I sequence the product:

  • I build only what supports the core operating model
  • I improve quality through moderation before trying to automate it
  • I keep infrastructure lightweight and low-cost
  • I treat monetization as something to earn through trust and usefulness, not force at launch
  • I leave room for future verification, assessment, and football-CV products

This sequencing matters because a product like FutVia has to earn legitimacy before it can responsibly expand into heavier monetization or more complex platform behavior.

11 // Stack and Implementation

STACK AND IMPLEMENTATION

FutVia is built with a lightweight, stage-appropriate stack:

Frontendstatic HTML, vanilla JavaScript, Tailwind CSS via CDN
Backendplain PHP exposed through a JSON API
SecurityPHP sessions, CSRF protection, security hardening
DatabaseMySQL via PDO
RoutingApache with .htaccess
Adminserver-rendered admin pages
Deploymentshared hosting via FTP

The goal is not technical novelty. The goal is stage fit: low cost, low overhead, fast iteration, and enough structure and security to support a real live product.

12 // What This Case Study Shows

WHAT THIS CASE STUDY SHOWS

FutVia shows how I work when the challenge is not just interface design, but product definition under messy real-world conditions.

It shows that I can take an idea from ambiguity to execution: turning loose signals into a product thesis, narrowing that thesis into a disciplined MVP, and carrying it through strategy, UX, trust, governance, operations, business logic, and implementation until it becomes a real working product.

13 // What I Would Validate Next

WHAT I WOULD VALIDATE NEXT

The next layer of learning would come from both product metrics and business signals.

On the product side, I would want to understand:

  • profile creation start rate
  • profile completion rate
  • drop-off points across the player flow
  • moderation outcomes
  • time from submission to review decision
  • time from approval to publication
  • interest capture by actor type
  • lead quality and follow-up rate

On the business side, I would want to test:

  • which ecosystem actors generate the strongest demand
  • which types of player profiles attract the most interest
  • whether trust and moderation increase perceived value
  • willingness to pay for verification, assessment, documentation, or premium visibility

Those signals would show whether FutVia is not only usable, but moving toward a repeatable product and business model grounded in real ecosystem behavior.

14 // Reflection

FOCUSED PRODUCT LAYER, REAL BUSINESS CONDITIONS

FutVia does not try to solve all of football discovery. It solves a more focused problem: bringing order, structure, and trust to one fragmented but meaningful layer of the ecosystem.

This is not just a football idea. It is a product with the conditions to become a real business, because it addresses a real coordination problem for players, families, and evaluators while creating room for operational discipline, demand capture, and future monetization.

More than anything, it reflects the kind of work I do best: identifying the layer that matters most in a messy ecosystem, shaping it into a clear product thesis, and carrying it through to a real MVP with practical value.