How it works

From reference definition to lifecycle governance.

OBAM combines workflow and category education: it explains how public customer references should be governed and gives teams the system to do it in practice.

Step 1

Define the reference

Capture the exact logo, statement, or relationship reference and bind it to policy context before anything goes public.

Step 2

Authorize the reference

Route authorizations to legal/IP or authorized owners with clear ownership, conditions, and accountability.

Step 3

Publish a verification surface

Expose authorized references through account-free verification pages that show status and authorization context.

Step 4

Update, expire, or revoke over time

Apply lifecycle controls so public references stay aligned with relationship reality, not historical marketing artifacts.

Why this is different from unmanaged logo/reference pages

Unmanaged pages are static; OBAM introduces lifecycle authority.
Self-published references are weak signals; OBAM shows governed status context.
Legacy references drift from reality; OBAM supports continuous updates and revocation.

Explore pricing Request demo

Verification JSON endpoint for procurement automation

Every public verification page exposes a machine-readable companion at /verify/[slug].json. The contract is normalized for vendor risk and procurement systems and excludes sensitive internal notes, emails, and private revocation rationale.

Schema

{
  "schema_version": "2026-03-14",
  "policy_version": "public-verification-v1",
  "verification": {
    "slug": "string",
    "status": "ACTIVE | PENDING | REVOKED | EXPIRED",
    "issued_at": "ISO-8601 timestamp | null",
    "expires_at": "ISO-8601 timestamp | null",
    "revoked_at": "ISO-8601 timestamp | null",
    "last_verified_at": "ISO-8601 timestamp | null"
  },
  "subject": {
    "organization_id": "string",
    "organization_name": "string"
  },
  "vendor": {
    "claim_id": "string",
    "vendor_name": "string"
  },
  "reference": {
    "summary": "string | null"
  },
  "audit": {
    "published_at": "ISO-8601 timestamp"
  }
}

Example payload (active reference)

{
  "schema_version": "2026-03-14",
  "policy_version": "public-verification-v1",
  "verification": {
    "slug": "acme-procurement-suite-2026",
    "status": "ACTIVE",
    "issued_at": "2026-02-18T11:12:30.000Z",
    "expires_at": "2027-02-18T11:12:30.000Z",
    "revoked_at": null,
    "last_verified_at": "2026-03-13T10:05:00.000Z"
  },
  "subject": {
    "organization_id": "org_9JX2K4",
    "organization_name": "Northwind Manufacturing"
  },
  "vendor": {
    "claim_id": "claim_A12B34",
    "vendor_name": "Acme Procurement Cloud"
  },
  "reference": {
    "summary": "Northwind confirms active deployment of Acme Procurement Cloud for supplier onboarding workflows."
  },
  "audit": {
    "published_at": "2026-03-14T08:00:00.000Z"
  }
}

Example payload (revoked reference)

{
  "schema_version": "2026-03-14",
  "policy_version": "public-verification-v1",
  "verification": {
    "slug": "legacy-procurement-reference",
    "status": "REVOKED",
    "issued_at": "2025-06-02T09:10:15.000Z",
    "expires_at": "2026-06-02T09:10:15.000Z",
    "revoked_at": "2026-01-10T14:55:03.000Z",
    "last_verified_at": "2026-01-10T14:55:03.000Z"
  },
  "subject": {
    "organization_id": "org_33HK9M",
    "organization_name": "Aperture Retail Group"
  },
  "vendor": {
    "claim_id": "claim_7P9Q2R",
    "vendor_name": "Beacon Sourcing Platform"
  },
  "reference": {
    "summary": "Reference withdrawn after contract sunset; procurement systems should mark trust signal as inactive."
  },
  "audit": {
    "published_at": "2026-03-14T08:00:00.000Z"
  }
}