Remote Product Designer · Async-first
Remote product designer for early-stage B2B SaaS teams.
I work async, across time zones, without slowing your team down. 20 years designing for SaaS, B2B, and productivity tools, remote by default.
Who it's for.
This is for you if
- You're pre-seed to seed, team of 5–30
- Your team is already distributed across time zones
- You need design output without a daily sync meeting
- You want decisions documented, not just made
- You're comfortable working async in Slack, Loom, and Figma
This isn't for you if
- You need someone physically in an office
- You want to co-design live, in real time, every day
- The problem isn't defined yet. That's a discovery engagement, not remote execution
How remote work happens.
No daily standup required to know where things stand.
01
Async updates
A written update after every work session: what shipped, what's blocked, what's next.
02
One weekly sync
A single live call, scheduled inside the overlap our time zones give us. Everything else happens async. The exceptions are the product discovery workshop at the start and any design sprint I facilitate, which run live on video.
03
Your tools
Figma for design, Loom for walkthroughs, and whatever your team already uses for tracking: Linear, Notion, Jira.
04
Documented handoff
Specs and components go straight to your engineers, documented well enough that a call isn't required to build from them.
Work I've shipped.
Partner & Principal Designer
Trial-to-paid went from 9% to 21% in the six months after the onboarding redesign. Owned onboarding strategy end-to-end. Set the process and standard before handing off to a full-time hire.
Read the Pleexy case studyFirst Designer
One designer to twelve engineers. An AI engineer and a salesperson built customer demos from the design system I documented, two days each. Pilots went up 300% in the first two weeks.
Read the Oraion case studyUX Designer
Legacy internal tool with significant UX debt and no AI readiness. Led the redesign, then designed the UX for King’s first AI feature, which A/B tested every Candy Crush level at once.
Read the King case studyYears after we worked together, I still go to Jorge for sparring on work, on decisions, on things outside the original scope. That kind of trust doesn't happen by accident.Niels Prip · VP HR & Business Development, Actimo
Questions.
How do you work across time zones?
Most of the work happens async (written updates, recorded walkthroughs, and Figma comments), so it doesn't depend on us being online at the same time. We keep one live call a week scheduled inside whatever overlap our time zones give us.
Do you join standups?
If your team's standup falls in a workable window for me, yes. If it doesn't, I post a written update instead so the team still knows what shipped, what's blocked, and what's next.
How fast can we start?
Usually within a week of getting in touch. If there's a hard deadline, tell me upfront and I'll say honestly whether it's realistic.
What tools do you use for async collaboration?
Figma for design, Loom for walkthroughs, and whatever your team already uses for tracking and docs: Slack, Linear, Notion, Jira. I fit into your stack rather than asking you to adopt mine.
How do you keep us updated without daily meetings?
A written update after every work session: what shipped, what's blocked, what's next. You can see where things stand without waiting for a call.
Can you overlap with a specific time zone?
Tell me your team's working hours on the first call and we'll find the overlap that works. Usually a few hours is enough for the one weekly sync.
Do you work exclusively remote, or can you travel on-site?
Remote by default. Occasional on-site time is possible for kickoffs or workshops if it's genuinely useful. We'd scope that separately.