
The shift determines whether Pfizer can sustain earnings after pandemic peaks and navigate looming patent expirations, making its oncology and obesity bets critical for investors and the broader pharma landscape.
Pfizer’s earnings surge during the pandemic has largely receded, with 2024 revenue slipping to $63.6 billion after a peak of $101.2 billion in 2022. The decline reflects waning demand for its Comirnaty vaccine and Paxlovid antiviral, prompting the company to strip COVID‑related earnings from its 2026 outlook. This normalization forces Pfizer to confront a $1.5 billion patent‑cliff headwind and to prove that its core commercial engine can deliver sustainable growth.
Oncology now sits at the heart of Pfizer’s pipeline renaissance. The $43 billion Seagen acquisition supplies four marketed products and, more importantly, an antibody‑drug conjugate platform that can be paired with Pfizer’s existing immuno‑oncology assets. Complementing this, a $1.25 billion upfront deal with 3SBio secures a PD‑1×VEGF bispecific antibody, a modality designed to enhance checkpoint inhibition with anti‑angiogenic effects across solid tumors. With over 40% of R&D spending earmarked for oncology, Pfizer aims to launch roughly 20 pivotal studies in 2026, betting on these advanced backbones to offset upcoming losses on drugs like Eliquis and Ibrance.
Beyond cancer, Pfizer is re‑entering the metabolic arena through the $4.9 billion Metsera acquisition, which brings an ultra‑long‑acting, once‑monthly GLP‑1 candidate poised to compete in the fast‑growing obesity market. The deal, coupled with a licensing pact for an early‑stage GLP‑1 from YaoPharma, expands Pfizer’s cardiometabolic portfolio while diversifying revenue sources. To fund these ambitions, the company targets $7.7 billion in cost savings by 2027, redirecting efficiencies into pipeline development. Execution risk remains high—managing 20 pivotal starts and competing against entrenched GLP‑1 leaders will test Pfizer’s ability to translate its post‑COVID strategy into long‑term value.
Comments
Want to join the conversation?
Loading comments...