RFP and tender response drafting

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. incoming_rfp_intake

   REQUIREDREADhuman

   Where the RFP document arrives and gets ingested into structured form.

   DATA SHAPE

   RFP document in any common format (PDF, Word, Excel, native portal). Pattern parses to a list of structured questions with metadata (section, required-or-not, format expected).
   COMMONLY FILLED BY

   • upload interface in the RFP tool
   • shared folder where the RFP team drops new RFPs
   • RFP portal that exposes questions via API
2. answer_library

   REQUIREDREAD + WRITEcorpus

   The structured library of approved answers, statements, and content blocks the pattern composes responses from.

   DATA SHAPE

   Q&A pairs and content blocks tagged by topic (security, compliance, product capability, references). Each answer has approval status, last-reviewed date, and source.
   COMMONLY FILLED BY

   • purpose-built RFP response tool with content library
   • structured wiki section maintained by RevOps and product marketing
   • spreadsheet with approved answers tagged by category
3. compliance_artifact_store

   REQUIREDREADcorpus

   Security certifications, insurance certificates, financial statements, references — the supporting documents commonly attached to RFP responses.

   DATA SHAPE

   Versioned documents with expiry dates and the questions they typically answer.
   COMMONLY FILLED BY

   • compliance artifact library inside an RFP tool
   • shared drive of certifications maintained by security/legal
   • data room with current security documentation
4. draft_response_destination

   REQUIREDWRITErequest

   Where the assembled response lands for human review, in the format the customer expects to receive.

   DATA SHAPE

   Completed response document with all answers filled, attachments referenced, ready for human walk-through.
   COMMONLY FILLED BY

   • Excel response file matching the customer's template
   • Word document with answers in the prescribed format
   • submission to the customer's RFP portal via API or import file
5. reviewer_approval_loop

   REQUIREDWRITEbatch

   Humans who review the drafted response before submission. RFP responses commit the firm contractually; AI doesn't get the final word.

   DATA SHAPE

   Per-question approval status with comments, edit suggestions, and final-approved version.
   COMMONLY FILLED BY

   • review workflow in the RFP tool
   • Google Doc or Word doc with track changes routed to reviewers
   • split-screen review UI built for the engagement
6. deal_context_lookup

   RECOMMENDEDREADrequest

   Information about the specific deal: customer name, industry, deal size, any prior interactions. Lets the response feel tailored rather than boilerplate.

   DATA SHAPE

   Deal record with customer details, prior touch history, and any deal-specific configurations.
   IF MISSING

   Responses are technically correct but feel generic. Win rates on competitive RFPs erode about 10-15% from missing the customer-specific framing.
   COMMONLY FILLED BY

   • CRM lookup by RFP issuer or deal owner
   • deal record linked to the RFP in the response tool
   • manual deal-context entry by the RFP team lead