How security questionnaire credits work

What a credit is, and why we use them

A credit is one unit of completed work, not a per-question or per-hour charge. When a buyer sends you a security questionnaire, completing it costs one credit. That holds true no matter how the questionnaire is delivered or how long it is. A short vendor intake form and a 200-question portal both count as a single credit. You can see the full workflow on the how it works page.

We price this way for two reasons. First, it keeps your costs predictable. You can read most incoming reviews and estimate the credit cost up front, and if anything would add a credit we flag it before doing the work, so you avoid surprise invoices in the middle of a deal. Second, it keeps your team in control. Every answer we draft is evidence-backed and routed to you for approval, so the credit pays for the work of building customer-approved responses, not for handing your security posture to a black box.

Credits do not expire mid-task. A credit covers a work item from the first draft through the buyer-approved submission, including the back-and-forth that a normal review involves.

What counts toward a credit

Here is the full credit model. Each row is a work item and what it costs. This is the core reference for the page, so bookmark it and check any incoming request against it.

Two items add a credit on top of the questionnaire itself: a buyer security call and a rush turnaround. Everything in the Included rows comes at no extra charge.

What is included at no extra credit

Several of the most common requests do not consume an extra credit. Knowing this keeps you from over-budgeting a single deal. The following are included as part of completing a review:

• Submitting through a spreadsheet or a web portal. The format the buyer uses does not change the count.
• A small follow-up request from the buyer tied to a questionnaire you already completed.
• A lightweight policy or document draft that supports the review, such as a short access control summary.

These are part of supporting a review, not separate work items. If a follow-up grows into a brand-new questionnaire or a full policy build, that becomes its own credit, and we will flag it before any work starts.

Worked examples

The model is easiest to read through real scenarios. Here is how items add up, step by step.

1. 01

   A 150-question web portal review plus one buyer security call = 2 credits

   The questionnaire is 1 credit regardless of its 150 questions or the portal format, since portal submission is included. The buyer then asks for a live call with their security team, which adds 1 credit. Total: 2 credits.
2. 02

   A 40-question spreadsheet with a rush deadline = 2 credits

   The questionnaire is 1 credit, and the spreadsheet format is included. The buyer needs it back ahead of normal sequencing, so the rush turnaround adds 1 credit. Total: 2 credits.
3. 03

   One questionnaire with a rush deadline, a buyer call, and a small follow-up = 3 credits

   The questionnaire is 1 credit. The rush adds 1 credit and the buyer security call adds 1 credit. The small follow-up that arrives a few days later is included, so it adds nothing. Total: 3 credits.

The pattern holds across every deal: start at 1 credit for the questionnaire, add a credit for a buyer call, add a credit for a rush, and treat submissions, small follow-ups, and lightweight drafts as included.

How credits map to each plan

Each Vouchway plan bundles credits differently. Use this table to match your expected volume to the right capacity. One note before you read it: a single review can cost more than one credit when it includes a buyer call or a rush, so the credit total is what to budget against, not the raw count of questionnaires. You can compare every plan and what it includes on the pricing page.

The 24 credits on the Starter Pack and the 60 on the Annual Trust Desk cover questionnaires plus any add-ons such as buyer calls and rushes, not that many separate questionnaires. The Security Review Sprint is the right starting point for a single urgent questionnaire with full onboarding. The Enterprise Security Review Starter Pack fits a steady flow of enterprise deals, and its rollover gives you room for uneven months. The Annual Trust Desk suits teams running five reviews a month.

How to estimate the credits you need

To pick the right plan, forecast realistic monthly demand rather than guessing. Work through these steps with your sales pipeline in hand.

1. 01

   Count expected enterprise deals per month

   Look at your pipeline and count how many deals will likely trigger a security questionnaire in a typical month. Each questionnaire is a baseline of 1 credit.
2. 02

   Add likely buyer security calls

   Estimate how many of those deals will want a live call with their security team. Add 1 credit for each expected call on top of the questionnaire.
3. 03

   Account for rush requests

   Enterprise deadlines move. Estimate how many reviews will need a rush turnaround in a given month and add 1 credit for each.
4. 04

   Match the total to a plan

   Add the credits together for a realistic month, remembering that a review with a buyer call or rush costs more than 1 credit, then multiply across the year and compare to the plan totals: 24 credits a year on the Starter Pack or 60 on the Annual Trust Desk. Those credit pools cover questionnaires plus add-ons, so budget against the credit total rather than the questionnaire count. If you have one urgent review and no recurring flow yet, start with a one-time Security Review Sprint.

If your volume sits between plans, the Starter Pack rollover absorbs lighter months, so you rarely need to overbuy. When deal flow climbs past two reviews a month consistently, moving up to the Annual Trust Desk is the cleaner fit.