> ## Documentation Index
> Fetch the complete documentation index at: https://docs.findtempo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding

> What a standard Tempo deployment includes, the outcomes it delivers, and what your team provides.

Onboarding is the work of getting Tempo from signed to steady state. It is scoped to outcomes, not hours, and it runs for a defined deployment period. After that, your team is supported under the [support policy](https://docs.findtempo.co/support/support-policy.md).

This page is for the admin or project owner coordinating the deployment. If you are a seller, go to [Getting Started](https://docs.findtempo.co/using/getting-started.md). For the step-by-step configuration checklist, see [Set up your organization](https://docs.findtempo.co/admin/setup.md).

## Deployment period

The standard deployment period is **60 days** from the Effective Date on your Order Form. Tempo and your team work through the outcomes below during that window. If you already used Tempo before signing, outcomes that are already met count as done on day one.

## Outcomes

Onboarding is complete when each of these is true for your organization. Where an outcome depends on a source you are not using, it does not apply.

**1. Your context sources are connected**

Every supported source in your Order Form is connected and syncing: your CRM, email and calendar, a transcript source, and Slack or Notion where used. See [Connect your context](https://docs.findtempo.co/integrations/overview.md).

**2. Your pipeline is reconciled**

Your open opportunities appear as deals in Tempo with current deal state, and CRM fields are mapped with an update mode set. See [Fields and CRM objects](https://docs.findtempo.co/admin/fields.md).

**3. Your Slack deal channels are mapped and backfilled**

Deal and customer channels are linked to the right deals, and available history is imported up to the backfill allowance in your Order Form. See [Slack](https://docs.findtempo.co/integrations/slack.md).

**4. Your Playbook is seeded**

At least one sales process source is ingested so answers reflect your methodology and stage criteria. See [Playbook sources](https://docs.findtempo.co/playbook/sources.md).

**5. Your first signals are live**

Two or three signals your team already tracks by hand are defined, previewed, and active. See [Signals](https://docs.findtempo.co/signals.md).

**6. Your sellers are connected**

Each seller has connected Tempo to their AI platform over MCP and has run their first prompts. See [Connect your AI platform](https://docs.findtempo.co/integrations/mcp.md).

**7. Your developers are onboarded**

Where your team builds on Tempo, an API key is issued and your engineering lead has walked through the [REST API](https://docs.findtempo.co/api-reference/introduction.md) and [MCP tools](https://docs.findtempo.co/developers/mcp-tools.md).

**8. Training is delivered**

Tempo leads the sessions described below.

You can check progress at any time by asking Tempo:

```text wrap theme={null}
Show me our Tempo instance setup. What's configured, what's blocked, and what should I do next?
```

## Training

Tempo delivers these sessions at mutually agreed times, in group or one-on-one format as needed:

| Session | When | For | Covers |
| - | - | - | - |
| Technical onboarding | Early in the deployment period | GTM engineering and admins | The REST API, the MCP server, and defining signals |
| Month 1 follow-up | About 30 days in | Sales, marketing, and customer success users | Your team's use cases and the prompts that work |
| Month 2 follow-up | About 60 days in | Sales, marketing, and customer success users | Refinement, signals, and what to do next |

## Who you work with

Tempo assigns a **deployment lead** as your point of contact for the deployment period. The deployment lead coordinates the outcomes above, brings in Tempo engineers as needed, and runs the training sessions. Tempo may change who holds the role with notice to you.

## What your team provides

Deployment moves at the speed of access. Your team:

* Names a project owner who coordinates the deployment and is Tempo's primary contact.
* Makes the right people available when needed: revenue operations, IT, security, and admins for each connected source.
* Grants Tempo access to each connected source in time, including any admin approval your CRM requires. See [Requirements](https://docs.findtempo.co/requirements.md).
* Schedules training sessions and gets the right people to attend.
* Shares how you sell: your sales process, stage criteria, playbooks, and which data sources matter. Tempo uses this to configure Playbook, signals, and fields.

Delays in access, approvals, or availability extend the timeline. They do not extend the deployment period unless agreed in writing.

## What onboarding does not include

The following are delivered as professional services under a separate Statement of Work:

* Integrations with sources Tempo does not support. See the [supported list](https://docs.findtempo.co/integrations/overview.md).
* Custom workflow or agent development against the API or MCP server.
* Historical data import beyond the backfill allowance in your Order Form. See [Usage and limits](https://docs.findtempo.co/admin/usage-and-limits.md).
* Dedicated Tempo staff beyond the deployment period.

## After onboarding

Once the outcomes are met, your organization is in steady state. Questions and issues go through [support](https://docs.findtempo.co/support.md). Training refreshers for new team members are available on request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.