What is Measure?

Peerbound helps you find happy customer moments and turn them into proof: reviews, quotes, and stories. Peerbound Measure closes the loop. It looks at your sales activity while a deal is open, finds where reps used that proof with prospects during the sales cycle, and ties it back to revenue and the specific piece of proof that was used to close the deal.

Two things to note:

• Measure tells you how customer proof influences your sales cycle. It's not usage analytics for the Peerbound platform itself.

• Measure works with Salesforce today and covers new business only, so renewals and expansion aren't included yet. HubSpot support is planned for the near-to-medium term.

Who is it for, and when should I use it?

Measure is built for you, the marketer running customer advocacy at your company. You can use the data two ways:

• Tactically, to see what proof your reps actually reach for, what's helping land deals, and what to create or promote next.

• Strategically, to answer one of the hardest questions in marketing: the effect of advocacy on the sales cycle, backed by a defensible number for the impact of customer proof.

How does it work?

Measure cross-references three data inputs:

1. Your CRM (Salesforce): opportunities, accounts, contacts, and the emails logged against them.

2. Call recordings from your connected call integration (Gong, Clari, and similar): transcripts scanned for proof mentions.

3. Your Peerbound proof library: the stories, reviews, and quotes it matches against.

Peerbound uses LLMs to scan that activity and surface moments where a rep shared a customer story, review, or quote, whether as a link, an attachment, or a spoken mention on a call. In email, the match is usually direct: a link or a recognizable quote. On calls, the match relies on account name or on how closely what was said resembles existing customer proof.

Results land in your dashboard, ready to explore and export.

Can I see Measure in Salesforce or other platforms instead of the dashboard?

Not yet, but both are on our radar. In the meantime, you can export your data from the dashboard and use it wherever you need. If you have a specific destination in mind, let your CSM know. That kind of input directly shapes what we build next.

What counts as "impacted"?

Measure counts genuine use of proof, meaning any time proof reaches the prospect. To avoid counting every passing mention of a customer, it applies deliberate requirements, and the bar differs by channel.

On calls, the bar is more lenient since reps tend to paraphrase rather than quote directly. What counts as a match: a rep mentioning a customer by name along with a concrete outcome, for example, "We work with Acme, and they saw a 9% retention increase with feature X." A name-drop alone, without that outcome, doesn't count.

In email, the bar is higher. These count:

• A link to a story

  • Note: The content does not have to live in Peerbound to count, but it does have to live in Peerbound to be tracked in the Measure dashboard

• A quote used verbatim or lightly edited, as long as it's a quote the customer approved for external use or one that's anonymized

• Phrasing that clearly signals proof is being shared, for example "attaching the Acme case study"

These don't count:

• A link to a company's G2 page rather than a specific review

• A customer mention with no supporting artifact

What revenue gets attributed?

Measure credits the opportunity's mapped ARR, which today is the standard Salesforce Opportunity Amount field.

• Influenced revenue counts deals that are closed won within the time window you're viewing. The proof usage itself can have happened earlier, even before the window started.

• Closed-lost deals aren't counted as influenced revenue, but they're still analyzed. They feed into win-rate and time-to-close comparisons.

• Open pipeline doesn't count as revenue, but proof usage on those deals is still detected and shown, so you can see proof working in live deals.

• Revenue is counted once per deal and never double-counted, even if multiple pieces of proof were used on it. You'll see every piece of proof involved.

• Deal-level metrics (revenue, win rate, speed to close) are tied to the close date. Proof-usage metrics are tied to when the proof was actually used, which can fall in a different window than the deal's close date.

How are the win-rate and time-to-close comparisons calculated?

Measure takes all deals that closed in the period, won and lost, and splits them by whether proof was used. It then compares the two groups on revenue, win rate, and time to close.

Two things worth keeping in mind:

1. This is a comparison, not a controlled experiment. Deals that use proof may differ from other deals in other ways too, so proof may not be the only factor driving the difference.

2. Compare like with like. Mixing different sales motions together, say, upmarket and downmarket, in a single view makes the comparison unreliable. You'll get the most meaningful results by comparing cohorts that follow the same sales process.

What do I need to get Measure working?

Getting started is simple, and Peerbound may already have most of what is needed. Measure can run on partial data, but here's the full picture.

