# AI Agent Vendor Onboarding Template

Use this free public preview to prepare vendor onboarding or supplier intake for a `$203` seven-seat Agent Ops Command Center team license covering Codex, Claude Code, Cursor, MCP, browser, GitHub, and local AI-agent workflows.

This is a public discovery mirror. The paid Agent Ops Command Center ZIP is delivered only after checkout, receipt, payout, or seller-dashboard proof exists.

## 1. Vendor Onboarding Summary

| Field | Value |
| --- | --- |
| Vendor onboarding title | Agent Ops Command Center team license |
| Buyer / team |  |
| Request owner |  |
| Vendor setup owner |  |
| Procurement owner |  |
| Approver |  |
| Budget owner |  |
| Onboarding date |  |
| Requested package | Team license - 7 seats |
| Gross amount | `$203` |
| Decision deadline |  |

## 2. Supplier Intake Details

| Intake Field | Value |
| --- | --- |
| Vendor name | Agent Ops Command Center |
| Vendor contact |  |
| Billing contact |  |
| Delivery contact |  |
| Support contact |  |
| Invoice path |  |
| Receipt path |  |
| Internal vendor record owner |  |
| Supplier intake notes |  |

## 3. Product And License Line Item

| Line Item Field | Value |
| --- | --- |
| Product / service | Agent Ops Command Center paid ZIP |
| License scope | Seven-seat team license |
| Intended users |  |
| Primary workflows | Codex / Claude Code / Cursor / MCP / browser / GitHub / local agent |
| Delivery artifact | Paid ZIP plus delivery manifest |
| Unit amount | `$203` |
| Quantity | 1 team license |
| Renewal / expansion note |  |

## 4. Billing And Compliance Notes

| Requirement | Notes |
| --- | --- |
| Billing requirement |  |
| Invoice requirement |  |
| PO requirement |  |
| Receipt requirement |  |
| Security review requirement |  |
| Data boundary note |  |
| Access / delivery note |  |
| Internal compliance note |  |

## 5. Approval Evidence

| Evidence Field | Value |
| --- | --- |
| Manager approval owner |  |
| Budget approval owner |  |
| Security review owner |  |
| Quote approved? | Yes / No |
| PO required before checkout? | Yes / No |
| Invoice required before checkout? | Yes / No |
| Business reason |  |
| ROI note |  |
| Risk note |  |
| Decision requested | Onboard vendor / request PO / request invoice / pilot / reject |

## 6. Checkout Readiness

| Readiness Gate | Evidence |
| --- | --- |
| Checkout link exists |  |
| Receipt path exists |  |
| Seller-dashboard proof path exists |  |
| Vendor record is ready |  |
| Paid ZIP digest is ready |  |
| Delivery manifest is ready |  |
| Buyer acknowledgement path exists |  |
| Revenue proof rule is accepted |  |

## 7. Delivery And Acceptance

| Delivery Field | Value |
| --- | --- |
| Delivery artifact | Agent Ops Command Center paid ZIP |
| ZIP digest |  |
| Delivery method |  |
| Delivery owner |  |
| Acceptance owner |  |
| Buyer acknowledgement |  |
| Support / handoff note |  |

## 8. Decision Record

| Decision | Evidence Required |
| --- | --- |
| Onboard vendor | Vendor record, billing contact, approved amount, package, checkout or payment path |
| Request PO first | PO owner, PO reference, billing contact |
| Request invoice first | Invoice recipient, vendor details, receipt requirement |
| Pilot first | Pilot owner, success criteria, decision date |
| Reject | Reason, blocker, revisit condition |

Decision notes:

-

## 9. Revenue Proof

Do not count any of these as revenue:

- GitHub stars
- forks
- page views
- issue opens
- preview downloads
- template use
- request intent
- comments saying a buyer may purchase
- quote preparation
- purchase-order preparation
- invoice preparation
- vendor onboarding
- supplier intake

Count revenue only after one of these exists:

- checkout proof
- receipt proof
- payout proof
- seller-dashboard proof

Primary team request:

https://ivelly42.github.io/agent-ops-command-center/team-request-url.html

Fast template request:

https://github.com/ivelly42/agent-ops-command-center/issues/new?template=template-pack-request.yml