What to know before you start.

An AI integration, a business system, an iOS or Android app, connections between existing tools or automation of a specific process. We also develop more complex websites and existing software. For a first conversation, a description of what is not working today is enough.

Describe the process you want to improve, the systems you use and the people who work with it. Sample inputs and the expected result also help. Please avoid sending sensitive material with your first enquiry; we will agree on how to provide access.

We first check the available interfaces, permissions and vendor support. We then propose an integration or extension. We confirm the specific options after a technical assessment.

Yes. We have more than 80 published mobile apps for cities, municipalities and other organisations. We also develop custom business apps and connect them to websites, administration interfaces and existing systems.

We include preparation for release on the App Store and Google Play in the agreed scope. We establish publisher accounts, required material and responsibilities in advance. We can then agree on maintenance and subsequent app updates.

For a process with precise rules, a workflow and integration are often enough. We consider AI for documents, questions or other inputs that are difficult to process with fixed rules. The choice depends on the task and how the results will be checked.

After the initial conversation, we clarify the scope, integrations, available material and operational requirements. For more complex briefs, we start with analysis or a pilot. Estimates and delivery terms should reflect that agreed scope.

Yes, if we can choose a self-contained task with available data and a clear way to evaluate it. We agree on criteria, limitations and the steps needed before production deployment.

Before accessing data, we agree on the scope, permissions, environment and providers involved. During design, we determine which data the solution needs and who may see the output. The specific terms are part of the project.

We agree on the handover scope within the project. It includes a working solution, the required access, documentation and an explanation of operating procedures. Ownership, licences and responsibilities should be clear in the contract.

We can agree on support, monitoring, updates, backups and further development. We tailor the scope of responsibility and response times to the system and its operational needs.

We start by assessing the code, documentation, licences and available access. The result is a proposal for takeover or modernisation that identifies the risks and changes required.