G2Research Hub
Skip to content
Executive Summary

What We Found

99%

AI Is Rewriting the Roadmap

AI is no longer a side initiative. Nearly every team reported that it is now influencing product roadmap and planning decisions in a material way.

56%

Balanced Commitment Is the Dominant Posture

The most common investment model is not all-in transformation, but steady capacity reallocation toward AI while core product work continues.

52%

Speed Favors Vendor-Led Execution

A slim majority prefer buying or wrapping vendor APIs and tools, showing that time-to-market is often winning over fully custom development.

79%

The End State Is Invisible AI

Most product leaders expect AI to fade into the product experience as an embedded enhancement, rather than remain a standalone feature or interface.

Why this matters · For SaaS vendors

Why SaaS Software Vendors Should Care About This Study

OPPORTUNITY 01

Sponsor Spotlight — Aha! · Tier 2 (silver)

Vendor Implication
OPPORTUNITY 02

Sponsor Spotlight — Amplitude · Tier 2 (silver)

Vendor Implication
OPPORTUNITY 03

Sponsor Spotlight — Productboard · Tier 1 (bronze)

Vendor Implication
OPPORTUNITY 04

Sponsor Spotlight — Launchdarkly · Tier 1 (bronze)

Vendor Implication
OPPORTUNITY 05

Lead With Roadmap Validation, Not Feature Lists

Vendor Implication
OPPORTUNITY 06

Win the Governance-Speed Tension

Vendor Implication
OPPORTUNITY 07

Solve the Hybrid Architecture Problem

Vendor Implication
OPPORTUNITY 08

Prove Value on Both Sides of the Business

Vendor Implication
OPPORTUNITY 09

Become Infrastructure Before the Market Consolidates

Vendor Implication
OPPORTUNITY 10

Help Buyers Meet Customer Expectations Faster

Vendor Implication
Chapter 01

AI Has Moved From Exploration to Roadmap Reality

AI is no longer a side bet: it is actively reshaping product planning, driven in part by rising customer expectations. But that urgency collides with governance, compliance, security, and broader execution uncertainty, creating the core strategic tension teams must navigate.

We have several initiatives that we are testing right now. So one is from feature road map to capability road map. Where we use to plan around discrete features. Now we plan around AI capabilities. Like search, summarization, classification, generation, agent workflows, and let product teams plug into those. That forced us to pause several road map items to rebuild foundation first.

Project Manager, Unknown Organization

Listen
Finding 1.1

AI Impact on Product Roadmap and Planning

99%
of respondents said AI is impacting product roadmap and planning
Key Takeaways
01
02
03
Strategic Implication
AI Impact on Product Roadmap and Planning - Label Distribution
40%
Full roadmap rewrite / AI-first shift
Full roadmap rewrite / AI-first shift
40%
Moderate roadmap reprioritization
35%
Minor tweaks, not a wholesale rewrite
25%
Incremental feature or roadmap adjustment
<1%
Listen

We had a number of bolt on features and expansions into other technology areas, like integration with different ERPs that we had to put on hold in order to get right the AI

Chief Technology Officer, Global Pharmaceutical Manufacturing
when asked about Moderate roadmap reprioritization
Listen

And better data better research that we could do maybe twelve months ago. We are not rewriting product road map as such, but we are writing it better. With generative AI.

Head of Architecture, Global Telecommunications
when asked about Minor tweaks, not a wholesale rewrite
Finding 1.2

Customer Perception of AI as Must-Have Vs Novelty

60%
of respondents discussing AI see it as must-have or increasingly expected
Key Takeaways
01
02
03
Strategic Implication
Customer Perception of AI as Must-Have vs Novelty - Label Distribution
60%
Must-have / increasingly expected
Must-have / increasingly expected
60%
Mixed or role-dependent necessity
26%
Novelty / nice-to-have
13%
Mostly novelty / nice-to-have
<1%
Listen

it's it's a it it's at a, must have now. So it's more con it's considered to be more akin to table stakes. But there's still a premium premium premiumization aspect to how they perceive AI.

Head of Pricing and Packaging, None
when asked about Customer Perception of AI as Must-Have vs Novelty
Listen

I'd say to mix when it is under the hood, like, when we are using AI features to auto categorize transactions, for example, they are a must have. But when I talk about insights and how we use AI to help them understand how their business is performing, it's is still a novelty to them.

Senior Product Manager, None
when asked about Customer Perception of AI as Must-Have vs Novelty
Finding 1.3

