Corpus features, step by step
11 how-to guides. Each says what the feature does, who uses it, how to try it in the live demo as Priya Ramesh, PE (Principal), and what a person still checks. Corpus answers from any document-heavy archive; the demo's worked example is a civil engineering firm. Demo data is fictional: the firm, Cedar Run Civil + Water, its people, and every record marked Fictional sample are made up. The rest of the archive is real public engineering documents, filed under the fictional firm's project names, and the RFQs are real public RFQs.
Find and check
Ask the archive and open the page behind each answer.
Cited answers from your archive
Ask a question about past projects. The answer cites the document and page, and the page opens with the passage highlighted. If the archive has no answer, it says Nothing on file.
Ask in plain words
Answers show their steps as they run. A Try asking sheet suggests questions, and a change you type in the chat comes with an Undo.
Win the work
From a new RFQ to a go/no-go, an SOQ, a fee and a draft contract.
Research and go/no-go on a new RFQ
Corpus researches a new RFQ from your past projects, then suggests scores for 6 of the 9 go/no-go criteria. Fit, relationship and capacity are your call.
SOQ draft from your past projects
The SOQ builder follows the RFQ's items in order, drafts the ones your archive can support with page citations, and leaves the rest for a person to write.
Staff records and a suggested team
Corpus suggests key staff for the SOQ from the roster and résumés, with reasons. A person accepts or edits each pick.
Fee build and principal approval
A fee built the way WSDOT M 27-50 Appendix AA prescribes, with the math done by code, each rate checked against GSA CALC+ benchmarks, and approval by the principal only.
Contract package from the approved fee
Once the principal approves the fee, Corpus fills WSDOT's Cost Plus Fixed Fee agreement from it, quotes the key clauses word for word, and exports a PDF marked as a draft.
Control and record
Who sees what, contract review, past results and every saved version.
Contract review against your playbook
A client's draft agreement is checked against your contract playbook: Hard, Soft, matches and what the playbook does not cover. A person reads every clause.
Bid results, competitors and win/loss
See who won each pursuit and at what price, read cited write-ups on competitors, and save the lesson from each loss.
History and versions
Past awards with each client, cited. Every save of the fee, SOQ and contract becomes a version you can compare and restore.
Roles: who sees what
The same archive, opened by different people at the firm. Restricted files are removed before search runs, and rates, contracts and HR records stay with the roles allowed to see them.
On your own archive
Set up for you Corpus is cloud-agnostic. It runs on AWS, Azure, Google Cloud, or your own servers.
Our commitment In the pilot, your files are never used to train or fine-tune a model. In full deployment, fine-tuning on your files happens only if you agree in writing.
New in October 2026: What's new in Corpus. How we handle your files: data handling.
Try it on your own documents
Start with a free 30-minute call. Then run the $5,000 pilot on one real project or pursuit, credited toward setup if you sign a deployment within 60 days of the pilot's end.