Skip to content
OpenCorvus

Inspect the team before use

Active database publication

Sales Strategy & Customer Research

Builds an attributable customer dossier, parallel opportunity and positioning analyses, an audited sales strategy, and a practical sales playbook.

Install in OpenCorvusDownload this exact revisionTrust model

Opens the installed OpenCorvus desktop app. The client re-downloads and re-verifies this exact revision, then asks you for an install scope. No desktop app yet? Install OpenCorvus first

Bound execution graph

Workflow and handoffs

The graph shows who owns each step and which earlier result it depends on. It explains the team's collaboration contract; it is not live task progress and does not schedule Agents from the page.

Bound revision · 1 workflows · 7 nodes · 7 Agents
Bound revision34263482
01Evidence-backed Sales Strategy Playbook7 nodes
  1. 01sales-strategy-plannerPublishes sales-strategy/research-charter.root
  2. 02sales-customer-researcherPublishes sales-strategy/customer-dossier.← sales-strategy-planner
  3. 03sales-opportunity-analystPublishes sales-strategy/opportunity-analysis.← sales-customer-researcher
  4. 04sales-positioning-analystPublishes sales-strategy/positioning-analysis.← sales-customer-researcher
  5. 05sales-strategy-synthesizerPublishes sales-strategy/strategy-brief.← sales-opportunity-analyst + sales-positioning-analyst
  6. 06sales-strategy-fact-checkerPublishes sales-strategy/audit.← sales-strategy-synthesizer
  7. 07sales-playbook-writerPublishes sales-strategy/playbook.← sales-strategy-fact-checker
Evidence output1

Intended scope

Use for a bounded product, market, or account set that needs customer research, opportunity prioritization, positioning, and an audited sales playbook.

  • Product pillarswork
  • Agent roster7 declared roles
  • Declared workflows1 complete responsibility and dependency graphs
  • Full capability projection2 Skills · 4 tools · 0 MCP refs

Walkthrough pinned revision

Role and dependency walkthrough

This workflow explanation is pinned to the current package digest. It is not a running Agent session, timer, or generated language-model output. Real execution occurs in the OpenCorvus client.

builtin/sales-strategy@2026.08.19.1package sha256:3426348224ae6926d58e74559ab3b9dc6a3d44c43910b9cd849ee730aabc93ea

A node becomes schedulable only after its depends_on evidence is terminal. This page explains that contract and does not advance runtime state.

sales-strategy-playbook

Evidence-backed Sales Strategy Playbook

  1. 01sales-strategy-plannerdepends_on: []
  2. 02sales-customer-researcherdepends_on: sales-strategy-planner
  3. 03sales-opportunity-analystdepends_on: sales-customer-researcher
  4. 04sales-positioning-analystdepends_on: sales-customer-researcher
  5. 05sales-strategy-synthesizerdepends_on: sales-opportunity-analyst, sales-positioning-analyst
  6. 06sales-strategy-fact-checkerdepends_on: sales-strategy-synthesizer
  7. 07sales-playbook-writerdepends_on: sales-strategy-fact-checker

Install handoff boundary

The OpenCorvus client owns the real scope choice when a later import is performed. This page only explains project and global behavior and does not submit an install itself.

The client requires an explicit scope

Project scopeApplies only inside the current project; the same package ID overrides a global installation.
User-global scopeAvailable to the current user, but never silently overrides a project installation.

The public page hands over one exact revision, or completes a signed bundle download. It never batch-installs or activates a team. The scope explanation describes client responsibility; it is not a web form that can be submitted.