Reference strip
Turn proof into publishable references
Keep the customer proof loop honest: approvals first, live signals next, then sales export and enablement.
review
Markdown, CSV and JSON handoff
needs attention
Flow Customer Proof Hub
Customer proof loop, reference wall and readiness
Tenant focus: global | This page only promotes tenants with enough live signals for proof. Published references still need customer signoff.
Open publish gate
Proof recovery path
Keep proof publishable without slowing sales
Verify consent, approve the strongest customer story and hand it off to enablement when it is truly ready.
Check proof readiness, consent and live usage signals.
Close legal or data gaps before publishing references.
Publish the strongest story and reuse it in enablement.
No proof yet
Open onboarding and activation first so the tenant has enough live signals for a real reference.
Need signoff
Keep the proof loop internal until legal notice, consent and the customer quote are ready.
Go live now
When a tenant is ready for reference, move it through publish flow and reuse the story in enablement.
Proof-ready references
0
Tenants with enough live signals to draft a customer reference.
Live-data candidates
0
Accounts with product usage but not yet strong enough for public proof.
Consent artifacts
0
Published capture trail across widgets, tickets and API events.
Publish gate
needs attention
Legal notice, retention and market coverage for sales use.
Work next
Activation needed
No reference-ready tenants yet. Use onboarding and activation to generate proof first.
Primary approval action
Open activation hub
The publish gate should always start with the strongest live tenant signal, not a generic checklist.
Approval queue
References awaiting approval
Keep the proof loop public only when legal notice, consent and market coverage are ready.
Ready logos
No logo wall candidates yet
Customer-approved proof should come from the strongest live tenants, not generic placeholders.
- Use onboarding and activation to produce the first publish-ready account.
Proof gate summary
This is the point where tenant evidence becomes something sales can actually reuse.
Consent window
0
Inside current review window: insufficient test data
Retention
insufficient test data
Consent artifact retention days from compliance policy.
Market coverage
insufficient test data
Required markets that already have coverage signals.
Top market
insufficient test data
No market concentration yet.
Revenue proof snapshot
Enough revenue movement makes the proof story believable instead of decorative.
Lead to paid
insufficient test data%
Lead, booking and paid-order progression for the last 30 days.
Gross revenue
insufficient test data
Revenue used as proof input for case studies and packaging.
Paid orders
0
Orders that can back up a proof pack without hand-waving.
Average order
insufficient test data
Gives the commercial story a more realistic price anchor.
Approval queue
Prioritized tenants that can move into publish, signoff or activation work next.
| Tenant | State | Next action |
|---|---|---|
| insufficient test data | ||
Sales export pack
Reusable export paths for CRM, enablement and customer-facing proof review.
Ready logos
insufficient test data
Publish gate
review
Proof candidate table
Tenant rows sorted by strongest revenue signal first. This is the draft logo wall and reference queue.
| Tenant | Package | Usage | Revenue | Proof state | Next action |
|---|---|---|---|---|---|
| insufficient test data | |||||
Logo wall draft
These are the companies that look most reference-ready from the current live signal set.
insufficient test data
Consent source mix
Where the proof ledger is actually captured from.
| Source | Artifacts |
|---|---|
| insufficient test data | |
Compliance coverage for proof publishing
This is the guardrail that stops us from publishing proof before legal notice, retention and market coverage are in place.
| Market | Artifacts | Coverage |
|---|---|---|
| insufficient test data | ||
Ready rows
0
Can be translated into a draft reference with approval.
Needs live data
0
Good candidate, but not yet strong enough for a public story.
Needs signoff
0
Needs activation or customer approval before it can be used externally.
Proof ready rate
insufficient test data
How much of the current tenant set is reference-ready today.