Sales & Onboarding

Answer RFPs and security questionnaires faster

Draft questionnaire answers from your compliance docs.

The pain

Every enterprise deal brings a 300-question security questionnaire, and answering it steals a week from security and sales engineering. Most answers were already written for the last questionnaire — but nobody can find them.

How Kelu solves it

Index your security docs, policies, and previously answered questionnaires as a restricted internal knowledge base. Your team asks each question through the Ask assistant and gets a drafted, cited answer to review — turning a week of archaeology into a day of review, with SSO and audit logs keeping the sensitive corpus governed.

How it works

  1. 1

    Upload security docs, policies, and past questionnaires (PDF/MD) into a restricted internal knowledge base.

  2. 2

    Governance applies: restricted visibility, SSO, and audit logs for the sensitive corpus.

  3. 3

    For each questionnaire item, your team asks the Ask assistant and gets a drafted, cited answer.

  4. 4

    Reviewers verify against the cited source and finalize — review, not archaeology.

What you get

  • Turn a week of questionnaire archaeology into a day of review.
  • Reuse every answer you have ever written, findably.
  • Keep the compliance corpus governed with SSO, restrictions, and audit logs.
  • Answer consistently across questionnaires instead of re-deriving each time.

Features that make it work

Restricted documentsInternal Ask assistantFile upload sources (PDF/MD)SSO & audit logs

Got questions?

Frequently asked questions

How do we get past questionnaires into the system?

Upload them directly as file sources (PDF, Markdown, TXT, HTML) alongside crawled policy pages. They are indexed into a restricted internal knowledge base only your team can query.

Is this safe for sensitive compliance material?

The corpus lives in a restricted knowledge base: document-level visibility, per-knowledge-base chat permissions, OIDC/SAML SSO, and the workspace activity log govern who can access it, and conversation history records what was asked.

Does the AI answer the questionnaire for us?

It drafts — with citations to the policy or previous answer it drew from — and your security team reviews and finalizes. The human stays accountable for every submitted answer.

How long does setup take?

Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and Kelu crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack bot installs in a few clicks. There is no model to fine-tune and no infrastructure to run.

Are answers backed by citations?

Yes. Every answer from your docs includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.

Is my content used to train AI models?

No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, a widget without Kelu branding, and a custom SLA.

Which knowledge sources can I connect?

24 source types: websites, GitHub (docs files, source code, issues, pull requests, discussions), Notion, Confluence, Google Drive, OneDrive, Zendesk (Help Center and solved tickets), Jira, Jira Service Management, Linear, Salesforce Knowledge articles, Salesforce Cases, Discourse, Stack Overflow for Teams, YouTube, OpenAPI specs, S3, curated Q&A, and direct file uploads (PDF, DOCX, XLSX, CSV, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub sources can re-index automatically via webhook on every push.

What happens when the AI is not confident in an answer?

Answers are grounded in your sources. When they do not cover a question, Kelu returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.

Ready to answer RFPs and security questionnaires faster?

Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.

Free to start · No credit card required