Our work / Case studies

Good software should feel like it belongs there.

These are real operating workflows we shaped, extended, and kept improving. The screens are privacy-safe, but the problems and design decisions are genuine.

See the work

01Built around the real job

The screen follows the decision, exception, and handoff—not a generic demo path.

02Improved in repeated passes

The useful version emerges by watching the work and returning to what still gets in the way.

03Honest about the foundation

We explain where standard, community, or commercial software ends and our work begins.

Seven working systems

A closer look at what changed.

Each case has its own page with the full workflow, the starting point, the improvements, and the operating result.

Actual submitted customer-return workspace with progress, office action and timeline. Customer identity, contact details and sales-order reference are covered. No review action was taken.

Recent · Sales and customer experience

A return request became a guided customer workflow.

The original sale, eligible quantities, reasons, photo evidence, office next action, customer instructions, and warehouse outcome stay connected.

View the case

Actual statement run with 50 candidates, 42 selected and prepared, one duplicate and seven excluded. All 42 prepared statements were accepted by the email server, with no reported delivery problems. Server acceptance is not proof the recipient read the email.

Finance · Custom operating workflow

Statements became a process, not a PDF button.

Preflight review, delivery status, payment paths, account policies, and recovery came together in one place.

View the case

Actual purchase-order catalog with two product cards and their Basic Forecast Debug panels. The category browser, supplier-price columns, stock signals and order controls are preserved. Supplier names and the order header are protected.

Inventory · Decision support

A product screen became a purchasing cockpit.

Buyers can see the inventory, reservations, receipts, categories, and sales signals behind the next decision.

View the case

Actual Biometric Device Attendance Log with local and UTC fields, status and audit flags. Employee names and device labels containing staff names are covered. No punches were edited.

Workforce · Device to workflow

A scanner connection became usable attendance work.

Device events gained local and UTC context, corrections, audit fields, privacy controls, and a path for exceptions.

View the case

Actual posted landed-cost record with linked transfers, journal context, received products, quantities and costs. Chatter is outside the crop; nothing was posted or changed.

Inbound operations · Cost traceability

Containers and landed costs began speaking the same language.

Inbound progress, transfers, supplier context, duties, cost preparation, and price review became one traceable flow.

View the case

Actual Fitment Workbench with product SKU, make, model, year, body, trim, engine, qualifiers and category. No mappings were changed.

Commerce · Product compatibility

Fitment became something a team could maintain.

A working surface ties SKUs to makes, models, years, body, trim, engine, qualifiers, and category rules.

View the case

Actual eBay Order Data Queues filtered to draft, partial or failed batches. Existing queue-line counters and batch statuses are preserved. Counters represent queue records, not a claim about unique orders or revenue.

Integrations · Operable connections

Marketplace connections became visible operations.

Accounts, fulfillment paths, orders, product counts, trends, queues, and recovery are visible without babysitting the connection.

View the case

See where this work helps

Find the case by the team it supports.

These seven system-design stories sit alongside ten more workflow examples in Our Work. Explore inventory, purchasing, administration, finance, customer experience, and integrations.

Real workflow, protected context

Real screens. Private details protected.

The screenshots come from the actual Pro-A-Motors modules. Focused crops exclude private records; small opaque masks cover the remaining private details. Captions identify existing records and unsaved setup forms. No screen data is recreated.

That lets us explain the engineering without exposing the company or the people the system was built to support.

Where should we look first?

Show us the workaround people have stopped complaining about.

That quiet workaround is often the clearest map to the system your team actually needs.

Start with the messy version