SOFTWARE & PORTALS
Software that fits your processes.
We build custom applications and portals that bring people, data and processes together – from the initial idea through integration to ongoing development. For less manual work and digital services that work in everyday practice.
OUR FOCUS AREAS
From business idea to
working application.
We combine business requirements with intuitive usability and a solid technical foundation. What matters is what your employees, customers and partners need to achieve with the software.
HOW YOUR DIGITAL APPLICATION TAKES SHAPE
One interface.
End-to-end processes.
A portal delivers real value when the user interface, business logic and connected systems work together. We plan these layers jointly and define their responsibilities.
People & Interfaces
Customers · Partners · Employees
Web Applications · Portals
Application & Business Logic
Workflows · Roles · Approvals
Business Rules · APIs
Data & Business Systems
CRM · ERP · Business Applications
Documents · Databases
Identity · Permissions · Data Protection · Testing · Accessibility · Monitoring
Product Strategy & Requirements Analysis
The right software starts with the right requirements.
Many software projects start with a long list of desired features. What’s often missing is a shared understanding of which problem to solve first. That’s why we start with the people and the processes involved: Who will use the application? What information is needed? Where do delays, duplicate data entry or unnecessary coordination occur?
Together with the business department and IT, we describe the key usage scenarios, review existing applications and clarify the boundaries of the project. We also look at data sources, interfaces, roles, security requirements and later operations. These decisions influence effort and architecture just as much as the visible features.
The results form a prioritised product scope with verifiable acceptance criteria. A first usable version focuses on one complete, relevant workflow. Further features are then prioritised so that their value and dependencies remain traceable. This creates a foundation for planning and collaboration without having to anticipate every later insight.
Outcome: an agreed target picture, prioritised requirements and a clearly scoped first implementation step.
Customer & Partner Portals
Good access makes collaboration easier.
Customers and partners often need information that already exists within the company: the status of an order, current documents, contract records or the progress of a request. When this information is only shared by email, it creates extra coordination effort on both sides.
We design portals that bring these processes together in one place. Depending on the use case, users can submit requests, exchange documents, track orders or grant approvals. We define which information is available independently and when a personal point of contact needs to be involved.
A key factor is the separation of organisations, users and permissions. A partner may only see the processes assigned to them; internal teams need different functionality than external users. These rules are enforced within the application and taken into account when connecting source systems. This turns an additional website into a genuinely useful part of the business process.
Typical applications: customer service portals, partner access, project portals and digital document spaces.
Custom Business Applications
Your way of working shapes the application.
Not every business process can be meaningfully mapped in standard software. This often leads to supplementary spreadsheets, email chains and small helper tools that fill the gaps. As usage grows, these workarounds become hard to follow and dependent on individual people.
We develop business applications for processes where specific requirements make the difference. Examples include resource management, application processing, project coordination or multi-stage review and approval processes. Before building something new, we check which existing functionality can be reused.
Business rules, status changes and responsibilities are explicitly defined and reflected in the application. This includes input validation, traceable changes and handling exceptions. Implementation happens in agreed stages with early feedback from the business department, so it stays visible whether the software genuinely supports day-to-day work.
Outcome: a business application with clear processes and responsibilities instead of scattered workarounds.
UX, UI & Accessible Usability
Good usability shows in everyday use.
A powerful application is of little use if people can only complete their tasks by taking detours. That’s why we design interfaces around concrete usage situations: What needs to be visible immediately? What decision comes next? What information helps avoid mistakes?
Usage scenarios, wireframes and clickable prototypes make these questions tangible early on. Business users can walk through typical tasks before full development begins. Consistent components then ensure that navigation, forms, tables and status indicators fit together throughout the application.
Keyboard operability, contrast, clear labelling and helpful error messages are part of both design and testing. Which accessibility requirements are mandatory is defined for each individual product. Clear priorities also matter on smaller screens: a complex business form needs adapted interaction logic, not just a shrunk-down desktop view.
Outcome: traceable interaction flows and reusable UI components with verifiable quality requirements.
Architecture & Modernisation
Further development needs a reliable foundation.
Software needs to be able to change without every new requirement triggering a fundamental rebuild. That’s why we align the architecture with business boundaries, expected usage and the available operating model. What matters isn’t the biggest technical solution, but a structure that fits the product and the teams responsible for it.
For existing applications, we first look at dependencies, data model, interfaces and risks. We then determine which parts should be retained, revised or replaced. A step-by-step modernisation approach can help keep usable functionality running while renewing individual areas in a controlled way.
Migrations require more than a data export. Field mappings, data quality, test runs, reconciliation and fallback options are planned before the switch. Technical decisions and interfaces are documented so the application can continue to be maintained after the initial project phase. We use reusable standards wherever they make sense from a business and organisational perspective.
Outcome: a traceable architecture and modernisation path with plannable transitions.
Quality, Operations & Continuous Improvement
Go-live marks the start of the next product phase.
The first productive release is an important milestone. But whether an application fulfils its purpose in the long run is also decided in operations: Are errors detectable? Can changes be rolled out reliably? Do the responsible teams know how to respond to an incident?
We plan quality assurance around the most important functions and risks. This can include automated tests, business acceptance testing, permission checks and load tests. For deployment, we define environments, approvals and fallback options. Operational documentation and handover to the responsible teams are part of the preparation.
After launch, user feedback and agreed metrics form the basis for further improvements. These include processing times, drop-offs in key workflows, response times or recurring support requests. Scope, responsibilities and response times for maintenance and operations are agreed on a project-specific basis. This keeps further development aligned with actual requirements.
Outcome: an agreed path from acceptance into operations and on to further product development.
Let's build the software that moves your business forward.
Planning a new portal, looking to modernise an application or digitise a manual process? Let's work out the right starting point together.