# Master Strategy (Network Effects)

[Network effects](https://www.nfx.com/post/network-effects-bible) are what makes products unstoppable, when each new user makes the product more valuable for everyone else. Avici is built on this principle: growth comes from connecting multiple nodes that reinforce each other and compound over time. Its highly important in a competitive market like Fintech to have this. 

Avici’s network effect nodes:

* Trust Score
* Payroll Account
* Employer
* Employee
* Spend Card

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

***

### 1. Cold Start Problem

We solve this by bootstrapping with strong incentives and utility using the card

Our edge:

* Users don’t join Avici for others; they join for instant utility, spend card + USD account.
* Once they join, their actions (spending, salary deposits) start generating Zk data → trust score → yield → more users.

&#x20;Designing the cold start loop:

* Reward early usage (e.g. cashback, referral, yield boost).
* Highlight instant utility first, network benefits second.&#x20;

***

### 2. Multiple Network Effects in Avici

We have at least 4 overlapping network effects:

* Data Network Effect: Every user spend improves the Trust Score algorithm, making credit scoring more accurate.
* Two-Sided Network Effect: Employers ↔ Employees (Payroll system). More employers onboard → more employees → more card usage.
* Social / Behavioral Network Effect: Once friends or coworkers are on Avici (getting salary, cashback, etc.), switching becomes hard.&#x20;
* Platform Network Effect: As more merchants start accepting stablecoins, legacy payment rails face the innovator’s dilemma, they lack the incentives to adapt quickly, while the new ecosystem compounds value with every new participant

***

### 3. Defensibility

Our moat compounds through data, reputation, switching costs, and multi-product integration.

* Data: Trust Score becomes the standard.
* Switching Costs: Once salary + spend + savings are within Avici, leaving breaks the loop.
* Ecosystem Depth: Owning both payroll (employer) and card (employee) builds resilience, each reinforces the other.
* Reputation: Avici becomes synonymous with “crypto credit identity,” like Plaid became for data pipes.

***

### 4. Designing Incentives That Align Each Node

| Node                | Incentive                                                   | Effect                            |
| ------------------- | ----------------------------------------------------------- | --------------------------------- |
| Employer            | Lower payroll fees, instant payouts, yield on idle treasury | Motivates onboarding employees    |
| Employee            | Cashback, yield, credit line via Trust Score                | Drives transactions + retention   |
| Spend Card          | Rewards, 0-FX, instant off-ramp                             | Incentivizes everyday use         |
| Trust Score         | Unlocks higher limits, better rates                         | Incentivizes responsible behavior |
| DAO / Token Holders | Governance over credit & yield pools                        | Aligns ecosystem-level incentives |

Design principle:

Everyone should be rewarded when others use Avici more, so there is compounding alignment.

***

### 5. Compound Network Design

This is the holy grail, it’s a network of networks:

* Payroll network (employers ↔ employees)
* Spend network (users ↔ merchants)
* Credit network (users ↔trust score↔lenders)
* Data network (user data↔yield models)

Each strengthens the others, forming compound network effects, which is the most defensible moat in the world.

***

### 6. TLDR

* Starting with one strong wedge (e.g. spend card + payroll).
* Instrument every interaction to increase value for others (data, liquidity, reputation).
* Introduce status loops (e.g. High trust score = unlocked higher credit line + Early access to exclusive Events)
* Focus on node density, not just total users. Depth before breadth.

***


---

# 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.avici.org/how-to-fix/master-strategy-network-effects.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.