> For the complete documentation index, see [llms.txt](https://tembi.gitbook.io/tembi-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tembi.gitbook.io/tembi-knowledge-base/jobs-library/protecting-and-growing-existing-customers.md).

# Protecting and growing existing customers

Tembi supports Key Account Management by acting as a continuous monitoring layer on top of your customer portfolio.

Instead of relying on periodic checks or ad-hoc reviews, you maintain a clear view of how your accounts are performing in the market – and get alerted when something changes that may affect revenue.\
\
**If you’re new to using Tembi for account management, start with the short tutorial below.** It walks through the core setup: building your account list, attaching notifications, and using checkout score as a health check.

{% @arcade/embed flowId="yQxTtksBfwSGqMfJ2zwF" url="<https://app.arcade.software/share/yQxTtksBfwSGqMfJ2zwF>" %}

### Account management in the Tembi platform

The KAM workflow in Tembi is built around a simple idea:\
define your portfolio, then monitor changes automatically.

The core setup consists of:

* A clean list of accounts
* A small number of signals that matter
* Notifications when those signals change

Once this is in place, Tembi becomes a background monitoring layer rather than another tool to check manually.

### Build your account list

Start by representing your client portfolio as a list in Tembi.

This list becomes your default scope when reviewing changes, risks, and opportunities across accounts.

Typical setups include:

* A list with all active clients
* A separate list for strategic or top-tier accounts
* Additional lists for long-tail accounts with lighter monitoring

Using lists ensures that changes are reviewed in context, not as isolated events.

### Turn changes into notifications

Attach notifications to your account lists so you do not have to rely on manual spot checks.

Common account-level signals to monitor include:

* First-position changes
* New competitor in checkout
* New product categoreis added

If notifications become too noisy, split your portfolio into multiple lists and apply different thresholds. Strategic accounts usually require closer monitoring than long-tail accounts.

### Use checkout score as a health check

[Checkout score](/tembi-knowledge-base/product-how-to/checkout-score.md) works as a fast, comparable health indicator across your accounts.

Use it to:

* Identify accounts with poor brand visibility
* Prioritise where to spend time and attention
* Locate clients where checkout isn't showing your services properly

### Track and defend first position

First position correlates strongly with selection and volume.

Monitor it as a leading indicator:

* Track when first position is gained or lost
* Defend it where it exists
* Investigate immediately when it changes

This allows you to intervene early, before changes turn into lost volume.

{% @arcade/embed flowId="cjiLn7E73aO8yoLGfWQ7" url="<https://app.arcade.software/share/cjiLn7E73aO8yoLGfWQ7>" %}


---

# 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:

```
GET https://tembi.gitbook.io/tembi-knowledge-base/jobs-library/protecting-and-growing-existing-customers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.