Begüm Yüzgülen
Full Stack Engineer
5 min read
Recovering a CMS that nobody in the building owns
5 min read
22 August 2026

Strategy and technical delivery
We combine MedTech expertise, governance and technical delivery – from AI strategy to integration with existing workflows and systems.
Move from AI ambition to governed adoption, operational workflows and connected platforms.
Where transformation gets stuck
We align business, IT and compliance around one transformation path—then prove it in a focused workflow.
See our approachWhat we do
One partner for strategy, workflow automation and digital platforms.
How it operates
The solution runs inside infrastructure agreed with your IT team—not on a shared Veren platform.
How we work in regulated environmentsOnly trusted sources and approved versions.
ERP, CRM, PIM, CMS, QMS and documents stay connected.
People approve sensitive and visible actions.
Inputs, decisions and follow-ups stay documented.
Models can change without rebuilding the workflow.
Code, accounts and operating knowledge remain yours.
Geuder AG
01A B2B customer portal and shared workspace that connects product data, AI-assisted content work and guided product experiences.
See the Geuder AG case studyTecan AG
02A discovery across teams, markets and systems, translated into a shared platform blueprint and implementation roadmap. Currently in progress.
See the Tecan AG case studyEpiseras
03We translated a complex neurotechnology product, technical inputs and launch priorities into a clear product story and a focused digital product platform.
See the Episeras case studyOpen live platformMEDNET
04A structured Product Finder that makes a large medical-component catalogue searchable and turns product discovery into a qualified inquiry.
See the MEDNET case studyFlash Biolab
05A guided digital journey for a contract manufacturer, with clear capabilities, a transparent process and an interactive project check.
See the Flash Biolab case studyA practical first step
We turn one recurring medtech process into a working AI workflow—connected to your existing systems, governed by clear rules and tested with the team that uses it.
Identify a recurring process with clear ownership, available data and visible value.
Define inputs, decisions, exceptions and where human approval remains essential.
Connect the relevant systems and implement a working workflow around your current operations.
Test it in daily work, measure the result and decide what should scale next.
One workflow. Clear scope. A working result.
Discuss your pilot workflowAI Automation example
Choose a workflow. See the path from input to approved outcome.
Input
Email, web or phone
Operational AI
Understands the product question
Connected systems
Built around the systems you already use.
Outcome
Approved answer. The next action is logged.
Choose a workflow
Input
Email, web or phone
Operational AI
Understands the product question
Connected systems
Built around the systems you already use.
Outcome
Approved answer. The next action is logged.

Merdan Özdogan
Chief Executive Officer
Strategy, UX, Project leadership

Victor Daj
Chief Technical Officer
Architecture, Development, Technical leadership

Begüm Yüzgülen
Full Stack Engineer
Product features, APIs, Frontend and backend

Ievgeniia Dubrovska
SEO & GEO Expert
Search strategy, AI visibility, Content intelligence

Ionut Burghel
Principal AI Engineer
APIs, Infrastructure, Systems architecture

Samuel Niguleasa
AI Native Engineer
Agent tooling, Prototyping, Applied AI

Denis Sorescu
AI Native Engineer
AI-assisted development, prototyping, automation

Silviu Vijiala
Senior AI Native Engineer
AI architecture, agent systems, integrations

Paul Bucea
Senior Project Manager
Delivery, Planning, Client communication

Bogdan Monea
Frontend Architect & Design Systems
Interface architecture, Design systems, Performance

Jose Rodriguez
DevOps Architect & Integrations
Infrastructure, Deployment, Third-party integrations
Our team consists of seasoned experts with a genuine passion for technology and design — the same people you’ll work with from first call to launch.
It covers AI strategy, use-case priorities, governance and technical delivery. The delivery can include controlled workflows, system integrations and digital platforms.
Start with recurring work that has a clear owner, approved source information and an outcome the team can review. Product enquiries, service cases and document requests are common starting points.
Usually not. We connect the systems already responsible for product data, customers, content and documents. A new platform is considered only when the existing setup cannot support the required workflow.
It runs in infrastructure agreed with your IT team. It is not a shared Veren platform, and the client retains control of the relevant code, accounts and operating knowledge.
They help define approved sources, responsibilities, exceptions, review steps and records before implementation. They remain involved in review and acceptance where the workflow requires it.
A focused discovery usually takes two to four weeks. It produces priorities, a system and information map, governance decisions and an implementation roadmap. Delivery time then depends on the selected workflow.
Align the business case, governance and first implementation—without starting a large programme.