Your Questionnaire
Counted in your browser, priced before anyone calls
The file does not leave your browser for this quote.
Refused:
No questions found in
The page looked for rows ending in a question mark; rows starting with a question ID, such as A&A-01.1 in a CAIQ, HFIH-01 in a HECVAT or A.1 in a SIG; and columns headed Question, Control, Requirement or Criteria. None matched.
If this is the questionnaire, the desk counts it by hand: [[CONTACT EMAIL NEEDED]].
Offline. The count still runs, because it never needed the network. Paying waits for the connection.
Work Order
No. 23486bff
Sample: a CAIQ-shaped file we wrote, counted on . Drop your own to price it.
Price and date back: $5905 business days
Box 9 is five business days from the day you pay and send your documents, Monday to Friday. Public holidays are not in the calendar.
Receipt 23486bfffd285afdf0c274b792ac09ee5e835df2d2d2c8364316576ab41e0fd2, named by the SHA-256 of its own contents.
Your Answer Bank
Every answer and its evidence, as files you keep
A security questionnaire is the spreadsheet or document a customer's security team sends before they sign, asking how you protect their data. The desk answers it in your own file and hands you the answer bank beside it: every question, the answer drafted, and the document each answer cites, as a CSV and a Markdown file. The next prospect who asks the same thing gets an answer you already own, from a file no platform holds behind a login.
Your Friday
Five business days from your documents to our draft
The clock starts once you have paid and sent your evidence: your own policies and reports, such as an information security policy, a SOC 2 or ISO 27001 report, or a pen test letter. Five business days later the draft comes back, every answer read against the document it cites and initialled by the person who reviewed it. A draft is only as good as those documents. A vendor with none gets a shorter questionnaire back and a list of what to write first.
Does my file leave the browser?
Not for the quote. The page opens the file in this tab with your browser's own decompression and counts it there. When you pay, the server receives the receipt: the file's SHA-256, its row and question counts, the framework and the tier. The file itself reaches the desk only after payment, through the upload step on your order page.
What if the count is wrong?
The count is a rule, and rules miss. A four-word section heading can count as a question, and a question written as a statement, with no ID and no question column, can be missed. The desk recounts at intake. If the recount lands in the other tier, you hear before any work starts: a lower tier is refunded the difference, and a higher one is yours to pay or to cancel for a full refund.
What about more than 400 questions?
The page does not sell it. Over 400 questions, the desk quotes by email, [[CONTACT EMAIL NEEDED]], and the price comes back as a number with a date beside it.