NoticeKit is primarily for the SaaS team receiving the AI security questionnaire, not the buyer sending it. Start with the AI deal blocker path first when one live thread is blocked, then use the builder, inventory, evidence map, AI agent review, or answer bank as needed. The free builder already gives you one answer block, a pasted-question response pack for up to 25 real spreadsheet or portal rows, CSV or TSV questionnaire upload, preserved row references, 20 reusable follow-up answers, a reviewer workspace export, an answer-bank draft, and an imported-row preview. Keep the subprocessor notice and partner paths secondary.
Pick the shortest path that matches the blocker in the live buyer thread. The point is to get you to the right artifact, not make you browse six pages.
Best when the buyer needs a copy-ready answer now and your team needs the proof prompts, reviewer handoff note, CSV or TSV questionnaire upload, pasted-question response pack, imported-row preview, 20 reusable follow-up answers, and repeat-review coverage in one local draft.
Use this when the deal is blocked earlier than the answer itself and you still need the providers, regions, owners, proof links, and review notes in one clean local file.
Best when the reviewer wants the vendor chain, framework mapping, approval owner, review date, and escalation path in one buyer-language packet instead of a shorter questionnaire answer.
Best when the same AI questions keep coming back and you need reusable wording, proof links, owner notes, segment variants, and the fuller repeat-review operating files.
Best when the buyer already has the paragraph and now wants proof assets, the named owner, review date, approval path, or framework-reference notes behind it.
Best when the buyer wants the exact tool list, mutating actions, approval gate, service-account scope, and audit trail instead of a generic AI answer.
Best when the reviewer already named OpenAI, Anthropic or Claude, customer-data training, proof gaps, tool access, or approval gates and you want the shortest matching page.
Open answer libraryBest when you want the same inventory, one-answer, and repeat-review split plus the route finder, worksheets, and supporting tools before choosing a paid path.
Open free toolsUse this when one live page, vendor setup, or segment-specific blocker still needs a blunt next-step read before you choose builder, packet, or audit.
Request teardownUse this when the questionnaire has already expanded into customer notice timing, objection windows, or evidence logging around a vendor change.
Open generatorFor consultants, fractional DPOs, and attorneys who want referral terms, client-delivery rights, or white-label boundaries after the core buyer path is clear.
Open partner previewNoticeKit keeps the public flow narrow: answer first, reusable file next, broader review pack when repetition is real, then secondary notice or partner paths only if the job expands.
Use when the buyer needs one credible answer first.
Use when the same AI review work keeps repeating.
Use when the review expands beyond the questionnaire into notice operations.
Use when your clients need the workflow and you need a cleaner delivery model.
Use the risk checklist if the vendor story itself is fuzzy. Use the due-diligence route when the buyer already wants vendor chain, framework notes, or approval-owner coverage. Use the evidence map if the paragraph exists but the proof trail does not. Use teardown if one live thread or page needs a blunt read. Use the self-audit when the work has clearly shifted into the older subprocessor notice workflow.
Use the AI procurement hub when the live thread already needs a fuller route chooser across builder, evidence map, template, example, answer bank, Pro kit, packet, sample, or teardown paths.
The sample teardown shows the exact 3-bullet async read, and the kit preview shows the paid artifact list without exposing the private files.