RFP Response Manager

By General Input

Turn a fresh RFP into a draft response package in hours. Reuses approved answers from your docs and chats, then tracks every gap.

Integrations

  • Google Drive
  • Notion
  • Microsoft SharePoint
  • Slack
  • Microsoft Teams

Type

Agentic Task

Categories

  • Sales
  • Operations

Build me an agent workflow that helps me respond to RFPs, security questionnaires, and proposal requests. I will start the workflow whenever I get a new one, attaching or pasting the RFP document, questionnaire, or proposal request as the kickoff input.

Step 1: Parse the RFP I provide. Extract every section, question, requirement, deadline, deliverable, attachment, and submission rule. Build a structured response plan with section owners as placeholders, due dates, and a flagged-risks list.

Step 2: Find prior answers and owner context across whichever of these sources I have connected. Treat each as optional and use what is available:

Google Drive: search the folders I designate as my proposal/answer library by listing files with Drive query syntax, then download the content of any hits that look relevant.

Notion: search pages by title across the spaces I share with the integration, then retrieve page content as markdown to pull approved answers and boilerplate.

Microsoft SharePoint: search drive items in the sites I point you at and download matching files for context.

Slack (use the per-user Slack integration, not the deprecated slack-bot): list the channels I designate, pull channel history and thread replies, and follow conversations to surface prior discussions, decisions, and likely subject-matter owners.

Microsoft Teams: list channels and channel messages for the teams I designate, plus list chat messages for the group chats that handle proposal work.

Step 3: Draft first-pass answers grounded in those sources. Every answer must include a citation back to the file, page, or message it came from. When two sources conflict, surface the conflict and pick the most recent approved version. Never invent content I cannot back up.

Step 4: Build a gap tracker. Any question without a high-confidence source goes here, with a suggested owner inferred from past Slack or Teams activity and document authorship, a priority based on RFP weighting or risk, and a draft request I can forward to the owner.

Step 5: Produce a single review package. Default to creating a Notion page that contains the response plan, the draft answers with citations, the gap tracker, the owner ping list, and a submission checklist with risks. If Notion is not connected, create a Google Doc in Drive instead with the same structure.

Step 6: Only after I confirm, send Slack direct messages or Microsoft Teams chat messages to the suggested owners with their specific gaps and a deadline. Do not message anyone without my explicit go-ahead.

Style rules: be conservative on anything not backed by a source, prefer citing and summarizing over rewriting, and match my company voice from prior approved proposals when examples are available. Keep the gap tracker honest: it is better to flag a missing answer than to bluff.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionScreen chartered vessels for AIS gaps and sanctions red flags