OBAM | Public reference governance

Control every public customer reference.

OBAM gives legal and IP teams a system to authorize, govern, and revoke how vendors use customer logos, reference statements, testimonials, and partnership statements.

When a relationship changes, your public representation should change with it.

Authorize who can say whatWithdraw or expire references when reality changesCreate a clearer public verification signal

What OBAM is

OBAM is a governance system for public reference claims. It records authorization decisions and publishes a public verification surface with current status.

Who it's for

OBAM is for legal, IP, security, and procurement teams that need a verifiable control layer for external reference usage.

What it verifies

OBAM verifies whether a specific logo, testimonial, case study, or partnership statement is currently authorized by the referenced organization.

How status changes

Authorization lifecycle state changes are explicit: active, expired, or revoked. Revocation and expiry are reflected on the public verification surface.

Core outcomes

Authorization control

Operational controls designed for high-accountability external reference governance.

Lifecycle governance

Operational controls designed for high-accountability external reference governance.

Revocation and expiry

Operational controls designed for high-accountability external reference governance.

Public verification

Operational controls designed for high-accountability external reference governance.

Auditability

Operational controls designed for high-accountability external reference governance.

Team-based authorizations

Operational controls designed for high-accountability external reference governance.

Public verification surface

OBAM helps organizations publish verification pages with reference status visibility and authorization lifecycle state clarity.

Buyers get authorization context and auditable trust evidence without relying on static logo pages.

Public verification pages for authorized references

Current reference status and authorization lifecycle visibility

Authorization context tied to policy control

Auditable trust signal for external buyers

Less reliance on unverifiable customer-logo pages

Measured support for procurement diligence workflows

How OBAM works

1. Define and authorize the reference

Capture what is being stated and who is making it.

  • Record the reference content and channel.
  • Assign the company-side approver with authority.

2. Govern its lifecycle over time

Apply policy rules as relationships evolve.

  • Set expiry windows and special conditions.
  • Revoke authorization when context changes.

3. Publish a verification surface buyers can trust

Expose current authorization state to the public.

  • Show whether a reference is active, expired, or revoked.
  • Back trust claims with auditable evidence.

Public B2B references are easy to publish and hard to control.

Logos remain live long after relationships change

Testimonials and case studies are reused without ongoing authorization

Public reference statements rarely reflect lifecycle changes

Legal teams carry risk without a dedicated control layer

Buyers and procurement teams are left interpreting unverifiable references

OBAM gives control back to the referenced company.

Authority belongs to the referenced company

Vendors should not effectively self-certify public references.

  • Keep authorization power with the customer named in the claim.

Governance must continue after authorization

Authorization should be managed over time, not only once.

  • Track changes with policy-aware lifecycle controls.

Public trust should reflect current state

Revocation, expiry, and updates should be built into workflow operations.

  • Let public verification surfaces update when relationship reality changes.

Built for teams with different responsibilities

Legal & IP Teams

  • Authorize or decline public references
  • Control logo and brand usage
  • Set expiry or conditions
  • Withdraw references when relationships change
  • Maintain an audit trail

Procurement Teams

  • Get a clearer verification signal
  • Reduce reliance on back-channel diligence
  • Understand whether a reference is still authorized
  • Evaluate public verification surfaces with more confidence

Brand / Partnerships

  • Govern which assets and statements can be used externally
  • Keep reference usage aligned with policy and relationship reality
  • Coordinate authorizations with legal and account stakeholders

Security / Compliance

  • Understand access control and tenant isolation
  • Review token workflows and logging coverage
  • Assess auditability and operational accountability

What OBAM controls

Customer logos

Govern authorization and permitted usage across public channels.

Reference statements

Track which relationship references are active, expired, or revoked.

Testimonials

Control public use with time-bound and policy-aware authorizations.

Case studies

Keep publication tied to current authorized relationship context.

Partnership statements

Approve external language against legal and brand policy.

Expiry and revocation status

Show lifecycle status as part of the public verification surface.

Relationships change. Your public verification surface should change with them.

  • Withdraw outdated references quickly.
  • Expire references automatically where needed.
  • Replace older references with current ones.
  • Maintain governance over time, not just at authorization.

See governed pricing options

Choose the rollout path that matches your control model and governance depth.

Explore pricing

Put control in place

Start with legal/IP governance and expand to procurement and brand workflows over time.

Request demo