IQV Gather

Requirements, gathered where your customers already are.

Ask each question once. Customers answer on the web, in Slack, or by replying to the email, and the answer lands on the question, with the documents and credentials the project needs, encrypted.

Sign in Connect an AI agent

One question, four ways to answer

A question is created by a developer, a product manager, or an AI agent. The person it is assigned to is notified over the channels you choose, and whichever one they reply on, the answer is recorded against the question.

Web

Customers sign in with their email and a one-time code. No password to forget, nothing to install.

Slack

The Gather bot sends the question as a direct message. Reply in the thread or use the answer form; reminders go out until it is answered.

Email

Each question is an email with a link. Replying to the email records the reply as the answer.

AI agents

Agents ask, assign, and read answers through the REST API or the built-in MCP server, with scoped keys and webhooks.

Built for agents as much as people

Give an agent an API key and it can run a discovery session on its own: ask structured questions, assign them to the right people, wait for answers, and read them back.

  1. Create a product and invite respondents by email.
  2. Ask questions in bulk, with types: text, yes/no, choice, number, date, or file.
  3. Respondents are notified on the web, Slack, and email.
  4. Read answers as they arrive, or subscribe to a webhook.
POST /api/v1/questions
Authorization: Bearer vg_…

{
  "product_id": "0192f…",
  "title": "Which SSO provider do you use?",
  "kind": "single_choice",
  "options": ["Okta", "Entra ID", "Other"],
  "assignees": { "emails": ["pat@customer.example"],
                 "channels": ["email", "slack"] }
}

Built to hold what customers hand you

Requirements come with architecture diagrams, contracts, and sometimes credentials. Gather treats all of it as sensitive by default.

Per-object encryption

Every uploaded document is sealed with its own key from AWS KMS before it reaches storage, and the storage layer encrypts it again.

A vault for credentials

Test accounts and API keys are stored the same way, revealed only to signed-in staff, and every reveal is written to the audit log.

Single sign-on for your team

Staff sign in through your identity provider. Customers never need an account password at all.