MVP
- Authentication
- Player and club databases
- Transfer requests
- Role-based access control
- Administration interface
Platform · Architecture · Engineering Leadership
TransferHub
Professional Football Transfer Platform
A closed professional platform for football clubs to discover players, manage transfer opportunities and communicate directly with other clubs.
RoleLead Developer / Technical Lead
01Built from scratch
026-month MVP
03Production platform
04Used by Russian football clubs
01
Overview
TransferHub is a professional platform designed to digitalize interaction between football clubs on the transfer market. The system aggregates player data, connects players with their clubs and provides tools for discovering, evaluating and discussing transfer opportunities.
02
Challenge
The platform had to launch on a fixed timeline while the scope continued to evolve and client approvals introduced significant delays. One of the main challenges was defining what was essential for the first production release and moving non-critical functionality into a structured backlog without compromising the core product.
03
My Role
I worked with the engineering team on the complete architecture and was responsible for final technical decisions, decomposition, planning and delivery. I evaluated technical proposals from developers, adjusted solutions where necessary and coordinated the implementation through the MVP and subsequent development phases.
04
Architecture
The platform uses a microservice-oriented architecture with a FastAPI backend and Vue frontend. Separate services handle areas including data parsing, messaging, notifications and authentication. PostgreSQL is used as the primary relational database and Redis supports high-speed data access and service requirements.
01Vue Frontend
02FastAPI Services
AuthenticationPlayers & ClubsMessengerNotifications
03PostgreSQL
04Redis
05
Launch Strategy
The initial MVP focused on authentication, player and club databases, transfer requests, role-based access and administration capabilities. Messaging, notifications, news, analytics dashboards, additional data sources, saved searches and extended filters were moved into the post-MVP backlog.
Post-MVP backlog
- Messaging and notifications
- News and analytics dashboards
- Additional data sources
- Saved searches
- Extended filters
06
Features
01Closed club accounts
02Player and club database
03Advanced player search and filtering
04Transfer and loan listings
05Transfer requests
06Club-to-club messaging
07Notifications
08Role-based access control
09Team formation simulator
10Player statistics comparison dashboards
11Football and platform news
12Django-based administration interface
13External data synchronization
07
Screenshots
The home screen brings together the club's core workflows, news and events.
The player marketplace combines advanced filters with a comparison workflow.
A responsive player search and profile workflow for mobile devices.
08
Data & Integrations
Player and club information is aggregated from external football data sources and synchronized with the platform. The architecture was designed to support additional sources and future expansion into European and Asian markets.
09
Result
The MVP was developed over approximately six months and successfully moved into production. Development continued for another six months, expanding the platform with functionality originally moved to the backlog. The system is currently used by football clubs in Russia and continues to evolve, with expansion into additional markets planned.