From rebuilding my life to building QRelia
I did not enter software through a conventional route. I came through hospitality,
pressure, self-education and real operational problems.
Since arriving in the UK in 2017, my journey has moved from survival and service-floor experience
into full-stack product engineering. QRelia is the clearest result of that path:
a live hospitality platform built from the inside of real operations, not from outside assumptions.
- Czech-born, UK-based builder
- Hospitality operator turned product engineer
- Self-taught developer since 2019
- Founder in formation
- Creator of QRelia
A builder whose credibility comes from lived operations
My advantage is not only technical skill. It is context. I understand hospitality because I have lived
inside its pressure: guests, timing, staff communication, menus, service gaps, complaints, handovers,
and the small inefficiencies that quietly become business problems.
That context shaped the way I build. I do not treat software as isolated screens. I treat it as a system
that must survive real human workflows.
Positioning
A product-minded hospitality operator who taught himself to engineer production systems and turned operational experience into QRelia.
Core thesis
Hospitality taught me the problem. Software gave me the instrument. QRelia is where those two worlds meet.
The first layer of the journey was not technology. It was rebuilding.
I arrived in the United Kingdom from the Czech Republic in 2017 with very little security and no guaranteed path.
The early chapter was shaped by adaptation, financial pressure, service work and the discipline to keep moving.
That background matters because it explains the later pattern: learning without permission, building under pressure,
accepting difficult constraints and proving capability through working systems rather than words.
- Pressure tolerance and the ability to keep moving through uncertainty.
- Practical understanding of hospitality operations, not theory from outside.
- A proof mindset shaped by real constraints rather than ideal conditions.
Timeline of professional transformation
The route from hospitality worker to product builder, SaaS founder in formation and creator of a live hospitality platform.
Move from Czech Republic to the UK
A reset point: relocation, adaptation, financial pressure and the beginning of a new professional identity.
Self-taught development begins
I started learning programming independently and built practical applications instead of waiting for formal permission.
QRelia accelerates
A focused hospitality platform emerges: QR guest access, real-time receiver/KDS, admin dashboards and device integration.
Public launch and recognition
Le Pommier publicly announced the purpose-built QR system and credited my technical work by name.
Hospitality was the laboratory
QRelia did not come from abstract SaaS brainstorming. It came from service reality: rooms, tables, poolside orders, outdoor dining, allergens, sauces, sides, timing, staff visibility and the pressure of getting details right when a venue is busy.
Guest simplicity
QR access, mobile browsing, basket flow, modifiers and order context without unnecessary friction.
Staff clarity
Orders arrive structured with location and context, reducing ambiguity for the receiving team.
Management control
Menus, categories, items, modifiers, allergens, availability, QR routing and venue settings.
The self-taught engineer
My development path is applied. I learned by building systems that had to work: booking flows, admin dashboards, payment integrations, live restaurant tools, mobile wrappers, portfolio assets, legal pages, deployment pipelines and hospitality platforms.
The portfolio before QRelia
QRelia is not an isolated lucky build. It sits on top of a wider pattern: business systems with admin control, customer journeys, booking flows, payments, dashboards and operational logic.
BarberCore
Booking SaaS direction with Razor/.NET and Stripe-style commercial logic.
InnControl
Internal hospitality operations tooling focused on workflows and visibility.
Detail & Go
Car detailing booking and admin systems with customer flow and management control.
QRelia is where the journey converges
QRelia is the clearest expression of my current identity as a builder. It connects guests, staff, managers and physical venue feedback in real time. On the surface it may look like QR ordering. Underneath, it is an operational routing layer.
Le Pommier moved the product from private execution to public proof
The live pilot created a real hospitality proof point: practical requirements, real menus, staff reactions, QR placements, receiver/KDS workflows, launch-day pressure and public communication.
A venue publicly describing the system is different from a founder describing his own product. Public validation turns technical delivery into visible reputation.
Pride without overclaiming
A strong founder moment is not only what others say. It is how the founder responds.
Public founder behaviour becomes part of the product's brand.
The right tone is proud, grounded and generous: ownership without entitlement, credit to the venue,
and a clear signal that the product was built properly in a real environment.
The stakeholder layer
The project is also a relationship story: trust, timing, proof and strategic restraint. The strongest move was gradual proof - solve a concrete problem, demonstrate capability, absorb feedback, improve the product, then let the public story emerge.
Operational champion
Practical venue feedback and real requirements shaped the product into something operationally honest.
Senior credibility
Public support and trust created a bridge from delivery into wider credibility.
Venue team
The live environment where adoption, training and fast fixes turn software into working service.
This is not only a biography. It is a competence profile.
The journey proves a specific combination of capability: product ownership, full-stack delivery, real-time systems, commercial architecture, operational empathy and narrative building.
From surviving to designing systems
The emotional force of the journey is that it was not inevitable. It contains relocation, hardship, service work, frustration, ambition, self-education and public recognition that carries weight because it was not handed over.
Before
A self-taught developer trying to prove capability while building with limited resources.
Now
A builder with a live hospitality deployment, public credit, operational product and commercial story.
Next
A founder converting proof into repeatable sales, stable revenue and long-term independence.
The next 12 months
The goal is not more proof that I can build. The goal is proof that QRelia can sell, onboard, retain and support venues repeatedly without every deployment becoming a custom rebuild.
Stabilise proof
Order data, staff feedback, screenshots, testimonial language and refined onboarding.
Package the story
Venue PDF, pricing page, demo script, public case study and walkthrough.
Secure customers
Target 2-5 paying venues, setup process, support boundaries and device options.
Assess transition
Review MRR, runway, support load, pipeline health and job transition readiness.
All graphics from the journey profile
The full PDF visual system is included below as a portfolio gallery. Each rendered page can be opened as a standalone image, while the web page above turns the same material into a native portfolio story.
A man who rebuilt himself, then built systems for the world he came from.
My journey is not clean, linear or comfortable. That is exactly what gives it force.
I did not enter technology through a protected route. I entered it through need, curiosity,
hospitality, pressure and the repeated decision to keep building.
QRelia is the result of that path: a real hospitality platform shaped by real operations,
live venue proof and the belief that software should make service clearer, faster and more human.