proposal-rfp-orchestrator

name	proposal-rfp-orchestrator
description	Orchestrate proposal and RFP response work across owners, deadlines, compliance, and review cycles. Use when asked to coordinate an RFP response, build a proposal workplan, map requirements to owners, or run structured proposal reviews. For single-meeting briefing needs, use executive-briefing-builder or account-brief-builder.

Proposal RFP Orchestrator

Create a controlled response process that keeps the team compliant, on time, and focused on the buyer's evaluation criteria.

Confirm Inputs First

Collect the minimum required inputs:

• Whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• Request type (proposal, RFP, or both)
• Submission deadline and mandatory milestones
• Buyer requirements and evaluation criteria
• Available contributors and owners
• Approved content sources and reusable answer libraries
• Known differentiators, risks, and constraints

If critical inputs are missing, ask for the smallest missing set. If speed is required, proceed with labeled assumptions.

Read The Right Reference

• For compliance matrix, review gates, and role definitions, read references/proposal-governance-framework.md.

Default Workflow

1. Decide bid/no-bid and response scope. Confirm fit, required effort, and whether the team should respond at all.

2. Build the requirement matrix. List every requirement, where it is answered, who owns it, and what proof supports it.

3. Assign section owners and source inputs. Set the writer, SME, approver, and source of truth for each section.

4. Shape the response strategy. Define the main buyer problems, win themes, proof points, and any gaps that need escalation.

5. Run structured reviews. Use a draft review, challenge review, and final proofing pass with clear gates.

6. Finalize the submission package. Check compliance, formatting, approvals, and delivery instructions before sending.

Tool Notes

• Docs/Office suites are useful for collaborative drafting and version control.
• Project tools are useful for owner tracking and deadline management.
• Knowledge bases are useful for reusable approved content blocks.

Keep workflow tool-agnostic when these systems are unavailable.

Output Contract

Deliver:

1. Response strategy summary
2. Requirement matrix
3. Section owner plan and timeline
4. Win-theme and proof-point map
5. Approved-content source map and reuse rules
6. Review plan with gates and owners
7. Submission readiness checklist
8. Open questions and assumptions

Quality Bar

• Every requirement is answered once and owned by someone specific.
• The response uses buyer language, not internal jargon.
• Proof points are current and tied to approved sources.
• Review buffers are built in before the deadline.
• Unsupported claims, missing compliance items, and stale content are removed.
• Do not fabricate qualifications, certifications, references, or customer outcomes.