Hi, I'm Klaudia

I've been leading tech teams for 8+ years turning unclear needs into shipped products that make a difference.

Designs, prototypes, code, hand in hand with the team.

Based in Spain · English, Spanish, Polish, Finnish

⌄
gap.flow
what people ask forwhat gets built
Known issue

Products often go wrong long before the code.

Somewhere between what people ask for and what gets built, things drift apart. Customers describe symptoms, teams build from tickets, and somewhere in between, the real need gets lost.

The fix

That gap is where I work.

I've spent eight years in rooms where each side spoke a different language: clients describing frustrations, managers describing goals, engineers describing constraints. My job is to hear all of it, find what actually matters, and turn it into one clear direction.

I bring the experience of knowing where things usually break, before they do.

Shipped

And with everyone on the same page, we deliver.

The team stays close to the decisions. I turn them into specs, designs and working prototypes myself, and step into the code when it moves things forward. With AI in the toolkit, that happens in days, not months, and the release matches what everyone agreed on.

2018

Chapter one · Adalia · Senior Software Product Manager

Seven years at the meeting point between clients and code, learning what people mean when they ask for something.

  1. Listening.

    Enterprise clients rarely say what they need. They say what hurts. I spent years working with 15–20 clients at a time across 5+ time zones, learning to hear the need behind the complaint.

  2. Translating.

    Then I turned it into something developers could build: clear specs instead of vague feedback, so everyone knew exactly what to build and why. Work plans were delivered 30% faster.

  3. Owning the whole journey.

    From the first proposal to delivery, onboarding and training, I followed each client all the way through. Seeing every consequence of a decision teaches you to make better ones.

  4. Changing big things carefully.

    The bigger the system, the more careful the change. I learned to move large, critical software forward without breaking what over 100,000 people rely on in their daily work.

2025

Chapter two · OnTheGoSystems · Product Manager, WPML

Then I brought it all to a much bigger product, and rebuilt how I work around AI.

  1. A product at scale.

    WPML is used on over 1.5 million websites, built by many teams. At this size, a small misunderstanding becomes a big one, so decisions must be clear before building starts.

  2. AI-native process.

    One end-to-end process for every feature: validating the need, reviewing what exists down to the code, product and technical specs, interactive mockups, and measuring the impact after release.

  3. One direction across teams.

    The core product, backend services, infrastructure: different teams, each building part of the same product. I keep them pointed the same way, so the pieces fit when they ship.

  4. Listening to customers, at scale.

    With so many customers, feedback comes from everywhere. I look for the patterns behind individual requests, decide what matters most, and make sure it reaches the roadmap and ships.

If you're building something, I'll help you build the right thing.

Let's chat about it.

Book a free intro call

15 minutes, no pitch.

EmailLinkedIn

Product advisory

For product teams

Identifying the right problem, defining the direction, and creating clear specs and processes for your team. Involved from start to launch, hands-on whenever needed.

Technology solutions

For companies of any size, anywhere

Websites, automation and custom tools, built with the right technology for the job. From first conversation to launch, every solution is tailored to what you actually need.