
The design language, still going
Building a Brand That Lasts
When I joined Marxent it had four employees, an office in Beaver Creek, Ohio, and a budding sales location in St Petersburg. When I left the company (now 3D Cloud), it had offices in Ohio, Florida, and London and a client list that included Joybird, Macy's, and many more.
I was there for a whole decade. I built three separate identity systems, produced the brand's entire content output largely by hand, and eventually arrived (through years of iteration) at a visual language clean enough to show the work on its own. The logo, the device mockup library, and the overall video approach are still in use today.
Step 1
Four People and a Blank Page

Early brand system documentation – establishing the basics
The first identity system had one job: establish that Marxent was a real company with internal logic. That's not a glamorous brief, but it's the honest one. At four employees you're not positioning against competitors; you're proving to the world and to yourselves that you exist.
Everything was hand-built. Brand documentation, marketing materials, the website: there was no team to delegate to and no budget for agencies. What came out of that period was a foundation scrappy enough to survive rapid growth and structured enough to build onto.
Step 2
The Content Machine

Marketing site iteration – mid-era, brand at scale
Branded motion graphics — animation presets built for the content pipeline
The InReality Podcast
The InReality Podcast — three seasons on AR, VR, and the future of spatial commerce
By the middle years, the brand had real output to manage. A video series covering interior design, product visualization, and 3D modeling education. The InReality podcast, which ran three full seasons. Trade show presence at SXSW, CES, and the furniture industry's flagship conference, plus a circuit of smaller events designed to build thought leadership.
The website was redesigned repeatedly: each iteration a response to where the company was positioning itself, each one produced with the same small team.
The discipline was building repeatable systems that could sustain that volume. If the brand only worked when I was personally producing every asset, it wasn't a brand; it was a style. The goal was something that could run.
Step 3
Stripping Away Artifice
Rocket Mortgage creative brief — the visual language applied to a prospecting pitch
The 3D Cloud rebrand was the result of years of iteration with CEO Beck Besecker: someone with exacting standards for his marketing materials and a clear instinct for what wasn't working. Through each revision, something kept getting removed. Complexity, decoration, context. Eventually what remained was the work itself.
The visual language we arrived at was clean isolated 3D device mockups (laptops, phones, tablets produced in-house) with visualization experiences composited directly into them. No lifestyle photography. No graphic treatment. Just the product, rendered beautifully, doing what it does.
It was the right answer because it let the technology speak. When your product is 3D visualization, the most compelling marketing is showing 3D visualization at e-commerce scale.
Step 4
The Design Language That Outlasted

The visual approach, still running
3D motion graphics — the overview piece
A design language is only truly finished when someone else can pick it up and keep going without you.
The logo hasn't changed. The device mockup library is still in use. The approach for video assets (the visual logic of how the product is shown) is the same one running on the current 3D Cloud site. Other team members continued producing brand work I never oversaw, and it cohered.
The true measure of corporate design work is how much of it is still around when you look back later.
Key Takeaways
- A brand built for where you're going, not where you are, is the only kind worth building
- Stripping away artifice is harder than adding to it; it takes years of iteration and a willingness to keep asking what else can be removed
- A design language is only finished when someone else can run it without you
- At small scale, doing everything by hand isn't inefficiency; it's how you learn what the system actually needs to be
Software & Skills
- Adobe Creative Suite · InVision · Sketch
- Brand identity systems · Content pipeline design · Video production · Podcast production · Trade show & exhibit design · SEO · Web design · 3D asset direction