# Request Routing Fabric

*/Opportunities/Request_Routing_Fabric*

## Opportunity Overview

**Wedge**: Target internal IT helpdesks at companies with 2,000 to 10,000 employees. This niche offers bounded, highly measurable ticket categories where instant semantic triage immediately eliminates the need for dedicated human dispatchers. Expansion moves horizontally to HR and Legal internal routing, then crosses over to external customer-facing inbound support channels.
**Timing**: Sub-second inference speeds and plummeting token costs for foundational models now permit deep semantic classification and entity extraction on every inbound message without introducing unacceptable latency to the user experience.
**Why This I C P**: Enterprise IT and customer support centers manage thousands of distinct request categories and suffer measurable financial losses from high ticket misroute rates, making them highly motivated buyers for automated triage.
**Size Of Prize**: Approximately 40,000 enterprise and mid-market contact centers globally spend an average of $60,000 annually on manual triage labor and rigid routing software infrastructure. This yields an addressable market of $2.4B.
**Gap Narrative**: Enterprises deploy multiple specialized AI agents and human support tiers but rely on rigid decision trees or manual dispatchers to direct inbound requests. They lack a semantic routing layer capable of instantly analyzing complex user intent, extracting required payload data, and dispatching the request to the correct specialized node.
**Defensibility**: Defensibility scales through deep workflow lock-in and integrations. As the fabric connects to dozens of downstream departmental queues, agent APIs, and data stores, replacing the central dispatch logic requires rebuilding the organization's entire routing infrastructure. The system also builds proprietary data lock-in by fine-tuning its classification models on the specific company's historical reroute corrections.
**Why This Thesis**: A pure infrastructure software approach fits perfectly because the ICP already licenses the endpoint execution systems (Zendesk, specialized AI agents, human teams) and strictly requires a headless orchestration layer to sit above them.

## Opportunity Linked Thesis

**Thesis**: [Software](/Theses/Software)

## Opportunity Linked I C P

**Icp**: [Enterprise SaaS Company](/CompanyTypes/Enterprise_SaaS_Company)

## Opportunity Market Sizing

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**S A M**: ~$2B-$3B representing North American and European enterprise SaaS organizations
**S O M**: ~$50M-$150M realistic 3-year capture
**T A M**: ~100,000 global software and tech-forward enterprises × ~$100,000/yr on API and traffic routing infrastructure ≈ $10B
**Growth Rate**: ~22-28%/yr, driven by microservices architecture adoption and explosive growth in internal API traffic
**Paid Comparable Spend**: ~$75,000-$200,000/yr on legacy API gateways, load balancer licenses, and dedicated DevOps engineering hours to maintain custom Envoy meshes

## Opportunity Incumbents

- [Kong API Gateway](/Products/Kong_API_Gateway) — Tool
- [Envoy Proxy](/Products/Envoy_Proxy) — Open-Source
- [AWS API Gateway](/Products/AWS_API_Gateway) — Service
- [NGINX Plus](/Products/NGINX_Plus) — Tool
- [Custom Proxy Scripts](/Products/Custom_Proxy_Scripts) — DIY
- [Istio Service Mesh](/Products/Istio_Service_Mesh) — Open-Source

## Opportunity Win Conditions

**Kill Thresholds**:
- P99 latency overhead remains above 10ms at 90 days
- Average migration time from legacy gateway exceeds 14 days
- Less than 20 percent of staging pilots convert to paid production deployments
- Customer acquisition cost exceeds 15,000 USD for target 50,000 USD contract value
**Leading Metrics**:
- Time to first routed request in staging environment
- Percentage of total API traffic migrated to fabric within first 30 days
- P99 latency overhead added per request in milliseconds
- Number of routing rules automatically converted from legacy gateways
**What Proves Right**: DevOps teams deploy the routing fabric in staging within 48 hours and migrate at least 20 percent of their production internal API traffic within the first 30 days. Customers commit to 50,000 to 75,000 USD annual contracts to replace legacy gateways or custom Envoy setups. The system actively processes 10,000 requests per second with sub-5ms added latency.
**What Proves Wrong**: Platform engineers reject the fabric due to perceived latency risks or missing edge-case protocol support required by their microservices. Pilot deployments stall indefinitely in staging because legacy monolithic endpoints demand manual mapping. The engineering effort required to migrate exceeds the operational savings over existing AWS API Gateway setups.