Required: Salesforce needs to share its sales data objects and fields, have deal-level attributes configured and mapped to Peerbound (including the deal value field, standard Opportunity Amount today), and give access to email through the Task and Email Message objects.

Fields needed:

• Task: AccountId, ActivityDate, CreatedDate, Description, TaskSubtype

• EmailMessage: CreatedDate, FromId, HtmlBody, Incoming, IsDeleted, MessageDate, Subject, TextBody

• CurrencyType: ConversionRate, DecimalPlaces, IsActive, IsCorporate, IsoCode

• DatedConversionRate: ConversionRate, IsoCode, StartDate, NextStartDate

For the full list of objects and fields, and instructions on updating Salesforce permissions, see the Salesforce Integration Instructions.

Highly recommended: a call integration. Without it, Measure still runs on email signal alone, but you'll lose proof detected on calls. Most teams already have one connected (Gong, Clari, or similar).

What currency are the numbers shown in?

If your Salesforce org uses a single currency, everything is shown in that currency. If your org is multi-currency, aggregate figures (totals and influenced revenue) are shown in your organization's corporate currency. Where an individual opportunity's amount appears, such as in a tooltip in the feed, it's shown in that deal's local currency.

Where does the data come from?

Two channels: call recordings from your connected call integration, and emails logged in Salesforce against an account.

Does Measure see all emails?

No, Measure doesn't see all your emails. It only sees email logged in Salesforce against an account, meaning messages sent to or received from a prospect or customer. It doesn't connect to your email client or inbox, so internal or unrelated emails are never seen.

What can Measure not see yet?

• Deal rooms (Highspot, Seismic, and similar), unless the message passes through Salesforce. Measure may see a link but not the proof inside it.

• Multi-logo "NASCAR" slides on calls. Measure has the transcript, not what's on screen. If a rep says "we have case studies from X and Y, I'll send them," that's captured, but a silent slide isn't.

• Email attachments, which aren't analyzed unless referenced by name in the email body. "The case study from [Company]" with a single match gets credited, but the specific file won't show in the proof breakdown.

• Slack, Teams, texts, and DMs.

How fresh is the data, and how far back does it go?

Data refreshes with roughly a one-day lag.

Two dates matter for this initial release of Measure:

• October 1, 2025: when Peerbound began processing sales activity. Proof shared before this date isn't found.

• January 1, 2026: the earliest date you can filter to in the product. The first quarter of processing built up history so that deals closing in January and beyond have their full recent cycle covered and don't look artificially low.

Trust and Accuracy

How do you know a rep actually used the proof?

For email, three things have to line up: the sender is an internal employee, the recipient is a contact on the account tied to the opportunity, and the email falls within the opportunity window. That window runs from the opportunity's creation date to its close date, or, for open opportunities, from creation to now. The proof itself can predate all of this. Measure can ingest stories created before Measure existed, and older proof used on a new deal counts exactly the same as newly created proof.

For calls, Measure first classifies the call as either a net-new sales conversation or an existing-customer conversation, and analyzes only net-new sales calls. It then scans the transcript for proof use and matches it to Peerbound content by account name or by how closely what was said resembles the proof.

Can we trust the number?

Three things make it trustworthy:

1. It's designed to undercount. Blind spots like attachments, deal rooms, Slack, and pre-October history all suppress the number, so real usage is almost certainly higher than what's reported. Think of it as "you shared at least X case studies this quarter," not the full total.

2. It's inspectable. Every data point shows up in the drill-down, so you can check individual attributions and the math behind them.

3. It's correctable. Occasionally Measure counts something that isn't actually relevant. You can exclude any individual item from the impact feed, and exclusions are removed from the totals.

Troubleshooting

Measure is counting emails or calls that aren't relevant.

Exclude individual items directly in the impact feed. If this is happening in large numbers, contact your CSM.

My numbers look lower than expected.

The most common causes, roughly in order:

1. History cutoff. Processing began October 1, 2025. Proof shared earlier isn't found, and long-running deals are most affected.

2. No call integration connected, so call usage is invisible to Measure.

3. Proof shared through channels Measure can't see: attachments, deal rooms, Slack, Teams, texts.

4. Recipients not saved as contacts. Email only counts when the recipient is saved as a contact on the account tied to the opportunity, so unsaved recipients won't register.