Our team

Behind every project there are real people

At iQuest you are not buying anonymous developer capacity. From the first consultation to live operation you have one named person who knows your brief, your processes and your budget – and who makes sure the result matches what you had in mind.

Book a free consultation
years of custom software development – since 2003
23+
person who leads your project from brief to live operation
1
public case studies from real projects
13

Meet the people you will work with

From the first phone call to live operation you deal with a handful of named people, not a rotating bench of consultants. Here they are.

Vladimír Charvát, iQuest

Vladimír Charvát

Founder and managing director

At iQuest: 23+ years
LinkedIn profile

Vláďa has been with iQuest from the very first day. He founded the company in 2003 with two friends from his grammar school in Beroun and still runs it. He started programming while studying at the Faculty of Informatics and Statistics of the Prague University of Economics.

The first big jobs included an information system for the telecoms operator GTS, later part of T-Mobile, and a bespoke system for a private health insurer. While still at university he and a colleague built a unique web application with a CMS and an official notice board for Černošice, a municipality with extended powers (formerly a district authority) — which won his company the Czech Ministry of the Interior's "Discovery of the Year" award.

As managing director he now mostly makes sure that what we deliver makes business sense to the client, looks after the commercial and financial side of projects, and works with the team on the long-term development of iQuest. The full story is in our account of the years since 2003.

“I am here for you when the system is being shaped strategically, and throughout the whole commercial cycle.”
Vladimír Charvát
Lucie Vystrčilová, iQuest

Lucie Vystrčilová

Product Owner & UX designer

At iQuest: 6+ years
LinkedIn profile

Lucie connects two worlds: the business brief that comes from the client on one side, and the development team on the other. She takes your idea, breaks it down into processes and user scenarios, and turns it into a specification developers can start working from straight away.

She designs applications in Figma and other advanced tools and builds interactive prototypes, so you can click through the system before the first line of code is written. As Product Owner she then guards priorities, scope, and the promise that what ships is what the client needs and what we agreed on.

Most of the expert articles on our blog are hers. She writes about MVPs, UX design in Figma, the MCP protocol, and where AI-driven development helps and where it hits its limits.

“First I go deep — I get to understand your processes, find room to make them more efficient, and design a system that is a pleasure to work with. Then I run the development and make sure we keep talking and stay on the same page throughout.”
Lucie Vystrčilová
Kamil Kopejtko, iQuest

Kamil Kopejtko

Project manager

At iQuest: 16+ years

Kamil holds projects together. He plans the iterations, watches the schedule and the budget, organises the development work, and he is usually the one who tells you what has been achieved, how development is going, and — should any problem arise — finds a solution in good time.

Kamil runs projects from the first brief through to live operation. He is a partner to clients as their applications keep growing. He handles company information systems, customer portals and mobile apps. He also works with artificial intelligence (AI). He keeps an overview of every project, assigns tasks and checks they are carried out properly and on time, and deals with any problem promptly.

After go-live he stays on as your contact for further development. We do not hand you over to an anonymous support desk — you always deal with a colleague who knows your system from the inside.

“I make sure the project runs smoothly on the iQuest side. I like straightforward, friendly communication with clients and developers alike.”
Kamil Kopejtko

Which developers will lead your project

More developers work on our projects than fit on this page. These are the ones who own the technical decisions.

Pavel Dušánek, iQuest

Pavel Dušánek

Senior backend developer, Ruby on Rails

At iQuest: 21+ years

Pavel is the most experienced backend developer on the team. He is the person the others turn to when they are stuck. Pavel can solve even very complicated problems and is always ready to help other developers.

He owns the architecture and the data model — the decisions made right at the start. He looks after robustness, and after making sure the system keeps living with the client for many years to come. Pavel enjoys third-party system integrations, performance tuning and working with large data sets.

Ruby on Rails has been his main tool for years. That lets him design an application that will still be running years from now, thanks to well-chosen architecture and tooling.

Pavel also understands the infrastructure the applications we build run on.

“I build large systems, I keep an eye on sound architecture, and I am glad to help my colleagues.”
Pavel Dušánek
Jan Voňavka, iQuest

Jan Voňavka

Senior full stack developer

At iQuest: 14+ years

Honza looks after both the frontend and the backend of the applications we build. He is a hard-working expert developer whose skill, calm and good ideas contribute a great deal to the quality of iQuest's work. He enjoys learning new things and follows IoT and hardware developments closely.

Alongside his expertise and commitment on the frontend, he has years of backend experience behind him — and puts that knowledge to good use at iQuest too.

“What I enjoy about development is that technology never stands still. I follow new trends on the frontend and the backend and look for ways to use them meaningfully. My background at the Faculty of Electrical Engineering also keeps me close to hardware and IoT — I simply see the field as a whole.”
Jan Voňavka
Zlatka Šubrová, iQuest

Zlatka Šubrová

Senior backend developer, Ruby on Rails

At iQuest: 14+ years

Zlatka builds large web applications and customer portals in Ruby on Rails. She takes on whole features, from the data model through to the screen the end user actually works with.

She likes clean, readable code and projects that keep growing for years — the kind where doing it properly the first time pays off. Anyone on the team can pick up her code without a long handover.

As a senior developer she likes projects that make sense, and she is never afraid to propose a better solution, however complicated the situation.

“I like large systems I can build from beginning to end. Complicated solutions do not scare me, and I am always happy to help other developers.”
Zlatka Šubrová
Jiří Dušek, iQuest

Jiří Dušek

Senior frontend developer

At iQuest: 8+ years

Jirka gives our systems a great user interface. He has an eye for detail and for applications that are comfortable to use. Testing new frontend approaches and technologies to get the best possible result is his passion.

Thanks to Jirka, iQuest applications are not only technically sound but also clear and genuinely usable.

“In my work I think about the user first. I like using modern technology and I care about the detail that gives our systems the right polish and added value.”
Jiří Dušek

What working with our team looks like

No handovers between departments and no brief lost in translation. Four steps you go through with named people.

  1. Free consultation

    We meet in person or online and go through what you need to solve. You leave with a realistic estimate of scope, schedule and price. You can also get a ballpark figure yourself in our price calculator.

  2. Analysis and solution design

    We map your processes, ask about the exceptions and propose how the system should work. Process analysis is the cheapest place to fix a project – which is why we spend time there before anyone starts coding.

  3. UX design and clickable prototype

    You see and click through the application before development starts. UX/UI design in Figma means changing a screen costs an hour of work, not a week of rewriting.

  4. Iterative development and operation

    We develop in an agile way, in short – usually two-week – cycles, so you keep seeing what is being built and what you are paying for. After go-live we stay: support and further development are part of the deal. Our references show how that works out in practice.

Let's talk about your project

Write or call us. You will hear back from someone who understands your brief and can tell you right away whether we have understood it correctly.