About

Why I am building this

A technical founder, a principle about evidence, and design partners who answer questionnaires every month.

Where this comes from

I came to this product from video, e-commerce and data work, not from presales or security. What I kept seeing from that side was the same pattern: a questionnaire arrives with a deadline, the people who know the answers are busy, and the response is assembled from old documents by someone who cannot check every line. It is slow, and sometimes it is wrong in ways nobody notices until a buyer does.

The tools that promised to fix this mostly produced fluent text. Fluent text is the problem. A confident paragraph with no source behind it is harder to catch than a blank cell.

Evidence first, as a rule in code

So the product has one principle and it is enforced in the pipeline, not suggested in a prompt. An answer is drafted only from passages retrieved from your own library, it must cite the passages it used, and if it cannot, the pipeline rejects it and marks the question No evidence found with a note about which document would answer it.

That rule costs something. The platform will leave questions blank that a chat assistant would have filled in. I think that is the right trade for a document that goes to a buyer with your company's name on it.

How I am building it

The application runs on Vercel, with Google Cloud behind it: Firebase Authentication for sign in, Firestore for the database and Cloud Storage for the files, every query scoped to one organization on the server. The evidence pipeline reads each page, keeps page numbers on every passage, retrieves with keyword and vector search over one index per organization, and drafts from retrieved passages only.

Everything on this site is rendered by the product's own components. The examples are labelled as illustrative samples until a design partner's anonymized content replaces them with written permission. When there is no evidence for a claim on this site, the claim is not here.

Design partners

I am building with two or three design partners who answer questionnaires every month: a presales lead, a security manager or a bid manager who lives the problem. They supply real documents and a real questionnaire under NDA, and their feedback sets the roadmap.

Design partners are named on this site only with their permission. If you answer RFPs, security questionnaires or DDQs on a recurring basis and want to shape the product, the contact page has a partnerships option.

Become a design partner

Bring ten documents and one real questionnaire under NDA. We index them, draft every answer with evidence, review the result together and fix what breaks. Your questionnaires are answered first and your feedback sets the roadmap.

Start your response library