Access code

This case study requires a six-digit access code. If you do not have one, contact me and ask.

Currently: Shaping how brands launch loyalty & gamification experiences in a headless future at Open Loyalty.

I design thesoftware that runsprocurement.

Enterprise SaaS and data-dense operational platforms. The harder the domain, the better the fit.

Selected work

The domains in question.

All work, including earlier projects

How I work

My value is the span: product strategy at one end, shipped interface detail at the other, and the domain model holding the two together. These are the principles that keep that range honest.

  1. Domain before interface

    The best outcomes get set up early, in the middle of things: learning how the business actually runs, who decides, what the words mean, where the data lives. Foundations laid there scale; screens drawn without them get redrawn.

  2. From zero, or mid-flight

    I take products from a blank page: discovery, the domain model, the product strategy, the first components. I also join platforms already in motion, where the stack and constraints are fixed. Either way the work starts at the foundation, not the screens.

  3. Prototype the argument

    I check technical feasibility before promising anything and prototype fast, lately with AI in the loop: a working prototype ends debates that static specs keep open. With leadership, I connect those prototypes to time-to-decision, data integrity, and risk, so design gets weighed as a business instrument.

  4. Every claim carries its evidence

    Craft tells you what should work; testing tells you whether it did. Depending on the question, I reach for contextual observation, moderated usability tests, tree tests for the information architecture, or an instrumented pilot, and the result decides what ships. Every outcome on this site is labeled measured, modeled, or usability tested, because I hold my own claims to the same standard.

  5. Dense does not mean dull

    Operational screens hold a person's attention for more hours than any consumer app, and that exposure deserves finish: typography with a rhythm, motion that explains instead of decorates. I enjoy this part of the work unapologetically. Exhibit: the site you are reading.

Where I go deep

Complex product & UX architecture

  • Data-dense operational platforms and admin tooling
  • Multi-role workflows with divergent approval logic
  • Analytics dashboards built around decisions, not charts
  • Information architecture for inherited domain models
  • Typography, motion, and visual finish that survive information density

Design systems & scalable foundations

  • Tokenized architecture and component libraries
  • Extending third-party frameworks (MUI, AG Grid) without forking them
  • Dual documentation: UX intent plus technical deviation
  • Adoption and governance models, not just component inventories

Product strategy & discovery

  • Discovery in organizations with no single source of truth
  • Stakeholder alignment across operations, engineering, and C-level
  • Product design strategy documents that hold across teams
  • Prioritization under governance and compliance constraints

AI & emerging interfaces

  • Conversational interfaces for AI agents: text, voice, and video workflows
  • Computer vision–assisted UX patterns, piloted with engineering
  • Making system reasoning legible: scores, confidence, and audit trails
  • AI-assisted prototyping for faster stakeholder validation

Domains worked in

  • Procurement
  • Media operations
  • PropTech
  • IoT & connected hardware
  • Gaming & social
  • Loyalty & gamification
  • Fintech & private banking
  • Security & intelligence
  • HealthTech & AI diagnostics
  • Marketplaces & gig economy
  • Automotive
  • EnergyTech

Areas of expertise

Where the depth above gets applied. Each area opens into the thinking, the skills, and the work behind it.

Outcomes, with the evidence stated.

The shape of the win repeats across engagements: less manual work, faster delivery, adoption that holds. Each figure below comes from one of the case studies and states how it was established: measured in production, modeled from workflows, or observed in testing.

  • 65%

    less manual data processing after consolidation

    Measured · procurement platform · first 6 months, pilot

  • 30%

    faster feature delivery from design system reuse

    Measured · localization platform · reported by engineering

  • 60–70%

    shorter proposal preparation cycles

    Modeled · real estate platform · MVP-stage workflows

  • 95%

    first-time task success in usability testing

    Usability tested · safety device, first-use activation · NEEDS-VERIFY: sample size

What I am a good fit for

Principal or lead product design roles

In-house, on enterprise or B2B SaaS products with real domain complexity. I lead design teams and stay a working contributor; what I am not looking for is a purely managerial seat away from the craft.

Embedded platform engagements

Three to nine months inside a product team, owning a complex surface area end to end: usually a platform rebuild, a data-heavy module, or a workflow that has resisted several attempts.

Design system foundations & audits

Establishing or repairing a tokenized foundation, particularly where a third-party component library is already in production and cannot be replaced.

Less useful for

  • Marketing sites and landing pages
  • Visual refreshes with the architecture held fixed
  • Logo and brand identity work
  • Fixed-scope work priced before the problem is understood
Contact