
A PE-backed European dental laboratory network (~80 labs, ~700k orders/year) operating across Germany, Benelux and Scandinavia, engaged through Brightgrove. The group runs a fragmented software landscape — multiple ERPs, legacy lab systems (Talas on MariaDB), and a Microsoft-centric analytics and app layer (Azure SQL, Power BI, Power Apps, Alteryx) on private-cloud infrastructure. There is a small internal IT team; most delivery is handled through external partners.
The customer is consolidating its lab operations onto a common platform — in practice an ERP-style "lab operating system" covering order intake, production steering, lab-to-lab and lab-to-factory (China) data exchange, billing and finance integration. Several workstreams run in parallel: platform engineering on the private cloud (Airflow, CI/CD, containerisation), integration of newly acquired labs into the group data contract, replacement of Alteryx workflows, and concept work for the target platform. Requirements arrive verbally and change frequently; architectural decisions are centralised with one internal decision-owner. Brightgrove supplies engineers under written-instruction, time-and-material terms and needs a senior BA/PO embedded with the customer to convert intent into executable, traceable scope and to be the single point of context across all workstreams. This is a long-running embedded role, not a fixed project.
You will work with the customer's IT Director (sets technical direction, owns all architecture decisions), the operational sponsor who manages day-to-day priorities, and an internal handover contact.
Elicit, structure and document requirements across all active workstreams: process flows, sequence diagrams, data flows, acceptance conditions.
Maintain the backlog so that every item traces to a written instruction, a ticket, and logged hours.
Run discovery and scoping for the target lab platform, including order-to-cash, production and finance/SAP touchpoints.
Keep a decision log: record decisions, name open decisions and their owner, and escalate stalled ones to the customer's decision-owner rather than filling the gap.
Distinguish commissioned scope from new requests, in writing, and hold the boundary calmly.
Act as Brightgrove's context-holder: brief incoming engineers, hand over cleanly, keep the account lead informed of risks early.
Prepare status material for customer and Brightgrove stakeholders.