# Product at a glance

![](/files/Qd0Rv2Nz10FGnqDb0smi)

Sudo combines high-frequency social behavior with differentiated Web3 actions. The result is a messenger that can become a daily app, a wallet command center, and a community growth engine.

## Executive snapshot

| Metric                   | Value | Meaning                                                                     |
| ------------------------ | ----: | --------------------------------------------------------------------------- |
| Counted product features |   148 | Large product surface across chat, Web3, social, privacy, AI, and settings. |
| Product categories       |     6 | Clear product pillars for documentation and navigation.                     |
| Engagement buckets       |     6 | Useful for prioritization and GTM messaging.                                |
| Primary tabs             |     5 | The app likely supports multiple high-level behaviors, not one single flow. |

## Category split

| Category           | Count | Product role                                                                    |
| ------------------ | ----: | ------------------------------------------------------------------------------- |
| Social / Viral     |    45 | Stories, groups, channels, invite links, QR, creator and growth loops.          |
| Web3 / Finance     |    31 | Wallet, swap, tokens, escrow, governance, validators, payments, audits.         |
| Settings / Utility |    27 | Profile, storage, backup, notifications, language, help, premium.               |
| Core Chat          |    23 | Daily messaging, media, search, inbox behavior, composer actions.               |
| Privacy / Trust    |    16 | Encryption, locks, permissions, blocking, disappearing messages, wallet safety. |
| AI / Bots          |     6 | AI Explorer, transaction history, watcher alerts, approvals, tokens, locks.     |

## Engagement model

| Bucket                  | Count | Strategic meaning                                                                                         |
| ----------------------- | ----: | --------------------------------------------------------------------------------------------------------- |
| High engagement         |    28 | Frequent surfaces that can drive retention: chats, reactions, calls, stories, live location, watcher bot. |
| Medium engagement       |    43 | Important secondary depth: events, scheduled calls, media libraries, management screens, validators.      |
| Core utility            |    26 | Required trust and hygiene: archive, backup, export, restore, permissions, linked devices, onboarding.    |
| Unique / differentiated |    21 | The strongest product story: chat payments, wallet, AI Explorer, token creator, escrow, multisig, audits. |
| Viral / growth          |    16 | Loops that spread the product: stories, invites, QR, groups, channels, forwarding.                        |
| Trust / retention       |    14 | Features users rely on before adopting the app deeply: E2EE, locks, approval risk, seed backup.           |

## What this means for product strategy

Sudo has three major strengths:

1. **Daily habit potential** through chat, stories, calls, groups, and channels.
2. **Differentiation** through wallet-native and AI-assisted Web3 workflows.
3. **Retention trust** through privacy, backup, lock, verification, and approval-risk features.

The best public positioning is not “another messenger.” It is **secure social messaging plus wallet-native actions plus AI-assisted Web3 workflows**.


---

# 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://docx.sudochat.app/overview/product-at-a-glance.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.