Governance, Compliance, and Security Constraints on AI

Key Takeaways
01
02
03
Strategic Implication
Governance, Compliance, and Security Constraints on AI - Label Distribution
High compliance and security constraints55%
Low / light governance constraints45%
Listen

That is a problem that we have with our customers where nine times out of 10, we'll always get the question around you know, are you training our data? How are you using our data? Is our data, you know, leaving the jurisdiction?

Chief Technology Officer, None
when asked about Governance, Compliance, and Security Constraints on AI
Listen

The reason behind that is that some of these customers have a very I would say, strict requirements because they do have to what do we call it, the be compliant with the regulators and the financial lens of the government or the central banks and the regulatory framework, I would say.

Head of Product Management, one of the top banks in Canada
when asked about Governance, Compliance, and Security Constraints on AI
Finding 1.4

Primary Bottlenecks and Strategic Risks in AI Adoption

97%
of respondents discussed primary bottlenecks and strategic risks in AI adoption
Key Takeaways
01
02
03
Strategic Implication
Primary Bottlenecks and Strategic Risks in AI Adoption - Label Distribution
42%
Execution speed and strategic uncertainty
Execution speed and strategic uncertainty
42%
Reliability, trust, and adoption risk
30%
Compliance and vendor ecosystem risk
27%
Execution, integration, and adoption friction
<1%
Listen

And that's there's a risk inside the strategy because you have you don't have a strategy in a long period. You have to review it every two or three months.

Data Manager, Verweeg enterprise
when asked about Primary Bottlenecks and Strategic Risks in AI Adoption
Listen

Still makes it very difficult to test and also to fully trust. Especially at a enterprise scale when, you know, let's say, one of our clients, like a health insurer, you can't be get a different answer every time.

Product leader, Salesforce
when asked about Primary Bottlenecks and Strategic Risks in AI Adoption
Chapter 02

Teams Are Making Room for AI Through Controlled Commitment

Rather than going all-in blindly, most teams are balancing AI investment while carving out capacity from adjacent work. To reduce the risk of wasted effort, they lean on customer research and co-design as a practical validation mechanism before building.

So we are roughly around 30% of the engineering capacities are focused on AI initiative right now, Initially, we started with 10%, but now it's has been increased over the time. Up to 30%, and the rest remains on the product maintenance integrations feature development, customer satisfaction, client, department, and stuff like that.

IT Manager

Listen
Finding 2.1

AI Resource Allocation and Capacity Commitment

Key Takeaways
01
02
03
Strategic Implication
AI Resource Allocation and Capacity Commitment - Label Distribution
Balanced but growing AI investment57%
AI-dominant capacity commitment28%
Minimal / limited AI allocation15%
Listen

We have ramped up our engineering capacity to, our dedicated, engineering capacity for AI projects to about 75% of our engineering development organization.

Group Product Manager, Large Technology Company
when asked about AI-dominant capacity commitment
Listen

Yeah. We were gonna change our our kind of front end point of sale system. And that got canned because we needed the money to basically push it into the AI projects.

Global Technology Leader, Retail
when asked about AI-dominant capacity commitment
Finding 2.2

What Gets Deprioritized to Make Room for AI

52%
of respondents said adjacent work was deprioritized to make room for AI
Key Takeaways
01
02
03
Strategic Implication
What Gets Deprioritized to Make Room for AI - Label Distribution
52%
Adjacent work deprioritized (technical debt, UX, exploration, expansion)
Adjacent work deprioritized (technical debt, UX, exploration, expansion)
52%
No visible tradeoffs / AI is additive
29%
Core non-AI product work deferred for AI
18%
Budget/profit/staffing reallocation drove tradeoffs
1%
Listen

Well, we deprioritized technical debt. All the time, unfortunately. So there's a lot of paper cuts in our product that hurts our usability or the experience that we intend to fix, but have to trade off for the sake of more quickly innovating, AI development.

Group Product Manager, big tech company
when asked about What Gets Deprioritized to Make Room for AI
Listen

We had a number of bolt on features and expansions into other technology areas, like integration with different ERPs that we had to put on hold in order to get right the AI

Chief Technology Officer, a large global manufacturing company in the pharmaceutical business
when asked about What Gets Deprioritized to Make Room for AI
Finding 2.3

How Teams Validate AI Use Cases Before Building

Key Takeaways
01
02
03
Strategic Implication
How Teams Validate AI Use Cases Before Building - Label Distribution
Customer research and co-design68%
Pragmatic pilots and lightweight testing18%
Business-case / stakeholder-led validation14%
Listen

