Engagement model 02
Embedded partner
You have a product and a team. You need design that reaches production, not just approval.
How the engagement is shaped
Typical duration
3 to 6 months
Rolling monthly, one month's notice either way.
Commitment
Your rhythm
Days a week set by your team, inside your standups.
Scope
Your roadmap
Priorities move with the team. No change requests for a reordered sprint.
Best for
Continuous work
Teams shipping weekly with no design lead, or one who is stretched.
Where I can help
Five positions. Most teams need two or three, depending on the hole in the team, not the stage of the product.
01
Design lead, or your only designer
As lead I set the standard and direct designers; as the only designer I hold everything from strategy to shipped code. I have done both, and will tell you which you need.
You need this whenYou have no designer, or designers nobody leads.
02
Product designer on the roadmap
End-to-end design at your cadence: flows, interaction, interface, and usability testing where the stakes justify it.
You need this whenThe roadmap moves faster than design, and specs run out mid-sprint.
03
Design system owner
Tokens in code, component decisions written down, and validation that catches drift in CI.
You need this whenYou have a system nobody owns, or three, and engineers rebuild their own.
04
The person who finds what is leaking
An audit of what you ship (states, flows, inconsistencies), taken to strategy, not filed as tickets.
You need this whenThe backlog is full of symptoms and the underlying problem has never been named.
05
Prototyping and shipping
Working HTML, CSS and JS on your data, so the team argues about behaviour, not images. It lands on your branch, through your review.
You need this whenDesign stops at approval, and the last ten percent falls to whoever has capacity.
Kinds of engagement
Lighter weekOne workstream, monthly retainer
Core weekProduct design plus the system
Full weekDesign lead, or your only designer
What I need from you
- 01Treat me as part of the team: standups, Slack, sprint planning, not a vendor channel.
- 02Repository access and a review process I can push into.
- 03One engineer who cares about the front-end and will review my PRs.
- 04A roadmap I can see, even a rough one, so design lands before the sprint.
What this does not include
Both can be arranged; say so on the call.
Backend engineering I write the front-end. Server-side belongs to your team or a developer you bring in.
Brand identity A different discipline. I design inside your brand, or a plain one, and can refer you.
Relevant work
Questions
What teams ask before embedding
How is this different from hiring a contractor?
I ship the front-end, so work doesn't stop at a handoff, and I argue about what's on the roadmap, not just how it looks.
We already have designers. Does that work?
Often better. I take the system and front-end, or the lead, so they can stay on product depth. I've led designers and supported them.
What happens when the engagement ends?
The system is the handover: tokens, component docs and validation in CI keep the standard without me.
Is AI writing our product?
No. Claude Code and Claude Design speed up exploration and implementation. Every decision, review and shipped line is mine, gated by the same checks as any engineer's.
Could this become a full-time role?
Yes. I'm open to senior and lead roles, and embedding is a good way to start that conversation.
Which time zones do you cover?
Remote worldwide, in English, Spanish and Portuguese, on hours that overlap yours. I travel for onsites when it matters.
Who you'd be working with
- Role
- Senior Product Designer · design lead and design system owner
- Experience
- Nine years across fintech, logistics and energy
- Engagements
- Project work · embedded with your team · advisory · senior & lead roles
- What I take on
- 0→1 products · design systems in code · AI-native workflows
- Based
- Barcelona, Spain, remote worldwide. English, Spanish and Portuguese.
- Availability
- Available now