# The Problem

### User Acquisition and Retention: 

In today's digital landscape, User-Generated Content (UGC) is a primary driver of growth. 

{% tabs %}
{% tab title="Conversion" %}
UGC boosts online product conversion rates by 161%
{% endtab %}

{% tab title="Revenue" %}
UGC increases revenue per user by more than 100%
{% endtab %}

{% tab title="CPC" %}
UGC lowers the Cost-Per-Click by 50%. 
{% endtab %}
{% endtabs %}

However, achieving virality through UGC often depends heavily on **luck** rather than **structured capital deployment**, which makes success hard to replicate for founders and developers.

***

### Monetization and Financialization:

The financial sector is experiencing a massive shift. 

* The neobank market is projected to grow at a **54.8%** Compound Annual Growth Rate (CAGR) through 2030
* Top neobanks manage over **$2,400 billion** in Assets Under Management (AUM) compared to the broader DeFi market's **$164 billion.** 
* Neobanks now capture **40%** of all new US account openings, officially overtaking traditional banks, largely because their user acquisition costs are **4x lower** than those of traditional online banking.

While the playbook for neobanking is proven and highly lucrative, the infrastructure required for Web3 projects to easily integrate these features is nonexistent. Historically, building neofinance capabilities has been complex, high-cost, and uncertain for individual projects.

<div data-full-width="true"><figure><img src="/files/BcgdMUJLLgcerlxFLawh" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Key Insight:** Leveraging UGC and Neofinance are two major mountains businesses must climb to stay competitive today.&#x20;

At City Protocol, we believe both can be tackled together through a unified, one-stop platform.
{% endhint %}


---

# 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://city-protocol.gitbook.io/docs/introduction/welcome-to-city-protocol/the-problem.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.