Overview
Nomad is a digital platform that helps engineering teams source machining services faster and with fewer back-and-forth emails. The goal is to connect the “engineering intent” (part requirements, drawings, tolerances, materials) with the “manufacturing reality” (capabilities, lead-times, pricing, and quality constraints).
What I worked on
- Product flow: RFQ → requirements → supplier matching → quoting → order tracking
- Engineering-first UX: make it easy to specify what matters (material, finish, tolerance-critical notes) without overwhelming the user
- Operational tooling: internal views to review requests, manage suppliers, and keep the pipeline moving
Key features
- RFQ creation & management
- Upload part files and capture manufacturing requirements in a structured way
- Iterate on requirements without losing context
- Supplier & quote workflow
- Route requests to the right suppliers based on capability/availability
- Track quote status and provide a single place to compare options
- Order visibility
- Centralized status tracking so engineers know what’s happening and when
- Quality & repeatability
- Store key constraints/notes per part so repeat orders are quicker and more consistent
Tech stack (high level)
- Frontend: Next.js + TypeScript + Tailwind CSS
- Backend/API: Node.js (service/API layer)
- Data: MongoDB
Learnings
- Engineering tooling lives and dies by clarity: the UI has to reduce ambiguity, not add it.
- The hardest part isn’t a single feature — it’s building a workflow that supports many edge cases while staying fast for the common case.