Systems & Solutions Architect
I'm Arsen. I design and build the software behind football work: web and mobile apps, data, workflows and AI.
My projects.
Three products of my own and a platform I built for a client in Australia. Each page walks through the decisions inside, with screens from the product.
- 01
rgusFootball intelligenceA workspace for football agencies, clubs and scouts.Everything an agency, a club or a scout knows about a player in one place: the data, the market around him, the deals and the money.Own productLive→ - 02
Connect with humanity's wisdom.Talk to fifteen philosophers, take any claim apart in five layers, and argue in debates that run by rules. The product is in development; the landing film is live.Own productIn development→ - 03
A platform for parents of young footballers.A weekly paper for football parents, an AI newsroom that writes in the editor's voice, an assistant that knows the family, and a CMS of its own.Client · AustraliaLive→ - 04
SKILL20Master the art of beginningLearn any skill in 20 hours of practice.A plan of subskills worth 20 hours, obstacles picked from a vetted library, a reflection with every logged hour and three AI coaches that remember you.Own productLive→
Arsen Dzantiev
As a child I asked strange questions. If I wanted it badly enough, could I walk through a wall? What if we were microbes living in the belly of a giant and never knew it?
I never walked through a wall, but I found out that human thought can: it breaks through every wall in its way, finds another behind it and keeps going. The giant is still an open question. The world we can see is already a system where everything is connected, and I build software to understand a small part of it and make that part work better.
I design and build software for football: web and mobile apps, data systems and AI.
In most clubs and agencies the work is spread across tools that don't talk to each other: a spreadsheet of targets, a WhatsApp group for club requests, contracts in a shared folder, data in a browser tab. I turn that into one system. First I learn how the work really runs, then I decide what the software should do on its own and what stays with a person, then I build it.
Usually one person draws the plan and another builds it. I do both, from the first call to a system in daily use.
Analysis
Every system starts with the people who will use it: who does the work, who makes the call, who pays. Before I draw anything, I learn how the job runs today, step by step, and where it breaks.
Argus →I mapped 58 jobs an agency does; Argus covers 44 of them in full and 13 in part.
Around it: the market, the rules of the game and the tools a club already uses.
Systems engineering asks for depth in at least one field, and mine is football: I edited football news for three years, studied sport direction and tactical analysis, and now build software for the game.
I work with agencies, clubs, federations, academies and scouts. The same approach fits any team that runs on data and routine.
The discipline behind it: systems engineering (INCOSE, SEBoK)
Tell me what your team still does by hand.
Maybe it's the spreadsheet someone updates every Monday, the bonus nobody counts or the club request that waits in a chat. On a short call you walk me through the work and I ask how it really runs. If I can help, I'll tell you what I'd build first. If I can't, I'll say that too.