Clean up the facts
Use this when you cannot trust the vendor list, region list, owner list, or proof trail enough to draft the answer yet.
Open inventory workspaceNoticeKit works best when you match the artifact to the blocker. Use inventory when the facts are messy, the workbook template guide when the buyer already sent a sheet or portal export and you need to decide whether to stay in rows or move into the builder, the response-software guide when the team is shopping approved-answer workflow, the management-software guide when the conversation has shifted into broader administration, named-vendor or exact-match SIG / CAIQ / VSAQ routes when the reviewer already named the vendor or questionnaire family, due diligence when the buyer is already speaking procurement, Starter when one answer is blocking the deal, Pro when the same questions keep returning, and the AI deal blocker path when the thread needs judgment instead of another template. The spreadsheet route keeps the workbook template, CSV fallback, builder, and answer-bank branch visible before you buy. If you want the fuller route map after that, jump into the AI procurement hub from the chooser.
This chooser is for the company answering the questionnaire, not the buyer sending it. If you already know the route, go straight to checkout or the free tools hub.
Inventory first when vendor facts, owners, regions, or proof links are still scattered.
Workbook template when the buyer already sent rows or a portal export and you need the shortest branch into the workbook template, CSV fallback, the builder, or a reusable answer bank.
Due diligence when the buyer already wants vendor chain, framework mapping, approval owner, review date, or escalation path coverage.
Response software when the team is shopping approved answers, answer libraries, or a heavier response-management platform instead of solving one live answer first.
Management software when the conversation has shifted into workflow administration, approvals, assignments, or a broader managed program around the response queue.
Software fit scorecard when the team is still deciding whether the route is a lightweight NoticeKit workflow, response-software reuse, management software, or a broader platform shortlist.
Named-vendor or exact-match when the reviewer names OpenAI, Anthropic, Gemini, Claude, Copilot, SIG, CAIQ, or VSAQ and you want the shortest matching route.
Packet builder when the thread is already a full procurement packet and you need the claim, proof trail, owner path, and framework notes assembled together.
Starter when one live answer is blocking the deal and you need copy-ready wording now, especially if the buyer already sent spreadsheet rows or a questionnaire export.
Pro when the same review keeps coming back and you need reusable wording plus packet files.
Deal blocker when the blocker is proof, scope, or judgment and you want the shortest triage page before choosing free teardown or paid audit.
Pricing fit guide when Starter, Pro, and Audit are all plausible and you want the smallest paid step spelled out before checkout.
If the facts are messy, inventory first. If the buyer already sent spreadsheet rows or a portal export, use the workbook template guide first. If the team is shopping response software, use the response-software guide first. If the conversation has shifted into management software, use the management-software guide first. If the buyer wants vendor chain, framework notes, approval owner, or escalation path, use the due-diligence route. If one answer is blocking the deal, use Starter. If repeat review is the real job, use Pro. If the thread needs a human read before more work, use the deal blocker path.
Pick the blocker and the buyer language, and this page will surface the shortest route plus one backup path. It is faster than scanning the whole table when the thread is already live.
Use the table to move from the problem you have to the smallest NoticeKit route that solves it.
| If the blocker is... | Start with... | Why |
|---|---|---|
| Vendor facts, owners, or proof links are messy | Inventory workspace | It gives you a clean local fact base before you draft the answer. |
| The buyer already sent spreadsheet rows or a portal export | Workbook template guide | It keeps the downloadable template, builder, answer-bank, and software branches visible before you force spreadsheet-first traffic into a single workflow. |
| One live questionnaire answer is blocking the deal | Starter pack | It gets you a copy-ready answer block plus a handoff bundle for the first buyer thread. |
| The team is not sure whether the blocker is still a lightweight workflow or a real software purchase | Software fit scorecard | It scores whether you should stay with NoticeKit, move into response-software reuse, widen into management workflow, or evaluate a broader platform. |
| The buyer wants vendor chain, framework notes, approval owner, or escalation path | Due diligence template | It keeps buyer-language review work in a dedicated route instead of forcing it back into the older generic risk-checklist path. |
| The team is shopping response software or approved-answer workflow | Response software guide | It separates one blocked answer from answer-library, SME-review, and heavier platform decisions before you overbuy. |
| The conversation has shifted into management software, workflow administration, or broader queue ownership | Management software guide | It separates reusable answer cleanup from assignments, approvals, and bigger program-management decisions before you formalize churn. |
| The reviewer named a vendor or model family, or wants exact-match SIG / CAIQ / VSAQ wording | Answer library or SIG guide | It keeps the vendor-specific template, example, answer bank, or exact-match route one click away instead of falling back to a generic AI paragraph. |
| The same review keeps coming back | Answer bank or Pro kit | It keeps reusable wording in one file and steps up to matrix and packet support when repeat review is already bigger than a free answer bank. |
| The thread needs judgment, proof prioritization, or a safer next move | Deal blocker path | It keeps the triage choice in front of you so you can pick free teardown or paid audit without restarting the thread. |
Use this when you cannot trust the vendor list, region list, owner list, or proof trail enough to draft the answer yet.
Open inventory workspaceUse this when the buyer needs one direct answer now and your team needs the fastest clean handoff behind it, including spreadsheet or portal-row import if the questionnaire already exists.
Open Starter packUse this when the buyer already sent a sheet, CSV, TSV, or portal export and you want the spreadsheet-first guide to keep the downloadable template plus the builder and repeat-review branches visible before you pick a workflow.
Use this when the blocker has shifted into vendor chain, framework notes, owner metadata, customer scope, or escalation path instead of only one questionnaire paragraph.
Use this when the debate has shifted into approved answers, answer libraries, SME review, or response-management software and you need the startup-fit branch before buying a larger system.
Open response software guideUse this when the conversation has shifted into management software, assignments, approvals, or operating the queue and you need the startup-fit branch before buying a bigger system.
Open management software guideUse this when the review keeps recurring and you need reusable wording now, then move to Pro kit if matrix and packet files are part of the job.
Use this when the blocker is not writing, but deciding what to fix first, what proof to add, or whether a bigger packet is warranted.
Open deal blocker pathOpen pricing to compare the paid paths, use free tools if you want to inspect the bundle shape before you buy, or open the broader AI procurement hub if you want the full browseable pack after the branch is clear.