Reference

EVEX Group – A new generation of PMS for optical and hearing care

How EVEX Group and Turing 42 are turning an established system landscape into a shared, cloud-native generation of practice management systems.

Greenfield under real-world conditions

From day one, the new PMS must reflect established clients, highly specialized workflows and a heterogeneous system landscape.

Two client segments

Independent practices expect simple, end-to-end workflows. Multi-site organizations need additional modules, roles, integrations and controls.

Domain depth

Appointments, consultation, configuration, orders, billing and aftercare are tightly connected. Errors directly affect client experience and operations.

Hardware and ecosystem

Diagnostic devices, labs and other partner systems make the platform a demanding integration product – not just a web application.

Migration without a big bang

New and existing solutions need to operate in parallel for a period of time. Rollout and migration are therefore part of the product strategy.

Why Turing 42?

EVEX Group defines the product vision and retains overall responsibility. Turing 42 complements the team with experienced senior engineers and product specialists who translate complexity into robust product slices and an executable delivery path.

Architecture and Go expertise for complex platforms

Product, UX and engineering in a shared delivery model

Hand-picked specialists with more than ten years of experience each

Short decision paths and an experienced team

Pragmatic focus on what creates impact at each stage

AI-first delivery from requirements to verifiable product slices

From risk to product program

Rather than building the entire PMS at once, the team first focuses on the assumptions and risks that matter most for the path ahead.

01 · Foundation

Decompose the complexity

A focused product-engineering cell clarifies requirements, key UX flows, architecture and technical foundations. Backend, frontend and product are treated as one connected system.

Abstract requirements become prioritized product slices and a shared development process.

02 · Feasibility

Make feasibility visible

Appointment booking and eyewear configuration are implemented as visible end-to-end slices. This allows UX, product logic and technical feasibility to be demonstrated and assessed together.

The first robust presentation succeeds ahead of plan and creates the foundation for the next stage.

03 · Product program

Expand through modules

Domain-focused module teams work on billing, lens configuration, hardware integrations and the coexistence of old and new solutions.

Migration strategy and validation with selected clients enter delivery planning early.

AI first – from day one

AI first is part of the greenfield plan, not a later addition. The approach shapes both delivery and the product's target state.

AI in development

A structured information flow shortens the path from product requirements to verifiable product slices.

Structured artifacts from product and UX through to UI components
AI support across analysis, implementation and review
Earlier validation before teams and scope are scaled
Shared code and knowledge context for delivery

AI in the product · target state

AI support is intended for situations where it tangibly improves revenue, quality or efficiency.

L1 Invisible: defaults and plausibility checks
L2 Assistive: support users can choose
L3 Proactive: guidance at the right moment

What changed along the way

The most important outcomes are not just technical artifacts, but reduced risk and a robust perspective for the product, organization and clients.

01

The first proof point stands

Core product slices are delivered ahead of plan and can be presented early.

02

Core workflows become tangible

Appointment booking and eyewear configuration make the new product experience concretely testable.

03

Platform prepared to expand

Modularization, hardware integrations and migration questions become part of product development.

04

Delivery organized to scale

Experienced specialists work along domain modules and suitable team typologies.