Chief Technology Officer
Kelly connects architecture, engineering, CAD production, BIM coordination, and delivery standards so project teams can move from concept drawings to coordinated construction documents with fewer gaps between disciplines.
Drawing systems, sheet logic, and QA controls for consistent deliverables.
Model review workflows that expose clashes before they become field issues.
Templates, data, and team routines that keep architecture and engineering aligned.
Kelly Trey’s career is a story told in stages: he began as a designer in the classic sense, with an eye for composition, clarity, and visual order, then deepened that craft inside engineering environments where design also means systems, constraints, and data. Today, as CTO, the canvas is broader: workflows, software, and how teams create coordinated buildings together.
Early on, Kelly trained the eye: grids, typography, hierarchy, and the patience to iterate. He treated every sheet set and presentation as a designed object because clarity for a client is itself a deliverable.
Multidisciplinary projects pushed him from styling outcomes to sequencing work: what must be true first for structure and MEP to stay coherent with architecture. In that stage, design became an interface between disciplines.
Kelly now works around systems design: standards, automation, model health, and the guardrails that let creatives and engineers work in parallel without drifting apart.
Software changes faster than culture. Kelly’s challenge is to introduce capability without chaos - so teams adopt better methods because they reduce friction, not because policy says so.
Kelly’s approach pairs empathy for how people actually work with a hard edge on standards where they matter most - interfaces between architecture, structure, and MEP.
These visuals present the type of drawing coordination, model review, and design communication Kelly helps organize for architecture and engineering teams.