How the customer's files become an RFQ package
Every RFQ you receive becomes a package that holds the drawings, models, spreadsheets and emails your customer sent. Each file is hashed on arrival, given a role and kept for good, so the quote is always built against exactly what came in.
What happens to each file when it arrives
27 file types
PDF prints, STEP, IGES, Parasolid, SAT, DXF, DWG, native SolidWorks files, STL meshes, ZIP archives, Excel and CSV parts lists, images, Word documents and Outlook emails. Up to 384 MB a file.
A hash on every file
Each file is content-hashed on arrival. Send the same drawing twice and the package says "seen before" instead of storing a second copy, and every archive member remembers where it came from.
A role on every file
Files are filed automatically as drawing, model, specification, purchase order, parts list, archive or source email. An estimator can re-declare any of them in a click.
ZIP archives are unpacked on arrival
Archives explode on arrival with zip-bomb limits and traversal guards. Withdraw the archive and its members follow; restore it and they come back.
A scan state the whole product obeys
Where a scanner is deployed, a held file cannot be downloaded, previewed, read by the AI, measured or turned into a quote line until it is clean. A flagged file is refused everywhere.
Broken files are flagged on the row
Zero-byte, flagged, scan-failed and no-preview files show a glyph on the row, and the quote line carries a thumbnail with a problem badge so nothing broken hides in a long list.
How a package becomes the first quote lines
An estimator creates the package, or the customer submits one
An estimator creates the package (the number is created for them), or the customer submits it through your public request form and gets an acknowledgment.
Files are hashed, filed and scanned before anyone opens them
Hashes, roles, lineage and scan state are written before anyone opens anything. Emails added as files become dated entries on the package timeline.
The product writes a brief of what arrived
A deterministic brief says what arrived, what is covered and what is missing, and proposes the bill of material. One click adds an AI narrative over it.
Drawings, models and the parts list become quote lines
Drawings, models and the customer's parts list become quote lines, pre-ticked and editable, quantities carried, part numbers reconciled against the title block.
Common questions
How does an RFQ get in? Does someone have to key each one?
Three ways. An estimator creates the package and drops the files in; your customer submits through a public request form on a link you control (name, company, email, notes, files); or the customer's email is added to the package as a file and its text lands on the package timeline.
What file types can I upload?
PDF, STEP and STP, IGES, Parasolid, SAT, DXF, DWG, SolidWorks part, assembly and drawing files, STL, ZIP, Excel and CSV, plain text, PNG, JPG and TIFF, Word, and Outlook .msg and .eml email files. Per file the limit is 384 MB; a request can carry 700 MB.
Do you scan uploads for viruses?
Where a scanner is deployed for your instance, yes. A new upload is held until it comes back clean, and a flagged file can never be opened, previewed, read by the AI, measured or turned into a quote line. Without a scanner the file is marked "not scanned".
What if someone uploads the wrong file?
It is withdrawn with a reason, not deleted, and can be restored. The quote stays a record of what it was quoted against.
See it on one of your own RFQs
Send us a drawing and a model you have already quoted and we will walk through it with you in the product, in your rates. If you would rather look first, the interactive demo is open, with no form in front of it.