Announcing o11's backing from Y Combinator.

# AI for Coupa

## AI that moves requisitions through Coupa.

- Triage requisitions and route them to the right approver.
- Pull contract terms into supplier records automatically.

## Requisition #4781 — Marketing software
### Draft

| Feature               | Detail                     |
|-----------------------|----------------------------|
| Requestor             | M. Chen                    |
| Department            | Marketing                  |
| Need-by              | 5/01/2026                  |
| Currency              | USD                        |
| Justification         | FY26 marketing tooling      |

### Lines (2)
| Description                           | Supplier | Qty | Unit       | Total        | Account          |
|---------------------------------------|----------|-----|------------|--------------|------------------|
| Mailchimp - Standard plan annual      | Mailchimp| 1   | $14,400.00| $14,400.00  | 6300-Marketing   |
| Klaviyo Pro annual                    | Klaviyo  | 1   | $11,000.00| $11,000.00  | 6300-Marketing   |

### Requisition Total
$25,400.00

### Approval Chain
| Role | Name     |
|------|----------|
| MC   | M. Chen  |
| AM   | A. Mehta |
| PL   | P. Lin   |
| RP   | R. Park   |

## o11 for Coupa: an AI agent layer for source-to-pay

o11 is an AI execution layer that runs inside Coupa. The agent moves requisitions through approval, onboards suppliers, and pulls contract data into supplier records — without sending a procurement analyst into a side spreadsheet to retype what was already in the contract PDF.

If you have searched for **AI for Coupa**, a **Coupa AI agent**, or an **alternative to Coupa AI** for actual workflow execution, the question is the same: does the AI describe the requisition or move the requisition.

## What teams use o11 for in Coupa

- **Requisition approvals.** Triage and enrich requisitions, then route them to the right approver with policy context attached.
- **Supplier onboarding.** Build clean supplier records from intake forms, certificates, and contract PDFs.
- **Contract data extraction.** Pull terms, renewal dates, and price tables out of contracts and into Coupa fields.
- **Cross-system tie-out.** Cross-check requisitions and POs against ERP, CRM, and contract repositories.

## Why o11 differs from Coupa-native AI

Coupa AI is scoped to summaries, recommendations, and chat-style answers. It can describe a requisition or supplier, but the approval, record creation, or contract update still ends with a human clicking through screens. o11 operates on records. The chat is the control surface, Coupa is where the work lands.

## Built for teams that live across systems

Coupa is one part of a much larger source-to-pay stack — usually paired with an ERP, a contract repository, an inbox of supplier emails, and a close calendar. o11 is positioned to act across all of them. A new supplier request becomes a clean Coupa record, an ERP vendor master entry, and a Slack handoff to AP without the analyst stitching tools together by hand.

## Where Coupa teams typically start with o11

- **Procurement analysts** with requisition triage and routing.
- **Supplier management** with onboarding and document collection.
- **Contracts** with extraction into Coupa fields.
- **AP and finance ops** with PO and invoice match prep.

## How o11 respects Coupa permissions

The agent operates with the user’s own role and content group. Approval chains, segregation-of-duties rules, and policy controls apply exactly the way they do in the UI. Nothing is bypassed. That is what makes o11 deployable in regulated procurement orgs that cannot trust a tool that runs as an over-privileged integration user.

## FAQ

**Does it sign contracts?**  
No. It prepares records and routes for human signature.

**How does it score risk?**  
Configurable rules over policy, spend tier, and supplier history.