I coach and advise founders, product and engineering leaders whose teams are stuck.
Usually that’s a team that’s too slow, or shipping a lot without moving the needle.
The client is usually a founder, CPO, CTO or Head of Design, with a product + engineering team somewhere between 15 and ~400 people.
Tell me where your team seems off. In one conversation I’ll tell you whether it’s skill, tooling, process or trust, and what I’d try first.
Ways to work together
Whatever the shape, the work is the same: untangling the unspoken fears and messy context (technical, organizational, and human) that keep a team stuck or spinning.
Coaching. You and me, once or twice a month, on what's burning: AI adoption that's not yielding speed, misalignment with a founder or a peer leader, processes that need to evolve, role definitions that got stale.
I bring pointed questions, but also advice when I've got it, pulled from lived examples. Every session ends with an immediate move to test. Over time, you build the pattern recognition and playbook to handle the next one without me. Warning: it may be fun (and occasionally uncomfortable).
Diagnosis. You know something's off, but you can't see why. Part of the team flies, others stall, leadership isn't rowing in one direction, pace isn't what you expected. I come in and untangle it, reading across multiple functions at once, having been in those seats myself.
This can be just an hour with you, but often a few conversations across the team, sometimes a codebase audit (agent friction derails everything). You get a sharp outside read of what's going on, what matters, and clarity to act on: what to ignore, what to defer, what to tackle first. No dance (and usually no slide decks).
Workshops. Even the best leaders sometimes need help shaking up and aligning their team. I come in (a workshop, a talk, a working session) with something designed to shift how a team sees a problem – often their own identity and way of working. Like a working session where the team maps what it still does by hand, and decides what to stop doing altogether. A one-off shock, to let you rebuild your way.
Been there, suffered that
- I've spent 20 years building software and the teams behind it, across product, design, and engineering, as an IC, founder, and executive.
- I helped take Metabase through 25x revenue growth and Gladly through 12x.
- I’ve reported to the visionary founder, and sat in most of the seats I now help align.
- I became a VP of Product without ever having been a PM. I built design teams in deeply technical companies that didn't believe in design.
- For over a year I've been shipping intensely to production (not pet projects), operating directly in AI native teams.
I don’t look at friction through a single lens.
I know what it feels like when engineering is expected to move faster than seems possible, when design is treated like late-stage polish, or when a founder feels the team has lost its edge.
I understand the underlying incentives and social pressures because I’ve held those jobs. And I won’t just nod along: you’ll leave every conversation knowing what to do next.
No theoretical consultant theater, just real, grounded problem-solving.
Act on it
I only work with a handful of people at once, and fit matters. Tell me where your team seems off. In one conversation I’ll tell you what I think is going on and what I’d try first. No pitch, no commitment.
If this resonates, let’s talk. No pitch, no commitment. I'm fluent in English and Brazilian Portuguese.
Reach out on me@brunobergher.com