We have a dedicated user research team who conducts very extensive research on our customer segments to understand what they want and what they need and the value that they would get from any features that we build.

Group Product Manager, large tech company
when asked about How Teams Validate AI Use Cases Before Building
Listen

What we always do is we would have, set of customers whom we call as, like, our design partners. Before we even start building that, we would go to them and we would validate some of these concepts

Senior Director of Product Management, Salesforce
when asked about How Teams Validate AI Use Cases Before Building
Chapter 03

Pragmatic Technical Choices Create New Dependency Questions

Execution pressure pushes teams toward faster build-vs-buy decisions, with vendor APIs and hybrid approaches emerging as the practical default. That speed comes with a downstream consequence: vendor reliance is being managed, but ownership of ecosystem risk is still not fully settled.

We primarily wrap, with the external APIs like OpenAI and Antopartic. So rather than, like, building the proprietary models from scratch, this allows us to leverage the state of the art, AI quickly without, the huge investment in the training and maintenance and stuff like that.

IT Manager

Listen
Finding 3.1

AI Build-Vs-Buy and Technical Architecture Strategy

Key Takeaways
01
02
03
Strategic Implication
AI Build-vs-Buy and Technical Architecture Strategy - Label Distribution
Buy / wrap vendor APIs and tools53%
Hybrid build-and-buy35%
Build in-house / proprietary models12%
Listen

Yeah. So we are actually doing both. So, we are building some models, our own proprietary models, and we also provide the capability where we are wrapping some APIs over OpenAI and Anthropic. So we do both.

Senior Director of Product Management, Enterprise Software
when asked about Hybrid build-and-buy
Listen

So we are, at this point, like, we are still not allowed to use any of the AI tools, that are already in the market. We have instead developed our own internal tool, that, you know, we developed it last year.

Aerospace Systems Engineer, Space Technology
when asked about Build in-house / proprietary models
Finding 3.2

Vendor Dependency and Ecosystem Risk Management

87%
of respondents discussed vendor dependency and ecosystem risk management
Key Takeaways
01
02
03
Strategic Implication
Vendor Dependency and Ecosystem Risk Management - Label Distribution
44%
Cautious managed reliance
Cautious managed reliance
44%
Low concern / accepted vendor reliance
40%
Active vendor lock-in mitigation
7%
Issue deferred, unclear ownership, or limited visibility
5%
Low concern due to buffers or positioning
4%
Trusting or positive reliance
1%
Listen

So, to manage those risk we have what we call as the trust layer. So what that ensures is that any data which is passed to vendors like OpenAI or Anthropic, needs to first go through the trust layer, which we have built ourselves.

Senior Director of Product Management, Salesforce
when asked about Vendor Dependency and Ecosystem Risk Management
Chapter 04

AI Value Is Broad, Embedded, and Increasingly Monetized

Where teams have found traction, AI is not confined to a single use case: it creates value across both customer-facing experiences and internal operations. Commercially, companies are already translating that value into pricing strategies, most often through bundled offers and premium tiers.

It will be much more personalized for the consumer, and internally, we will be able to develop new products and features faster. Due to AI.

Senior Lead Product Manager

Listen
Finding 4.1

Where AI Creates Value in the Product and Business

86%
of respondents said AI creates both customer-facing and internal value
Key Takeaways
01
02
03
Strategic Implication
Where AI Creates Value in the Product and Business - Label Distribution
Hybrid customer-facing and internal value
86%
Internal efficiency and operational value
11%
Customer-facing product value
3%
Listen

Well, I think, with AI, and and if it's well programmed and done, customer get a very, good and easy access to our to our pro products and, we can save, customer service time and cost.

Senior Business Analyst, Software Rollout
when asked about Hybrid customer-facing and internal value
Listen

Even I had a magic wand, I will eliminate the giant of integrating high seamlessly into a system workflows. So that our teams could deploy their features quickly reliably, and without disrupting current processes. Thus, maximizing value for both customer and internal users.

Chief Technology Officer
when asked about Hybrid customer-facing and internal value
Finding 4.2

AI Monetization and Pricing Strategy

Key Takeaways
01
02
03
Strategic Implication
AI Monetization and Pricing Strategy - Label Distribution
Bundled / no separate AI pricing44%
Premium or direct AI monetization34%
Usage-based or cost-pass-through pricing23%
Listen

