Tier 3 · AI & Agents

Service-as-Software

Service-as-Software is the commercial model in which AI performs actual work (resolves exceptions, processes documents, schedules appointments) rather than providing tools for humans to perform the work, representing the shift from selling software access to selling completed services.

Why It Matters

SaaS sold access to tools. Service-as-Software sells completed work. The distinction matters because it changes the value equation: the buyer does not pay for a dashboard they may or may not use. They pay for exceptions resolved, documents processed, appointments scheduled. The pricing reflects value delivered, not software consumed.

The FourKites Perspective

FourKites' Outcome as a Service model is a supply chain implementation of Service-as-Software. The Digital Workers perform the work. The outcomes are measurable. The pricing reflects operational footprint, not seat count. This is the commercial model Foundation Capital and Bain Capital identify as the next platform shift in enterprise software.

Frequently Asked Questions

What is service-as-software in the context of supply chain?

Service-as-Software is the commercial model in which AI performs actual work (resolves exceptions, processes documents, schedules appointments) rather than providing tools for humans to perform the work, representing the shift from selling software access to selling completed services.

How does service-as-software differ from traditional supply chain automation?

Traditional automation follows static rules configured by humans. Service-as-Software introduces reasoning, adaptation, and learning. The system makes decisions based on live intelligence, adapts when conditions change, and improves over time through decision trace feedback from the FourKites Graph.

What should enterprises evaluate when considering service-as-software?

Three criteria: (1) What intelligence powers it? Network data from hundreds of shippers or just the customer's data? (2) Does the system learn from outcomes through decision traces that compound over time? (3) Is enterprise compliance infrastructure in place: SOC 2, ISO 27001, audit trails, role-based access?

See how this concept powers autonomous operations.