> For the complete documentation index, see [llms.txt](https://tutorials.kuasa.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.kuasa.io/getting-started/getting-started.md).

# Getting Started

Welcome to Kuasa! Kuasa is one of the secrets for merchants to create large and consistent online sales by using the 8 Kuasa systems.

{% embed url="<https://www.youtube.com/watch?v=_4Wbt404B4Y>" %}

Kuasa is a Customer Relationship Management (CRM) system that helps you build an online store without the need for technical skills! This platform is specially prepared to help you build an online store as fast as 10 minutes, blasting, customer follow-up, even managing orders from your customers! Not only that, you can also set your own payment online or offline! And it is easy to receive orders from customers quickly without requiring high technical skills. This page will be your main guide.

Customers can also make this guide as your first step to build your online store. Enjoy your business journey with Kuasa!


---

# 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://tutorials.kuasa.io/getting-started/getting-started.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.