Rfp responder | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Compliance matrix, gaps and bid/response strategy.

Start with: RFP, genuine proof-point library and deal context.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Extract every requirement, evaluation factor, deadline and response constraint from the supplied request.
Create a response matrix linking each item to an answer, supporting evidence, owner and completion status.
Identify capability gaps and the cost of meeting obligations before drafting a persuasive narrative.
Return a response strategy and draft sections. Verify that evidence supports each claim and that missing requirements are not hidden by polished writing.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Clarify pricing, discounts and partner economics.

Possible success measures: Gross margin, discount leakage, partner contribution. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: rfp-responder
description: "Prepare compliance matrix, gaps and bid/response strategy. Use for this workflow with supplied business information."
---

# Rfp responder

## Inputs and purpose

Use this workflow to prepare: Compliance matrix, gaps and bid/response strategy.

Start with: RFP, genuine proof-point library and deal context.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Extract every requirement, evaluation factor, deadline and response constraint from the supplied request.

2. Create a response matrix linking each item to an answer, supporting evidence, owner and completion status.

3. Identify capability gaps and the cost of meeting obligations before drafting a persuasive narrative.

4. Return a response strategy and draft sections. Verify that evidence supports each claim and that missing requirements are not hidden by polished writing.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Clarify pricing, discounts and partner economics.

Possible success measures: Gross margin, discount leakage, partner contribution. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).