Custom software for the way your business works

When your team has to connect the applications by hand

An enquiry arrives by email. The quote is in a document, the job status is in a spreadsheet and the invoice is created in your accounting application. That can work while the handovers remain manageable. When people repeatedly enter the same details, responsibilities become unclear or information goes missing, it is worth examining the whole process.

We develop business software for service companies whose work cannot be adequately supported by a standard product alone. We first look at what your applications already do. A custom app provides the missing workspace and business logic, while useful existing tools can remain part of the solution.

• Your team needs one place to see open cases, next steps and the person responsible.
• Information needs to move between jobs, documents and accounting in a controlled way.
• Exceptions and approvals need an explicit place in the process.
• An existing application meets some needs but forces your team into manual workarounds elsewhere.

What a purpose-built workspace can provide

• Manage cases

  An internal web app brings together the details, files and tasks needed for each case. Your team can see what is complete and what needs to happen next.

• Make responsibility clear

  Roles, ownership and progress are reflected in the actual work. Who can view, change or approve something is defined before implementation.

• Connect applications

  Existing customer management, document storage and accounting applications can be connected. Available data transfers depend on their interfaces, access rights and your software version.

• Handle exceptions

  Missing information and failed handovers receive a clear path for resolution. Your team can correct the issue, check it again and continue the case deliberately.

Open to other programs and AI assistants

The web apps we build for you are not isolated islands. They usually offer an interface (API) through which other programs can read and hand over data, and speak MCP, the Model Context Protocol, the open standard through which AI assistants use tools. Where the central login is set up, several apps share single sign-on: one login for the connected tools. This depends on the project and is a principle for our own apps, not an offer to retrofit third-party software.

• Sovereignty and open systems

  Almost exclusively servers in the EU and open source or custom code, local AI models on request.

From a real work situation to an agreed deliverable

• Understand the process: work through real cases, people, applications, data and typical exceptions together.
• Define the first scope: agree in writing on the result, boundaries and acceptance criteria for a useful component.
• Develop the workspace and logic: walk through the work with you and check it using suitable example data.
• Test handovers: try permissions, missing information, error handling and human approvals before use.
• Prepare for operation: agree documentation, responsibilities, maintenance and the handling of future extensions.

The agreed deliverables may include the web app, required integrations, documented processes and an introduction for the people using it. Source code handover, usage rights, data export and operational responsibility are recorded in the agreement. Later extensions are assessed as a separate scope.

When a custom solution makes sense

A custom app needs ongoing responsibility for updates, access and changes. It is particularly useful when the process is used regularly and a suitable solution would remove meaningful work from your team. If a setting in an existing application or a simple connection between two systems is enough, that may be the appropriate first step.

Automation does not replace business decisions. Price approvals, exceptions and binding communication need designated owners. AI can support suitable tasks, but is not a requirement for business software. Hosting, data use and access are clarified for the individual project.

Working together and planning a budget

One specific bottleneck is enough for an initial conversation: what happens today, who works on it and what should become easier? An available budget helps define a viable first component. A complete business solution is priced according to its functions, integrations and operating requirements.

• Scope and indicative budgets

  The services overview explains the budget ranges and the difference between a small component and a comprehensive solution.

• Project process

  How your starting point becomes an agreed scope, a tested implementation and a defined operating arrangement.

• Data protection in your project

  Clarify data, roles, hosting and access before implementation.

• Discuss your plans

  Describe your process or choose a time for an initial conversation.

Frequently asked questions