These features are typically baked in to those various editions. So you wouldn't pay more explicitly to for an AI feature. You would go and get it as part of those existing categories.

Product leader, Salesforce
when asked about AI Monetization and Pricing Strategy
Listen

we basically ended up restructuring bundles So there was, like, a core, an advanced, and then an intelligent or the AI powered set of capabilities. So basically, like, tiered and charge differently accordingly.

Associate Director of Product Operations, None
when asked about AI Monetization and Pricing Strategy
Chapter 05

The End State Is AI as Invisible Product Infrastructure

The forward-looking opportunity is not simply to add more AI features, but to normalize AI as an embedded, largely invisible enhancement to the overall product experience.

AI is embedded into the core product, and so we don't pitch the We don't need to pitch the air features separately.

Head of Product, Advertising Technology

Listen
Finding 5.1

Future Product Experience Shaped by AI

Key Takeaways
01
02
03
Strategic Implication
Future Product Experience Shaped by AI - Label Distribution
AI as normal embedded enhancement79%
More automation and self-service15%
Conversational / agentic interfaces6%
Listen

How we present the features is we present the features as enhancing what humans are able to do today as to making it faster, making it more consistent, and providing twenty four seven services.

Marketing Director, Customer Integration, Large Technology Company
when asked about AI as normal embedded enhancement
Listen

The biggest shift that I see is that we have to spend less time on UI features and UI flows which used to be the front of our work, really, and that's being replaced by spending the time to develop, AI capabilities that essentially do the work of the user for them, and it takes care of the users needs for them.

Group Product Manager, Big Technology Company
when asked about More automation and self-service
Strategic Patterns

Cross-Cutting Themes

PATTERN 01

The Expectation-To-Execution Squeeze

As AI increasingly shapes product roadmaps and becomes more expected by customers, teams face a squeeze between market urgency and the practical limits imposed by compliance, security, and execution uncertainty.

Implication

Winning teams will need operating models that turn AI demand into disciplined execution, rather than allowing urgency to outpace trust, governance, or delivery capability.

PATTERN 02

The Capacity Reallocation Tradeoff

Because AI is commanding roadmap attention, teams are making balanced but real investment commitments and freeing capacity by deprioritizing adjacent work. Customer co-design then acts as a safeguard to ensure the limited capacity spent on AI is directed toward validated use cases.

Implication

AI investment should be evaluated not just by what gets funded, but by what gets delayed; stronger validation helps reduce the opportunity cost of those tradeoffs.

PATTERN 03

Pragmatism Now, Platform Risk Later

To move quickly, teams often prefer vendor APIs and hybrid architectures over fully custom builds. That pragmatism accelerates delivery, but it also shifts strategic attention toward dependency management and unresolved ecosystem risk ownership.

Implication

Short-term speed advantages from external AI tooling should be paired with clearer governance around vendor concentration, fallback options, and accountability for ecosystem risk.

Quick Answers

Common Questions

Question 01

How Widespread Is Ai’s Impact on Product Planning?

Strategic Recommendations

What This Means for You

01
Critical

Build an AI Operating Model That Balances Speed With Control

Treat AI demand as a governance and execution challenge, not just a roadmap opportunity. With 99% reporting roadmap impact, 89% citing compliance constraints, and 97% naming material bottlenecks, teams should define clear approval paths, risk thresholds, and delivery guardrails before urgency outruns trust.

02
Critical

Make Capacity Tradeoffs Explicit and Customer-Validated

AI investment should be evaluated alongside what gets delayed. Since 56% are making balanced but growing commitments, 52% are deprioritizing adjacent work, and 68% rely on customer co-design, leaders should formalize tradeoff reviews and require evidence of customer need before shifting more capacity.

03
High

Use Vendor Speed, but Govern Dependency Early

Leverage external AI tooling where it accelerates delivery, but pair it with explicit fallback, portability, and accountability plans. With 52% favoring vendor APIs, 35% using hybrid approaches, and 87% discussing ecosystem risk, dependency management should be designed in from the start rather than retrofitted later.

04
High

Design AI Around Hybrid Value and Monetization Pathways

Prioritize use cases that improve customer workflows while also lowering internal operating cost, then align packaging to match that value. Because 86% see both customer-facing and internal benefits, and 88% are already discussing pricing strategy, teams should connect product design decisions to bundled and premium monetization models earlier.

05
Moderate

Plan for AI to Become Core Infrastructure, Not a Feature Shelf

