Custom software development, front door to back office.

It depends on things you can name upfront: how many types of user and screens there are, which existing systems it has to talk to (accounting, payments, an old ERP, hardware), how much data has to be migrated, whether parts must work offline, and what has to be audited. A focused internal tool and a multi-app platform are very different budgets. After the intro call we send a written plan with a fixed-scope estimate for the first stage, so you decide the budget one stage at a time instead of signing up for a number nobody can know yet.

The first stage - brief, research and a written plan - takes about two weeks. After that we aim to get a first slice in front of real users as early as the scope allows, then keep shipping in small increments with a demo every week. The plan gives a timeline per stage and we re-estimate at the end of each one, so a surprise shows up as a conversation, not as a missed launch.

Both, depending on how well the work is understood. Clearly scoped stages get a fixed price - you know the number before we start. Open-ended work, such as ongoing product development or a research spike, runs on time and materials within an agreed monthly budget and a weekly note of where the hours went. Changes to a fixed scope are written down and priced before they are built, never discovered on an invoice.

You do. Once the work is paid for, the source code, repositories, design files and infrastructure accounts belong to your company. We can work in your own Git organisation and cloud accounts from day one, so there is never a handover moment where access has to be negotiated. No proprietary framework, no licence that ties you to us.

Yes, and it is a common way to start. We begin with a short code audit: does it build, is it tested, how old are the dependencies, where are the security holes, how is it deployed and backed up. You get the findings in writing with a prioritised list. Usually the right move is to stabilise and improve what exists; we recommend a rewrite only when the audit makes the case for it.

Yes - most of our work is remote. The studio is in Ugljevik, Bosnia and Herzegovina, and in Vienna, Austria, on Central European Time, and we work in English, German and Serbian, Bosnian or Croatian. Day to day that means a shared channel, a weekly demo call and decisions written down. When a project involves hardware or an on-site workshop, we come to you.

Software needs looking after the way a building does. After launch we offer ongoing maintenance: monitoring and alerts, security patches and dependency upgrades, checks that backups actually restore, and a budget of hours for small changes. If your own team takes over instead, you get a runbook, documented deployments and a handover period in which we answer questions.