# Welcome

### Built for Enterprise Growth Teams

Nami is the only no-code subscription platform purpose-built to optimize the full revenue funnel — from acquisition to retention — with the speed and intelligence modern growth teams demand.

#### No-Code That Moves Fast

Launch and iterate faster with cloud-based tools that eliminate engineering bottlenecks. From pages to onboarding flows, your team can build, test, and optimize every touchpoint of the subscriber journey — no app update required.

#### Full-Funnel Optimization, Out of the Box

Nami powers every stage of the funnel:

* Top of funnel: Drive conversions with targeted acquisition campaigns and high-converting landing pages.
* Mid-funnel: A/B test native pages, personalize pricing, and surface smart offers that move users to purchase.
* Bottom of funnel: Improve retention with cancel-saver flows, win-backs, and predictive churn models.

#### AI-Powered Revenue Acceleration

Our proprietary machine learning models help you identify high-value users, predict intent, and trigger the right message at the right time — automatically. No guesswork. Just smarter monetization.

#### Trusted by the Enterprise

Fortune 100 companies rely on Nami to manage their subscription infrastructure, optimize revenue outcomes, and deliver personalized subscriber experiences at scale. To learn more, [request a demo](https://www.namiml.com/request-demo).

{% if !visitor.claims.unsigned.plan %}
{% hint style="info" %}
[Looking for docs? Access the documentation portal from the Nami Control Center.](https://app.namiml.com/)
{% endhint %}
{% endif %}


---

# Agent Instructions: 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://docs.namiml.com/get-started/readme.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.