Portfolio

Before Amiatex, I managed several online stores built on PrestaShop. Each had its own admin interface, imports, and set of customisations. Whenever I needed to develop or change something, I had to repeat the same work for every store.

What increasingly bothered me was constantly switching between admin interfaces and duplicating work. I imported the same products into several systems, stored the same images on the server more than once, and had to roll out every new feature to each store separately.

That experience led me to build my own multi-store platform. I wanted to manage multiple stores from a single admin interface: one import for a shared product range, one source of images, and one dashboard instead of several disconnected systems.

Each online store could still retain its own identity and configuration. Margins, descriptions, translations, countries, currencies, and shipping rates could all be set independently — without copying and maintaining everything several times over.

Amiatex was not just another e-commerce system for me. It was a way to simplify everyday work and provide a shared foundation for future development: I could make each change once and roll it out wherever it was needed.

In 2013, I had already built a few websites and an online store. I decided to try running a store of my own and experience first-hand everything it involved.

I started with a model where I forwarded orders to a supplier. Over time, however, I ran the store from A to Z: I handled customer calls, managed supplier relationships, purchased stock, packed parcels, and dispatched orders.

Alongside daily operations, I kept developing the system. I built features that made ordering from suppliers easier and gave customers clearer delivery estimates.

I integrated the store with partner websites and linked it to social media and advertising channels. The technical work was never separate from operations — every change had to make sense for customers, suppliers, and the people actually fulfilling orders.

Running MEBOTY.cz gave me hands-on experience of the entire e-commerce operation and helped me recognise both my strengths and weaknesses. That experience later shaped my work on other e-commerce projects.

It was 2015. I had already built my own e-commerce system, a lightweight website admin system, and various small tools for everyday work. At the time, I wanted to build a central booking platform — a marketplace and comparison service for reservations. Someone arriving in a city could search for something such as bowling, immediately see businesses with available slots, and book one in the same place.

Amiatex took priority, so the idea receded into the background for a while. It never disappeared; instead, it gradually matured as I found myself using more and more tools in my daily work.

Slack, Trello, Toggl, iDoklad, and many other services each work well on their own. But connecting them is often difficult, and every new need can mean another subscription, another account, and another place where important data lives.

With the rise of AI, it made even more sense to build a central SaaS platform for small business owners and smaller companies: a system that could gradually bring day-to-day operations into one place and grow around what clients actually need.

What matters most to me is how the individual parts work together. They should not merely sit alongside one another: they should work with the same data and share context. An AI assistant can then become a natural part of the whole and help a business operate much more effectively than with today’s fragmented toolset.

I have been interested in esports for years. I remember meeting a bookmaker at Tipsport and telling him that esports was something they should add to their betting markets. A year later, Tipsport had done exactly that.

Several years later, live FIFA matches caught my attention. Traditional football comes with a wealth of statistics and tables, whereas for competitive FIFA I could mostly find only match results. What was missing was context: which players were in form, how they performed against each other, and what longer-term data could reveal.

So I began building my own application to monitor and analyse every match. It now works with data from nearly two million matches and provides player comparisons, head-to-head records, form, tournament summaries, historical context, and live signals.

At the same time, I developed widgets for betting companies including Tipsport, Fortuna, and Betano. For a period, the system also supported my own match analysis: starting with CZK 1,000, I made roughly CZK 200,000 in profit. I do not present this as betting advice — and I no longer bet.

I later made the application available to a small group of users. In an ironic twist, Tipsport noticed what I was doing and blocked my account on a forum where I had been very active. The system continues to run for a small group of people and analyse matches using new metrics.

By 2011, I had already spent several years helping different gaming portals. I noticed the differences between them, and it bothered me that a player could cheat, receive a ban, and then simply continue playing on a competing portal.

At the time, the portals saw one another primarily as competitors, and every new player was welcome. I approached the leading Czech and Slovak Counter-Strike portals and worked with them to establish a shared system for handling offences and enforcing global bans across portals and game servers.

We gradually standardised some of the rules and penalties. I built an extensive system that helped partners handle protests and made disciplinary records transparent to the wider player community.

The partners’ websites were connected through an API. This created the largest Czech and Slovak anti-cheat portal, giving a shared solution to a community that had previously been fragmented.

The project also included a Counter-Strike plugin that prevented banned players from joining game servers, plus another innovative plugin that streamlined and automated competitive matches.