Question 1

When is custom development worthwhile compared to off-the-shelf software?

Accepted Answer

Custom development makes sense when standard products fail to cover more than 20–30 % of your core processes, when integrating with existing systems creates substantial effort, or when proprietary data models and compliance requirements force specific adaptations that would permanently exceed licence costs.

Question 2

How do you handle unclear or changing requirements?

Accepted Answer

We start with a structured requirements analysis and produce a technical specification before development begins. Agile development cycles with regular demos allow flexible prioritisation. For changes after sign-off, a defined change request procedure ensures transparency about cost and schedule impact.

Question 3

How do you ensure integration with our existing ERP or Microsoft 365 environment?

Accepted Answer

We analyse existing interfaces and data models during the requirements analysis. Connections are made through standardised REST or Graph APIs; for legacy systems without open interfaces we use proven middleware solutions. Integration tests are a fixed part of every release cycle.

Question 4

Which security and data protection standards do you meet?

Accepted Answer

Security is a design principle, not an afterthought: role-based access control, encryption (at rest and in transit), audit trails and data minimisation are anchored architecturally from the start. All systems are built GDPR-compliant; on request we also support ISO 27001-aligned requirements.

Question 5

What happens after go-live — what does long-term support look like?

Accepted Answer

After go-live we take over operations on request, with defined service level agreements (SLAs), automated monitoring and structured incident management. We support updates, extensions and migration projects as a long-term IT partner — either on a fixed-price or time-and-materials basis.

Related Articles