Skip to main content
A context layer needs context. Tempo reads from the systems your team already works in, so getting started is mostly a matter of connecting them. You need three things: a source of opportunities, email and calendar, and an AI platform to talk to Tempo through.

​
A source of opportunities

Tempo organizes everything around your deals, so it needs to know what your deals are. There are three ways to provide that.

Salesforce

Connect Salesforce as your system of record. Data stays reconciled both ways, and Tempo can propose CRM updates with citations. Requires a Salesforce Admin to approve the integration.

HubSpot

Connect HubSpot as your system of record. Deals, companies, and contacts sync in, and Tempo can propose property updates with citations.

CSV import

No admin approval needed. Upload a CSV of your opportunities during onboarding. Gets you running quickly, but it’s point-in-time — data doesn’t stay in sync.
A connected CRM is the better experience, but it isn’t a prerequisite. Start with a CSV if approval will take a while — you can connect Salesforce or HubSpot later without losing anything.

​
Email and calendar

Gmail

Email context is used to understand deal activity and surface relevant information at the right moment.

Google Calendar

Calendar access connects upcoming meetings to the right deals automatically.

​
An AI platform

Tempo connects to your AI platform over MCP. This is where you actually talk to Tempo.

Claude

Connect Claude to Tempo.

ChatGPT

Use ChatGPT as your interface.

Anything else

Any MCP-capable tool works.

Granola

Granola is not required, but preferred for the best experience. It captures call and meeting context that Tempo uses to take action on your behalf. Gong and Fathom are also supported.