Online stores and e-commerce
Development of online store solutions and e-commerce features connected to real-world processes, data, and business growth.
PHP BACKEND · E-COMMERCE · AUTOMATION
E-shops, internal systems, various applications, automation and technology solutions for greater efficiency.
01 Services
Development of online store solutions and e-commerce features connected to real-world processes, data, and business growth.
Development of applications and systems that streamline operations, support growth, and address real business needs.
Digitizing repetitive processes, integrating services, and speeding up work wherever unnecessary friction exists today.
02 Who it is for
It works best when there is a shared goal, room to understand the wider context, and a willingness to build a solution that makes sense in the long term.
02 How the collaboration works
HOW I WORK
First, understand how the project works. Then design a solution that can support its continued growth.
03 Selected systems
Every project starts with a different need. The goal is always a clear and reliable solution that performs well in day-to-day operation.
ALL‑IN‑ONE
A website and online store, bookings, CRM, invoicing, project management, marketing, and automation in one connected system.
AMIATEX
An innovative platform for multiple currencies, languages, domains, and stores — all managed through a single central admin interface.
LEETgg.com
An analytics platform for live and historical match data from FIFA, NHL, NBA and CS2 — from player form to fair odds and AI exports.
05 Stack
APPLICATION
DATA
FRONTEND
QUALITY
DELIVERY
WORKFLOW
06 References & historie
The same curiosity led me from my first websites and gaming servers to e-commerce platforms, APIs, and automation.
I value a deep understanding of the project and long-term collaboration — more like a shared virtual marathon than quickly hopping from one job to the next.
Together with a graphic designer colleague, we created an online project attracting 5,000 visitors a day. For me, it was the first experience of bringing a project of my own to a wider audience.
Security testing of web applications and responsible disclosure to their operators — including an early report of an XSS vulnerability in Seznam.cz email. I also found and reported security flaws in the veweb.cz content management system used by dozens of websites, reviewed the nRS system for dreamstudio.cz, and checked the security of vsadte-se.cz, Grunex.com, and eSuba.eu. I reported several serious vulnerabilities on Undzwei.eu. I also worked on eG-Sports.eu and other community websites.
On Undzwei.eu, I organized dozens of tournaments and administered a competitive Counter-Strike 1.6 league. In 2011, I also created an innovative game-server plugin for competitive Counter-Strike 1.6 matches, on which tens of thousands of matches were played.
A three-week work placement and a two-month temporary job at the Radegast brewery, part of Plzeňský Prazdroj. I am glad I had the chance to experience it from the other side — thankfully!
A four-week work placement at Veolia Transport, where I helped automate the creation of fare tables.
My own project, which connected gaming portals and made it easier to resolve cheating cases, protests, and bans in Czech and Slovak esports.
Finding an SQL injection vulnerability on the website of the Secondary School of Information Technology.
I co-founded a web studio where we initially created simple company websites, templates, and various scripts. I later shifted my focus to online stores, while my graphic designer colleague pursued his own path.
My own online store built on PrestaShop — from developing custom features and marketing to supplier communication and order fulfilment.
Another online store of my own built on PrestaShop — from developing custom features and marketing to supplier communication and order fulfilment.
I founded an esports team / clan that at one point included more than 40 players under my leadership. At the same time, I took over and managed an H1Z1 Facebook group with 6,000 players.
Co-founder. A custom multistore platform developed over several years, enabling multiple online stores, domains, language versions, and currencies to be managed through a single central admin interface.
At the end of 2025, I was forced to shut the project down.
Development of game-server plugins for competitive CS:GO matches across Czech and Slovak gaming portals.
A year of development work for SPORTISIMO, a business with turnover in the billions and dozens of developers. Compared with my own projects, it was a valuable change and an opportunity to understand the technology behind a large online store. More specifically, I worked in a team developing an internal system for store employees. The PDA-based solution covered inventory movements from goods receipt through backroom stock to the shop floor.
An analytics platform for esports matches. It processes live and historical data across FIFA, NHL, NBA, and CS2, offering head-to-head comparisons, player form, scoring patterns, fair odds, an opportunity radar, and exports for AI workflows.
Development of a system that brings together a website and online store, bookings, CRM, invoicing, project management, marketing, and automation in one place.
I build systems that solve a real problem and last beyond the first release.
OFF THE HAPPY PATH An honest look
Some lessons did not come from books or successful projects. They came through unpaid work, taking on too much, and moments when I was right but did not know how to communicate it. These are the ones I remember.
You finish a project and the client disappears. Other times, you work for months and one day the communication stops too.
I started with online freelance work. As is often the case: no contract, no deposit. You do exactly what the client asked for, deliver the finished work — and the client disappears. No payment, no explanation, simply gone.
I had a similar experience after developing for several months under nothing more than a verbal agreement. I could feel the team gradually abandoning the project until communication stopped altogether.
Trust is a great starting point, but it is not a substitute for a contract. Scope, price, deposit, milestones, and exit terms must be clear before the first line of code is written.
You price the job. Then comes another adjustment, another idea, and one more small request — ideally free of charge.
You quote a project based on the brief. Then the client comes back with another change, another idea, and one more small request. You are still learning, want to do good work, and try to accommodate them out of goodwill. But one favour easily becomes an expectation, and the project turns into an endless loop.
For a long time, I thought being accommodating meant saying yes. In reality, I was blurring the project boundaries, undervaluing my time, and eventually damaging the client relationship as well.
The scope of work must be specific. Change is not a problem, but it needs a new estimate, price, and deadline. An honest “this is additional work” is healthier than a tired yes.
I gave everything to my first full-time development job. Within a month, however, the person without whose approval I might never have joined the company was gone.
I started my first full-time development role, and my workaholic side went all in. A developer with a degree who had been with the company for roughly a year was dismissed during my first month. The company saw that I worked considerably faster and that the existing way of working was holding me back.
I did not see it as a victory. I felt deeply uncomfortable that someone without whose approval I might never have joined lost his job shortly after my arrival. It was not my decision, but for the first time I clearly saw that performance and change affect real people.
Performance is not merely the number of completed tasks. Humility, respect for the people around us, and awareness that every organizational change is part of someone’s real story matter too.
The supplier did not honour the agreed terms. The goods remained in storage, and after returning them I was left with neither the goods nor the money.
You reach an agreement with a supplier, order the goods, and rely on the terms you discussed. But those terms are not honoured, leaving you with a warehouse full of products that do not sell. When you return them, you discover that you have neither the goods nor the money.
Technology alone cannot protect you from a bad business partner. For me, it was an expensive reminder that an online store is not just code and marketing. It is also cash flow, inventory, contracts, and risk that someone must carry.
I put supplier agreements in writing, spread the risk, and start with smaller volumes. Trust, but verify as you go.
I joined a marketing team, started improving the website, and overlooked that the company already had an IT supplier. A serious conflict followed.
I began working in marketing for a company and, because I know how to build websites, naturally started modifying theirs. But the company had its own IT supplier, and I stepped into an area where responsibilities had not been clearly agreed. The director called me in, and the collaboration quickly turned into a conflict.
They installed a remote-monitoring tool on my personal computer.
Before changing anything, I need to understand the responsibilities, system ownership, and approval process. I also keep work access separate from private devices and communication.
I liked both the project and the people around it. But I did not yet understand how they worked or my own capacity for working in a team well enough.
I agreed to work with an online store I genuinely liked. But I did not yet understand how it worked, had little experience of working in a larger team, and underestimated how much context, communication, and responsibility the collaboration would bring.
Instead of saying early enough that it was too much, I tried to handle everything. I became so overloaded that the collaboration ended very quickly. It was not a lack of technical ability, but a poor estimate of my capacity and communication that came too late.
Before starting, I need to understand the team, expectations, and pace. When I do not have the capacity, I say so before the problem turns into silence and disappointment.
I had promised a colleague we would go on holiday together. But the owner wanted one of the IT team members to stay and gave me a choice: the job or my word.
I promised a colleague that I would go on holiday with him. But the owner wanted one of us from IT to remain at work. He gave me a simple choice: either come to work on Monday, or return the laptop and leave.
On Monday, I brought back the laptop. Not because the job meant nothing to me. I wanted to stand by the promise I had made and to be someone others could rely on. If I had broken that promise merely to keep the position, I might have saved the job — but lost something that mattered more to me.
Today, I would clarify holiday plans, cover, and expectations much earlier. But once I give someone my word, I want to stand by it. Work matters, but money is not everything.
At a larger company, bureaucracy and outdated practices frustrated me. I spoke frankly about changes I wanted to make — perhaps too frankly.
I joined a larger company and soon became frustrated by the bureaucracy. I brought ideas for improvement, but development decisions were often made by people who were no longer active developers, and some practices seemed long outdated. This gradually demotivated me.
I am direct. When something does not make sense, I say so because I want to improve it. But being right and knowing how to make change happen are two different skills. My criticism may have been valid, but the way I delivered it did not help those responsible accept it.
Change needs more than a good argument. It needs context, respect, allies, and the right timing. I remain honest, but think more carefully about how to communicate it.
I accepted a lower hourly rate than I had four years earlier. Then came a breakup and other personal issues. It was a recipe for trouble.
I accepted an engagement at a lower hourly rate than I had earned four years earlier. I liked the team and wanted it to work. But other personal matters arose at the same time. Work I would normally have handled began to feel like a waste of time.
The problem was neither just the price nor just my personal life. I accepted the engagement when my motivation, capacity, and conditions were out of balance. Enjoyment turned into frustration — even towards people who were not responsible for my situation.
I do not say yes merely because I like the other party or do not want to refuse. Price, energy, and life circumstances must all make sense; otherwise, the agreement is fair to neither side.
ARCHIVE Webtrh 2012—2013
“Very satisfied — both communication and project delivery were fast.”
“Fast, high-quality work.”
“A fast solution and quality work, explained clearly. Highly recommended!”
LET'S BUILD Contact
Tell me what is holding you back. I will get in touch with some initial questions, and together we will find the shortest path to a solution.