
Trusted by 15+ B2B teamsProduct Design
for Complex Software
I design SaaS platforms, AI tools and B2B web apps that teams pick up without training, from the first MVP to a product thousands of people rely on.
Who product design is for
How a product design project runs
Eight weeks from audit to handoff, with your sign-off at each step. Hover a step to see what happens.
You · Demo access. Demo access, analytics and the requests your team hears most.
What you get
You want to test a feature or an MVP with real users before committing your team to it.
Two ways to work together
A defined project with a fixed price, or a designer on your team month after month.
Not sure which one fits? Book a 30-minute call
Where products lose their users
Every audit ranks problems by impact and effort. These are the ones that come up first, product after product.
What clients say
“From the get go, Lucas was of incredible help and took leadership in his role - naturally taking over product management tasks to make sure everything ran more smoothly across our team. […] Lucas demonstrated great communication skills and his ability to take clear, relevant decisions to accelerate development process. I highly recommend him to any future partner or client that may consider working with him.”
Camille BosselFounder @ FoodHackreviews and recommendations
from clients, teammates and mentees







+73Questions about product design
A product audit, the user flows, wireframes, a visual direction, every screen on desktop and mobile with its states, the components behind them, and a handoff with specs and design QA on what your developers build.
About 8 weeks for a product or a major feature, from audit to handoff. A smaller scope, like one key flow or one area of the product, takes 3 to 4 weeks. The schedule is agreed at kickoff.
Both. For a new product, we start from the users and the problem and design the first version. For a product already in use, the audit comes first: what works, where users get stuck, and what to fix before adding features.
In your tools: Figma, your tracker and your chat. Your developers see the flows and wireframes early, so nothing reaches them as a surprise. At the end, they get the specs and the components, and I review what they build against the designs.
When it helps the decision. The audit draws on your analytics, the support requests and a few user interviews or recorded sessions when your users can be reached. What we do is agreed at kickoff.
Access to the product and its analytics, the requests your team hears most, and one person who can sign off at each step: flows, wireframes and the final review.
You do. The Figma files live in your workspace from day one, and the components and their documentation are handed over at the end.
A fixed price, based on the scope agreed during the first call, quoted in writing within 48 hours.
Ready to design your product?
Share your product and your goals. You get a reply within 48 hours with a written quote, or an honest answer if this isn't the right fit.


