OctiAI

Categories

RFP Response Mapper — Draft production-ready RFP responses from fragmented inputs

A single-domain prompt pack (Markdown) that converts messy RFP fragments and internal notes into a complete, auditable RFP response package for ops leads, PMs, founders and peop...

What You'll Get

How to Use

Tip — Prioritize evidence and deadlines

Before generating, upload or reference any certificates, SOWs, case studies, security docs, and your pricing model. The prompt will not invent evidence—missing docs become explicit actions. Also set the submission deadline and desired tone so narrative answers and the action plan align to timelines.

Works Best With

Use this prompt pack when you must convert messy RFPs and notes into a compliant, auditable submission quickly

Prompt Template


## Goal
- Map fragmented RFP text and internal notes to company capabilities and produce a production-ready draft RFP response that includes: requirements mapping, matched answers, proposed attachments, identified gaps and exceptions, required clarifications, risk register, decisions, action items with owners and due dates, and recommended next steps.

## Inputs
- Provide the following when you paste this prompt (fragments are acceptable):
  - RFP text fragments or transcript of RFP questions
  - Internal capability notes, product/service facts, and evidence (certifications, case studies, SOWs)
  - Constraints and compliance requirements (legal, security, regulatory)
  - Pricing model or guidance (if available)
  - Any existing draft answers or boilerplate
  - Deadline for RFP submission and preferred tone (concise, formal, sales-forward)
  - Point of contact for clarifications
- If any of the above are missing, the assistant must ask explicit clarifying questions before producing the final response.

## Prompt
You are an expert business-ops writer and RFP responder. Using the RFP fragments and internal notes provided, produce a complete, stakeholder-ready RFP response package and an internal action plan. Follow these precise steps and output exactly the requested sections and formats in Markdown.

1. Quick intake check (respond only if inputs missing)
   - If any required input from the Inputs section is not present, list the missing inputs and ask one concise clarifying question per missing item. Wait for answers before proceeding.

2. Executive summary (one paragraph, 3-4 sentences)
   - Summarize fit: top 3 strengths vs. RFP, one primary gap (if any), recommended bid posture (Full compliance / Conditional with exceptions / Decline).

3. Requirements mapping table (Markdown table)
   - For every RFP requirement or question, produce one table row with these columns:
     - Requirement ID: use RFP numbering or a short generated ID (R1, R2…).
     - Requirement text: verbatim short excerpt (<= 150 chars).
     - Company match: concise statement of how we meet it (cite internal note label or evidence).
     - Proposed answer (final text to paste into RFP): complete, submission-ready paragraph (<= 200 words).
     - Evidence / Attachment: filename or reference to supporting doc we will attach.
     - Gap / Exception: explicit statement if requirement is unmet or partially met.
     - Assumption & Confidence: list any assumption made and a confidence level (High/Medium/Low).
   - Ensure the table is complete and sorted by RFP order.

4. Narrative responses
   - Convert longer RFP narrative questions into finished draft answers. For each: include a short header with the RFP question identifier, then the answer in final-form prose. Use bullets for lists and bold any commitments (SLA numbers, dates, prices). Do not invent certifications—only state certifications if evidence was provided and cite the evidence.

5. Proposed attachments and mapping
   - Provide a bulleted list of all supporting attachments to submit (proposal cover, SOW, security docs, certifications, pricing sheet, case studies). For each, state:
     - Filename to attach
     - Which requirement(s) it supports
     - Short preparation notes (e.g., “redact client names”, “update date”).

6. Exceptions log and compliant alternatives
   - List any contractual, compliance, or capability exceptions we must declare. For each exception:
     - Requirement ID
     - Text of the exception we will propose (legal-ready phrasing, one sentence)
     - Alternative offering or mitigation (if available)
     - Impact on eligibility (Acceptable / May reduce score / Disqualifying)

7. Clarifying questions for the issuer
   - Produce a numbered list of exact, concise clarification questions to send to the RFP issuer. For each question include:
     - Which RFP clause it refers to
     - Why the clarification is needed (1-2 sentences)
     - Suggested acceptable responses or options we expect.

8. Pricing and commercial notes
   - If pricing guidance provided, produce a short priced summary and any pricing assumptions. If none provided, list the exact pricing inputs required to produce a compliant commercial response.
   - Highlight any terms that require negotiation (payment terms, liability caps, renewal pricing).

9. Risk register (top 5 risks)
   - Bullet the top five proposal risks with: Risk statement, Likelihood (High/Medium/Low), Impact (High/Medium/Low), Mitigation action.

10. Decisions & Actions (ready-to-assign table)
    - Produce an action table (Markdown table) with columns: Action item, Owner (role or name), Due date (ISO or relative days), Status (Not started/In progress/Blocked), Priority.
    - Include at least the following actions: finalize narrative answers, prepare attachments, legal review, pricing finalization, clarification submission, submission QA and sign-off.

11. Ready-to-send section outputs
    - a) “Submission packet” header: list exactly what to upload and in what order.
    - b) “Stakeholder summary” (3 bullets): what reviewers must approve and by when.
    - c) Provide a one-paragraph ready-to-send email to attach to the RFP submission (formal tone) and a second, short internal Slack message to request sign-offs.

12. Final checks and sign-off criteria
    - Provide a checklist of mandatory verification steps before submitting (e.g., confirm attachments, confirm signatures, confirm SLAs numbers match SOW). If any check cannot be satisfied with current inputs, mark which and why.

