Gustavo Polin

About

Product designer who stays close to the build.

I’m Gustavo, a product designer based in Valencia, Spain. Nine years designing SaaS platforms, B2B tools and operational software, most of it for teams where the designer also ships. Today I design AI-assisted products and build with AI in the loop.

  • Valencia · Remote
  • EN · ES
  • 9+ years
Dithered portrait of Gustavo Polin

What I’m looking for

Roles where design and build sit together.

Role
Product Designer, UX/UI Designer or UX Research. Full-time, contract or freelance.
Company
B2B SaaS, operational tools, early to growth stage. Teams of 5 to 50 where decisions are traceable.
Where
Remote, any time zone. Hybrid in Valencia works too.

How I work

Four principles, each one with a receipt.

Connect user needs, business goals, and technical constraints

Every project is framed around product clarity first, so the interface supports real business and delivery decisions.

Design systems that make products easier to scale

Reusable UI logic, shared patterns, and implementation-aware structure help teams move faster without losing coherence.

Use AI as a workflow advantage, not a shortcut

AI-assisted ideation and prototyping are used to accelerate thinking, explore options, and sharpen delivery.

  • Claude
  • Claude Code
  • ChatGPT
  • Codex
  • Lovable

Stay close to execution

Technical context matters. I work comfortably with developers, stakeholders, and operational constraints to keep ideas buildable.

The framework

The questions I carry into every project.

A repeatable question sequence I bring to any product problem: why before who, who before what, and what before how. It's what keeps design judgment consistent and transferable from one project to the next.

Understand the goal.

  • What problem are we trying to solve?
  • How does this product benefit customers?
  • What business opportunity does it create?

Define the audience.

  • Which groups have significantly different motivations for using this?
  • What are their pain points and emotions?
  • What is their high-level motivation for solving the problem?

Map the context of use.

  • Where does the product meet the user's day?
  • What has to be true right before and right after each interaction?

List and prioritize ideas.

  • What could we build to fulfill the customer's needs?
  • What already exists, and why isn't it enough?
  • Which idea has the best effort-to-impact ratio?

Make it concrete.

  • What tasks must the customer complete to succeed?
  • What do four fast sketches teach before high fidelity?

Measure success.

  • How would we know the solution worked?
  • Which metric would expose the riskiest assumption first?

Contact

Let’s talk.