Head of Design · Valencia, Spain
Consistent product
design thinking
I design the software people work inside all day — then I build it. Head of Design at Mobupps, an 80-person B2B advertising technology company. Thirteen years turning dense, data-heavy products into interfaces people can move through without stopping to think — the design system, the product work, a small team, and the internal tools the business runs on. Prototyping in code means the work gets judged by being used rather than by being presented.
13 years
One company, one design function
Built the design function at Mobupps from nothing — the design system, the product work, the brand and a small team — and still hands-on in every part of it.
3 – 6h → 2min
To rebuild a client deck on-brand
Designed and built the internal platform that does in about two minutes what used to take a designer half a day, and took the designer out of the critical path entirely.
3 roles
Designer, front-end and back-end on the company site
I led the Mobupps website redesign — the audit, the design system, thirteen page templates — and then built it into the production codebase myself: Blade views, CSS and database migrations, committed to the same repository as the engineers.
Selected work
An internal AI product I designed and built, a fintech concept researched and usability-tested, and a brand-led interface exploration. Each is written up the way I would explain it to a team — the constraint, the options I turned down, and the decision I got wrong.
Mobupps·2026·12 min
Paggy: a rough draft in, a brand-perfect deck out
An internal service that reads a manager's own PowerPoint draft and rebuilds every slide on the company design system — in about two minutes, where a designer used to spend three to six hours. I designed and shipped it end to end: research, product strategy, the design system, the interface, the pipeline rules, the admin tooling and the telemetry.
- Design systems
- AI product design
- Internal tools
- Design engineering
- Telemetry
Self-initiated conceptSelf-initiated concept·2026·10 min
Predictive banking for freelancers with variable income
A banking interface built around the one question a freelancer actually has: how much of this balance is really mine to spend? A self-initiated concept that turned a reactive balance display into a predictive decision-support system — researched, prototyped and usability-tested end to end.
- Fintech
- UX research
- Design systems
- Product design
Self-initiated conceptSelf-initiated concept·2025·3 min
LEGO — a brand-led redesign concept
A self-initiated concept exploring how a catalogue with enormous visual variety can still feel like one system. Interface design, a component set and 3D motion, built to test whether LEGO's playfulness survives being put on a strict grid.
- Visual design
- Concept
- 3D and motion
How I work
01
I design for the person who has it open all day
Nobody opens a reporting dashboard for pleasure. The people I design for have a job to finish and my screens stand between them and finishing it, so the win is never a first impression — it is the four hundredth use, when the interface has to be invisible. That single framing decides most of what I do: remove a step before adding a feature, and stop when someone gets through the flow without thinking about it.
02
When the same request keeps arriving, I remove the reason for it
Most of what lands in a design queue is not a new problem. It is the same problem arriving again because nothing upstream changed. Rebuilding a client deck by hand cost a designer three to six hours every single time, and no amount of staffing was going to fix that. I would rather spend a month removing the queue than a career servicing it.
03
A design system is a contract, not a request
A component library people are asked to remember is really a rule someone has to enforce, and enforcement is where design leadership quietly disappears. On the internal platform, layouts are chosen and filled by code against fixed rules, so being on-system is the path of least resistance instead of an act of discipline. Consistency stops being something to police. Judgement is what the team gets paid for.
04
AI is the last resort, not the first idea
The interesting part of the AI product I built was not adding a model. It was working out how little of it the problem actually needed. A deterministic scorer resolves the overwhelming majority of decisions at zero cost, and the model is consulted only where the rules genuinely cannot decide — and even then it may only move the author's own words, never invent new ones. Knowing where AI does not belong is now part of the craft.
05
I prototype in code, because that is where the argument ends
A static mockup produces opinions. A working thing produces evidence. I build the real version, hand it to the people who will live in it, and let them tell me what is wrong — which is faster, and considerably less political, than defending a Figma file in a meeting. Certified by Anthropic in Claude Code and Agent Skills.
06
I would rather have one honest number than five flattering ones
A crashed build, a failed export, a dropped edit — those vanish forever if nothing records them, so those are the things I instrument. Everything else can be found out by asking someone. And at a small user count I report names rather than percentages, because a percentage of a dozen people is a lie with a decimal point in it.
Tools I work in
- Figma
- Claude Code
- Claude Design
- ChatGPT
- Contentsquare
- HTML & CSS
- JavaScript
- Python