The mechanics can be repeated — a catalogue with filters, payments, a client dashboard, an admin panel. What we will not do is copy it verbatim: what works for one business often gets in the way of another. In the first conversation we work out which part of someone else’s solution you actually need and which would only add to the price.

The timelines are on the cards: the marketplace with its own CRM, five payment systems and a ticket system took 40 days. We do not publish the cost of specific projects — that is the client’s call — but we name the order of magnitude in the first conversation: it depends on the size of the catalogue, the number of integrations and whether you need an admin panel built around your processes.

No, this is a selection. Some of the work is under NDA, some we keep off the site by agreement with the client — usually internal systems and admin panels a business would rather not put on display. If there is no example here for your task, ask: chances are it exists and simply is not public.

No. A catalogue, payments, a client dashboard and an admin panel are built the same way for cosmetics and for industrial equipment — the data and the scenarios change, the engineering does not. Industry specifics come out in the interview: that is the first step of the work, and it is where we ask the questions for you.

Every project in the portfolio was built by us from the brief to launch: system design, design, development, migration onto the servers. We take on existing projects too, but we start with an audit — first we look at what is inside, then we name a deadline.

Yes, most of them. After launch they stay on our infrastructure: monitoring, backups, updates, improvements as the business grows. Development does not end at delivery — that is usually where the interesting part starts.

Yes. Tell us which project is closest to yours and we will ask that client whether they are up for answering a couple of questions about working with us.