Shift long-term product thinking away from isolated AI launches toward embedded workflow enhancement. With 79% expecting AI to become a normal, invisible layer of the experience and 60% saying customers increasingly expect it, the winning strategy is to integrate AI into the product's fabric rather than market it as novelty.

Key Takeaways

Conclusion

1

Build an AI Operating Model That Balances Speed With Control

Treat AI demand as a governance and execution challenge, not just a roadmap opportunity. With 99% reporting roadmap impact, 89% citing compliance constraints, and 97% naming material bottlenecks, teams should define clear approval paths, risk thresholds, and delivery guardrails before urgency outruns trust.

2

Make Capacity Tradeoffs Explicit and Customer-Validated

AI investment should be evaluated alongside what gets delayed. Since 56% are making balanced but growing commitments, 52% are deprioritizing adjacent work, and 68% rely on customer co-design, leaders should formalize tradeoff reviews and require evidence of customer need before shifting more capacity.

3

Use Vendor Speed, but Govern Dependency Early

Leverage external AI tooling where it accelerates delivery, but pair it with explicit fallback, portability, and accountability plans. With 52% favoring vendor APIs, 35% using hybrid approaches, and 87% discussing ecosystem risk, dependency management should be designed in from the start rather than retrofitted later.

4

Design AI Around Hybrid Value and Monetization Pathways

Prioritize use cases that improve customer workflows while also lowering internal operating cost, then align packaging to match that value. Because 86% see both customer-facing and internal benefits, and 88% are already discussing pricing strategy, teams should connect product design decisions to bundled and premium monetization models earlier.

5

Plan for AI to Become Core Infrastructure, Not a Feature Shelf

Shift long-term product thinking away from isolated AI launches toward embedded workflow enhancement. With 79% expecting AI to become a normal, invisible layer of the experience and 60% saying customers increasingly expect it, the winning strategy is to integrate AI into the product’s fabric rather than market it as novelty.

The research shows a market moving decisively from AI exploration to AI execution. AI is no longer competing for attention at the margins: with 99% reporting roadmap impact and 60% saying customers increasingly expect it, it is now shaping what gets built, when it gets built, and how product strategy is framed. This is the core expectation-to-execution squeeze: rising demand is real, but so are the operational limits that determine whether that demand can be translated into trusted delivery.

Challenges

Those limits are now the defining challenge. Governance, compliance, and security constraints were raised by 89% of respondents, while 97% cited broader execution, trust, or ecosystem bottlenecks. At the same time, the capacity reallocation tradeoff is becoming visible: 56% are making balanced but growing AI investments, and 52% are freeing room by delaying adjacent work such as technical debt and UX improvements. To manage that risk, many teams are leaning on customer co-design, with 68% validating AI use cases through direct customer research before building.

Looking Ahead

The near-term winners are likely to be the organizations that combine pragmatic delivery with stronger operating discipline. Today that means using the fastest viable architecture, often vendor-led or hybrid, as seen in the 52% favoring external tools and the 35% combining them with internal components. But the longer-term strategic task is to govern the platform risk that comes with that pragmatism, especially as AI value spreads across both customer experience and internal operations for 86% of teams. Looking ahead, product leaders should design for AI as embedded infrastructure, not a standalone attraction, aligning delivery, validation, governance, and monetization around the 79% future expectation that AI becomes an invisible enhancement to the overall experience.

The bottom line: the AI race will not be won by the teams that add it fastest, but by the teams that make it trustworthy, validated, and invisible enough to feel like the product was always meant to work that way.

Methodology

This research draws on 246 in-depth interviews with business professionals representing a wide mix of roles, industries, and company sizes.

Interviews ran 1 to 35 minutes and covered AI impact on product roadmap and planning, AI resource allocation and capacity commitment, what gets deprioritized to make room for AI, and where AI creates value in the product and business. The conversational format allowed respondents to discuss their actual practices rather than select from preset options, surfacing nuance that closed-ended surveys typically miss.

Respondents included business professionals across software and technology, financial services, healthcare, retail, and manufacturing. All participants were selected for their direct experience with AI strategy, product planning, and business decision-making. Company sizes ranged from small businesses to large enterprises.

The analysis of 246 interview transcripts was conducted using AI for semantic understanding, with multi-iteration validation and cross-verification to ensure analysis quality. Each transcript was independently reviewed by G2's AI Custom Research team to inform narrative, context, and clarity.

G2 Research, June 2026

G2 is the world's largest and most trusted software marketplace.