G2Research Hub
Skip to content

Key Research Findings

93%

Failure Modes Are Now Mainstream

77%

Sensitive Work Remains Human Approved

50%

Hybrid Models Have Become the Center of Gravity

79%

Preparation Is Outpacing Full Readiness

Why this matters · For SaaS vendors

Why SaaS Software Vendors Should Care About This Study

OPPORTUNITY 01

Design for Failure Modes, Not Demos

Vendor Implication
OPPORTUNITY 02

Win the Risk-And-Liability Conversation

Vendor Implication
OPPORTUNITY 03

Make Human Oversight a Product Feature

Vendor Implication
OPPORTUNITY 04

Sell Bounded Autonomy, With Red Lines

Vendor Implication
OPPORTUNITY 05

Enable Low-Risk Pilots That Build Trust

Vendor Implication
OPPORTUNITY 06

Position for the Hybrid Operating Model

Vendor Implication
Chapter 01

Uneven Progress Meets Real Limits

The report opens by showing that while AI adoption is advancing, production maturity is still uneven and practical limits remain sharp. Organizations have seen automation break down on exceptions, judgment, and context, which helps explain why risk, liability, and sensitive-work red lines continue to cap autonomy.

Finding 1.1
Advanced AI adoption leads, but production maturity remains uneven

Current AI Adoption Maturity

40%
of respondents were in the advanced embedded or strategic stage of AI adoption
Key Takeaways
01
02
03
Strategic Implication
Current AI Adoption Maturity
40%
Advanced embedded/strategic adoption
Advanced embedded/strategic adoption
40%
Mid-stage operational use
36%
Early experimentation
14%
Mid-stage with uneven or limited production use
7%
Embedded daily use with human oversight
3%
Finding 1.2
Exceptions and nuance expose AI automation’s biggest reliability gaps

Observed Failure Modes in AI Automation

93%
of respondents discussed observed failure modes in AI automation
Key Takeaways
01
02
03
Strategic Implication
Observed Failure Modes in AI Automation
42%
Exception-handling and judgment failures
Exception-handling and judgment failures
42%
Data and context limitations
29%
Inconsistent or incorrect outputs
28%
Context and judgment limitations
1%
Context and complexity limitations
1%
Finding 1.3
Risk and liability set the limits of AI autonomy

What Sets the Boundary on AI Autonomy

Key Takeaways
01
02
03
Strategic Implication
What Sets the Boundary on AI Autonomy
Primarily risk/liability constrained55%
Balanced risk-and-capability constraint40%
Primarily technical capability constrained5%
Chapter 02

Trust Concentrates Where Work Is Structured

What works best today is not universal autonomy but targeted use in more structured, operational contexts. Trust is highest in practical automation use cases, while sensitive work remains assistive-only and subject to human approval, reinforcing a pattern of selective adoption rather than broad substitution.

Finding 2.1
Trust Concentrates in Operational Automation Over Research and Technical Use

Most Trusted Current AI Use Cases

93%
of respondents discussed the most trusted current AI use cases
Key Takeaways
01
02
03
Strategic Implication
Most Trusted Current AI Use Cases
52%
Operational workflow and transaction automation
Operational workflow and transaction automation
52%
Document/report processing and synthesis
37%
Technical/IT analysis and support
10%
Research, synthesis, and document intelligence
1%
Research and synthesis
1%
Finding 2.2
Sensitive work remains human-controlled, with AI limited to assistance

Red Lines in Regulated or Sensitive Work

77%
of respondents said AI should stay assistive-only in sensitive work with human approval
Key Takeaways
01
02
03
Strategic Implication
Red Lines in Regulated or Sensitive Work
77%
Assistive-only in sensitive work with human approval
Assistive-only in sensitive work with human approval
77%
No autonomy in regulated or high-stakes work
17%
Bounded autonomy allowed in select sensitive cases
4%
Human-only for external or commitment-making actions
1%
AI may draft or support but humans finalize
1%
Finding 2.3
Exception-based human review defines bounded autonomy for most organizations

