Constraints:
- Always use precise, factual language.
- No unverifiable claims.
- Keep reading level at grade 9–10.
- Use headings and short paragraphs.
- Use the client's industry terminology where appropriate.
- If information is missing, state assumptions explicitly and mark them as assumptions.
Inputs:
- ClientName: {{ClientName}}
- Industry: {{Industry}}
- NeedSummary: {{NeedSummary}}
- Tier: {{Tier}}
- Price: {{Price}}
- Deadline: {{Deadline}}
- ReferenceLinks: {{ReferenceLinks}}
Task: Draft a proposal with these sections:
1) Executive Summary (3–4 paragraphs)
2) Scope of Work (bulleted deliverables tailored to Tier)
3) Timeline (phases with weeks)
4) Investment (reference Price with brief justification and optional add-ons)
5) Assumptions & Dependencies (clear bullets)
6) Next Steps (call to action before Deadline)
Formatting:
- Start with a title: "Proposal for {{ClientName}}"
- Use H2/H3 headings
- Output plain markdown (no images)
- Include a short FAQ at the end (3 Q&A)

Constraints: No hype. Show outcomes and proof points. Grade 9–10 reading level.
Inputs: {{ClientName}}, {{Industry}}, {{UseCase}}, {{Tier}}, {{Price}}, {{Deadline}}, {{KeyRisks}}
Sections: Executive Summary, Business Outcomes, Solution Overview, Scope, Timeline, Pricing, Assumptions, Risks & Mitigations, Next Steps.
Formatting: Markdown with H2/H3, short paragraphs, tables where helpful.

Constraints: Non-binding draft, highlight clauses needing legal review. No legal advice.
Inputs: {{Parties}}, {{Term}}, {{PaymentTerms}}, {{SLA}}, {{IP}}, {{Liability}}, {{GoverningLaw}}.
Sections: Definitions, Services, Fees, IP, Confidentiality, Data Protection, Warranties, Indemnity, Limitation of Liability, Term & Termination, Governing Law, Schedule Templates.
Formatting: Numbered clauses, placeholders for exhibits.

Constraints: Align with MSA; flag any conflicts.
Inputs: {{ProjectName}}, {{Objectives}}, {{Deliverables}}, {{Milestones}}, {{AcceptanceCriteria}}, {{Team}}, {{Dependencies}}, {{ChangeControl}}.
Sections: Project Overview, Detailed Deliverables, Schedule, Roles & Responsibilities, Acceptance Criteria, Assumptions, Out of Scope, Change Control, Pricing, Invoicing.

Constraints: Avoid gendered language. List must-have vs nice-to-have.
Inputs: {{Title}}, {{Team}}, {{Location}}, {{Level}}, {{TechStack}}, {{Outcomes}}, {{CompRange}}.
Sections: About the Role, Day-to-Day, What You’ll Achieve, Must-Haves, Nice-to-Haves, How We Hire, Benefits.

Constraints: No proprietary data unless provided. Cite metrics and source.
Inputs: {{Customer}}, {{Industry}}, {{Problem}}, {{Solution}}, {{Results}}, {{Quote}}.
Sections: Snapshot (table), Challenge, Approach, Results (metrics), Customer Quote, Why It Worked, Call to Action.

- Do not include personal data beyond provided inputs.
- If asked for medical, legal, or financial advice, add: "Consult a qualified professional."
- Cite any external stats with the provided ReferenceLinks only; otherwise omit.

Style: Clear, structured, professional; grade 9–10; moderate persuasion, high specificity.
Governance: No claims without provided sources; mark assumptions; redact PII beyond inputs.
Inputs:
- ClientName: {{ClientName}}
<a7>- Industry: {{Industry}}</a6>
- NeedSummary: {{NeedSummary}}
- Tier: {{Tier}}
- Price: {{Price}}
- Deadline: {{Deadline}}
- ReferenceLinks: {{ReferenceLinks}}
Task: Produce a proposal with these sections: Executive Summary, Solution Overview, Scope of Work, Timeline, Pricing, Assumptions, Risks & Mitigations, Next Steps.
Formatting: Markdown; H2/H3; bullets; 900–1,100 words; end with a 5-bullet key takeaway list.
--- Example ---
[Short example showing structure, 2–3 paragraphs per section, realistic tone]

1) MARKDOWN_BODY: main narrative
2) JSON_SUMMARY: {
"client": "{{ClientName}}",
"tier": "{{Tier}}",
"price": "{{Price}}",
"deadline": "{{Deadline}}",
"keyDeliverables": ["..."],
"risks": ["..."],
"nextSteps": ["..."]
}