About FLWR Tech

Meet the engineer behind FLWR Tech

Based in Limassol, serving companies across the world. FLWR Tech turns operational problems and product ideas into reliable digital systems.

Marcell Virág

CEO & Founder

I’m Marcell, the founder and technical lead at FLWR Tech. I bring comprehensive, hands-on experience building and running web platforms, mobile applications, integrations and cloud infrastructure in Europe.

I started FLWR Tech to work directly with business owners: understanding how the work gets done, choosing what to improve, and carrying that through into working software.

Most of the businesses we work with are not short of software. They have a website, an accounting package, a booking tool, a spreadsheet that someone built years ago and everyone now depends on, and a WhatsApp group where the real decisions get made. Each part works. The problem is the space between them, which is filled by people re-typing the same information.

That gap is rarely solved by buying another product. It is solved by understanding how the business actually runs — not how a process diagram says it runs — and then connecting, replacing or automating the parts that cost the most time and cause the most mistakes.

At FLWR Tech, you work directly with Marcell on the scope, design and delivery of your software. The person hearing your requirements stays responsible for the work, so decisions retain the context of your business.

We agree the scope and delivery capacity before committing. Larger projects are divided into phases, with any additional specialist involvement discussed upfront.

How delivery runs

What you can expect every week

Regular reviews, written decisions and clear scope keep you informed throughout delivery.

Regular reviews of working progress

During development, you can review a running build and discuss what changed. Discovery and planning reviews focus on the findings and decisions needed for the next phase.

Decisions are written down as they are made

Why a database was shaped a certain way, why an integration was rejected, what was deferred. Six months later that record is what makes the system safe to change.

Scope changes are priced before they happen

When a new requirement appears mid-project — and it usually does — you get the cost and the schedule impact before work starts, not on the final invoice.

Risks are raised early

If something is slipping or an assumption turns out to be wrong, you hear it that week. Late surprises are a communication failure, not a technical one.

Straight answers

Clear commitments from the start

Know how recommendations, project scope and ownership are handled.

Independent recommendations

Recommendations are not influenced by reseller margin. If an off-the-shelf product solves your problem better than custom software, we will say so — including when that means a smaller engagement for us.

Clear specialist boundaries

Security is built into architecture, access control and delivery as a matter of course. Formal penetration testing and regulatory certification are separate disciplines, and we bring in qualified specialists rather than implying we cover them.

Responsible project scope

We agree what we can deliver and support before work starts. Where additional expertise is needed, we discuss specialist involvement or a referral with you before committing.

Your ownership

Source code, cloud accounts and third-party services should sit in environments you control wherever practical. Ownership and handover are written into the agreement, not negotiated later.