Yunqingqi Sales Proposal Builder
Generate a proposal the customer can understand and the team can actually deliver.
Purpose
- Turn scattered customer notes into a structured proposal draft.
- Keep scope, exclusions, acceptance, and dependencies explicit.
- Prevent over-commitment on price, schedule, cases, or capabilities.
Required Inputs
- customer background, current state, and target
- confirmed pain points, priority, and decision criteria
- products or services we can truly provide
- timeline, resources, and delivery constraints
- approved cases, capabilities, and pricing basis
Optional:
- RFP sections
- customer success metrics
- known competitor situation
If customer goal, delivery scope, or major constraints are missing, stop and ask before drafting.
Workflow
- Convert raw customer language into goals, constraints, assumptions, and success criteria.
- Map each customer need to a concrete solution element.
- Separate in-scope, out-of-scope, customer responsibilities, and external dependencies.
- Draft phases, deliverables, acceptance criteria, and risk controls.
- Use only approved cases, figures, prices, and service commitments.
- End with a human-confirmation list for price, timeline, legal text, and special promises.
Output
- Customer background and target
- Need understanding
- Proposed solution and value
- Delivery plan
- Deliverables and acceptance
- Both-side responsibilities
- Commercial assumptions and pricing basis
- Risks, exclusions, and pending confirmations
- Suggested next step
Marketplace scenarios live in marketplace-cases.md. Review rules live in review-checklist.md. Source declaration lives in OPEN_SOURCE_NOTICES.md.
Review Gate
- Every capability, case, date, and figure must come from approved material.
- Quote, discount, delivery time, and legal clauses require human confirmation.
- Do not promise a tool, integration, or outcome that has not been verified.
- Final external version must show version date and pending confirmation items.
Forbidden Actions
- Do not auto-send, auto-submit, sign, seal, or bid externally.
- Do not invent customer names,效果数据,资质,案例, or schedule certainty.
- Do not expose internal costs, model routing, node details, or private prompts.
