RFQ quality control
Know what's wrong
before you quote.
Upload the drawings, BOM, specs and customer email. Missing requirements, conflicting values and revision problems are found before they reach your estimator.
A real finding from the messy-package sample, in the report's own layout. Both statements stay visible and neither is picked — a value only reaches a report when it can be found verbatim in the file it is cited to.
AI extracts
It may only claim a value it can quote back, verbatim, from the segment it was read in. Anything it cannot cite does not exist.
Software checks
Missing fields, conflicting values and superseded revisions are found by ordinary TypeScript. The model does not get a vote on what is wrong.
You decide
What governs, what gets quoted and whether the job is worth taking at all stay with the estimator.
None of it is a judgement about whether to quote. That is yours, and it is the reason the report shows its work instead of handing you an answer.
See what it catches
The same part, quoted at two different quantities in two files that arrived in the same package. Neither value is treated as the answer — both sources stay visible, and the report will not pick one for you.
Source → RFQ-7712-email.txt · line 13
BOM-7712.xlsx · sheet Parts, row 2
The package carries conflicting revisions and does not say which governs.
Source → RFQ-3390-email.txt · line 15
BR-3301-RevC.pdf · page 1
Reported as absent, never guessed from the drawing sitting next to it.
Source → GR-8801.pdf · "MATERIAL: NOT SPECIFIED ON THIS SHEET"
Every finding has a source.
BOM-5502.xlsx · sheet Parts · row 2
500 pcs ≠ 250 pcs
The email says 500 and the BOM says 250. Both are shown. You decide which one governs.
No value is inferred and nothing is merged. A value reaches the report only when the quoted text appears verbatim in the segment it is cited to — otherwise the field shows a dash.
How it works
Upload
Drop in the RFQ package, or paste the customer's email straight in.
Extract
Requirements are pulled out of each file, each with a citation.
Cross-check
Conflicts, revision mismatches and missing fields are compared.
Review
Every finding points back to the line it came from.
The extraction contract and every check behind these steps are written out on how it works.
What it checks
Six ways a package goes wrong
Every one of these is a rule in the published list — published rather than hidden, so you can read what gets checked before you trust a report.
Missing information
Requirements that are referenced but never actually defined.
Conflicting information
The same field stated two different ways in two different files.
Revision mismatch
Drawings, the BOM and the email disagreeing about which revision governs.
Ambiguity
Wording that can honestly be read two ways and cannot be checked from the package.
Attachment problems
Unreadable files, empty exports, duplicates, and supporting material that is simply absent.
Part-level issues
Findings scoped to the part they affect, rather than condemning the whole package.
Want to see it in action?
Five fictional packages, each built around one real failure mode. Open the report any of them produces — nothing is charged and no signup is needed.
Your RFQs stay private.
Uploaded files are read once and deleted from storage as soon as the report is built — on failure as well as success. The report itself expires, and you can delete it from its own page at any time.
Priced per package.
5packages a month, free — every check, every export
then
$9per package, with no seats and no annual contract
No card is collected anywhere on this site, and everything stays free while the service is in preview. See the pricing detail.
Ready to check your next RFQ?
It will not quote, will not price, will not tell you whether to bid, and will not read a CAD solid. It checks the package in front of you and shows you where the problems are. No signup.