Custom software for when the off-the-shelf box stops fitting

We do not publish a starting price, because it would be invented — the spread between a simple customer portal and an ERP running a whole company is a factor of dozens. Instead, after a free workshop you get a written scope split into stages with a fixed amount for each. The document is yours even if we do not continue, and you can use it to compare offers.

Usually when the process is your competitive advantage and does not fit a ready-made tool, when you pay licences for dozens of users on features only a few touch, or when the gap between the tool and reality is covered with spreadsheets and retyping. If none of those apply, we will honestly tell you to stay with the off-the-shelf option.

The first working module usually goes live in 6–10 weeks, and the full system is built in stages across several quarters. We deliberately avoid one big launch — the longer a stretch runs without contact with real usage, the higher the chance of building something adjacent to the actual need.

That is normal and we assume it upfront. The scope is split into stages, so a change affects the next segment rather than the whole contract. We quote every larger change separately and show its effect on the timeline before starting it. Nothing gets added quietly.

Yes. We start with an audit: we review the code, infrastructure and documentation, then give you a report on the real state, the risks and the cost of maintenance. Only then do you decide whether we extend it or rewrite it gradually. The audit is a standalone, finite service — it does not require committing to further work.

You do, on settlement of each stage. We transfer full economic rights, the repository and infrastructure access. We use mainstream technology and write documentation precisely so that a handover to another team is realistic rather than theoretical.

We work remotely, based in Warsaw. The opening workshop can be run at your premises if the process has to be seen in person — with production or warehousing it usually should be. After that we work in two-week iterations with continuous contact and a demo at the end of each.

Where it shortens work, not because it is fashionable. It usually earns its place in document recognition, search across company knowledge and handling repetitive requests. We always document what data reaches the model and where it is processed; running the model inside your own infrastructure is also possible.