> For the complete documentation index, see [llms.txt](https://docs.churned.io/churned-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.churned.io/churned-docs/co-pilot/use-cases/use-cases-library-co-pilot/b2b-saas/expanding-within-existing-business-accounts.md).

# Expanding Within Existing Business Accounts

Trigger\
Business account with high product usage or satisfaction (e.g. multiple engaged users, NPS > 8).\
Segment: “Expansion Ready”

Action Flow Options\
Co-Pilot tests multiple upsell or expansion actions:

* Email to admin suggesting adding more teams or features
* In-app message or modal (if integrated) with upsell prompt
* Task for CSM to schedule expansion call
* Wait (control)

Co-Pilot Exploration\
Tracks which approaches lead to expansion (more seats, upgrades, features) → automates outreach or CSM task creation.

Next-Best-Action Push\
Best-performing expansion trigger pushed via CRM or marketing platform:

* Personalized by plan, usage, or success metric
* Message timing aligned with usage peak
* Routed to CS or AE team if needed

KPIs Tracked

* Expansion rate (seats, MRR, features)
* Click-through or reply rate
* CSM call booking rate
* Revenue growth from existing accounts


---

# 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.churned.io/churned-docs/co-pilot/use-cases/use-cases-library-co-pilot/b2b-saas/expanding-within-existing-business-accounts.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.