Projects from over 15 years of team experience

Receipts and orders arrive as PDFs, scans and emails and are currently entered by hand.

Extraction of the relevant fields, a proposal for approval, handover to the ERP. The final sign-off stays with the team.

Insured members need to manage documents, permissions and modules of the electronic health record securely on their smartphone, in a strictly controlled environment with strict audit requirements.

A new interface on an existing white-label base, FHIR data models, sign-in via the sectoral identity provider, consent management, integration of further specialist services such as the e-prescription and emergency data. Complete auditability and documentation designed for the Gematik audit.

The internal sales team looks up product details, prices and availability across many catalogs and systems, which costs time on every inquiry.

An assistant answers questions from the approved data sources with source references and respects roles and permissions. Connected to the inventory management system.

Calculating a first quote from incoming inquiries takes the internal sales team a lot of time.

The inquiry is analyzed and a calculation proposal is generated. Sales reviews and approves it; responsibility stays with people.

An application needs to behave identically on both platforms without maintaining the business logic twice.

The database and API client written once in Kotlin Multiplatform, embedded in a SwiftUI and a Compose interface. Shared tests, separate native interfaces.

The banking environment sets high requirements for auditability, traceability and stability.

Development of individual modules following the compliance requirements common in banking, with clean documentation and test coverage.

Employees find knowledge in the wiki, documents and tickets only slowly, and the answer needs to be auditable and permission-safe.

Retrieval with source references, access control at the document level, every answer with evidence. Built on the existing backend and security DNA.

Technicians in the field often work with a weak connection and need job data, photos and data capture even with no reception.

Local data storage with later synchronization, photo and capture features, distribution via enterprise channels.

A utility's customers need to submit meter readings, manage contracts and view invoices, anytime and on their own.

A self-service portal with a clear interface, connected to the billing and contract systems. Designed for many concurrent users.

Delivery notes, freight papers and invoices arrive in many formats and are sorted and entered by hand.

Extraction of the relevant fields, matching to the right transaction, handover to the target system. Edge cases go to a staff member for review.

After a health questionnaire, users should receive relevant content daily, with clean subscription logic and data-minimal analysis.

Questionnaire, score calculation and daily rotating content. Subscription via in-app purchase, content behind a valid subscription. Automated deployment for multiple environments.

A company wants to use AI while keeping its established ERP and legacy landscape.

Integration with SAP and database interfaces, controlled data handover, AI features layered on top of the existing systems. The existing investment is preserved.

A retailer wants a seamless shopping experience on the smartphone, with sign-in, payment and recommendations.

Native apps for iOS and Android, connected to the shop backend, payment via established SDKs, personalized content and push.

Findings and billing documents exist in unstructured form and should be processed further as clean FHIR resources.

Extraction, mapping to FHIR profiles, validation and handover to the target system. A review step with professional sign-off.

Service technicians on site need to find the right passage quickly in extensive manuals and service documents.

An assistant searches the technical documentation and returns the relevant passage with its source. Built on the existing backend and security DNA.

A health application needs to sign users in via the GesundheitsID and connect to services of the telematics infrastructure.

Sign-in via the sectoral identity provider, integration with the approved components, built and handed over as a self-contained building block.

Policyholders should be able to view policies, report claims and upload documents directly in the app.

A native app with a policy overview, claims reporting with photo upload and secure sign-in. Connected to the core insurance systems.

An app should analyze inputs intelligently, and the analysis should stay local on the device.

A model runs on-device and the analysis happens locally. Data-minimal and with a short path.

A growing platform needs a consistent, accessible frontend that can be extended quickly.

A reusable component and design system, accessible to the common standards, documented for the internal team.

A team loses time to manual releases and inconsistent quality assurance.

An automated pipeline, consistent tests including snapshot tests, monitoring of test coverage and code quality.

Care staff document right at the bedside and need fast, robust data capture that works even with a weak connection.

A tablet app with clear data capture, local storage and later synchronization, designed for everyday care work.

An established application runs on old infrastructure and is hard to maintain; it should become more stable and quicker to roll out.

A step-by-step move into containers, automated pipelines, monitoring and a clear operating path. Ongoing operation is preserved throughout the transition.

A product team lacks experienced iOS or Android capacity for a phase.

Senior developers reinforce the team, work within its processes and hand over cleanly documented code.

Payments and billing must be processed correctly, logged cleanly and connected to several systems.

A backend with clear interfaces, event-based processing and complete logging, designed for high load.

An app with many users needs to work reliably even with a fluctuating connection and display real-time data cleanly.

Robust offline capability, clear synchronization and an architecture that handles high load and frequent releases.

Public-authority specialist applications need data protection, traceability and long, stable operating periods.

Development and maintenance of specialist applications with clear permission and logging logic, designed for years of operation.