Description. Fig.OS is the operational heart of Fig Studio LLC. It is a custom-built dashboard and orchestration layer that drives every stage of the product lifecycle — from the initial identification of a market gap to the management of advertising campaigns for a shipping application. Every product the studio has built was built through this system.

The governing principle is simple: zero discipline required. Fig.OS works around the practitioner, not the other way around. It surfaces what matters, proposes what to do next, and executes on approval. The practitioner decides; the system handles the rest.

What It Does. Fig.OS operates across the full product lifecycle in four broad phases:

1. Research. The system monitors markets, researches competitors, scouts communities, and identifies gaps. When it finds a viable opportunity, it drafts a proposal for human review. Ideas that survive scrutiny move forward; the rest are filed and forgotten.
2. Build. Once a product is greenlit, Fig.OS generates a build plan to MVP — a sequence of small, gated, human-verified tasks. It dispatches and coordinates sub-agents, integrates with Fig Shipyard for task management, and keeps the work pointed at its north star.
3. Ship. Fig.OS connects directly to App Store Connect and Google Play Console. It manages submissions, monitors review status, and tracks versions across platforms.
4. Grow. After launch, the system conducts ASO analysis, manages Apple Search Ads campaigns, generates growth reports, and monitors revenue through RevenueCat. It scouts Reddit and other channels for user feedback and competitive intelligence.

Integrations. Fig.OS connects to the outside world through three Model Context Protocol servers:

Skill Domains. The system’s 28 skills are organized into seven domains:

Portfolio. Fig.OS maintains a live view of every product in the studio’s portfolio, with real-time status, download counts, and active-user metrics pulled from the connected integrations. At present the portfolio contains three applications: Flare (shipped), Bureau of Minor Bravery (in development), and Shipyard (internal beta).

Memory. An Obsidian vault serves as the system’s persistent memory. Research findings, decision logs, competitive analyses, and session notes are retained across sessions so that nothing is lost between conversations. The practitioner can review, edit, or discard any memory at any time.

Convictions. Fig.OS is built on a small number of non-negotiable principles:

• No product is greenlit, no task is transitioned, and no campaign is launched without the express approval of a human operator.
• The system proposes; the practitioner disposes.
• Automation exists to remove friction, not to remove judgement.

Inquiries. Write to andre@figstudiollc.com. Replies within seven business days.