Draft proposal

Use when the user only needs a proposal. Research or email too → run-pipeline.

Writing guidance: ${CLAUDE_PLUGIN_ROOT}/playbooks/proposal.md.

What a full version needs

Company name, what is being sold, the buyer's problem, scope, price.

Missing price or scope → produce a skeleton immediately. Do not ask and then wait. Ship the structure, mark the gaps, let the user fill them in — far faster than a round of questions.

Three levels

Default length 250–500 words. Longer only on explicit request.

Structure

1. Summary — 3–4 sentences, their situation first
2. Current situation — in the buyer's words
3. What we propose — tie each item to an item in section 2
4. Scope — what is included, and what is not
5. Cost — clear, or an explicit range
6. Next step — one action with a date

Output

### Proposal nháp
[Content following the structure above]

### Việc tiếp theo
- [What to fill in or check — max 3 lines]
- Gửi xong nhắn mình phản hồi của khách để cập nhật deal.

Headings follow the user's language.

ROI

A framework for discussion, not a promise. For Vietnamese SMEs a short "where the ROI could come from" section usually beats a spreadsheet — only build numbers when asked.

Banned: "will save", "guaranteed", "certain to", "100%", "we commit". Use: "if applied well", "estimated based on...", "we should measure by...".

Every ROI figure must show its assumptions.

Never

• Invent a price.
• Invent a past customer or their results.
• Write long and polished while the buyer's pain is unknown.

After writing

Always review with ${CLAUDE_PLUGIN_ROOT}/agents/sales-reviewer.md — proposals carry more numbers than emails, so more risk. Then update the deal file per ${CLAUDE_PLUGIN_ROOT}/policies/state-management.md.

References

Load one:

• references/proposal-sections.md — what each section should contain
• references/roi-calculator.md — only when ROI numbers were requested

Writing Vietnamese → ${CLAUDE_PLUGIN_ROOT}/knowledge/vietnamese-sales-language.md.