01 — The system
Three companies, one version of the truth.
02 — Manufacturing Collaboration
From a partner site down to a single parameter.
The problem. Sponsors lacked timely visibility into production at their partners' sites, so issues surfaced late.
What I designed. A shared view of production at partner sites: purchase orders, incoming materials, batch and manufacturing status, and deviations. Sponsor and partner read the same record, so neither side has to ask the other for an update.
A key decision. Lead with exceptions, not with tables. Partners range from spreadsheets to full ERP, so the data is dense and uneven. The view opens on what needs attention, such as an open deviation or a delayed batch, and keeps the full detail one level down.
03 — Tech Transfer
Scattered files, turned into one milestone plan.
The problem. Moving a product to a new manufacturing site meant transfer information scattered across files, which caused errors and delays.
What I designed. One workspace for each transfer: a milestone plan, a standard set of documents, and a clear owner on both sides for every step.
A key decision. Structure over storage. A better file folder would still leave people hunting. Instead, every document belongs to a milestone and an owner, so progress is visible at a glance and nothing waits in someone's inbox.
04 — Logistics Collaboration
Every shipment visible. No follow-up emails.
| ASN | Route | Contents | Conditions | ETA | Status |
|---|---|---|---|---|---|
| ASN-0042 | Partner site 02 → Sponsor DC | 6 pallets · 1.2 t | 4.8 °C · in range | Thu | In transit |
| ASN-0039 | Partner site 01 → Sponsor DC | 2 pallets · 0.4 t | 8.6 °C · check | Wed | Needs attention |
| ASN-0037 | Partner site 03 → Partner site 02 | 4 pallets · 0.9 t | 21 °C · in range | Fri | In transit |
| ASN-0031 | Partner site 01 → Sponsor DC | 3 pallets · 0.7 t | — | Mon | Received |
The problem. Shipments between partner sites and the sponsor needed constant manual follow-up.
What I designed. A shipment journey from plan to delivery, shared with logistics partners: advance shipment notices, inbound deliveries, and the pallet, weight and sensor details for each shipment.
A key decision. One status everyone agrees on. Each shipment shows a single, honest status that the sponsor, the partner and the 3PL all see, with messages attached to the shipment itself rather than a separate email thread.
05 — Designing inside the rules
What made this hard.
- GMP compliance. Every screen has to hold up in a regulated, audited environment.
- Audit-ready records. Who changed what, and when, is part of the product.
- Many companies, one record. Sponsors, partners and 3PLs each see their own slice of the same data.
- Enterprise integrations. Data flows in from ERP/SAP, MES, QMS and LIMS, each with its own structure.
06 — Outcome
What it delivers.
The designs support Mosymphony's product demos, client onboarding and investor presentations, and are built around the requirements of enterprise clients at global pharmaceutical companies.
Providing full transparency and traceability for end-to-end manufacturing processes, for both manufacturers and sponsors.
07 — What I learned
Clarity is a safety feature.
At Collabrix, I designed B2B SaaS products that simplify complex pharma and supply-chain workflows. I turned fragmented processes and dense data into clearer dashboards, workflows and decision-making experiences.
My work helped make complex enterprise processes easier to understand, navigate and act on.