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

# SMPLR is for..

## SMPLR is built for:

**CFO, Treasury managers and Accountants**

* Easily onboard to crypto, without the need to understand blockchain technology
* Add multiple wallets and exchanges with ease, get all transactions reconciled and organized for audit, tax and reporting purposes. 
* Rich reporting options - cash flow statement, balance sheet, income statement, end-of-day positions, realized and unrealized gains & losses, contacts etc.
* Rule-based transaction labelling - focus on financial planning and performance, not on transaction aggregation, manual reconciliation, and accounting.

**CEOs**

* Powerful analytic dashboards to fully grasp company finances, positions, assets and liabilities, revenue trend in real-time.
* Actionable insights to guide business decisions that will enable the company growth.


---

# 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.smplr.xyz/getting-started-1/getting-started/smplr-is-for...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.