Expertise · Operational software

Software for the decisions and actions that keep the business moving.

I design and build workflow-heavy products that remain clear when information is dense, work is repetitive, and every action affects the next person in the process.

Workflow clarityReliable executionModernizationApplied AI

Where friction appears

Operational complexity is real. Interface complexity does not have to be.

The goal is not fewer fields at any cost. It is the right information, in the right place, for the decision being made.

01

People reconstruct context before acting

The system records data, but users still search messages, files or other screens to understand the situation.

02

Repeated tasks carry repeated friction

A small delay in order entry, planning or status management becomes a significant operational cost over time.

03

The ordinary flow ignores exceptions

Experienced people bypass the product because real work does not always follow the ideal path.

04

The product is difficult to evolve safely

Years of business logic matter, but unclear boundaries make every improvement feel like a potential disruption.

How I improve the product

Make difficult work visible before trying to simplify it.

I treat product definition, UX and implementation as one system, because operational friction rarely belongs to only one layer.

01

Start with decisions

I identify what users need to decide, which context supports that decision, and what happens when it is wrong.

02

Respect operational density

I reduce navigation and ambiguity while preserving the information experienced people genuinely need.

03

Deliver in safe increments

I improve bounded workflows first, so teams can test real value without putting business continuity at risk.

04

Use AI where it earns its place

I apply AI to concrete tasks—retrieval, classification or summarization—with clear review and accountability.

Real-world delivery

Two ways operational software creates measurable value.

View all work

Distributed sales · New product

Order entry designed for the sales conversation.

Problem
Agents needed current product, pricing and order information while working with customers in the field.
Product
A tablet-first order-entry and sales-support system connected to central operations.
Read the case study

Mature systems · Progressive change

Modernization without breaking daily work.

Problem
The interface had accumulated friction, but the operational logic and team trust still mattered.
Approach
Workflow-by-workflow improvements delivered progressively instead of a disruptive rewrite.
Read the case study

What good looks like

Less effort around the work. More confidence in the system.

Faster repeated actionsFewer unnecessary steps in the moments that happen hundreds of times.
Clearer handoffsOwnership, state and relevant history remain visible to the next person.
Fewer shadow processesTeams stop maintaining parallel spreadsheets and unofficial workarounds.
Safer evolutionThe product becomes easier to improve without losing operational trust.

Let’s start from the workflow

Is daily work being slowed down by software that no longer fits?

Tell me what people are trying to do, where the current system gets in the way, and which part of the operation matters most.