proposal

name	proposal
description	Customer proposal generation. Researches prospect, designs solution, builds proposal document, writes executive narrative. On-demand, 2-3 per week. Octopus colors: Yellow (research) + Red-Orange (solution design) + Blue (document) + Green (narrative).

/proposal: Customer Proposal Generation

Octopus Colors: Yellow (Researcher) + Red-Orange (Designer) + Blue (Maker) + Green (Marketer)

Process

1. Gather context: Read $ARGUMENTS or ask Chairman for prospect details
2. Research (Yellow):
   • Prospect company: size, industry, known pain points
   • Previous interactions (check commercial knowledge base)
   • Competitive landscape for this deal
3. Solution Design (Red-Orange):
   • Match prospect needs to offerings
   • Define scope, timeline, deliverables
   • Structure pricing (tiers if applicable)
4. Document Build (Blue):
   • Build proposal from structure
   • Populate with prospect-specific data
   • Format professionally
5. Narrative (Green):
   • Write executive summary in the prospect's language
   • Frame value in terms of their specific pain points
   • Include one relevant proof point
6. Present to Chairman for review and pricing approval

Output Format

# Proposal: [Prospect Name]
Date: [date] | Prepared by: [Organization]

## Executive Summary
[2-3 paragraphs in prospect's language]

## Proposed Solution
[Scope, approach, deliverables]

## Timeline
[Phases with dates]

## Investment
[Pricing, payment terms]

## Why Us
[Relevant proof point, differentiator]

---
Chairman Review:
[ ] Approve and send
[ ] Adjust pricing to: ___
[ ] Revise scope
[ ] Hold

Rules

• Always read commercial knowledge base before researching
• Pricing requires Chairman approval (approval gate, always)
• Save approved proposals to departments/commercial/knowledge/proposals/
• If web research needed, cite sources