# Client Proposal Playbook

Use this playbook for proposal drafting, statement-of-work framing, scoped commercial offers, and pre-sales solution documents.

## Trigger

Use when a client need, request, or opportunity must be turned into a credible scoped document with clear value, assumptions, and next steps.

## Primary Roles

- Panglima
- Penulis Cadangan
- Strategi Jenama
- Strategi Produk
- Penggerak Pasaran
- Penganalisis if metrics or ROI framing matter
- Penyemak when the document carries meaningful commercial or delivery risk

## Workflow

1. Capture
- Define client problem, desired outcome, constraints, timeline, and known assumptions
- Use `vault/playbooks/discovery-call.md` first if the opportunity is still underdefined
- Use `vault/templates/proposal-brief.md` as the primary document scaffold

2. Shape
- Route through Strategi Produk if scope or solution boundaries are unclear
- Route through Strategi Jenama if message framing or offer positioning needs alignment
- Separate confirmed scope from options and future phases

3. Draft
- Lead with business outcome and recommended approach
- Make deliverables, assumptions, exclusions, and dependencies explicit
- Keep language concrete and commercially credible

4. Align
- If the proposal depends on implementation complexity, involve the relevant delivery roles
- If the proposal depends on traffic or growth assumptions, involve Penggerak Pasaran and Penganalisis

5. Verify
- Use `vault/checklists/content-copy-verification.md`
- Add `vault/checklists/product-support-verification.md` if scope clarity is a risk
- Use Penyemak when the proposal creates meaningful delivery or commercial commitments

6. Consolidate
- Update project memory if the proposal changes active priorities
- Write a decision file if proposal policy or scoping rules change future behavior

## Deliverables

- proposal brief
- scoped proposal or SOW draft
- assumptions and exclusions list
- verification summary and residual commercial risk