Creative Noyes is the practice of Joe Noyes. 12 years of agency design experience, now focused on the intersection of AI, design infrastructure, and product development. Currently building Intent Studio, a conversational AI tool that authors design systems directly in Figma.
Solo practice · Waltham, MA · Available for contract and full-time roles
Three areas of focus, each grounded in work I can point to.
Designing products where the AI is the core experience, not a feature bolted on. Prompt architecture, orchestration pipelines, model routing, cost engineering.
Built a 5-pass AI orchestration engine with tiered model routing that reduced per-use cost by 80% while maintaining output quality.
The variable layer that holds products together. Token architecture, semantic naming, multi-mode support, framework detection, and the handoff workflows that connect design to code.
Authored a three-tier token hierarchy (primitives, semantics, component-level) with automated WCAG AA contrast pairing across light and dark modes.
Market analysis, competitive positioning, pricing architecture, GTM planning. The thinking that happens before the first pixel.
Identified an unoccupied $18-36M niche in the Figma plugin ecosystem through bottom-up market sizing and competitive analysis.
Intent Studio is a Figma plugin that transforms natural language into production-ready design systems. It generates complete token hierarchies, component libraries, and documentation through a multi-pass AI orchestration engine. The system uses tiered model routing to balance quality and cost, producing over 1,000 structured elements in a single session. Currently in private beta with seven framework seeds tested across Material, iOS, Ant, and custom systems.
I start every engagement in read-only mode. Before changing anything, I map the existing system, understand the constraints, and identify what is already working. Tightly scoped work prevents drift and keeps every deliverable tied to a clear outcome.
I think deterministic-first. AI is powerful where judgment and nuance matter. Structured systems are better where consistency matters. Not every problem needs a model, and knowing the difference is most of the job.
Product economics are a design constraint, not an afterthought. Cost per use, margin math, and pricing architecture shape the product just as much as the interface. I build with the business model in view from day one.
Solo founder experience means every feature I ship justifies itself against one question: does this help someone reach their “wow” moment faster?
Available for product design roles, design systems consulting, and AI product development.
See my full portfolio at josephnoyes.com →