Your SaaS or app already works. Let's make it grow again.

If growth has flattened, onboarding isn't converting, or the team ships feature ideas without data, I help you prioritize with evidence, straighten the funnel, and make product decisions with judgment—not assumptions.

Book a call

Teams and brands I've worked with

Does this sound familiar?

You have users, traction, or even revenue, but the product isn't taking off the way you expect. Onboarding is weak, activation is low, or growth has gone flat—and every redesign pitch or new feature arrives without clear evidence behind it.

How do we approach it?

More than a decade has taught me that when a product stalls, what hurts most isn't a "lack of ideas": it's lack of focus. That's why I work in phases: clarity on the problem, hypotheses, prioritization, and measurable deliverables—without rebuilding everything blindly.

Diagnosis

We review data, funnel, and feedback to find the real bottleneck.

Hypotheses and prioritization

We define what to test first based on expected impact, cost, and risk.

Implementation

We ship concrete improvements to product, onboarding, or conversion.

Measurement and iteration

We measure outcomes, learn, and choose the next step with evidence.

At the end of each phase we review results with you, adjust based on what we learned, and only then continue. That reduces risk, avoids building on intuition alone, and keeps budget and timeline under control.

About me

I discovered programming at 14 and I've been combining code, business, and teams ever since. Today I use that mix to help you see where your product is stuck and what's worth building first.

I've spent more than a decade across engineering, leadership, and product. I've lived everything from the code to the table where build decisions are made—and I know how costly it is to invest in the wrong place when the real problem is elsewhere.

2017

I designed and developed invoicing software and a video training platform for the wine industry, digitizing processes and improving operational efficiency.

2020

I was part of Taxitronic, a leading company in taximeters and taxi dispatch with national and international presence, contributing to business-critical solutions.

2021

I worked as a developer for a Fortune 500 company, participating in global projects with high standards for quality, performance, and scalability.

2023

I led a development consultancy and a team of 8, delivering high-impact projects focused on results, deadlines, and client satisfaction.

2026

As Product Manager at Rockalingua, I drove product and growth improvements that increased signups by 60% in just 2 months.

If your product is already in market but growth isn't following, you don't need more noise: you need diagnosis, prioritization, and execution with metrics. That's where I come in.

What motivates me now?

I'm driven to help teams that already did the hard part—a live product, real users—stop fighting flat metrics and start gaining traction with smarter decisions.

If you want someone who speaks both product and engineering, knows when to measure and when to ship, and won't sell you a redesign before understanding the funnel, let's talk.

Book a conversation

Diagnosis before construction

First we narrow the bottleneck: activation, conversion, retention, or value proposition. Less “we need to redesign everything” and more decisions that make sense.

Prioritization with judgment

I turn internal noise into a short list of what matters most right now, so the team stops scattering across features with no return.

A funnel you can read

Onboarding, first steps, and friction points: we look at metrics and real usage—not opinions alone.

A product built to scale

Architecture and infrastructure ready to grow as traffic and complexity rise—without performance or cost surprises.

Phases, not endless bets

I work in deliverables with a review at the end of each phase: you control budget, timeline, and direction without getting stuck in a blind project.

Serious, dependable code

Strong practices, stability, and focus on perceived speed and user trust: a technical foundation to experiment without breaking what already works. Includes 6 months of bug fixes if the code hasn't been modified by third parties.

Full transparency

Clear communication, technical documentation when it matters, and visibility into what, why, and what's next—so you're not dependent on black boxes.

Yours stays yours

Repos, hosting, domains, and data under your control from day one. No unnecessary lock-in and no surprises at handoff.

Frequently asked questions

What does it mean that work happens in phases?

We split the effort into stages with clear deliverables: diagnosis, prioritization, implementation, and review. That reduces risk, creates tangible progress, and lets you correct course before investing in the next phase.

How do we know if the issue is UX, value proposition, or go-to-market?

We separate it using signals: usage and conversion data, onboarding friction, messaging that doesn't land, and qualitative feedback. It's not about guessing—it's about testing hypotheses with evidence and acting where it hurts most.

How long does each phase take?

It depends on scope and product state. Before we start, we align on goals per phase and a realistic timeline with reviewable milestones—no empty promises or impossible deadlines.

Can I request changes after a deliverable?

Yes. At the end of each phase we review the outcome and what we learned. If adjustments are needed, we make them before continuing—the goal is that each step moves you toward better metrics, not just “something new”.

What does communication look like during a project?

Meetings when they make sense, clear writing in tools like Notion or Drive, and email when that's enough. What matters is that you always know what phase we're in, what we're testing, and what decision comes next.