Three stages. The middle one is where the language model lives — and it is metered openly.
The tender package (PDF/DOCX — specifications, data sheets to be filled, standards references), your product datasheets, test certificates and manuals, and two or three past technical responses for voice and structure.
Extracts every numbered requirement, classifies it (performance, material, standard, documentation, commercial-technical), searches your documentation for evidence, decides Comply / Partial / Deviate / Needs engineer, and drafts the response paragraph with the supporting reference.
Compliance matrix (clause, requirement, status, evidence link), deviation table in the buyer's required format, draft technical response document, and an engineer question list sorted by impact — exportable to DOCX and XLSX.
| Clause | Requirement | Status | Evidence |
|---|---|---|---|
| 4.2.1 | Body material ASTM A216 WCB | Comply | Datasheet DS-V300 p.2 |
| 4.2.4 | Fire-safe to API 607 | Comply | Cert. FS-2025-118 |
| 4.3.2 | 150 bar at 120 °C | Partial | Rated at 100 °C — deviation D-03 |
| 5.1.1 | Hydrostatic test per API 598 | Comply | ITP-V300 §6 |
| 6.4 | ISO 15848-1 class B packing | Needs engineer | Class C certified — Q-07 |
| 7.2 | Documentation in buyer's EDMS format | Comply | Past bid PB-2025-022 §7 |
Illustrative output.
A single tender is 200–600 pages read against thousands of pages of your own documentation, then re-read as engineers answer questions. One bid is typically 30–80 million tokens; a team answering four tenders a month runs 100–300 million. Requirement extraction and matrix assembly are deterministic; the model is spent on reading and drafting.
We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.