> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/ai-product/growth.md).

# Growth

A product has to grow after it ships. The page first defines product-led growth and how usage and retention are driven inside the product, then looks at a growth tool whose claims were not validated here.

The same notes are in [Business](/ai-product/business.md), [Product Vision & Strategy](/ai-product/product-vision-and-strategy.md), and [User Experience Design (UX)](/ai-product/user-experience-design-ux.md).

The idea starts with a definition. [Productled.com](https://productled.com/blog/product-led-growth-definition/) — definition and why it is taking off. The practice behind it is [Mixpanel with Ken Rudin](https://mixpanel.com/blog/googles-head-of-user-growth-on-driving-product-usage-and-retention/) on "Google’s head of user growth on driving product usage and retention", which comes down to two moves. The first is raising feature awareness — through UI changes. Identifying and increasing the adoption of these features is very often a great way to accelerate product growth. The second is promoting a feature **in context** to drive usage and retention, i.e., when the user needs it.

Those moves only work when the product itself is the sales channel. [A guide to product-led growth](https://www.trychameleon.com/blog/product-led-growth) defines product-led growth (PLG) as users experiencing product value through free trials or freemium plans, having your product sell itself, with examples and a framework.

## Tools

After the growth idea comes the tooling that promises to automate it, and here the claim was not independently validated. The one tool listed is GrowthAI —

> a turn key solution to customer lifecycle

They promise a lot of things that I can't validate.

The archived copy of its site is <https://web.archive.org/web/20211217202430/https://www.growthai.co/>, which sells GrowthAI - GAIN & GROW customers never been EASIER as ROI based Data Driven Marketing Automation.

## Deprecated links

{% hint style="warning" %}
These links and images no longer work. The original wording is kept here. A same-resource copy, when one was checked, is used above.
{% endhint %}

* What is Product Led Growth (Unusual Venture Capital) - an excellent series that explains PLG. This address no longer opens: <https://www.field-guide.unusual.vc/chapters-enterprise/the-modern-go-to-market>
* blog post. This address no longer opens: <https://www.productled.org/foundations/what-is-product-led-growth#Chap4>
* GrowthAI - "a turn key solution to customer lifecycle", they promise a lot of things that I cant validate. This address no longer opens: <https://www.growthai.co/>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.mlcompendium.com/ai-product/growth.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
