For Revenue Operations
For the integration owner
Sales Lab connects to Salesforce, HubSpot, Slack, Stripe, and signed webhooks with clear boundaries. Your admin controls access, data retention, and which systems receive scorecards.
What is wired today
We list the integrations that work today. If you need another system, we scope it during onboarding instead of pretending it is already done.
A note on the integration list
You will see longer integration lists on other vendor sites. Sales Lab lists what works today and gives a straight answer about what still needs to be built.
4
Core systems covered: Salesforce, HubSpot notes, Slack, Stripe.
1
Customer workspace with company-level permissions and audit history.
18+
Permission checks across the product data model.
The integration model
Salesforce can turn opportunity context into practice. Salesforce and HubSpot can create scorecard notes after sessions. Slack can post manager digests to the channel your team chooses. Stripe runs billing.
The default setup covers the common path. If your team needs record-level CRM mapping, we scope the exact object, field, and webhook behavior during onboarding.
For systems outside the core integrations, the API can provide scoped access to scorecards, sessions, scenarios, and analytics. Access is permissioned and logged.
“Sales Lab lists what works today, then scopes the next integration clearly.”
Day one for RevOps
These are the things a Revenue Operations lead does on day one of a Sales Lab tenant. Each item is a real workspace path. Each one takes minutes, not a service ticket.
Provision SSO via Okta, Azure AD, Google Workspace, or JumpCloud. The endpoint is registered as part of the kickoff.
Create an API token at /admin/api. Choose the data it can read and the IP addresses it can use.
Connect Salesforce at /integrations/salesforce. Sales Lab can create practice from opportunity context, then send scorecard events through notes or webhooks based on your tenant mapping.
Set retention at /admin/data. Default is three hundred and sixty-five days. Audio is independently configurable. The cooling-off period on delete is seven days.
Require MFA at /admin/permissions when your rollout is ready.
Subscribe to webhooks at /admin/webhooks for scorecards, shared sessions, and certifications.
For the rest of your team
Day one
Five minutes. One scenario. One honest scorecard. The rest of your stack reports on what already happened.