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.
Discovery
A product discovery workshop with your team, then interviews, analytics, and a heuristic review to find where the product is actually failing.
Hypothesis
Testable ideas, turned into prototypes in a design sprint I facilitate, fast enough to validate before you build them.
Validation
Real users or real data confirm the hypothesis, or kill it, before engineering time is spent.
Delivery
The validated direction, handed off as specs and components your team can build from.
Outcomes, not opinions.
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 studyDesign Lead
Cross-functional team with no design decision-maker. Redesigned the SCADA dashboard for a water utility serving 1M+ residents; about 20 operators rated it 8 out of 10, up from 5.
Read the CABB case studyDesign Lead
Buying experience fragmented across multiple disconnected apps. Led the redesign of the full journey, consolidating it into a single product.
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.
Are you a consultancy or a single consultant?
Just me. You work directly with the person doing the work, without an agency layer or handoffs between account managers and designers. I'm also part of a couple of design collectives, so if I get sick or the project needs extra hands, they can step in.
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 like activation, onboarding, or a single prioritization call usually runs 3 to 6 weeks. Broader strategy work runs longer, scoped on the first call.