Product Design Consultant · Strategy + validation

Product design consultant for early-stage B2B SaaS.

Design decisions backed by evidence, not opinion. 20+ years helping founders and PMs fix activation, onboarding, and prioritization problems.

Problems I solve.

What usually brings someone to a consulting call

  • Activation — users sign up but never reach real value
  • Onboarding — the first-run experience loses more people than it should
  • Churn — users leave and the product team doesn't know why
  • Clarity — the product tries to do too much, and users can't tell what it's for
  • Prioritization — the roadmap is a wishlist, not a sequence backed by evidence

How I approach it.

01

Discovery

Interviews, analytics, and a heuristic review to find where the product is actually failing.

02

Hypotheses & prototypes

Testable ideas, turned into prototypes fast enough to validate before you build them.

03

Validation

Real users or real data confirm — or kill — the hypothesis before engineering time is spent.

04

Delivery

The validated direction, handed off as specs and components your team can build from.

Outcomes, not opinions.

Design Lead

1M+residents served

Cross-functional team with no design decision-maker. Aligned stakeholders, set direction, and owned all design outcomes from strategy to delivery.

Design Lead

~25%cost reduction

Buying experience fragmented across multiple disconnected apps. Led the redesign of the full journey, consolidating it into a single product.

Need ongoing leadership?

If the gap is a missing design leader rather than a specific problem to solve, that's a different engagement.

See Fractional Head of Design
"
Years 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.

Do you help define the MVP?

Yes. That's usually where consulting engagements start — narrowing a broad idea down to the smallest version worth building and testing.

How do you validate ideas?

Whatever the problem actually needs — sometimes a prototype in front of real users, sometimes existing analytics, sometimes a heuristic review. I don't default to formal user testing when a lighter method would answer the question just as well.

How do you work with founders/PMs?

Directly, usually weekly. I bring findings and a recommendation, not just options — if I disagree with a direction, I'll say so and explain why.

What if we don't have existing research?

That's fine — discovery is the first step of the engagement, not a prerequisite for starting it.

Do you make the final call, or just recommend?

I recommend, backed by evidence. The decision is yours — but I'll tell you plainly if I think a direction is wrong, and why.

How long does a typical engagement run?

A focused problem — activation, onboarding, a single prioritization call — usually runs 3 to 6 weeks. Broader strategy work runs longer, scoped on the first call.

Let's talk about the problem.

A 30-minute call is enough to know if there's a fit. See the full range of services if you're comparing options.

Book a call