Strategic Portfolio Management in MedTech: Where Should You Keep Investing?
How MedTech Leaders Can Make Smarter Portfolio Investment Decisions
Medtech companies are not short on opportunities. AI-enabled software, connected implants, remote monitoring, surgical robotics, new pricing models, and expanding global markets all offer paths to growth.
The harder question is where to place the next investment.
Each opportunity carries different demands across product development, regulatory strategy, cybersecurity, data, commercialization, service, and post-market support. As a result, portfolio decisions can no longer rely on market size and revenue projections alone. Medtech leaders also need to weigh technical debt, regulatory effort, data readiness, clinical value, security exposure, and the company’s ability to scale the product after launch.
This article begins a six-part series examining the forces reshaping medtech strategy across Agentic and Software as a Medical Device, smart implants and wearables, and surgical equipment.
MedTech Does Not Have an Innovation Shortage
Most medtech companies have no shortage of promising ideas. Product teams are exploring AI-enabled functionality, connected devices, new clinical applications, remote monitoring, robotics, software-based services, and more personalized patient experiences.
The challenge is deciding which opportunities deserve sustained investment.
That decision has become more difficult because a new product or feature rarely stands alone. An AI capability may require new data pipelines, model governance, clinical validation, cybersecurity controls, regulatory documentation, and post-market monitoring. A connected implant may introduce a patient application, cloud infrastructure, remote support requirements, and new responsibilities for protecting patient and device data. A surgical platform may require coordination across capital equipment, software, consumables, service, training, and hospital integrations.
The initial product concept may look compelling while the full cost and complexity remain unclear.
This is where strategic portfolio management needs to evolve. Medtech leaders must look beyond projected revenue, market growth, and development cost. They also need to understand what each investment will require across the complete product lifecycle—from design and regulatory approval to commercialization, service, cybersecurity, and eventual retirement.
The goal is not simply to identify the products with the largest addressable markets. It is to identify where the company has a credible path to create clinical value, achieve commercial scale, and support the product responsibly over time.
Start with the Right to Win
An attractive market does not automatically make an attractive portfolio investment.
Medtech companies need to ask whether they possess—or can realistically build—the capabilities required to compete. That includes more than the underlying product technology. It also includes clinical expertise, regulatory knowledge, proprietary or trusted data, provider relationships, commercial access, manufacturing capacity, service infrastructure, and the ability to integrate the product into established care pathways.
This is increasingly important as medtech companies actively reshape their portfolios around areas where they have a defensible position and a credible path to scale. PwC’s 2026 midyear medtech outlook highlights that leading companies are concentrating capital in higher-growth, higher-confidence segments and are deliberately evaluating where they have a differentiated “right to win” before committing investment. In other words, portfolio decisions are becoming less about pursuing every attractive market and more about focusing on where the organization can realistically compete and win over time.
Consider an AI-enabled medical device. The algorithm may show promising performance, but that is only one part of the investment case. The company must also secure appropriate data, establish how clinicians will use the output, validate performance for the intended population, manage updates, monitor the product after release, and explain its value to providers and payers.
The same principle applies to connected implants and wearables. Adding connectivity may support remote monitoring and new services, but it also creates responsibilities around patient enrollment, identity, data transmission, alert management, cybersecurity, and technical support.
For Surgical equipment companies, a compelling new platform may still struggle if hospitals face difficult installation requirements, extensive training needs, weak integration with existing systems, or an unclear financial case.
A portfolio decision should reflect the entire capability required to succeed, not only the quality of the product concept.
Are We Funding a Product or an Operating Model?
One of the most common portfolio mistakes is treating the product as the full investment.
A medtech company may approve funding for a new device, software platform, connected feature, or AI capability based on development cost, market opportunity, and projected revenue. But the product itself is only one part of what the organization must build, operate, and support.
Every new product creates an operating model around it.
That model may include data infrastructure, cloud services, integrations, cybersecurity monitoring, regulatory controls, customer support, field service, training, billing, post-market surveillance, and ongoing software maintenance. These capabilities may sit across different departments and budgets, which makes the total investment difficult to see during early portfolio planning.
For Agentic and Software as a Medical Device, the work does not end when the software reaches the market. The organization must manage releases, monitor performance, govern data access, document changes, maintain integrations, evaluate model behavior, and determine when an update requires additional validation or regulatory review. It must also define how clinicians interact with the system, when human review is required, and how users can understand or challenge its outputs.
The cost of maintaining that operating model may equal or exceed the cost of developing the first version of the product.
Smart implants and wearables create a different but equally complex set of responsibilities. Connectivity can extend the value of a device through remote monitoring, patient engagement, earlier intervention, and ongoing services. It can also require patient onboarding, mobile applications, identity management, cloud connectivity, device-data integration, alert routing, technical support, and cybersecurity oversight.
A company must decide who receives the data, who responds to an alert, how quickly they must respond, and what happens when the device loses connectivity. These are not only technical design questions. They affect clinical workflows, patient expectations, support requirements, risk management, and the overall economics of the product.
Surgical equipment companies face similar considerations. A new platform may involve capital equipment, software, accessories, disposables, hospital-system integrations, installation, clinician training, maintenance, and field service. The business case may depend on recurring revenue from software, service agreements, or consumables, but those revenue streams require the company to build the capabilities needed to manage subscriptions, contracts, inventory, upgrades, and customer support.
In each case, the investment extends well beyond product development.
This is why portfolio planning should identify the operating model before the organization commits to the product roadmap. Leaders need to understand which capabilities already exist, which require investment, which can be shared across products, and which may need to come from a partner.
These questions can also reveal opportunities to invest in shared capabilities rather than funding each product independently. A common data platform, device-integration layer, identity framework, customer portal, validation approach, or post-market monitoring capability may support several products across the portfolio.
That changes the investment discussion. Instead of asking whether one product can justify the full cost of a new capability, leaders can evaluate how the capability supports a broader product family or strategic direction.
The portfolio investment is not only the device or software. It is everything the organization must build and operate around it.
Companies that account for that reality early can make better funding decisions, reduce surprises after launch, and create products they can support responsibly at scale.
Can We Commercialize It at Scale?
A strong product does not automatically create a scalable business.
Medtech companies often invest heavily in product development, clinical evidence, and regulatory approval, then discover that the commercial model cannot support the complexity of bringing the product to market. Sales teams may struggle to explain the value, quotes may require manual engineering review, contracts may vary by customer, inventory may be difficult to locate, and service teams may lack the information needed to support the product after deployment.
These issues do not always appear in the initial portfolio business case, but they directly affect revenue, margin, adoption, and customer experience.
Commercial scalability starts with a clear value proposition. The organization must be able to explain not only what the product does, but also how it improves clinical outcomes, reduces operational burden, supports patient care, or creates financial value for the provider. That message must work across different stakeholders, including clinicians, procurement teams, hospital executives, IT leaders, quality teams, and payers.
The complexity increases when the product combines hardware, software, services, subscriptions, consumables, or usage-based pricing.
For Agentic and Software as a Medical Device, commercialization may require a different approach than a traditional device sale. The offering may depend on subscriptions, user licensing, implementation services, data access, or ongoing software updates. The company must determine how to package the product, price it, demonstrate value, manage renewals, and support customers as the software evolves.
The sales process also needs to account for questions that may not arise with a traditional device. Customers may want to understand how the system makes recommendations, what data it uses, how updates are controlled, where human review occurs, and how performance will be monitored over time. Sales, product, regulatory, legal, and security teams need a consistent way to answer those questions.
Smart implants and wearables present another set of commercial challenges. The sale may involve the device itself, supporting software, patient onboarding, remote monitoring, data services, and ongoing clinical engagement. Revenue may depend on adoption by providers and consistent participation by patients, not simply on the initial device placement.
That means commercialization extends into enrollment, activation, training, technical support, reimbursement, and continued use. A product can gain physician interest and still fail to reach expected adoption if patients struggle to connect the device, providers receive too many alerts, or support teams cannot resolve issues quickly.
Surgical equipment companies often face even greater complexity. A commercial offering may include capital equipment, configured components, software, accessories, consumables, service contracts, installation, training, and hospital integrations. Each element may follow a different pricing, approval, fulfillment, and billing process.
Without connected product, pricing, customer, inventory, and service data, the sales cycle can slow quickly. Representatives may rely on spreadsheets, engineering teams may need to validate configurations manually, and operations teams may not receive complete information until after the agreement is signed. These delays create rework, reduce forecast accuracy, and make it harder to deliver a consistent customer experience.
Portfolio leaders should evaluate these commercial requirements before approving investment, not after the product is ready to launch.
These questions may expose gaps in CRM, CPQ, product data, contract management, inventory visibility, order management, billing, or customer service. They may also reveal that the company needs new sales capabilities, partner channels, reimbursement support, or provider engagement models.
The objective is not to eliminate every commercial challenge before development begins. It is to determine whether the company has a practical path from product approval to repeatable revenue.
A portfolio investment should answer more than whether the market wants the product. It should also answer whether the organization can sell, deliver, support, and expand it without rebuilding the commercial process for every customer.
What Is the Full Lifecycle Burden?
Getting a medical device to market is a milestone, not the end of the investment.
Once a product launches, the company takes on years of responsibility for maintaining its safety, performance, security, compliance, and customer value. Those obligations may continue long after the original development team has moved on to the next product.
Portfolio planning often gives significant attention to development, clinical validation, regulatory submission, and launch. It may give far less attention to the continuing work required to support the product throughout its commercial life.
That work can include:
Each requirement adds cost, risk, and organizational complexity. Some products may remain profitable despite that burden. Others may consume resources that could support higher-value opportunities elsewhere in the portfolio.
The burden can be especially significant for Agentic and Software as a Medical Device. Software products may require frequent updates to address defects, improve performance, maintain compatibility, or respond to changing clinical and customer needs. AI-enabled products may also require ongoing monitoring to determine whether performance remains consistent across users, populations, and operating environments.
Each change can trigger questions about validation, documentation, intended use, risk controls, and regulatory impact. The organization needs a disciplined process for deciding which changes can move forward, what evidence is required, and how the update will be deployed and monitored.
The company must also support the technology surrounding the product. Cloud platforms evolve. APIs change. Security vulnerabilities emerge. Data sources shift. Hospital systems update their integration requirements. A software product that performs well today may become difficult to maintain if its architecture, dependencies, or data pipelines cannot adapt.
Smart implants and wearables introduce long-term responsibilities that may extend well beyond the physical device. Companies may need to maintain mobile applications, connectivity services, patient portals, clinician dashboards, and remote monitoring capabilities for many years.
They must also account for what happens when a supporting technology reaches end of life. A mobile operating system may stop supporting an older application. A wireless standard may change. A cloud service may be retired. A third-party component may no longer receive security updates.
These decisions become more sensitive when patients rely on the product or when the device remains implanted for an extended period. The company may need to support several generations of hardware and software at the same time while maintaining clear compatibility, update, and service policies.
Surgical equipment companies face similar challenges. Capital equipment may remain in hospitals for years or even decades. During that time, the company may need to maintain replacement parts, service expertise, training materials, cybersecurity protections, software compatibility, and integrations with changing hospital environments.
A product may still generate service or consumables revenue, but it may also depend on aging components, specialized technicians, or legacy systems that become increasingly expensive to maintain. Without clear lifecycle visibility, the company can underestimate the true cost of supporting an installed base.
These questions can reveal whether a product that appears attractive at launch will remain viable over time.
They can also help leadership identify where modernization is necessary. A strong clinical product may still require a new software architecture, data platform, service model, or integration approach to remain supportable. In other cases, the lifecycle burden may point toward partnering, consolidating overlapping products, or retiring an offering that no longer fits the company’s strategy.
The purpose of lifecycle planning is not to discourage investment. It is to make sure leaders understand the responsibility they are accepting.
A medtech company does not simply sell a product. It commits to protecting patients, supporting customers, maintaining compliance, and preserving product performance for as long as that product remains in use.
What Should We Modernize, Partner for, Acquire, or Retire?
Strategic portfolio management is not only about deciding what to fund. It is also about choosing the right path for each product, platform, and capability.
Some opportunities justify internal investment. Others may be better served through modernization, partnerships, acquisitions, consolidation, or retirement. The strongest portfolio decisions recognize that these options are not interchangeable.
Building internally may give a company greater control over the product, data, intellectual property, and customer experience. It may also require more time, specialized talent, regulatory effort, and long-term support than the organization expects.
A partnership may provide faster access to technology, market reach, clinical expertise, or operating capabilities. But it can also introduce dependencies around data, integration, support, security, product roadmaps, and customer ownership.
An acquisition can accelerate entry into a new category or fill a capability gap, but the value depends on how well the acquired product fits the broader portfolio and how effectively the company integrates its systems, processes, teams, data, and commercial model.
Modernization may be the right choice when an established product still has market value but depends on aging technology, fragmented data, manual workflows, or unsupported integrations. In other cases, the company may need to consolidate overlapping offerings or retire products that no longer justify their cost, risk, or strategic attention.
The right answer will vary by segment.
For Agentic and Software as a Medical Device, leaders may need to decide whether to build an AI capability directly into a regulated product, offer it as a separate workflow tool, partner with a specialized technology provider, or acquire an existing platform. That choice affects regulatory scope, data access, validation, cybersecurity, intellectual property, and ongoing model oversight.
A company may also need to modernize legacy software before adding new AI capabilities. Layering an agent or predictive model onto fragmented applications and inconsistent data can create more risk than value. In that situation, the strategic investment may need to begin with architecture, integration, and data readiness rather than the AI feature itself.
For smart implants and wearables, companies may need partners for connectivity, cloud infrastructure, mobile applications, patient engagement, analytics, or remote monitoring. These partnerships can speed development, but they also create long-term responsibilities. Leaders need to understand who owns the patient and device data, who maintains the integration, how security incidents will be handled, and what happens if the partner changes direction or leaves the market.
Acquisition may make sense when the company needs a mature capability, existing evidence, an installed customer base, or specialized talent. But the acquired technology must fit the company’s quality systems, regulatory strategy, product architecture, and support model. Without that fit, the organization may inherit another disconnected product rather than a scalable strategic capability.
Surgical equipment companies often face difficult decisions around mature product lines. An established platform may still generate revenue but depend on outdated software, aging components, manual configuration, or specialized service knowledge. The company must decide whether to modernize the platform, limit investment, consolidate it with another offering, or begin a structured retirement.
These decisions should consider more than current sales. A mature product may remain valuable because of its installed base, service revenue, consumables, customer loyalty, or clinical role. At the same time, it may create hidden costs through cybersecurity exposure, component shortages, fragmented support, and technical debt.
The answers should lead to a deliberate portfolio action, not another year of limited investment and unresolved complexity.
A useful approach is to classify each product or capability into one of five paths:
These categories create a clearer connection between strategy and execution. They also force leadership to make decisions that may otherwise remain unresolved across several planning cycles.
The most expensive portfolio choice is not always the wrong acquisition or failed product launch. Sometimes it is continuing to fund products and platforms that the company has never clearly chosen to grow, modernize, consolidate, or retire.
Strategic portfolio management should make those choices visible and give the organization a practical path forward.
A Practical Lens for Portfolio Decisions
In my experience, portfolio discussions become more productive when teams evaluate opportunities through a common lens.
Instead of debating one product at a time from a single perspective, leadership can assess each opportunity across the factors that most often determine success or failure in medtech. That includes not only market potential, but also commercialization, technology readiness, lifecycle burden, and strategic fit.
The goal is not to turn portfolio planning into a scoring exercise. It is to create a more complete view of what the company is truly choosing to fund.
No single factor should determine the decision on its own.
A product may score well on market opportunity but create a heavy regulatory or support burden. Another may have modest near-term revenue potential but align strongly with the company’s technology base, customer relationships, and long-term strategy.
This kind of framework helps leadership compare opportunities more consistently and make clearer choices about where to invest, where to modernize, where to partner, and where to step back.
Better Portfolio Decisions Require a Connected View
Strategic portfolio management works best when clinical, product, regulatory, quality, commercial, service, finance, data, and technology leaders are looking at the same opportunity through the same lens.
That connected view helps leadership see where an investment creates value, where hidden dependencies exist, and where the organization may be underestimating the work required to bring a product to market and support it over time.
It also makes the hard choices clearer.
Some products deserve more investment. Others need modernization before further expansion. Some capabilities may be better built through partnerships or acquisitions. And some products may no longer justify the regulatory, technology, service, or operational burden they carry.
The objective is not to remove uncertainty from medtech innovation. That is not realistic. The objective is to understand the tradeoffs earlier and make deliberate choices about where the organization can create clinical value, build a sustainable business, and support the product responsibly.
Once those choices are made, the next question becomes just as important: how quickly can the organization turn a strong portfolio decision into customer adoption and revenue?
In the next article in this series, we’ll look at Commercial Velocity and why medtech companies need to remove friction across the entire path from opportunity to revenue, not just ask sales teams to move faster.
