Kyle Bruxvoort

things I've made

Fetch

A Revit plugin that puts manufacturer-accurate families one click away and keeps them synced to live product data.

  • Revit
  • C#
  • React
Open project

Revit MCP

Gives an AI agent the Revit Family Editor, so a product cut sheet becomes a family that flexes correctly.

  • MCP
  • Python
  • Revit API
Open project

Layout Studio

Space planning inside Revit. Import a room, lay out the seats, then place them in the model.

  • WebView2
  • TypeScript
  • Revit
Open project

Cipher

One record for SSG product data. Hundreds of manufacturers, one structure, read by Fetch and every tool after.

  • TypeScript
  • React
Open project

Fetch Analytics

Who uses Fetch, which families they download, and which searches come back with nothing.

  • Next.js
  • Docker
Open project

Fetchbim.com rebrand

Redesign of fetchbim.com. Identity, a component library, and the pages architects use to find Revit families.

  • Figma
  • React
  • Next.js
Open project

pySSG

pyRevit scripts that enforced our Revit content standard, later rebuilt in C# as the plugin the team uses now.

  • pyRevit
  • Python
  • C#
Open project

Content Creation Strategy

SSG's move to BIM. I wrote the content standard the library still runs on, covering naming, parameters and detail.

  • Revit
Open project

Japayuki

Cover and interior for a poetry collection, in print and ebook, where the layout has to hold the line breaks.

  • InDesign
  • Photoshop
Open project
KYLE BRUXVOORT
Director of Design Technology
RÉSUMÉ

Drag · throw · click to flip · 9 projects

2025Product lead

Cipher

TypeScriptReact

The problem. Product data arrived from hundreds of manufacturers in as many shapes. A spreadsheet here, a PDF price list there, images named by whoever exported them. Every tool we built solved that mess again from scratch.

What I built. Cipher is the one record. A product carries its images, its documents, its technical data, its variants and its price, and everything downstream reads from there instead of importing its own copy.

The hard call was variants. A product can be permuted a thousand ways, and modelling every permutation makes the data unusable. Only the axes that change the price count as a variant, so finish and colour are attributes of one product rather than products of their own. That rule is the difference between a catalogue a salesperson can quote from and a combinatorial explosion. I lead product here, which means scope, the data model, and what the team builds next.

FIGURES
One product record holds its images, documents, variants and combinations.