Skill 1
RFP intake safety check
Use when RFP, RFI, questionnaire, attachment, or buyer-provided material needs classification before drafting or source matching.
Back to Skill Library
RFP response workflow library
RFP and RFI response
Triage questionnaire requests, map answers to approved sources, flag risk, and prepare review-ready responses.
This is a complete workflow library with 5 individual skills. Download the full library or pick the specific skill folder your team needs first.
Individual skills in this library
Use one skill at a time, or keep the full workflow together.
Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.
Skill 2
Question classifier
Use when RFP or RFI questions need category, sensitivity, ownership, confidence, and routing before answers are drafted.
Skill 3
Approved answer drafter
Use when an RFP or RFI response can be drafted from approved source material while preserving caveats and review status.
Skill 4
SME review packet
Use when blocked, sensitive, low-confidence, legal, security, privacy, or product-specific RFP questions need specialist review.
Skill 5
Submission QA
Use when an RFP or RFI response set is ready for final review against unsupported claims, missing approvals, sensitive details, and external-use readiness.
Security fit check
Is the public RFP and RFI response library enough, or does this need deeper review?
Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.
Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.
RFP responseSales EngineerPresalesSecurity Reviewer
Good deeper-review trigger signals
- The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
- Different teams disagree on the approved source of truth.
- The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
- You need reusable eval checks before asking more people to use the workflow.