Revenue intelligence

The revenue intelligence layer

Calls, recordings and forecasting, sitting downstream of everything else in the stack.

revenue-intelligence 1 tool
layerRevenue intelligence
forCalls and forecasting
tools here1
integrations4
with a guide4
checked Tool hubs 1 of 1
The short version

What this layer is actually for

Calls and forecasting. In this directory that is Gong.

Revenue intelligence sits furthest downstream: it reads what the rest of the stack produced and tries to say something about what will happen next. That position decides its integrations, which are mostly about getting conversation and activity data out of the other layers and into one place.

This directory covers one tool in this layer so far. That is a statement about the directory, not about the category, and the honest version is worth more here than a page padded out with tools that belong in other layers. What is covered is below, with the integrations that touch it.

In this layer

The one tool this directory covers in the revenue intelligence layer

A tool can sit in more than one layer, and several here do. The layers on each card are the full set, not just this one.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 1 of 1

Gong

Putting what was said onto the record
4 integrations
LayerRevenue intelligence
Guides

Gong is a one-directional integration by design: it reads the calendar and the CRM, and it writes intelligence back. The value is entirely in the write-back, so the field mapping is the whole configuration.

  • Call, email and meeting data attached to CRM records
  • Deal-level signals written to CRM properties
  • Read access to the CRM is required before anything writes back
Entry priceQuote only Visit See the 4 integrations

A forecast is only as good as the activity data underneath it, which is why this layer is so sensitive to what the engagement layer logs back.

Across the edge

4 integrations that touch this layer

Each record carries the layers it spans, so an integration appears here when this layer is one of them. Start with how it is built, because a native app and a webhook you maintain are the same feature with completely different owners.

4 of these 4 have a full guide behind them, HubSpot and Gong and Salesforce and Gong among them.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 4 of 4
↔

HubSpot and Gong

Two-way sync
BuiltNativeMarketplace app
WatchPaid licence first

Six hours before a call appears, and the transcript never does.

  • Moves: Activities, Deals, Contacts, Companies
  • Needs: A Gong contract, a HubSpot tech admin, and a dedicated integration user
Paid add-on or licence · hours Read the guide
↔

Salesforce and Gong

Two-way sync
BuiltNativeMarketplace app
WatchPaid licence first

Take a field off the integration user and Gong deletes what it already imported.

  • Moves: Activities, Deals, Contacts
  • Needs: A Gong contract, a Salesforce edition with API access, and a dedicated integration user
Paid add-on or licence · hours Read the guide
⋅

Slack and Gong

Events only
BuiltNativeMarketplace app
WatchPaid licence first

Channel alerts come from streams, and a stream has to be the standard kind.

  • Moves: Messages, Activities
  • Needs: A Gong contract, a Slack admin to install the app, and a Gong admin to connect it
Paid add-on or licence · minutes Read the guide
The data layer

Where Reverse Contact sits under this layer

Reverse Contact is not a revenue intelligence tool and has no marketplace app in this layer. It is the data layer underneath it: one API that resolves an email, a domain or a profile URL into a verified people and company record, so that what this layer moves is worth moving. This directory documents 1 route into this layer, 1 of them with a full guide.

Every documented route into a stack sits on the Reverse Contact hub.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every number on this page is derived from those records rather than typed, and each record was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-28
Sources
2 vendor documents
Paid placement
None

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant