InfuseOS Logo
Resources /

InfuseOS Workflow Stack #9: The RFP / Security Questionnaire Engine

Gmail → Drive → Docs → Web → Gmail → Calendar (reply fast, stay accurate, close deals) Nothing kills B2B momentum like the “can you fill out this questionnaire?” email.

Published

Gmail → Drive → Docs → Web → Gmail → Calendar (reply fast, stay accurate, close deals)

Nothing kills B2B momentum like the “can you fill out this questionnaire?” email.

It’s always the same failure mode:

  • the request lands in Gmail
  • someone hunts for last quarter’s answers
  • a doc gets duplicated 6 times
  • details drift, contradictions creep in
  • the response goes out late (or sloppy)
  • nobody schedules the follow-up, so the deal stalls

This stack turns an incoming RFP/security questionnaire into a complete, consistent response package—drafted in a canonical Google Doc, backed by the latest Drive assets, and shipped via Gmail with a follow-up meeting already queued.

What you get (every run)

  • A Drive folder for the deal: Deal Room / [Company] / [YYYY-MM-DD]
  • A Google Doc response: “RFP Response — [Company]”
    • structured sections
    • copied/updated answers from your “canonical” library
    • gaps flagged clearly (what needs human input)
  • A Gmail reply ready to send (or sent) with the doc link
  • A Calendar follow-up (so the request actually converts into a call)

Workflow playbooks (single prompts, multi-tool execution)

1) “Incoming questionnaire → response doc → reply email”

Find the latest email thread from [Company] requesting a security questionnaire or RFP. Extract exactly what they’re asking for and list required deliverables. Search Drive for our most recent “Security Questionnaire”, “SOC 2”, “Privacy Policy”, and any past RFP responses. Create a Drive folder “Deal Room/[Company]/[YYYY-MM-DD]” and copy/link the relevant files into it. Create a Google Doc titled “RFP Response — [Company]” with sections: Overview, Security, Privacy, Data Handling, Integrations, Support, Pricing (if needed), Open Questions. Draft answers using our latest existing docs and clearly flag anything that needs my input. Then draft a reply email to the thread including the Doc link and the 3 questions we need answered to finalize. Show me the email before sending.

2) “Speed mode: answer from our canon, keep it consistent”

Search Drive for our canonical responses (“Security Questionnaire Master”, “Privacy & Data Handling”, “Terms”, “Pricing”). Create a Google Doc response for [Company] and ensure phrasing is consistent across sections (no contradictions). If you find conflicting answers in older docs, pick the newest and note the conflict in a short “Review Needed” section. Then prepare a Gmail reply with the response doc link.

3) “Web verify + tighten claims (no fluff, no risk)”

For the RFP response to [Company], use web search to confirm any public facts we reference (integrations list, plan names, public pricing, support promises). Update the Google Doc to only include verifiable claims. Add a short “Assumptions” section for anything that depends on their environment. Then draft the final Gmail response.

4) “Close the loop: send response + book the next step”

After preparing the RFP response doc for [Company], propose 3 meeting times next week for a 30-minute security/RFP review. Include those options in the Gmail reply. If they accept one, create the calendar event titled “[Company] — RFP Review” and include the response Doc link in the event description.

The master prompt (copy/paste)

Run the RFP / Security Questionnaire Engine for [Company]. Pull the latest Gmail thread, extract requirements, and search Drive for the newest relevant assets (security questionnaire, privacy, terms, pricing, past responses). Create a Drive folder “Deal Room/[Company]/[YYYY-MM-DD]”. Create a Google Doc “RFP Response — [Company]” with complete drafted answers sourced from our latest docs; flag missing info as “Open Questions”. Use web search to verify any public claims and keep language precise. Then draft a Gmail reply including the doc link + 3 proposed next-step meeting times. Show me the email before sending.

Mini prompt library (still cross-tool, outcome-based)

  • “Make a deal room”
Create a Deal Room folder for [Company], find all relevant Drive assets, and generate a response doc with links.
  • “Answer fast, but safe”
Draft answers only using the newest canonical docs; flag anything uncertain instead of guessing.
  • “Ship + schedule”
Send the response and propose 3 times for a review call; once chosen, book the calendar event and attach the doc link.