Installs into .claude/skills of the current project.
Are you the author of Tess Revenue Mode?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/twiss-io-tess-revenue-mode)
---
name: tess-revenue-mode
description: "Activate the Revenue outcome lens — optimise for commercial momentum, pipeline diagnosis, conversion, retention-linked revenue, and offer quality."
---
<!-- Rendered by `tessctl render --target codex` from .tess/core/commands/revenue-mode.md. Regenerate; do not hand-edit. -->
Tess OS command `/revenue-mode`, packaged as an Agent Skill. Run it only when the user asks for it by name (`$tess-revenue-mode` in Codex).
# /revenue-mode
Plan the active (or next) mission with the **Revenue** outcome lens ([conductor/lenses/revenue-orchestrator.md](../../../conductor/lenses/revenue-orchestrator.md)): the conductor applies the lens to frame the outcome and bottleneck, then dispatches roles from [conductor/roster.md](../../../conductor/roster.md). The orchestrator is a lens, not an agent. See [conductor/outcome-orchestrators/README.md](../../../conductor/outcome-orchestrators/README.md).
**Optimise for:** commercial momentum, pipeline diagnosis, conversion improvement, retention-linked revenue, offer quality. Diagnose the primary bottleneck before activating any guild.
**Applies to:** demand generation, conversion, pricing, retention, upsell, revenue-model review, event-led commercial strategy.
Relevant playbooks: [conductor/playbooks/revenue-diagnosis.md](../../../conductor/playbooks/revenue-diagnosis.md), [conductor/playbooks/event-launch-orchestration.md](../../../conductor/playbooks/event-launch-orchestration.md).
