LucasCufré.design

Most product design problems are alignment problems wearing a UI costume. That's where I work.

Designer of record
Lucas Cufré · Product Designer
Working from
Rosario, Argentina
See the work →
#01 - Featured Case Studies

Selected projects from these past few years.

N° 01
  • QR-activated chain of custody
  • Gamified first response via Bees
  • Two-week response cut to three hours
Sensify → Cervecería y Maltería Quilmes (ABInBev) 2021–2023

Sensify — A theft problem that was a data problem

Quilmes runs 240,000 branded coolers across Argentina and loses three to five percent every year. Everyone called it a theft problem. It took a former database analyst about a month to see it wasn't one — and to trace recovery time from two weeks down to a three-hour average.

  • industrial-monitoring
  • iot
  • enterprise-ux
  • field-operations
  • latam
Read the case
N° 02 Gated
  • The constraint nobody could design away: the wallet
  • Institutional order types on a retail terminal
  • Making it fast enough to be believed
Cooking.gg (Ember) 2025–2026

Cooking.gg — a trading terminal disguised as a kitchen

Product design and management for a Solana trading terminal built to out-execute BullX and Photon. Institutional-grade order types, MPC wallets behind a social login, a 60% cut in execution time — and a clean PM handoff during the worst possible week to hand anything off.

  • web3
  • trading
  • solana
  • product-management
  • ux-design
  • mobile
Open with a key Request access ↗
N° 03 Gated
  • The market as material
  • What I couldn't get from a stakeholder
  • The bet: remove the constraints
Membrane 2022–2024

Membrane — where the trade was never the hard part

I led design, then product, on an OTC derivatives engine for crypto-native institutions. We shipped unrestricted trade configuration — then found the pain was never the negotiation. It was living with a position after it was booked.

  • fintech
  • derivatives
  • otc
  • web3
  • product-management
  • ux-design
Open with a key Request access ↗

Constraints aren't obstacles. They're the material.

Trading systems.Institutional treasury.Industrial monitoring.

The complexity can come from anywhere — I work where the engineering shows up on the surface.

#02 - Field Notes

Working notes from the practice. Published when something earns a footnote.

Read all field notes →
FN — 001 6 MIN

Alert Systems at Scale: When the Cure Is the Disease

Six months designing alerts for an industrial monitoring platform taught me the failure mode the spec couldn't see: alerts and silencing share the same off-switch, and once silenced, the system is structurally lying to itself.

FIELD-NOTES / ALERTS / INDUSTRIAL-MONITORING / UX-DESIGN / SYSTEM-DESIGN
FN — 002 6 MIN

What the next person inherits

The PM role I left had 650 documents prepared for whoever came next. None of them said what the team would actually need. On transitions, inherited substrate, and what documentation can't catch.

FIELD-NOTES / TRANSITIONS / PRODUCT-MANAGEMENT / ORGANIZATIONAL-DESIGN / LEADERSHIP
FN — 003 6 MIN

Four kinds of user, and why each one matters differently

For years I treated "user" as a uniform noun. The data didn't. Four kinds of user — First-Level, Second-Level, Passive, Hostage — and what each one's feedback actually means.

FIELD-NOTES / USER-RESEARCH / TAXONOMY / UX-DESIGN
Contact
Let's get in touch

If this resonates,
let's talk.

Direct
Reply window
Within 48h, weekdays
Currently
Open to senior / lead product roles
Timezone
UTC-3, overlapping US and EU hours

I started designing screens. I ended up designing the conversations that produce them.

In tech since 2014 — but only designing since 2021. I spent six years as a database analyst before Sensify gave me my first design role, and it shows in where I ended up: derivatives pricing, token trading terminals, industrial monitoring, a multi-state cannabis rebuild. The complexity can come from anywhere. The job is always the same: turn it into an interface people can trust.

Along the way I learned that what blocks a product is rarely on the screen. It's the approval chain, the vendor handoff, the meeting where nobody says the real number. I design for that layer too. It's where the work actually happens.

In 2014 I traded design school for a database job. Twelve years later I'm back in the classroom, finishing the degree people assume I already had.