Use cases / Sales engineers

One canonical link replaces 50 SOC 2 PDF attachments

Stop attaching the same PDFs to every deal. Trust page on your custom domain, embeddable verify badge, machine-readable JSON-LD that buyer procurement systems can ingest directly. Every prospect sees the same fresh evidence — pulled from one source, not your last sent email.

The problem

You're running 30 deals at once. Each one wants the security pack. You attach the same SOC 2 PDF, the same DPA template, the same subprocessor list — drift creeps in, you send the wrong version on Tuesday, legal flags it on Friday, the deal stalls. Even when you're consistent, the buyer's procurement system has no way to verify the artifact came from you and not the email that forwarded it.

And when you finally get to a hosted trust page, you discover you're tied into a vendor whose URL scheme broadcasts “outsourced.” Buyers click through and land on a domain that isn't yours. Looks unprofessional, costs trust.

How Provenance helps

Custom domain on Pro plan. Trust page lives at trust.your-company.com with automated TLS. Looks like part of your product. Buyer procurement systems treat it as a first-party source.
Embeddable verify badge. One HTML snippet (<iframe> + fallback link). Drop into email signatures, MSAs, pricing-page footer, GitHub README, sales decks. Every prospect routes back to the same canonical page.
JSON-LD + Atom feeds. Trust page exposes a machine-readable export at /trust/[slug]/export/jsonld. Procurement / GRC tools ingest it directly; your buyer stops manually transcribing your DPA into their system.
Static HTML / PDF / JSON-LD bundles. Free Community-tier export — for buyers who insist on offline copies, you serve a deterministic snapshot, not whatever a screenshot tool produced this Tuesday.
Webhooks for sales-side automation. Hook posture changes into your CRM, your Slack, your renewals workflow. When a competitor's SOC 2 lapses, your AE knows before their AE does.

Live example

One HTML snippet you paste into email signatures, README files, MSA footers. Visitors verify against the directory; you get attribution + traffic.

See the verify-badge embed snippet

Start free View live example

Scores and labels are evidence-weighted — informational, not a certification.

The problem

How Provenance helps

Custom domain on Pro plan. Trust page lives at trust.your-company.com with automated TLS. Looks like part of your product. Buyer procurement systems treat it as a first-party source.

Embeddable verify badge. One HTML snippet (<iframe> + fallback link). Drop into email signatures, MSAs, pricing-page footer, GitHub README, sales decks. Every prospect routes back to the same canonical page.

JSON-LD + Atom feeds. Trust page exposes a machine-readable export at /trust/[slug]/export/jsonld. Procurement / GRC tools ingest it directly; your buyer stops manually transcribing your DPA into their system.

Static HTML / PDF / JSON-LD bundles. Free Community-tier export — for buyers who insist on offline copies, you serve a deterministic snapshot, not whatever a screenshot tool produced this Tuesday.

Webhooks for sales-side automation. Hook posture changes into your CRM, your Slack, your renewals workflow. When a competitor's SOC 2 lapses, your AE knows before their AE does.

Live example

One HTML snippet you paste into email signatures, README files, MSA footers. Visitors verify against the directory; you get attribution + traffic.

See the verify-badge embed snippet

Scores and labels are evidence-weighted — informational, not a certification.