Procurement drafts the same kinds of RFIs over and over: ocean freight, SaaS, IT hardware, professional services. Each one takes weeks to write, then another round with legal, finance, and ops who end up rewriting half of it. With a reusable section template and a library of clauses your team already trusts, the draft you send to review is 80% complete. Stakeholders approve. They don't redo procurement's work.
No account · Saved locally · Powered by Claude
Recap of the pieces in the diagram above. Each gets its own deeper section below.
AI is not a one-shot draft generator bolted onto the end. It is present at every step where a procurement person would want help: extracting clauses out of prior RFIs, proposing blocks for a new outline, scaffolding a brand-new category, rewriting a section in your tone, suggesting vendor questions to add or revise.
Drop a prior RFI, vendor questionnaire, or stakeholder memo. Claude pulls out the reusable clauses and the individual vendor questions, lands them as Proposed blocks awaiting review.
Surfaces the right blocks for the right outline based on tags, content, and prior usage. New Proposed candidates show up where they fit.
When you spin up a new outline (e.g. “Sustainability & ESG”), Claude proposes which existing blocks belong in it based on its tags and your library.
Type the category name. Drop a few prior RFIs or skip. Claude builds the section template, extracts blocks, and assembles outlines in 30 seconds. You edit from there.
AI Rewrite regenerates a section in your tone, with an instruction box and side-by-side diff. AI Propose adds, revises, or deletes vendor questions, each change reviewable.
The block library is cross-category. A SOC 2 clause your team has approved gets attached wherever security applies. Every new category you build inherits the work you've already done.
Vendor must maintain a current SOC 2 Type II attestation, refreshed within the last 12 months …
Every block carries an explicit trust tier so your team always knows what's been reviewed. Sources land as Proposed by default; Approved blocks have been reviewed by the category team; Fundamental blocks are universal across categories and signed off at the org level (legal, finance, compliance).
SOC 2 Type II, GDPR data residency, NDA, force majeure, common payment terms. The clauses your legal and finance teams have already approved for use anywhere. Auto-attach by topic match across every category.
Promoted from Approved only after explicit corporate sign-off.
Category-specific clauses your team has reviewed and signed off on (e.g. IMDG hazmat compliance for ocean freight, cyber liability minimum for SaaS). Trusted in their scope; not yet broad enough to be Fundamental.
Promoted from Proposed after the category team confirms the language.
Default landing tier for AI-extracted blocks (from your uploaded sources) and for any directly-authored block that hasn't been reviewed yet. Visible, usable, but flagged so your team knows it hasn't been blessed.
Promote to Approved (team) or Fundamental (corp) when ready.
Outlines are reusable section templates. Compliance & Certifications, Service Requirements, Evaluation Methodology: every RFI has these, and they're nearly identical across categories. Define once; let your categories adopt them.
The outline holds the defaults. Each category adopts the outline and can add or remove blocks for itself, without touching the master. Edit the outline and every category that uses it sees the change immediately.
When you create a draft and export it, you get the paired packet that vendors actually receive. An RFI Guide they read, and a Vendor Questionnaire they fill in. Each comes from a different kind of block in your category.
The packet vendors read.
The workbook vendors fill in and return.
The Ocean Freight category is pre-seeded. Open it, scroll the workbench, regenerate a section, export the questionnaire. Or build your own category in 30 seconds.