Human Oversight and Review Design

Key Takeaways
01
02
03
Strategic Implication
Human Oversight and Review Design
Exception-based review with bounded autonomy54%
Human review for every output or key step39%
Checkpointed review for high-stakes cases7%
Chapter 03

Bounded Autonomy as the Default Operating Response

In response to those limits, organizations are not removing humans from the loop; they are redesigning the loop. Exception-based review, human review as a primary guardrail, and pilot-and-test trust-building form the current playbook for making AI usable without granting full autonomy.

Finding 3.1
Human Review Dominates Reliability, While Automated Guardrails Lag

Guardrails, Validation, and Reliability Controls

71%
use human review as the primary guardrail
Key Takeaways
01
02
03
Strategic Implication
Guardrails, Validation, and Reliability Controls
71%
Human review as the primary guardrail
Human review as the primary guardrail
71%
Testing, monitoring, and staged rollout
22%
Rule-based and model-based validation controls
4%
Layered automated validation and testing
2%
Rules, thresholds, or workflow constraints in place
1%
Human review as primary guardrail
1%
Finding 3.2
Trust grows through pilots, then expands with measured oversight

How Trust in AI Is Built

72%
of respondents who discussed trust in AI said it is built by piloting and testing before rollout
Key Takeaways
01
02
03
Strategic Implication
How Trust in AI Is Built
72%
Pilot-and-test before rollout
Pilot-and-test before rollout
72%
Extended proof period before broader autonomy
17%
Gradual rollout with ongoing monitoring
11%
Extended staged rollout before broad autonomy
1%
Chapter 04

The Emerging Blueprint for Scale

Looking ahead, organizations appear to be converging on a scalable model: hybrid copilot-and-agent designs, supported by active infrastructure and data preparation, with autonomous agents expected first in limited workflows. Finance and operations emerge as the clearest expansion zone because they likely offer the combination of structure, repeatability, and business value that makes bounded autonomy more feasible.

Finding 4.1
Hybrid AI Models Lead, With Boundaries on Autonomy

AI Operating Model: Copilot, Agent, or Hybrid

50%
of respondents favored a hybrid copilot-and-agent model
Key Takeaways
01
02
03
Strategic Implication
AI Operating Model: Copilot, Agent, or Hybrid
50%
Hybrid copilot-and-agent model
Hybrid copilot-and-agent model
50%
Copilot-first
41%
Agent model
8%
Hybrid model
1%
Finding 4.2
Preparation is widespread, but infrastructure maturity still splits organizations

Infrastructure and Data Preparation for Agentic Workflows

79%
are actively preparing infrastructure and data for agentic workflows
Key Takeaways
01
02
03
Strategic Implication
Infrastructure and Data Preparation for Agentic Workflows
79%
Actively preparing infrastructure and data
Actively preparing infrastructure and data
79%
Early or limited preparation
11%
Little visible preparation yet
10%
Finding 4.3
Autonomous agents split between near-term pilots and distant core use

Timeline Expectations for Autonomous Agents

42%
of respondents who discussed autonomous agents said core workflows are still multiple years away
Key Takeaways
01
02
03
Strategic Implication
Timeline Expectations for Autonomous Agents
42%
Multiple years away for core workflows
Multiple years away for core workflows
42%
Within 12 months for limited workflows
35%
12-24 month horizon
12%
Within 12-24 month horizon
5%
Within 12-24 months
3%
Within 12-24 months for limited workflows
2%
Not foreseeable for core work
1%
Finding 4.4
Finance and operations lead, but oversight remains nonnegotiable

Preferred Department for Broader AI Takeover

50%
of respondents discussing AI takeover said finance and operations should be the first department handed over
Key Takeaways
01
02
03
Strategic Implication
Preferred Department for Broader AI Takeover
50%
Finance/operations
Finance/operations
50%
Customer support and service
24%
No department for full takeover
22%
IT/QA/technical-focused
4%
Marketing
1%
Strategic Patterns