Formatting and behavior rules (enforce these):
- Output must be in Markdown and use clear headings for each numbered step above.
- Use Markdown tables for all tabular data. Keep tables readable (wrap long text into concise sentences).
- Separate facts vs assumptions explicitly at the end of each mapping row and in a dedicated "Assumptions" list near the end.
- Do not invent facts or certifications. If an evidence item is not provided, mark it as a gap and assign required action.
- For any ambiguous RFP language, present two answer options: Conservative (compliance-first) and Competitive (value-first), and recommend which to use with rationale.
- Provide confidence levels (High/Medium/Low) for each major claim.
- Keep final draft answers concise and submission-ready; avoid internal commentary inside the submission text.
- If an RFP question asks for attachments not present, do not fabricate; instead create a clear action to produce or request the attachment.

If you have all required inputs, proceed through steps 2-12 and produce the full package. If inputs are incomplete, stop after step 1 and list the missing items with one-line clarifying questions.

## Output Format
- Executive summary (1 paragraph)
- Requirements mapping table (columns: Requirement ID | Requirement text | Company match | Proposed answer | Evidence / Attachment | Gap / Exception | Assumption & Confidence)
- Narrative responses (by RFP question)
- Proposed attachments and mapping (bulleted list)
- Exceptions log (table or bullets)
- Clarifying questions for issuer (numbered list)
- Pricing and commercial notes (bulleted summary)
- Risk register (top 5 risks, bullets)
- Decisions & Actions table (Action | Owner | Due date | Status | Priority)
- Submission packet and stakeholder summary (bulleted)
- Ready-to-send external email and internal Slack message (separate blocks)
- Final checks and sign-off checklist
- Assumptions list and source citations (end of document)

## Guardrails
- Separate facts vs assumptions in every mapping row and in the Assumptions section.
- Mark confidence High/Medium/Low for all claims; cite internal note labels or filenames when available.
- Do not state any certification, compliance, or legal claim without a supporting document reference. If a claim lacks support, mark as Gap and create an action to obtain evidence.
- All proposed contractual exceptions must be phrased as negotiable alternatives and flagged for legal review.
- Do not modify user-provided verbatim RFP text except to truncate for table readability; always include the original excerpt in the mapping row.
- Keep answers submission-ready: no internal brackets, questions, or TODOs inside the proposed answer text.
- If conflicting internal notes exist, list both then recommend which to use with rationale and confidence.

## Examples
- Mini decisions/actions excerpt:
  - Decision: Submit with Conditional Exceptions for Data Residency (Legal to propose alternative clause).  
  - Action: Draft exception clause for Data Residency — Owner: Legal Counsel — Due: 3 days — Priority: High
  - Action: Obtain ISO 27001 certificate copy — Owner: Security Ops — Due: 2 days — Priority: High

Variables

Usage Notes

Not for

Do not include

RFP Response Mapper — Draft production-ready RFP responses from fragmented inputs

Map fragmented RFP text and internal capability notes into a fully structured, submission-ready RFP response with requirements mapping, narrative answers, attachments, exceptions, clarifying questions, risk register, and an action-ready plan.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

No placeholders required for this prompt.

Rules

Canonical Examples

Input: RFP fragments for Managed Backup & Disaster Recovery: Q1: Describe backup architecture and retention; Q2: Data residency: EU-only; Q3: SLA: 99.9% availability; Q4: Provide security certifications; Q5: Pricing model: per-GB monthly + setup fee. Internal notes: product_backup_platform.md, case_study_acme.pdf, SOC2_Attestation.pdf, SOW_draft_backup.docx. Constraints: GDPR, AES-256 at-rest encryption required, customer key management optional. Pricing guidance: $0.03/GB/month, $10,000 one-time setup. Deadline: 2026-03-15. Point of contact: rfp-ops@company.example. Preferred tone: concise, formal, sales-forward.

Loading result...

Failed to load output.


Executive summary: Top strengths: SOC 2 attestation, mature backup architecture, existing EU hosting. Primary gap: ISO 27001 certificate not provided. Bid posture: Conditional with exceptions.

Requirements mapping (sample row): R1 | Describe backup architecture... | Matches: agent-based incremental + object-store replication (product_backup_platform.md) | Proposed answer: ... | Evidence: case_study_acme.pdf, SOW_draft_backup.docx | Gap: ISO 27001 missing | Assumption & Confidence: Assumes EU-region can be provisioned; Confidence: Medium.

Why it works: This example includes all required inputs (RFP fragments, internal evidence, compliance constraints, pricing, deadline, POC), enabling the prompt to execute full steps 2-12 and produce a complete, submission-ready RFP package with mappings, attachments, exceptions, clarifying questions, pricing, risks, and an action plan. It demonstrates handling of partial evidence (SOC2 present, ISO absent) and producing conservative vs competitive answer options.

Input: RFP fragments for HRIS implementation: RFP questions about deployment model, payroll integrations, and support SLAs. Internal notes: hris_product_onepager.md (product features), sales_notes.txt (high-level client wins). Missing: compliance/regulatory constraints, pricing model, deadline, point of contact, and any audit/certification documents.

Loading result...

Failed to load output.


Quick intake check: Missing items: compliance requirements, pricing model, submission deadline, POC contact, certifications. Clarifying questions: 1) Please provide required compliance frameworks (e.g., SOC2, GDPR) — is SOC2 mandatory? 2) Provide pricing model or guidance — per-user vs fixed implementation? ...

Why it works: This example demonstrates the prompt's intake-check behavior: when critical inputs are missing, the assistant stops after step 1 and asks concise clarifying questions. It shows precise, one-line questions per missing input — which is exactly what the prompt requires before proceeding.

Works Best With

Use this prompt pack when you must convert messy RFPs and notes into a compliant, auditable submission quickly