# Business Model

## Setting

Our business model is structured on multiple monthly payment plans and follows 2 key objectives:

1. Facilitate the adoption of our platform by companies and realities of the web3 through a basic plan accessible to all to become in a short time the most reliable review platform for DeFi products
2. Reward users for the reviews they leave without however affecting our margin, thus structuring different plans with monthly fees based on the features we can offer to various companies/DeFi protocols.

## Subscription Plans

<figure><img src="/files/nXsGxQc2FD3lujkZNXcg" alt=""><figcaption></figcaption></figure>

The structure of the payment plans on this scheme seems excellent to us because we do not have particular fixed costs other than those of maintaining and updating the platform itself.&#x20;

The only cases in which we need active personnel correspond to functions of advanced plans that still guarantee us a good profitability to be able to have a good return on expenses.\
\
Another line of business that fits, albeit in the background, in our business model is that deriving from advertising that we can activate on the platform when we reach good levels of traffic.

Indeed, we anticipate that once we become the reference platform for reviews in the DeFi ecosystem, given the nature of our service, we could easily achieve traffic levels on the platform itself good enough to guarantee us another revenue line from on-site advertising.

<br>


---

# 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://trustyfi.gitbook.io/trustyfi-whitepaper/business-model.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.