Prediction Log

Tracking AI deployment predictions based on CMC infrastructure analysis. Each prediction includes specific timeline and verification criteria.

Verification follows the criteria defined in each prediction. See Data Quality for methodology details.

PRED-001Pending
2026-01-15
Salesforce
Agentforce (Mid-Market)

70% of mid-market Agentforce deployments will enter pilot purgatory by Q3 2026, with 50%+ of those cutting headcount experiencing irreversible knowledge loss.

Timeline: Q3 2026
Mid-market companies typically operate at CMC 1.5-2.0. Agentforce requires CMC 3.5+ for autonomous operation.
PRED-002Pending
2026-01-16
Amazon Web Services
Amazon Q Business

60-75% of Amazon Q Business mid-market deployments will fail or require major remediation by Q3-Q4 2026 due to Maintenance dimension collapse from stale content.

Timeline: Q3-Q4 2026
Target customers operate at Maintenance CMC 0.5-1.5 vs Required 3.0. AWS removed 60% of documents as stale in their own implementation.
PRED-003Pending
2026-01-16
Zendesk
AI Agents for Customer Service

Most mid-market Zendesk AI Agent deployments will plateau at 30-40% automation rate by Q3-Q4 2026, with <30% achieving the promised 70%+ automation rate.

Timeline: Q3-Q4 2026
Mid-market companies operate at CMC 2.0-2.5 average. Zendesk AI Agents require CMC 3.0-3.5 for complex query handling.
PRED-004Pending
2026-01-29
ServiceNow
Now Assist for ITSM

Performance plateau persists at 30-40% autonomous resolution through Q3 2026. Infrastructure constraints (Accessibility L2/L4 Gap 2, Integration L2/L4 Gap 2) block improvement until Armis integration arrives.

Timeline: Q3 2026
Confidence: 90%. Armis acquisition closes Feb 2026, integration requires 12-18 months minimum. No customer infrastructure improvements possible before Q3 2026 checkpoint. Gap 2 across two critical dimensions requires 24-30 months build minimum.
PRED-005Pending
2026-01-29
ServiceNow
Now Assist for ITSM

First customer performance improvements to 50-60% autonomous resolution occur in Q2-Q3 2027 window (15-18 months post-Armis close). Earlier improvement (Q4 2026-Q1 2027) unlikely.

Timeline: Q2-Q3 2027
Confidence: 85% for Q2-Q3 2027 window, 90% confidence improvements won't arrive before Q4 2026. Conservative timeline accounts for: API development between Armis-ServiceNow, data model alignment, customer environment deployment, adoption cycles. Vendors consistently underestimate integration timelines.
PRED-006Pending
2026-01-29
ServiceNow
Now Assist for ITSM

IF customers reduce IT headcount by 20%+ based on 50-60% automation promises, performance degrades to 20-30% autonomous resolution within 3-6 months of workforce reduction.

Timeline: 3-6 months post-reduction
Confidence: 85% (conditional - depends on headcount reductions occurring). Mechanism: Human compensation currently adds ~+0.75 levels across dimensions, keeping performance at 30-40%. Remove humans, effective CMC collapses from L2.75 to L2.0. Comparable: Klarna reversed 700-agent reduction in 2024 after performance degraded when human compensation removed.
PRED-007Pending
2026-01-29
Parloa
AI Agent Management Platform (Agentic AI)

Parloa's enterprise contact center deployments will encounter visible scaling failures within 5-9 months. Pilots will succeed through heavy vendor support and manual bridging, but scaling attempts will reveal systematic infrastructure gaps: Integration L1-2 vs. required L3-4, Structure L1-2 vs. required L3-4, Accessibility L1-2 vs. required L3-4, and Maintenance L1-2 vs. required L3-4. Observable signals: 'implementation complexity' language in public communications, timeline extensions beyond initial estimates, scope reductions to 'core use cases,' and increased professional services revenue as percentage of total revenue.

Timeline: Q2-Q4 2026
Based on CMC assessment showing 4-5 BLOCKED dimensions (Gap ≥2) in typical enterprise contact centers. Parloa requires unified context across CRM, CCaaS, order systems, and knowledge bases (Integration L3-4), queryable knowledge schemas (Structure L3-4), API infrastructure for real-time data access (Accessibility L3-4), and continuously current data (Maintenance L3-4). Most contact centers operate at L1-2 across these dimensions. Pattern: Islands + Locked Vault combination—strong individual systems but disconnected and not API-accessible. Comparable to Salesforce Agentforce, ServiceNow AI Agents infrastructure gaps. Confidence: 90%. Evidence tracking: Q2 2026 (scaling pressure), Q3 2026 (first public signals), Q4 2026 (analyst reports, customer churn signals).
PRED-008Pending
2026-01-29
Parloa
Operations Model (Managed Service)

Customers adopting Parloa's 'operations model' (vendor-managed deployment at $400K+/year) will discover extraction costs of $2-3M within 18-24 months when attempting to transition to self-operation. Knowledge base and integration architecture will reside in Parloa's systems rather than customer infrastructure. The promised 'gradual automation' will not materialize due to lack of vendor incentive to reduce dependency. Customers will face binary choice: continue paying increasing fees ($400K → $500K+ annually as scope grows) or invest $2-3M to rebuild infrastructure and extract operations.

