Frequently Asked Questions

IWIS builds digital products around specific business needs: web portals, mobile apps, automation and BI analytics systems, and e-commerce platforms. We also provide consulting services for cases where you first need to figure out which direction to take and whether anything should be built at all.

Our clients include international brands, retail, manufacturing companies, and even the public sector. In every project we immerse ourselves in the business context and find the optimal solution.

In Kyiv, but the team is distributed, and most of our processes have long been built without being tied to a single city or office. Our clients are based in Ukraine, Europe, the US, and Canada, and we work with all of them without losing communication quality — we simply adapt our rhythm to the time zone.

In 2017. We have delivered 90+ projects in industries that, at first glance, do not have much in common. But every time, the main question in front of us was the same: how to make technology solve a real business problem. Our experience allows us to quickly grasp new contexts and avoid wasting the client's time.

Mostly the B2B segment: finance, retail, manufacturing, distribution, pharmaceuticals, e-commerce, media, and government institutions. Among those we have already worked with: British American Tobacco, Planeta Kino, GoodWine, Helen Marlen, Skarbnytsia, Nazovni.Online. We are equally comfortable taking on large corporate projects with complex infrastructure and mid-sized businesses where speed and a clear focus on results matter most.

If there is a clear understanding of the task, we can start within days — as soon as the key parameters are defined, a team is assembled and the Discovery phase begins. If the request is still taking shape, we start by working together to understand what needs to be done and in what order.

Usually with a conversation. A short call or a free workshop where we break down the task and the business context together. What happens next depends on the request: a one-off consultation, an audit of an existing solution, or a full development kickoff.

Roughly, it looks like this: introduction and discussion of details → context analysis → agreement on the collaboration format → NDA signing if needed → start according to the agreed plan.

It is important to us that both sides understand what is happening before any work begins.

At the start, we agree not only on the scope of work but also on success metrics, areas of responsibility, and the communication rhythm. A team with relevant experience is assembled for each project. Throughout the work we hold regular meetings and provide reports, and every important point is documented. If something changes, we trigger a managed replanning process.

Google Meet, email, messengers, and Jira for task tracking. If the client already has their own system — no problem, we integrate into it. If not, we suggest a convenient format and explain how it works. At any point, the client knows what stage the project is at and what will happen next.

If priorities shift or new requirements appear during the work, we first assess how this affects the timeline, budget, and current scope.

Then, together with the client, we decide what is worth adding now and what is better to move to the next phase. This way, the project does not fall apart with every new idea, and changes remain manageable.

The first meeting is an open conversation. We ask questions about the business context, current problems, and the expected result, while you share your vision. By the end, both sides have an understanding of how to approach the task.

We can recommend a tech stack or architecture, give you an idea of the budget and timeline, and propose implementation options. If your request is outside our area of expertise, we will always say so directly.

Yes, we sign NDAs at any stage. We treat our clients' information with respect and value our own reputation. We have our own NDA template, but if the client has a different one, we will agree on it without unnecessary complications.

Post-release support is a separate area of our work. If needed, we sign an SLA and take responsibility for uptime, bug fixing, and updates. The format depends on the project: in some cases a response within an hour is required, in others a regular weekly log review is enough. The duration is also flexible: from a few months to long-term support.

The client, in full. The code, documentation, and infrastructure are transferred to the client after payment and signing of the documents. If the project uses third-party libraries or tools with separate licensing terms, this is discussed at the start.

Yes, of course. Before taking on such a project, we conduct an audit: we review the code, architecture, infrastructure state, documentation, and access rights. After that, we give an honest assessment of what can be developed further and what would be cheaper to rewrite. If the solution is viable, we take it under support, fix the critical issues, and gradually move forward.

Security is built into the architecture from day one. Access models, role control, encryption, and action logging are baseline elements present even in relatively simple projects.

In internal systems we restrict access and implement multi-level authorization. In BI, we isolate environments and control permissions down to the level of individual dashboards. In e-commerce — API protection, payment encryption, and traffic auditing. We have worked with banks, government institutions, and law firms, where security requirements are especially strict.