Cross-Cutting Themes

PATTERN 01

The Bounded Autonomy Consensus

Observed failures in exceptions, judgment, and context push organizations to define autonomy boundaries around risk and liability. That, in turn, leads to assistive-only treatment in sensitive work and to exception-based human review as the dominant operating design.

PATTERN 02

Trust Is Engineered, Not Assumed

Organizations build trust through piloting and testing, then reinforce it through human review and validation controls. This helps explain why trusted adoption concentrates in narrower, operational use cases rather than in complex or sensitive workflows.

PATTERN 03

Hybrid Models Bridge Today’s Readiness Gap

Even as organizations actively prepare infrastructure and data for agentic workflows, expectations for autonomous agents in core workflows remain years away. The preference for hybrid copilot-and-agent models reflects this gap between ambition and operational readiness.

FAQ

Common Questions

Question 01

What Is the Biggest Factor Limiting AI Autonomy Today?

Strategic Recommendations

What This Means for You

01
Critical

Design Around Bounded Autonomy, Not Full Replacement

Make exception handling, approval thresholds, and escalation paths explicit in workflow design. The strongest pattern in the research is that autonomy succeeds when it is constrained by risk level and backed by human intervention in edge cases.

02
Critical

Build Trust Through Structured Validation Before Scaling

Use pilots, side-by-side benchmarking, and staged rollout as standard operating practice before expanding AI into broader workflows. Trust is being earned through evidence and controls, not assumed from model performance alone.

03
High

Focus Expansion on Structured Operational Work First

Prioritize finance, operations, and document-heavy workflows where tasks are repeatable, outcomes are measurable, and errors can be more easily detected. These environments show the highest trust and the clearest path to safe scale.

04
High

Invest in Hybrid Architectures That Combine Copilot and Agent Modes

Avoid forcing a single autonomy model across the enterprise. Build platforms that let organizations shift between assistive and agentic behavior depending on workflow complexity, risk, and data readiness.

05
Moderate

Strengthen Data, Apis, and Observability Before Expanding Core Autonomy

Continue preparing the operational foundation for future agentic workflows, including cleaner data, access controls, and monitoring. Readiness work is already underway in many organizations and will determine how quickly bounded autonomy can expand safely.

Conclusion

**Challenges** The constraints are now clear. AI automation breaks down most visibly on exceptions, judgment, and context, and 93% of respondents reported seeing these failure modes firsthand. At the same time, governance concerns outweigh raw technical limitations, with 54% primarily constrained by risk and liability. These realities are keeping organizations from granting broad autonomy in high-stakes workflows and are concentrating trusted adoption in structured operational environments where outputs are easier to validate and consequences are easier to contain. **Forward looking** Looking ahead, the most credible path to scale is a hybrid model that combines assistive and agentic modes within clear operational boundaries. Organizations are already moving in that direction: 72% build trust through piloting and testing before rollout, 79% are preparing infrastructure and data for agentic workflows, and 42% still expect core autonomous workflows to remain multiple years away. Leaders should therefore prioritize workflow-specific autonomy, stronger validation and monitoring, and expansion into finance and operations, where structure, repeatability, and business value create the best conditions for safe adoption. The strategic implication is straightforward: the winners will not be the organizations that pursue maximum autonomy fastest, but those that design the most governable path from assistance to action.

About this Research

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

Interviews ran 4 to 32 minutes and covered AI operating model choices, human oversight and review design, boundaries on AI autonomy, and red lines in regulated or sensitive work. 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 technology, financial services, healthcare, manufacturing, and retail. All participants were selected for their direct experience with AI adoption, governance, and operational decision-making. Company sizes ranged from small businesses to large enterprises.

The analysis of 303 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.

This report was produced by G2 Research using a framework-based qualitative analysis of 303 interview records.