> For the complete documentation index, see [llms.txt](https://docs.salescaling.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salescaling.com/en/strategies-and-use-cases/como-implementar-un-ciclo-de-coaching-basado-en-datos.md).

# How to Implement a Data-Driven Coaching Cycle

Traditional sales coaching often relies on intuition and isolated memories, which makes objectivity and the scalability of best practices within a team difficult.

This guide explains how to use **Salescaling** to implement a continuous improvement cycle, transforming coaching from a subjective process into a discipline based on measurable data and real evidence.

## Step-by-Step Guide: The Continuous Improvement Cycle

**Step 1: Diagnose (Macro Analysis)** The first step is to identify the priority areas for improvement. Instead of reviewing recordings at random, you should use the Global Analytics Dashboard to look for patterns and trends.

* **Filter by Activity Type:** A particularly low Average AI Score in a specific category, such as "Product Demos," may point to an area to focus on.
* **Analyze Keywords:** The recurring appearance of a competitor's name in Most Used Keywords may indicate the need to strengthen the sales pitch.

**Step 2:** **Analyze (Micro Analysis)** Once an area for improvement has been identified, the Recording Explorer should be used to find specific examples.

* The meeting Detail View with a low score is accessed.
* The AI Score breakdown is reviewed, which indicates exactly which methodology criteria were not met.
* The Interactive Transcript is used to locate and listen to the exact moments that caused the low score.

**Step 3:** **Train (Create Reusable Material)** The findings from the analysis should be turned into standardized training material.

* From the Detail View, Clips of the key moments are created, saving both good and bad examples for later comparison.
* In the Clip Library, these clips are grouped into a thematic Playlist (e.g.: "Training: Handling Price Objections").

**Step 4: Coach (Evidence-Based Action)** With the material prepared, coaching sessions become more effective.

* In 1-on-1 sessions, the Playlist is played back to review real moments instead of discussing hypothetical situations.
* Specific, actionable comments are left in the Feedback tab of a recording for documented follow-up.

**Step 5: Measure Impact (Close the Loop)** The cycle closes by going back to the data to evaluate the effectiveness of the training.

* After a set period of time, you should return to the Global Analytics Dashboard.
* Check whether the Average AI Score for the meeting type worked on has improved. If so, a new friction point can be identified and the process repeated.

{% hint style="info" %}
To Learn More: Dive Deeper into Coaching Strategies. Now that you know *how* how to use the **Salescaling** tools for coaching, we invite you to read our blog article where we explore the most effective methodologies for leading high-performing sales teams.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.salescaling.com/en/strategies-and-use-cases/como-implementar-un-ciclo-de-coaching-basado-en-datos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.