Timeline: Q4 2026 - Q2 2027
Based on historical BPO failures (2000-2020): Delta, British Airways, Target all experienced $1B+ insourcing costs after contact center outsourcing. Structural incentive misalignment—vendor has zero economic incentive to build customer infrastructure or reduce dependency. Operations model creates lock-in through knowledge capture in vendor systems. Observable: First customer extraction attempts Q4 2026-Q1 2027, public acknowledgment of extraction complexity Q2 2027. This mirrors Parloa's likely Mitigation #2 (Enhanced Professional Services Pivot) response to primary scaling failures. Confidence: 85%.
PRED-009Pending
2026-01-29
Parloa
Strategic Positioning Pivot

By Q4 2026-Q2 2027, Parloa will pivot from 'easy integration' positioning to one or more of: (1) Enhanced professional services model with comprehensive deployment programs ($1-2M+ services on top of platform), (2) Vertical specialization in 2-3 industries with stable ontologies (insurance, utilities, travel), or (3) Integration platform positioning ('the platform that builds your AI infrastructure'). Marketing will shift from 'fast time-to-value' and '4 weeks to deployment' toward 'comprehensive transformation' and 'enterprise-grade implementation.' Alternative outcome: Strategic acquisition by Salesforce, Microsoft, Cisco, or CCaaS vendor (Genesys, Five9) at $1.5-3B valuation before scaling failures fully evident.

Timeline: Q4 2026 - Q2 2027
Vendor mitigation response to infrastructure gap discovery. Observable signals: (1) Services hiring surge (380 → 600+ employees), (2) SI partnership expansions beyond Deloitte, (3) Product announcements for infrastructure tools, (4) 'Parloa for [Industry]' launches, (5) M&A speculation in trade press. This represents rational vendor adaptation—acknowledge infrastructure reality, monetize solution. Most likely path: Hybrid professional services + vertical focus, followed by strategic acquisition Q2-Q3 2027 before customer resentment phase (Year 3-5) impacts valuation. Confidence: 80%.
PRED-010Pending
2026-02-09
Amazon Web Services
Amazon Q Business (Enterprise Knowledge Access)

Amazon Q Business deployments (Q4 2025 - Q1 2026 wave) will plateau at 30-40% of promised productivity gains by Q2-Q3 2026. AWS promises 3.6 hours saved per week per digital worker; reality at typical mid-market L2 infrastructure will be 1-1.5 hours/week. Companies will experience: (1) Initial success on simple queries (30-40% resolution: policies, org charts, basic FAQs), (2) Plateau at 4-7 months post-deployment as complex queries fail, (3) Internal recognition Q1-Q2 2026, (4) Soft public acknowledgment Q2-Q3 2026, (5) Full pattern recognition Q3-Q4 2026. Infrastructure remediation requires $3.2-4.8M investment over 18-24 months.

Timeline: Q2-Q3 2026
Confidence: HIGH (85% on infrastructure gaps being deterministic, 65% on public acknowledgment vs quiet acceptance). Mechanism: 4 BLOCKED dimensions at Gap 2 - Formality L2/L4 (knowledge tribal not documented), Capture L2/L4 (manual inconsistent capture), Structure L2/L4 (folder hierarchies not queryable schemas), Accessibility L2/L4 (critical knowledge in unreachable systems). Maintenance L2/L3 (Gap 1) and Integration L2/L3 (Gap 1) are STRETCH but not blocking. Deployment baseline: Q4 2025 deployers (Oct-Dec) at 2-4 months as of Feb 2026, Q1 2026 deployers (Jan-Mar) at 0-2 months. Proofpoint validation: succeeded but required "significant time investment," "dedicated AI resources," "time-intensive prompt engineering"—proves infrastructure work enables success but most mid-market lacks capacity. AWS internal success (450K hours saved) ran on Amazon-grade infrastructure, not typical SharePoint/wiki baseline. Differentiation from PRED-002: PRED-002 focuses specifically on Maintenance collapse; PRED-010 addresses overall plateau from multiple BLOCKED dimensions. Timeline calculation: Base 9-15 months for Gap 2 × 4 dimensions, adjusted by market maturity (0.8x), organizational learning (0.75x), public visibility (0.9x), deployment speed (0.85x) = 4-7 months to plateau evidence.
PRED-011Pending
2026-02-13
Google
Workspace Gemini (Mid-Market)

85-95% of mid-market Workspace Gemini deployments will plateau at 30-40% of promised productivity gains by Q3-Q4 2026 (Months 5-9 post-deployment). Simple documented tasks (email drafting, meeting summaries, FAQ queries) will work. Complex cross-department synthesis requiring unified context will fail due to 4 BLOCKED dimensions.

Timeline: Q3-Q4 2026
Deployment wave: Jan 27-29, 2026 auto-enable for all Workspace Business/Enterprise customers. Month 1-2 as of Feb 2026. CMC Assessment: Formality L2/L4 (Gap 2 - BLOCKED), Capture L2/L4 (Gap 2 - BLOCKED), Structure L1/L4 (Gap 3 - BLOCKED), Accessibility L1/L4 (Gap 3 - BLOCKED). Integration L2/L4 (Gap 2 - BLOCKED for Workspace Studio agents). Comparable: Klarna (Feb 2024 launch → May 2025 reversal at Month 15), Amazon Q Business (Q4 2025 deployment → Q3-Q4 2026 plateau), ServiceNow (30-40% autonomous resolution ceiling). Infrastructure requirements: $2.7-4.2M, 15-26 months to build L1-L2 → L4 across Structure, Accessibility, Integration. Observable signals: Q2 2026 (initial enthusiasm), Q3 2026 (performance questions in forums, support tickets increase), Q4 2026 (analyst coverage of "implementation challenges," scope reduction to "core use cases"). Confidence: 87% on infrastructure diagnosis, 85% on 30-40% performance ceiling, 90% on Q3-Q4 2026 timeline.