Coupa Supplier Portal

Supplier AI Agent Platform

Vision, architecture, and resourcing proposal for an agent-first supplier experience on CSP.

Spencer Smith · March 17, 2026

1 / 8

Strategic Context

Why now

2 / 8

Architecture

From workflows to a platform

Navi Today

Flowchart of current Navi workflow with central routing agent and assistant branches

Target Architecture

Agent architecture diagram showing agent, tool calls, skills registry, and CSP APIs
3 / 8

The Unlock

Cross-context reasoning

When one agent sees invoicing, catalogs, verification, and transaction patterns together, suppliers can ask strategic questions that siloed workflows can never answer.

"Which of my invoices are overdue, and which buyers are consistently paying late?"
"I'm seeing fewer POs this quarter — what changed in my buyer connections?"
"How is my company showing up in buyer searches, and what can I do to improve visibility?"

Today each question requires navigating multiple screens and synthesizing data manually. The agent does it in one turn.

4 / 8

Near-Term

First capabilities

Transact

Invoice Smash

Upload invoices, validate against POs, flag discrepancies. 96K monthly users touch this flow today — the agent makes it one conversation.

Transact

Strategic Views

Surface payment trends, buyer behavior, and AR insights without navigating between dashboards. Attacks the CoupaAdvanced activation gap directly.

Growth

Verification & Profile

Automate the 206-supplier manual verification workflow. Guide profile enrichment for buyer discovery. Reaches marketing teams who don't use the portal today.

Each capability is a skill file + API wrapper — not a new engineering project.

5 / 8

Execution

Phased plan

A · Cloud & Security
Isolation model, runtime, tenant security
B · API Layer
Top use-case endpoints as agent-callable tools
C · POC
Harness + skills + end-to-end demo
Wk 1-2 Wk 3-4 Wk 5-6 Wk 7-8

Workstreams A and B run in parallel. POC starts when both have enough surface area to wire together. Decision point at POC completion: scale investment or adjust scope.

6 / 8

What We Need to Resolve

Open questions

Product Experience

Chat interface, inline contextual assistance, proactive suggestions, or a combination? The product surface determines adoption. Resolved in Phase 1 via prototyping.

Cloud Architecture

Isolated VMs vs. containers? Hosting model, cost structure, and scaling approach for concurrent sessions with strict tenant isolation. Mikael brings direct experience here.

Security & Compliance

Tenant data isolation, full audit logging, and enterprise compliance for a system with model-driven autonomy. Infrastructure-level enforcement, not prompt-level.

These are the three unknowns we close before scaling investment. Each has a clear resolution path within the POC phase.

7 / 8

The Ask

Resourcing the POC

Two configurations. Both start immediately — no hiring delay.

Option A — Distributed
Role Allocation May–Dec cost
Spencer Full-time Existing headcount
Mikael 10–15 hrs/wk $105–158K
Senior Dev FTE ~$133K
Junior Dev FTE ~$87K

May–Dec total: ~$325–378K

+ hiring lead time & coordination overhead

Option B — Concentrated Recommended
Role Allocation May–Dec cost
Spencer Full-time Existing headcount
Mikael 25–30 hrs/wk $263–315K
Senior Dev FTE ~$133K

May–Dec total: ~$396–448K

Proven partnership, AI-amplified, move immediately

Costs are for May 1–Dec 31, 2026 (35 weeks). Mikael at $300/hr. FTE estimates are fully loaded (~$200K/yr senior, ~$130K/yr junior) pro-rated to 8 months. Spencer is existing headcount, excluded from totals.

8 / 8