Request access

How it works

Six steps from a blank workspace to a returned questionnaire.

Parsing is code. Drafting is grounded in what was extracted. Approving is yours. Every step says which.

  • Deterministic code
  • Grounded drafting
  • You decide
  1. Step 1

    Create a workspace

    You decide

    One workspace per product you sell. Name it, and you can start on the buyer's questionnaire straight away — resilience details (services, recovery objectives, plans) are optional and can wait.

    • Free plan: one workspace, no card
    • Invite teammates as editors or viewers on paid plans
    • Optional resilience setup when you need it
  2. Step 2

    Add evidence

    Deterministic code

    Import a GitHub repository, upload files or a ZIP, or load the bundled sample evidence to see the loop end to end. Parsers read configs directly; secrets are redacted before anything is stored. The result is organised across 26 control areas.

    • Dockerfiles, Compose, Terraform, CI, manifests, schemas, policies
    • Config-only mode keeps application code out
    • Optional outside-in scan of your public endpoint
    • Dependency check against the OSV vulnerability database
  3. Step 3

    Import the buyer's questionnaire

    Deterministic code

    Upload the file they sent — CSV, Excel, Word, PDF, Markdown or text — or start from a built-in template. Questions are detected from the table, decorative title rows included, and the column mapping is kept so answers can be written back.

    • A parse report shows what was found and what was skipped
    • Add a missed question by hand in one click
    • AI-assisted parsing only when you ask for it
  4. Step 4

    Draft cited answers

    Grounded drafting

    Each question is matched to your evidence and drafted with the passages that support it — with an AI model when one is configured, from the evidence text alone when not. Quotes are checked against their files; an answer without a verified quote cannot be marked Supported.

    • Statuses: Supported, Partially, Unsupported, Unknown
    • Approved answers are reused across questionnaires
    • Contradictions with earlier answers are flagged
    • Answers built on changed evidence are marked stale
  5. Step 5

    Review and approve

    You decide

    Read each answer next to its citations, approve it as drafted or edit it first. Filter to what needs attention; every gap becomes a tracked item with a suggested fix.

    • Approve, or edit and approve
    • Filter by status and approval
    • Gaps go to the readiness register
    • Every approval is recorded
  6. Step 6

    Send it back, or publish

    You decide

    Return the buyer's own spreadsheet with approved answers written in place, export Word, Excel, CSV or a print-ready report, or publish a trust room with NDA or approval gating.

    • Only approved answers are exported
    • Trust room re-verifies on your plan's schedule
    • Signed trust.json and an MCP endpoint for buyers' tools
    • Buyer questionnaires sent from the room on paid plans

Walk the loop with sample evidence.

A new workspace can load eight sample files in one click and answer a template questionnaire in minutes.

Request access Try the live demo