No. It prepares the register, matrix, deviation table, draft response and question lists. Your bid manager reviews, engineers answer the open items, commercial fills the cost column, and your team submits.
The line is marked Needs engineer with the closest evidence found and a specific closed question. The agent never writes Comply without a document behind it.
It recognises standard references (with edition) and matches them against your certificates and declarations. It reads the standard's own text only if you upload it to the library; it does not interpret standards from memory.
Any supplier answering technical tenders with specifications and data sheets: valves, pumps, compressors, electrical equipment, instrumentation, HVAC, structural steel, process packages, rolling stock components. The product is specification-driven, not sector-specific.
Commercial-technical requirements (warranty, spares, training, documentation) are extracted and matched to standard terms. Pricing, legal terms and contract conditions are outside scope; the deviation table leaves cost impact for commercial.
They stay in your tenant on Google Cloud, are used only for your bids, and are never used to train models. See the DPA and sub-processor list.
Indexed per revision; the offered revision is pinned per tender and every evidence citation carries it.
For structure and phrasing, yes. For evidence, no: a past Comply is verified against current documents before reuse, and unsupported past claims are listed rather than copied.
Validity dates are tracked. Citations of certificates expiring within the tender's validity period are flagged with renewal status.
Title blocks and notes on GA drawings are indexed. It does not interpret geometry.
Tender packages as PDF or DOCX (scanned PDFs OCR'd); data sheets as PDF/XLSX; library documents as PDF, DOCX, XLSX; exports as DOCX, XLSX, PDF.
One Tender covers a package up to 300 pages; each additional 150 pages is +0.3. Multi-lot packages add 0.3 per additional lot's data sheets. Re-runs within 60 days — addenda, engineer answers, clarification rounds — are free.
Not required. Upload the package; export the outputs. API access (packages in, matrix and draft out) is available on Enterprise.
One tender package analysed end to end: register, matrix, deviation table, draft response, engineer question list, clarification questions, with revisions free for 60 days.
Separately at the provider's list price, model_access_usd on your invoice. Reading a 300-page package and a few thousand pages of library is token-heavy; the ledger shows tokens per tender. With your own key the meter is zero.
The charge lands on your existing Google Cloud invoice and counts toward committed spend. Private offers for annual plans; direct invoicing from Carnegie Intelligent Technology Limited (Hong Kong) is available.
Monthly tender cap and model-spend cap per workspace; at the cap new tenders queue and the owner is notified.
The product is being built with a small number of equipment suppliers using their real tender packages and documentation. You get a workspace, direct access to the team and pricing locked at today's rates for the first year. Some capabilities on this site describe designed behaviour not yet live.
Upload one product range's datasheets, certificates and ITPs plus two past responses; the library indexes the same day. The first live tender produces a register and coarse matrix within hours of upload.
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.