## Opportunity Build Profile

**Hardest Part**: Achieving sub-millisecond overhead while parsing payloads for dynamic routing rules without becoming a single point of failure. Maintaining high uptime across diverse downstream dependencies requires flawless state management and circuit breaking.
**Min Viable Scope**: V1 focuses exclusively on outbound LLM API routing for cost optimization and rate-limit fallbacks for mid-market software companies. Deliberately leave out internal microservice mesh routing, complex payload modifications, and multi-region state synchronization.
**Cold Start Problem**: The system needs traffic volume to train predictive fallback heuristics, but engineers refuse to route production traffic through an unproven gateway. Break this by offering a passive shadow mode that ingests traffic copies to prove reliability and cost savings before entering the critical path.
**Time To First Value**: 1-2 weeks of shadow traffic observation to generate the first optimization report
**Data Moat Available**: true
**Technical Difficulty**: High

## Neighborhood

### Where the gap lives

- [Supplier Sourcing Agent](/Agents/Supplier_Sourcing_Agent) — latent gap · Agents

### Incumbent in

- [Kong Gateway](/Products/Kong_Gateway) — incumbent in · Products
- [AWS API Gateway](/Products/AWS_API_Gateway) — incumbent in · Products
- [Custom Proxy Scripts](/Products/Custom_Proxy_Scripts) — incumbent in · Products
- [Envoy Proxy](/Products/Envoy_Proxy) — incumbent in · Products
- [Istio Service Mesh](/Products/Istio_Service_Mesh) — incumbent in · Products
- [NGINX Plus](/Products/NGINX_Plus) — incumbent in · Products

### Applies thesis

- [Enterprise SaaS Company](/CompanyTypes/Enterprise_SaaS_Company) — applies thesis · CompanyTypes

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Similar Opportunities

- [Ticket Context Router](/Opportunities/Ticket_Context_Router) — similar · Opportunities
- [Inline Batch Triage](/Opportunities/Inline_Batch_Triage) — similar · Opportunities
- [Automated Ticket Triage](/Opportunities/Automated_Ticket_Triage) — similar · Opportunities
- [Headless Ticket Routing](/Opportunities/Headless_Ticket_Routing) — similar · Opportunities
- [Enterprise Signal Routing](/Opportunities/Enterprise_Signal_Routing) — similar · Opportunities
- [Bot Triage Agent](/Opportunities/Bot_Triage_Agent) — similar · Opportunities
- [Autonomous Ticket Triage for SaaS](/Opportunities/Autonomous_Ticket_Triage_for_SaaS) — similar · Opportunities
- [Escalation Routing API](/Opportunities/Escalation_Routing_API) — similar · Opportunities
- [Autonomous Routing Pipeline](/Skills/Active_Learning/Opportunities/Autonomous_Routing_Pipeline) — similar · Opportunities
- [Support Ticket Routing](/Opportunities/Support_Ticket_Routing) — similar · Opportunities
- [Tier-One Inquiry Triage](/Opportunities/Tier-One_Inquiry_Triage) — similar · Opportunities
- [AI Triage for MSPs](/Opportunities/AI_Triage_for_MSPs) — similar · Opportunities
- [Latent Signal Router](/Opportunities/Latent_Signal_Router) — similar · Opportunities
- [Proactive SLA Manager](/Opportunities/Proactive_SLA_Manager) — similar · Opportunities
- [Workflow Triage Router](/Departments/Example_Two/Opportunities/Workflow_Triage_Router) — similar · Opportunities
- [Automated Incident Dispatch](/Opportunities/Automated_Incident_Dispatch) — similar · Opportunities
- [Inbound Lead Triage](/Opportunities/Inbound_Lead_Triage) — similar · Opportunities
- [Automated Triage for IT](/Opportunities/Automated_Triage_for_IT) — similar · Opportunities
- [Intelligent Escalation for Enterprise Support](/Opportunities/Intelligent_Escalation_for_Enterprise_Support) — similar · Opportunities
- [Automated Feedback Triage](/Opportunities/Automated_Feedback_Triage) — similar · Opportunities