# Revenue Model

Simple, transparent, and scalable — aligned with the value we deliver across both core products. Here's how we generate revenue:

***

#### **1. AI-Powered Escrow Service**

Our escrow and verification engine is designed for professional Web3 collaborations, marketing campaigns, and agency-level operations. To access the platform and its full suite of tools, projects pay a combination of a monthly access fee and a transaction fee.

**Pricing Structure:**

* **Flat Monthly Fee:** $1,000\
  Grants full access to the SecroAI dashboard, AI verification engine, smart contract escrow system etc.
* **Transaction Fee:** 3% per campaign transaction\
  Applied to each escrow payout once deliverables are verified and payments are released. This incentivizes platform success and scales with usage.

**Why this model?**

* Predictable costs for clients running recurring campaigns
* Scales with project success and campaign volume
* Aligns our incentives with customer outcomes

***

#### **2. Tokenized Referral System**

Our referral system operates as a plug-and-play growth engine for Web3 operators.

**Pricing Structure:**

* **Flat Fee:** 5% of referred transaction value\
  This fee is applied only when a conversion takes place (e.g. staking, minting, protocol usage). It is automatically deducted via smart contract upon settlement.

**Why this model?**

* Simple, no-strings-attached pricing
* Only pays when real value is delivered


---

# 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://secroai.gitbook.io/secroai-2.0/revenue-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.