Judgment, not generation.

AI generates options. I decide which ones ship, and turn those decisions into a system your team can reuse.

See how I work
The process

From context to system in five steps.

Each step has one job. It keeps the speed of AI without losing the coherence of the product.

  1. Listen.

    I map users, flows, data and business logic before I design anything. Judgment without context is just opinion.

  2. Define.

    I set the criteria a screen must meet before AI proposes anything. Evaluation becomes a check, not a guess.

  3. Direct.

    I work with whichever tools support an agentic workflow and fit your team. I steer their output toward your product and quality criteria. The tools generate. I decide.

    See what tools I work with
  4. Curate.

    I keep only what holds up and structure it into components and patterns. The system grows, without screens piling up.

  5. Hand Over.

    I deliver infrastructure your team builds on without me. Design, development and product share one reference.

When to bring me in.

Signs your product needs a judgment layer.

Principles

The rules I work by, whatever the tools.

  1. -- 01

    AI-enabled, not AI-replaced

    AI speeds up the work. Every decision that reaches your product is still made by a person.

  2. -- 02

    Apps over websites

    I design products people use every day, not pages they visit once.

  3. -- 03

    Systems over one-off screens

    Every screen becomes part of a system your team can reuse and extend, with or without me.

  4. -- 04

    Simplest viable solution

    If a simpler approach does the job, that’s the one I recommend. Fewer tools, fewer steps, less to maintain.

  5. -- 05

    Pragmatic, not hype-driven

    New tools earn a place in my workflow when they prove useful in real work, not when they trend.

The approach in practice

NxtPeople: one system, multiple products.

Superflow built NxtPeople-DS for a consistent HR platform and its GoTemp sub-brand.

NxtPeople product interfaces, including login, AI assistant, mobile planning and scheduling.

The challenge

Multiple HR modules and GoTemp needed one consistent foundation.

The decision

Shared components, with semantic tokens separating brand from function.

The rejected option

Separate libraries per product: more maintenance, less consistency.

The outcome

One system for NxtPeople and GoTemp. New screens reuse shared components.

NxtPeople product interfaces, including login, AI assistant, mobile planning and scheduling.

Start with step one

A fixed-price diagnosis of your product: what holds up, what doesn’t, and what to fix first.

Book a call