Javier

I help shape digital products

I work with founders and companies on difficult product problems: from figuring out what is worth building, through design, to getting it built.

Product leader with a background in design and strategy. Based in Chile, working across Latin America.

Tell me about your problem

How I help

Figure out what matters

Strategy, discovery, opportunity and prioritization. I start with the data you already have, question the first hypothesis, and find the problem worth solving before anyone commits engineering time.

Shape the product

Flows, states, rules and roles. I turn complex operations into products people understand, and write definitions engineers can build from without me in the room.

Make it real

Working alongside engineering and operations from decisions through delivery. I prototype to validate, not to impress, and I stay until it is running.

Selected work

Surgical patient coordination

HealthtechFounder2026

Between a surgeon's order and the operating room there is a two-to-three-month process, run by one coordinator over WhatsApp and a spreadsheet. A third of 2,500 historical cases had no recorded outcome. The funnel was not leaking. It was invisible.

I rebuilt the baseline from the source data before designing anything, then audited my own numbers and cut the business case by 40%. I mapped the journey with the coordinator and turned it into a state machine. I defined what the system never does alone: talk to doctors, read handwritten orders, communicate a suspension. Autonomy is earned with a metric, 70% of drafts approved unedited, not declared.

First interview to production in four weeks. Runs alongside a live service with four surgeons and 150 to 200 open cases. Measured 45-day pilot with a control group from October 2026.

RialFit

ProptechChief Product Officer2026

A lead-to-project matching engine for real estate developers had to serve two businesses at once: a white-label product for each developer, and a broker channel where we capture leads and lend them out. The proposed data model treated ownership, management and origin as one thing.

I tested the product myself and isolated the real failures. I rejected the model in writing, with three contradictions and six edge cases, and redefined the domain around three relationships. That cut the change from over 3,000 lines to under 900. I ran the decision meeting in 34 minutes with three yes-or-no questions, then specified the new screening flow and the analytics to judge it.

Multichannel model, attribution and metrics in production one month after the spec. Catalog of 38 developers and 138 projects. Now in validation.

beClassmates

EdtechProduct and operations2026

A B2B language-learning platform with around 800 active students, 100 groups and 25 teachers was running enrollment, grouping and teacher payroll by hand. Its community features went unused for reasons nobody had named.

I diagnosed the community problem as psychological, not technical, and reframed it from blog to plaza. For the backoffice I sat with the people doing the manual work and scoped by pain: reduce 80% of it, not 100%. The system suggests, a person approves. Ten specs with a closed vocabulary, acceptance criteria and an explicit "not included" list. 275 decisions tracked in four weeks, 21 reversals, 18 of them my own proposals rejected.

Operations backoffice specified and prioritized in four weeks. First sprint scoped to what unblocks moving 500 people onto the new system.

Maré

SportechFounder2026

Canoe and rowing clubs in Rio de Janeiro fill their boats through a WhatsApp list copied by hand. I parsed 9,000 messages from two clubs: 83% were copies of the list, and 30% of cycles lost confirmations to concurrency. The clubs had no idea. The problem is invisible from inside.

I built the evidence, corrected my own occupancy number when it did not match the club's prices, and sized the market with a manual census. I designed a link that lives inside the group instead of an app. Rules: the coach approves, never drafts; nothing about the sea gets automated. I priced it, planned a gated pilot, and wrote two different decks for the club and the partner.

Pre-pilot. Brand, prototypes, and a plan that can stop without debt. Also the reason I row at 5:40 in the morning.

Also

  • Fidi · Fintech infrastructure · UX lead. A design system for a financial backoffice with rules about what the interface may never pretend: no data that does not exist, no simulated history, no assumed capabilities.
  • RialAds · Real estate marketing agency · Business strategy. Set up the operating system of a vertical agency: roles, a reporting process, a KPI glossary, and a dashboard with success criteria written before building it.

How I work

  1. Data before opinions. I rebuild the baseline from the source before I design anything. The first hypothesis is usually wrong.
  2. I audit my own work. If a number does not add up, I say so before anyone else does. Twice this year that cut my own business case by 40%.
  3. What we are not building is written down. Every spec has a "not included" list, with the reason, so it does not come back from an old mockup.
  4. The system suggests, a person approves. Automation earns autonomy with a metric, not a declaration.
  5. Decisions, not debates. A timeboxed agenda, three yes-or-no questions, a recommended option, and who decides what.

About

I started as a graphic designer in 2004 and spent years as a digital art director and strategist in agencies, working for airlines, insurers and banks. In 2022 I moved into product. Today I am Chief Product Officer at CSL, a startup studio in Chile, leading products in fintech, proptech, edtech, healthtech and sports.

I am not an engineer. I work closely with the people who are, and I make sure what the product needs survives the trip to what gets built.

I work in Spanish, English and Portuguese.

Javier López

Working on something difficult?

Tell me about it. A few lines is enough.

Or find me on LinkedIn.