Adam is a CAD copilot for hardware teams that connects to CAD, PLM, supplier, and collaboration tools for model edits, BOMs, drawings, and RFQs.

Adam

What Adam is

Adam is a CAD copilot for hardware teams. The site describes it as an AI workspace built for hardware work, with built-in skills for CAD, research, sourcing, and engineering documentation.

It connects to tools such as Onshape, Autodesk Fusion, SolidWorks, Arena, supplier catalogs, Google Drive, Jira, Linear, Notion, Airtable, Slack, and Gmail, then reads geometry, BOMs, drawings, and revisions in real time. The intended workflow is to let teams request work in familiar channels and receive finished outputs such as model edits, reconciled BOMs, updated drawings, render sets, RFQs, and factory handoff materials.

The homepage examples focus on practical hardware tasks: preparing design review briefs, comparing suppliers, cleaning up BOMs, creating ECO packets, drafting RFQs, tracking build blockers, finding component alternates, and packaging a manufacturer handoff. The pricing page shows a free tier and paid plans for more usage and higher limits, but it does not present the product as a generic chat tool; it is centered on hardware engineering workflows.

Core capabilities

Connects to the hardware stack

Connects to CAD, PLM, supplier catalogs, and adjacent tools so Adam can work from geometry, BOMs, drawings, and revisions in a connected graph.

Works from existing communication tools

Takes prompts from Slack or email and carries out tasks such as fixing geometry, building BOMs, or drafting RFQs without requiring a new workspace.

Produces finished engineering outputs

Returns specific deliverables including branched model edits, reconciled BOMs, updated drawings, render sets, and drafted RFQs.

Covers recurring hardware operations

Supports common hardware workflows such as design reviews, supplier comparison, ECO packets, component alternates, build blocker tracking, and factory handoff preparation.

Combines engineering and sourcing tasks

Positions itself as a workspace for CAD, research, sourcing, and engineering documentation, rather than only a text assistant.

Common ways teams use Adam

  • Prepare design review material

    Pull build notes, open issues, and CAD screenshots into a brief for an upcoming design review so the team has a single summary to work from.

  • Clean up a BOM

    Review assemblies for missing manufacturer part numbers, duplicate parts, long-lead items, and release mismatches before sending a BOM downstream.

  • Find component or supplier alternatives

    Search supplier catalogs for drop-in or pin-compatible alternatives, then compare cost drivers, lead times, and supply-chain tradeoffs.

  • Prepare change-control and sourcing documents

    Turn revision notes and affected parts into an ECO packet, or draft an RFQ with tolerances, finish, quantity breaks, and target delivery.

  • Package a factory handoff

    Collect drawings, BOMs, QA checklists, and open questions into a manufacturer handoff folder when a build is ready to move to production.

Pros and Cons

Pros

  • Connects directly to the hardware stack instead of requiring exported copies or a separate workspace.
  • Supports a broad mix of hardware tasks, from CAD edits to sourcing and documentation.
  • Produces concrete deliverables that can be reviewed, adjusted, or sent onward to other tools.
  • Offers multiple entry points for use, including Slack and email.
  • Includes a free tier and paid plans for scaling usage.

Cons

  • The site does not publish a detailed feature-by-feature technical specification, so some capabilities are only shown through examples.
  • The pricing page shows plan tiers and credits, but the rendered text available here is truncated before all plan details are fully visible.
  • The service terms say the product is provided as is and as available, which is a normal but important limitation.

FAQ

What tools does Adam connect to?

Adam is set up for hardware teams that work across CAD, PLM, supplier catalogs, and communication tools. The source explicitly mentions Onshape, Autodesk Fusion, SolidWorks, Arena, McMaster-Carr, Digi-Key, Xometry, Google Drive, Jira, Linear, Notion, Airtable, Slack, and Gmail, with support for 3,000+ integrations.

Is Adam meant for individual or team workflows?

The product pages show Adam as a team-oriented CAD copilot that can handle work across CAD, BOMs, sourcing, renders, and documentation. The pricing page also includes plans that mention shared folders, custom models, persistent memory, multimodal generation, and use in Slack and email.

What kind of output does Adam produce?

Adam returns finished work such as branched model edits, reconciled BOMs, updated drawings, render sets, drafted RFQs, and manufacturer handoff folders. The examples on the home page show those outputs linked back to their source material.

Are there any workflow limitations or boundaries stated on the site?

The product is positioned around connected work rather than file export workflows. The home page says Adam reads geometry, BOMs, drawings, and revisions in real time with no exported copies, and the terms of service note the service is provided as is.

Quick Facts

Category
CAD copilot
Primary users
Hardware teams
Source domain
adam.new
Core workflow
Connected CAD, BOM, sourcing, and documentation tasks
Communication surfaces
Slack and email
Pricing shape
Free tier plus paid plans