Enterprise software people don't dread

Complex B2B and enterprise products — network automation, analytics, data-heavy consoles — designed to be genuinely usable. Deep, technical product design for tools that experts rely on all day.

Book a Strategy Call Book a Call

Worked with

Most of this work is under NDA, so the case studies are private. Happy to walk through it on a call.

What enterprise work needs

Enterprise UX isn't consumer polish on hard problems — it's information design, dense data made legible, and workflows that respect an expert's time. I've designed network-automation and analytics consoles used by infrastructure teams at scale.

Dense data and complex state made legible
Workflows designed for experts, not first-time users
Design plus production front-end, so it actually ships
Comfortable in deeply technical domains

How complex software gets usable

Enterprise UX isn't consumer polish on hard problems — it's information design done with discipline. Here's the approach.

Learn the real workflow

Sit with how experts actually work — the states, the exceptions, the muscle memory. You can't simplify a workflow you don't understand.

Make dense data legible

Hierarchy, typography, and restraint applied to screens full of data, so the signal an operator needs is the thing their eye lands on first.

Design for the expert, not the tour

Fast paths and keyboard-speed workflows for people who live in the tool all day — not first-run hand-holding that gets in their way by week two.

Ship the front-end

Design plus production code, so the console that got designed is the console that ships — dense state and all.

Related ways to work together

From $40,000

Complex Data Visualization

When the dataset is genuinely complex — graphs, time series, networks, geospatial, real-time — off-the-shelf charts give up. Custom, performant visualization a real person can read and act on, designed and engineered as one thing.

From $30,000

AI Feature Design Sprint

AI features die two ways: a demo that never ships, or a shipped thing nobody trusts. A focused sprint to design and build one AI feature into your product — the interaction, the prompts, the failure states, the eval — not a chatbot bolted to the corner.

On request

Product & Design Due Diligence

A senior, independent read on a product's design and engineering before you write the check or the board signs off. Is the product as good as the deck? Is the codebase a foundation or a liability? You get a clear answer, not a hedge.

Enterprise & B2B questions

What product and engineering leaders ask before bringing in design help.

Enterprise and infrastructure clients rarely allow public case studies. The work is real — network-automation and analytics consoles used at scale — and I'm happy to walk through it in detail on a call.

Yes. I've designed network-automation and analytics tools for infrastructure teams. Dense, technical, expert-facing software is the comfort zone, not the exception.

Yes — embedded in your repo, standups, and design system, or delivering production front-end that plugs into your stack. One point of contact, expert-to-expert.

Either. Design through to shipped front-end code is the default, because enterprise UX so often dies in the gap between the mockup and what engineering has time to build.

Have something in B2B & Enterprise?

One senior who designs the product and ships the code. Let's see if it's a fit.

Book a Strategy Call