Files encrypted NDA standard Engineer review available before purchase order
Contact Fictivus

Bring the part question, not only the part file.

Use this page when a project needs a practical manufacturing conversation: quote scope, material comparison, DFM review, bridge production, or documentation planning. The fastest path is to describe what the part must prove, what deadline is real, and who needs to approve the result.

Before you send a note, gather the files and constraints that would help an engineer avoid assumptions. A STEP file is useful for geometry, a drawing is useful for tolerance and finish, and a short project note is useful for intent. If the part is only for a design review, say that. If it may become a recurring production item, say that too. Those details change the conversation around material, inspection, repeatability, packaging, and price.

Address

Manufacturing Desk

44 Additive Review Way
San Francisco, CA 94105
United States

Working hours

Engineering Review

Monday to Friday
8:30 AM to 6:00 PM Pacific
File checks continue across supplier time zones.

If the file package is sensitive, note NDA requirements in the message. If a drawing is not ready, send the CAD model and describe the critical surfaces or dimensions in plain language. We will help determine which missing details affect the quote and which can wait until after the first review. You can also flag buyer-side constraints such as approved materials, internal test dates, receiving requirements, or whether the quote needs to be shared with finance, quality, or program management.

Two-column quote form

Tell us what should happen after the prototype works.

That single detail changes the recommendation. A one-time fit model, a customer-facing sample, and a bridge production part may all start from the same CAD file, but they deserve different material, finish, inspection, and cost conversations. Use the message field to explain what happens if the part passes review, because that future state often determines whether the first build should optimize for speed, appearance, traceability, or repeatability.