# Your first week

A day-by-day route from first sign-in to the point where reaching for the coach is a reflex rather than a task.

Source: https://replicatelabs.ai/docs/getting-started/first-week
Last updated: 2026-09-03

---

Most people who abandon an AI coach do it in the first three days, and almost always for the same reason: they opened it with nothing real in hand, got a generic answer, and concluded it was generic.

This page is the route that avoids that.

<div class="dnote key">
<span class="dnote-h">The one rule</span>
<p>Every session in your first week should be about a named, live opportunity or a call that is actually in your calendar. Not a hypothetical, not a test, not "show me what you can do". The coach is built to work specifics, and it is only impressive on specifics.</p>
</div>

## Day one: bring the deal that is keeping you up

Not the easiest deal. The one where you cannot honestly say what happens next.

Open a call, name the account, and describe it the way you would to a colleague who has to help you. Expect the first few minutes to be the coach finding out what you actually know rather than telling you anything.

End with two asks: give me the words I open the next conversation with, and tell me what you need me to find out.

Twenty minutes. That is the whole of day one.

## Day two: bring a call you have already had

Take a conversation from the last week, ideally one that went sideways, and work it through. If your account has a recording or notes tool connected, point the coach at the call rather than describing it from memory. What was actually said is reliably different from what you remember being said, and the gap between the two is where the coaching is.

## Day three: rehearse something before you do it

Find a conversation coming up that you are not looking forward to and [run a roleplay](/docs/roleplay/running-one) against it. Read the score afterwards, and take the weakest criterion straight to your coach rather than immediately running the roleplay again.

<div class="dnote">
<span class="dnote-h">Why day three matters</span>
<p>Day three is where the platform stops being a thing you were told to use. People who do a meaningful piece of work on day three keep going; people who have not opened it by then usually never do. If you manage a team, this is the day to check on, not week four.</p>
</div>

## Day four: come back to day one's deal

This is the session that shows you what the product actually is. Say the account name and stop talking.

The coach will pick up where you left it, and it will ask about the thing it told you to go and find out. If you did not do it, it will notice. That is the point, and it is the closest thing in software to a manager with unlimited time and perfect recall.

## Day five: use it for something small

The habit is built on small uses, not on set-piece deal reviews. A tightened follow-up email. A second opinion on one line of a proposal. A quick read on whether an objection is real or a brush-off. Two minutes each.

The reps who get the most out of it are not the ones running the longest sessions. They are the ones who reach for it without deciding to.

## After week one

<figure class="dfig">
<div class="dframe">
<div class="dflow">
<div class="dstep"><span class="dstep-n">1</span><b>Weekly</b><span>Every open deal that is not moving gets a conversation. Fifteen minutes each.</span></div>
<div class="dstep"><span class="dstep-n">2</span><b>Before every call that matters</b><span>Prepare, or rehearse, or both.</span></div>
<div class="dstep"><span class="dstep-n">3</span><b>After every call that surprised you</b><span>Work out what you missed while it is still fresh.</span></div>
</div>
</div>
<figcaption><b>The steady-state rhythm.</b> Roughly an hour a week, spread thin rather than blocked out.</figcaption>
</figure>