I’m an engineer building Wave, @Amplitude_HQ’s proactive product agent for helping teams build self-improving products. This diagram gets at what we’re trying to build. The pod sets the outcome, shares the context, and defines the guardrails. Wave senses what’s happening, helps prioritize opportunities, and carries work across product, design, and engineering. Even a small customer problem can need all three, and lining them up is often harder than it should be. Wave can keep the same thread intact from customer evidence to a proposed design to a code change. The PM decides what’s worth doing, the designer shapes the experience, and the engineer owns what ships. What I want is for Wave to take on more of the coordination and execution, so PMs can spend more time talking to customers, designers on user research and design systems, and engineers like me on product architecture and long-term technical decisions. Wave takes on more of the execution load, so product teams can spend more time where their judgment matters. That’s the kind of agent I’d want on a team, and it’s what we're building with Wave.