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

# 1:1 Prep

> The rep's deals reviewed before every 1:1: what moved, what's stuck, where the manager can help, and what was agreed last time.

A manager with eight reps has eight 1:1s a week and prepares for maybe three. The rest open with "so how's it going," which hands the agenda to the rep and turns the meeting into a status update the manager could have read. 1:1 prep gives the manager the read before they walk in: what moved in this rep's deals, what is stuck, what was agreed at the last 1:1 and whether it happened, and the one or two places a manager can actually change an outcome.

## Data Sources

| Category         | Required | Recommended |
| :--------------- | :------- | :---------- |
| CRM              | ✓        |             |
| Calls            | ✓        |             |
| Email + Calendar |          | ✓           |
| Messaging        |          | ✓           |

**Starter** (required only): the rep's deals, what moved since the last 1:1, and what their calls say about the deals that are stuck.

**Full** (required + recommended): the same, plus engagement patterns between calls, so a deal that looks fine in CRM but has had no customer reply in three weeks shows up as what it is.

See the [Context Graph](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the prep.

### Choose your path

| Path                       | Best for                                                             | Output is delivered                   |
| :------------------------- | :------------------------------------------------------------------- | :------------------------------------ |
| Build in Clearskies        | Managers with 1:1s on a recurring calendar slot                      | To Slack DMs, ahead of each 1:1       |
| Build in Claude or ChatGPT | Managers who prep in the moment, and anyone shaping the format first | In the Claude or ChatGPT conversation |

## Build in Clearskies

Build the workflow once and every manager gets a read on the right rep's deals before each 1:1, without knowing the workflow exists.

### The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:

```text theme={null}
Thirty minutes before a recurring 1:1 on a manager's calendar, generate a
prep brief from the Clearskies Context Graph. Cover the rep's deals: what
moved since the last 1:1, what is stuck and why, which deals have no next
step, and where a manager could unblock something. Send it to the
manager's Slack DM.
```

The app configures the trigger (the manager's calendar, with an offset ahead of the meeting), the rep whose deals to pull, and the destination.

Meeting workflows always start with a filter. Every calendar event counts as a meeting, so the filter is what narrows the run to actual 1:1s rather than every internal block on a manager's calendar. A recurring 1:1 with a consistent title is the easiest thing to filter on, and getting that filter right is most of the work on this one.

Test it against a real 1:1 before publishing. Test runs are always dry, so nothing sends while you are still refining.

### Deploy to Slack

Once published, each manager gets this before each 1:1:

```text theme={null}
1:1 Prep — Daniel
1:1 at 10:00 AM · Last 1:1 Aug 4
Book: 7 open deals, $412K, 3 closing this quarter

Since your last 1:1
• Acme Corp, $84K, moved to Verbal. Renewal terms settled on the Aug 4
  call, the same day as your last 1:1.
• Ridge Analytics, $95K. Still no customer reply since Jul 18, now four
  outbound touches. This was on the list last time too.
• Two deals progressed a stage with no notable cause on the record.

Stuck
• Ridge Analytics — 24 days without a two-way exchange. Last recorded
  next step was "waiting on legal," set 19 days ago and never updated.
• Bellwether, $38K — no next step recorded at all, and none set on the
  last two calls.

Agreed last time
Daniel committed to getting a second contact at Ridge Analytics. The
record shows no new contact engaged there since.

Where you can help
Ridge Analytics is the same conversation as last week. It has had four
one-way touches and a stale next step, and the second-contact plan did not
happen. Either it needs a different approach or it needs to come out of
the quarter.

Worth noticing
On Acme, Daniel got to the implementation lead two days after committing
to it. That is the behaviour that moved the deal.
```

### Customize the rollout

* Set the timing anywhere from minutes to a day ahead of the 1:1
* Choose what is in scope: the rep's whole book, or only deals closing this quarter
* Add the sections your 1:1s use and drop the ones they do not
* Include a positive note by default, so the brief is not only a list of problems
* Send a copy to the rep as well as the manager, so both walk in with the same read
* Chain it with [rep coaching](/docs/use-cases/rep-coaching-from-real-conversations) so the deal read and the call-quality read arrive together

## Build in Claude or ChatGPT

For managers who prep in the ten minutes before a meeting, and for shaping the format before you automate it.

### The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). Replace the name and the window with your own.

```text theme={null}
Using the Clearskies Context Graph, prep me for my 1:1 with Daniel.

Cover:
- What moved in his deals since our last 1:1, and what caused each move
- What is stuck: no recent two-way activity, no next step, or a next step
  that has gone stale
- Anything we agreed at the last 1:1, and whether the record shows it
  happened
- The one or two places I can actually help rather than just ask about
- One thing he did well that is worth saying out loud

Ground everything in specific calls, threads, or CRM changes. Do not
speculate about how he is doing.
```

The last line matters. This prep is about the deals and the behaviour on record, not a read on the person.

### Make it yours

* Add `Compare this to our last three 1:1s and tell me what keeps coming back` to catch the pattern rather than the week.
* Add `What questions should I ask that the record cannot answer` to build the agenda.
* Add `Which of his deals would I bet against, and why` when the 1:1 is really a pipeline conversation.

### The Skill (Claude)

The `clearskies:rep-coaching` skill in the Clearskies plugin for Claude covers the conversation-quality half: it pulls a rep's recent call transcripts, surfaces coaching moments with timestamps, identifies patterns across calls, and drafts specific feedback. Run it alongside a deal read when the 1:1 is about how the rep is selling rather than what is in their pipeline.

`clearskies:pipeline-review` covers the deal half across a book, prioritized by urgency rather than close date.

<Tip>
  Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow.
</Tip>

## The Plugin

**Ready to make this part of your team's workflow?** We'll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works.

[**Book 15 minutes →**](https://calendly.com/pouyan/new-meeting)

## Next steps

1. [Sign in to Clearskies](https://app.clearskies.cc/)
2. Connect your data sources
3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)