# Rolling out to a team

Getting a team from provisioned to genuinely using it, and the checkpoints that predict whether it will stick.

Source: https://replicatelabs.ai/docs/managers/rollout
Last updated: 2026-09-03

---

Provisioning a team is not a rollout. This page is what happens after the accounts exist.

## The thing that decides it

Whether each person does one meaningful piece of real work in the first three days.

Not a training session, not a walkthrough, not a demo. One rep, one live deal that is genuinely stuck, one conversation with their coach. People who do that keep going. People who have not opened it by day three usually never do.

<div class="dnote key">
<span class="dnote-h">Check on day three, not week four</span>
<p>By week four the answer is already decided and the recoverable moment has passed. A five minute check on day three, per person, is the highest-return management action in the whole rollout.</p>
</div>

## A rollout that works

<figure class="dfig">
<div class="dframe dark">
<div class="dflow">
<div class="dstep"><span class="dstep-n">1</span><b>Before launch</b><span>Confirm the knowledge base has your products and buyers in it, and that at least one roleplay matches a conversation the team actually has. An empty account argues against the product.</span></div>
<div class="dstep"><span class="dstep-n">2</span><b>Launch</b><span>Thirty minutes, not two hours. Say what it is, say plainly what you can and cannot see, and have everyone bring one real deal.</span></div>
<div class="dstep"><span class="dstep-n">3</span><b>Day three</b><span>Per person. Anyone who has not started gets fifteen minutes with you on one of their own deals.</span></div>
<div class="dstep"><span class="dstep-n">4</span><b>Week two</b><span>Use it in a one to one. Once your reps see it in the management rhythm, it stops being optional.</span></div>
</div>
</div>
<figcaption><b>Four checkpoints.</b> Step one is the one that gets skipped and the one that causes the most damage.</figcaption>
</figure>

## What to say at launch

Three things, in this order.

1. **What you can and cannot see.** Be specific, because a vague answer here is worse than a blunt one. You see roleplays, call transcripts and scores. What they work through with their coach reaches you as what they are stuck on, not as a transcript. See [What you can see](/docs/managers/what-you-can-see).
2. **Bring a real deal.** Not a demo scenario. The one keeping you up.
3. **This is not a practice tool.** If the team hears "roleplay app", they will treat it as training and it will die as training. It is for the deals they are running this week.

Skip the feature tour. Nobody retains it, and the button row is self-explanatory once someone has a reason to click.

## What not to do

<div class="dsplit">
<div class="dpanel no">
<div class="dpanel-h">Mandate a usage number</div>
<p>"Three sessions a week" produces three sessions a week of nothing. You will hit the metric and change no behaviour, and you will have taught the team that this is a compliance exercise.</p>
</div>
<div class="dpanel no">
<div class="dpanel-h">Launch into an empty account</div>
<p>A coach that does not know your products and a practice list with no relevant scenario makes a first impression you will spend a quarter undoing.</p>
</div>
</div>

## What to measure

Not logins. Ask two questions at the end of the first month.

- **Is the same weak criterion still the weakest?** Across the team, that is the honest read on whether coaching is changing anything.
- **Are the deals people brought in week one further along?** That is the one that matters to your number.