Custom Software Solutions
Tailor-made Software for Complex Business Processes
We develop custom business applications, interfaces, and portals where standard software reaches its limits or creates operational bottlenecks.
Discuss a projectView the project processTargeted Software Solutions for Your Core Processes
Select the appropriate solution area to view concrete functional scopes, typical problem statements, and exemplary workflows.
Initial Situation
Rigid ERP systems do not cover industry-specific processes. Employees rely on error-prone spreadsheets and manual workarounds.
What We Develop
Custom Business Applications & ERP Extensions
Development of custom business applications and ERP extensions. Integration takes place after technical interface verification.
Core Topics & Features
- Specific screens and workflows
- Two-way synchronization with ERP
- Role-based input forms and permissions
Typical Workflow
A custom manufacturing order is entered in the business application, verified, and automatically created as a structured transaction in the ERP system.
Initial Situation
Isolated data silos across departments cause duplicate data entry, delayed information, and high error rates in daily operations.
What We Develop
Middleware & System Integration
Middleware for ERP, CRM, legacy systems, and databases. Data transfer occurs on a scheduled or event-driven basis depending on process requirements.
Core Topics & Features
- Interface and API integration
- Data transformation and validation
- Process monitoring and automated retries
Typical Workflow
Validation and transfer of CRM customer master data. Automated display of errors for targeted manual clarification.
Initial Situation
Customer inquiries, partner coordination, and internal requests are cluttered across emails, leading to long processing times.
What We Develop
Customer, Partner & Employee Portals
Web-based portals for customers, partners, and employees. Includes role concepts, process handling, and source-based knowledge search.
Core Topics & Features
- User management with Single Sign-on.
- Interactive dashboards and process tracking
- Structured document upload and exchange
Typical Workflow
Suppliers upload delivery confirmations to the portal. The system verifies the data and updates the order status in the ERP.
Initial Situation
Incoming invoices, contracts, and delivery notes are manually typed, laboriously checked, and approved on paper.
What We Develop
Document Processing & Approval Workflows
Processing unstructured documents with automatic data extraction, human quality checks in edge cases, approval workflows, dashboards, and electronic signatures.
Core Topics & Features
- Automated extraction of document contents
- Rule-based approval paths
- Integration of electronic signatures
Typical Workflow
Incoming delivery notes are extracted, matched with the ERP order, and posted after purchasing approval.
Initial Situation
Impending bottlenecks, missed deadlines, or quality deviations across multiple locations are often detected too late.
What We Develop
Data Logic & Process Automation
We develop application logic that analyzes operational data across locations, identifies bottlenecks early, and triggers targeted notifications or tasks.
Core Topics & Features
- Cross-location data consolidation
- Rule-based early detection of bottlenecks
- Automated task distribution to teams
Typical Workflow
A material shortage at Location A is detected. The system suggests a transfer and notifies logistics management.
Initial Situation
Established companies want to offer new digital services but lack suitable software products.
What We Develop
Digital Products for New Services
Customer-specific service platforms for new digital offerings, including evaluation of integration into existing processes.
Core Topics & Features
- Service and portal features
- Multi-tenant application architecture
- Integration of operational backend systems
Typical Workflow
An industrial company offers customers a predictive maintenance portal that evaluates sensor data and triggers service dispatches.
Examples serve illustrative purposes. Interfaces and scope of services are individually evaluated in advance.
Automation & AI
We connect your business processes across system boundaries and integrate tailored AI for documents and company knowledge. From economic consulting and development to integration and controlled ongoing operations.
- Connection of existing core systems and process automation
- Targeted use of AI for documents and enterprise knowledge
- Architecture, integration, and operations with tailored access rules
Another example
Modernise an old system one step at a time.
A business-critical application has grown over many years. Before promising a full replacement, one bounded part is examined.
- Understand
Expose the business rules
Business and IT teams map rules, data flows and critical exceptions before moving a function.
- Define
Rebuild one function
A clearly bounded function can move to a new application while the rest keeps running. Its interface and rollback path are checked.
- Move
Compare the results
Old and new processing are compared with approved test cases. Usage moves gradually only after business and operational checks.
Illustrative approach. Effort and feasibility depend on the actual legacy system.
Clarity before investment.
Support afterwards.
Before implementation
Clarify the goal
Problem → goal
Examine the workflow
Workflows → systems
Calculate the value
Impact ↔ effort
Recommend the route
Buy · connect · build
Plan the project
Scope → agreement
During implementation
Build and connect
Development → integration
Introduce it together
Acceptance → use
After launch
Support and improve
Operation → impact
Process in detail
- 01
Clarify the goal
LDS: LDS listens to the people involved and clarifies where work stalls and what needs to change.
Your contribution: The company describes its day-to-day work and the desired result.
Outcome: A shared goal with criteria that can be checked.
- 02
Examine the workflow
LDS: LDS examines workflows, responsibilities, data and existing applications.
Your contribution: The company shows how the work actually happens and which systems are involved.
Outcome: A reliable picture of the current situation and its bottlenecks.
- 03
Calculate the value
LDS: Using the company’s starting figures, LDS estimates the potential economic value and compares it with the estimated development and operating effort. Assumptions remain visible; capacity freed up is not automatically a cost saving.
Your contribution: The company provides available volumes, time estimates and costs, and checks the assumptions.
Outcome: A grounded value estimate rather than a blanket savings promise.
- 04
Recommend the route
LDS: LDS compares existing software, integration, automation and custom development. It may also recommend building nothing for now.
Your contribution: The company weighs the recommendation against its goals and priorities.
Outcome: A reasoned next route; implementation is agreed only afterwards.
- 05
Plan the project
LDS: LDS specifies the features, interfaces, effort, timeline and acceptance criteria. A focused PoC can answer an open technical question, earlier in the process if needed. It is not a required step.
Your contribution: The company prioritises requirements and agrees on the budget, its involvement and decision-making responsibilities.
Outcome: A defined scope and a shared plan for implementation.
- 06
Build and connect
LDS: LDS develops and tests the agreed features and data exchanges. An MVP can serve as a first usable version; later features depend on feedback and agreed goals.
Your contribution: Business and technical leads clarify the rules and test cases. Future users give feedback.
Outcome: A tested solution, or first usable version, against the agreed criteria.
- 07
Introduce it together
LDS: LDS supports testing, documents the solution and prepares its introduction and operation. The necessary training is agreed with the team.
Your contribution: The company involves future users and decides on business acceptance.
Outcome: An accepted solution with clear responsibilities for use and operation.
- 08
Support and improve
LDS: LDS provides maintenance and further development within the agreed scope. Together, LDS and the company use the goal criteria to check what has improved and what is still missing.
Your contribution: The company shares experience from use, brings new requirements and sets priorities.
Outcome: Targeted next improvements. The scope, availability and response times are agreed for each project.
Operational Reliability
Service Hours
Agreed service hours with optional 24/7 support coverage.
Service Targets
Separate response and recovery targets agreed per project.
System Maintenance
System monitoring, automated alerts, runbooks, and patch planning.
Testing & Ownership
Project-specific deployment, restoration, and failure tests, with named build, operations, and substitute owners.
Incident Priorities
- P1
- Core process stopped.
- P2
- Serious degradation without total outage.
- P3
- Minor issue or ordinary request.
IT Governance
Compliance and Security
Ongoing NIS2-Environment Project
Direct experience from one ongoing software and integration project for a company in a NIS2-regulated environment, not corporate certification.
GDPR & Data Minimisation
Principles of data minimisation and alignment with GDPR requirements.
Permissions, Audit Logs & Data Separation
Access controls, audit logs, and structural separation of sensitive data.
Code Reviews, Pull Request Reviews & CI/CD Scanning
Engineering practices such as code reviews, two-person review via pull requests, and CI/CD vulnerability scans, maintained as operational practices rather than fixed guarantees.
Common questions
When is custom software worthwhile?
When a significant gap remains in the existing systems and the business value of addressing it justifies development and ongoing support. LDS also checks whether existing solutions are sufficient.
How does a software project work?
LDS first clarifies the goals, expected business value and existing systems. The solution is tested with the teams involved and integrated through verified interfaces. The scope and responsibilities for maintenance, incident support and further development are agreed.
Do existing systems need to be replaced?
That is determined during the project. LDS first assesses what can remain in use and which interfaces are available.
What role does AI play?
AI is used selectively when it offers additional value. Data, output quality and any necessary human checks are considered for each use case.
What determines the effort and duration?
The scope of features, existing systems, available interfaces and data quality. Necessary approvals and the availability of the teams involved also affect planning. LDS establishes these conditions before the scope and timeline are agreed.
How much involvement is needed from the company?
The project needs a person responsible for the process, access to the relevant workflows and participation from future users in answering questions and testing. IT leads are involved in matters relating to systems and permissions. The specific effort depends on the project.
How are changes handled?
New requirements are assessed by their contribution to the company’s goals. Their impact on effort, the timeline and operation is discussed before changes are implemented. The agreed scope determines which adjustments are already included in ongoing support.