Real Deployments

From Siloed Approach to Governed Roadmap for CDMO

Concept to Launch – What changed?

Explore our proven pharma case studies to learn how PMSoft drives successful project delivery, regulatory compliance, and operational excellence for global life sciences organizations

Case Study 01 – NPD-Project Management – CDMO

A CDMO’s path from 141 scattered process gaps to a single prioritized NPD roadmap

Multi-site pharma & agrochemical CDMO, India · Modules used: NPD Project Management

What leadership gained: one ranked NPD roadmap across sites, and dashboard visibility of every project without waiting for review meetings.

Result highlights

30%

Fewer cross-functional review meetings

Fewer

Products sent back to earlier stages for rework

Global

Dashboard visibility for CDMO pipeline prioritization

The 141 raw findings were consolidated into a prioritized issue register – a single ranked roadmap leadership could act on.

Challenge

A structured project-management maturity assessment – competency and perspective surveys run across all four business units against a five-level maturity model – placed the organization at the lowest maturity stage: project delivery dependent on individual expertise rather than repeatable process, minimal formal PM knowledge, and no shared vocabulary across functions. The underlying issue log bore this out. Across the full new-product lifecycle – from product initiation through feasibility studies, process optimization, linking activity to cost and status, and cross-functional review meetings that varied inconsistently from one project to the next.

Solution

PMSoft ran a full As-Is process validation exercise across every NPD stage, capturing – for each process step – its inputs, outputs, activities, stakeholders, templates, checklists, sign-off authority, and outsourcing dependencies. The 141 raw findings were consolidated into a prioritized issue register, mapped by process, originating function, severity, and impact on critical path and rework – replacing a scattered list of complaints with a single ranked roadmap leadership could act on.

Result

Once the redesigned process and governance model were rolled out, cross-functional review meetings dropped by 30% – a direct result of clarified roles and sign-off authority at each stage removing the need for repeated status-alignment sessions. Products moving backward to earlier development stages for rework became measurably less frequent, as handoff gaps between R&D, Manufacturing, and QA that had previously caused late-stage surprises were closed at the process-design stage. Perhaps most valuably, Business Development teams gained dashboard-level visibility into project status across every site and business unit for the first time – giving them a real basis to prioritize which CDMO opportunities to pursue, instead of relying on ad-hoc updates and individual relationships.

Related: API tech transfer to a CDMO – key risks →

Case Study 02 – Formulations – Lifecycle Redesign

Redesigning the Product Development Lifecycle for a Formulations Manufacturer

Sector: Pharma & Chemical – Formulations / Generics · Engagement: Product Management transformation – diagnostic, process redesign, and rollout · PMSoft role: Lead consulting partner, Central Product Office design, and rollout enablement

What changed

Single Accountable Product Ownership

Stage Gates That Mean What They Say

Enterprise-Level Portfolio Visibility

The Client

A well-established formulations manufacturer with a healthy, growing product pipeline and a strong track record of first-time-right regulatory filings. Product development was coordinated through a Project Management Office (PMO), and the organisation had real strengths to build on: emotionally committed teams, open internal communication, and genuine management support for improvement.

But growth had outpaced process. The PMO had authority to coordinate projects – not to control them. Product development ran on activity tracking rather than product ownership. And a set of underused strengths – resource visibility, exploratory technology adoption, access to live project data – were sitting on the table.

The organisation was managing projects well, but not managing products.

The Challenge

Working directly with senior leadership and the PMO, PMSoft ran a structured diagnostic across the full product lifecycle – from Product Initiation Form (PIF) through regulatory filing and approval – assessed against 24 management parameters spanning scope, schedule, cost, quality, resourcing, risk, procurement, training, and governance. The diagnostic surfaced a consistent pattern. Specific gaps included:

  • No single product owner. Accountability was distributed across functions with no one holding the product from concept to launch.
  • Stage gates measured planning, not delivery. Gates could be crossed without deliverables actually being complete, creating downstream rework and hidden multitasking.
  • Completion tracked by duration, not fact. Activities were reported as a percentage of elapsed time rather than a binary done/not-done, masking real project health.
  • IVIVC treated as optional. A capability with outsized downstream value was being used inconsistently rather than built into the standard process.
  • No formal closing process. Products that should have been dropped for business reasons often weren’t – quietly inflating work-in-progress.
  • No enterprise-level visibility. Leadership lacked a single dashboard view across the portfolio; status lived in meetings, email threads, and individual spreadsheets.

The Approach

PMSoft’s engagement followed a Thinking → Doing → Delivering framework – first defining what “better” actually meant for this business, then redesigning the operating model, then building the rollout plan to make it stick.

Thinking – reframing the operating philosophy

The core shift was moving from a Project Management Office to a Central Product Office (CPO) – with three distinct layers of accountability: a Product Owner setting direction from the business side, a Product Manager managing delivery, and functional teams executing. This reframed the PMO’s role from coordinator to controller, and reframed “project managers” as product managers – shifting the organisation’s focus from completing activities to delivering products.

Doing – redesigning the lifecycle end to end

PMSoft redefined the stage-gate model itself, introducing:

  • A Full-Kit philosophy – no stage gate passes without its “must-meet” deliverables genuinely complete.
  • Three-level planning (Project / Stage / Team) replacing single-point stage-gate meetings.
  • Milestone-based control at roughly 10-15% intervals through each stage.
  • Mandatory IVIVC, moving it from a nice-to-have to a standard input.
  • A relay-race handover model between functions (sender-receiver accountability).
  • Product-level cost tracking alongside project cost.
  • A formal closing process with explicit criteria for dropping a product.

Delivering – making the redesign stick

PMSoft structured delivery around a tiered engagement model, letting the client choose the right level of tooling investment for their maturity and budget, while keeping the core deliverables consistent:

  • Central Product Office design and setup support
  • A rollout workshop run directly with the PMO and cross-functional teams
  • A written process handbook covering every redesigned stage and gate
  • Formal project/product management education for the PMO team
  • Tool training and hands-on configuration support
  • A post-rollout compliance audit

The Outcome

The redesigned lifecycle gave the client a genuinely different operating model, not just a relabeled one:

  • Single, accountable product ownership from concept through launch, replacing distributed, ambiguous responsibility.
  • A stage-gate process that means what it says – gates now represent real completion, not a scheduled meeting date.
  • Enterprise-level visibility into the product portfolio for senior leadership, with clear go/no-go decision points backed by product-level cost data.
  • A repeatable data asset in the form of the organisation’s own IVIVC model, compounding in value with every future product that runs through it.
  • A documented, trainable process – captured in a process handbook and embedded through direct PMO education, rather than living only in the heads of a few senior people.

Client details in this case study have been generalised to protect confidentiality. Specific metrics and outcomes are available on request under NDA.

Case Study 03 – Regulatory Query Management – Formulations

Beyond the Gantt chart: what one deficiency letter taught us about pharma leadership

Formulations company, Pune, India · 2019 · Area: agency query responses across functions

What leadership gained: one view of every open question, its owner and its due date, without access to confidential documents.

A deficiency letter with fourteen questions, answered by five functions through email, led to an extension and a second round of questions. A single management register, with one owner and one internal due date per question, changed how the next letter was handled, and showed us what leadership needs beyond project management.

Read the full case study

Want to see how this would look for your workflow?

Not a generic demo – we walk through your actual NPD, CDMO, or CRAMS process.

Book a 45-minute review