Key Takeaways

  • Ramp built dedicated internal AI agents, including Glass, Inspect, Review Buddy, Testo, and Gadget, to handle routine tasks across triage, testing, and review.
  • Speeding up code generation shifts organizational drag upstream to product definition and downstream to customer distribution, mirroring Formula 1 pit stops.
  • Geoff Charles argues that teams should welcome PMs stepping away from routine engineering tasks: “I think it's amazing for product managers to be out of the loop for a lot of things that engineers can drive.”
  • Product leaders must pivot from micromanaging sprint tickets to optimizing the software factory that creates the software.
  • Future product career growth splits cleanly across The Three AI-Era Product Manager Archetypes.

The Software Factory Shift

When writing code becomes cheap, the traditional product management playbook falls apart. For years, PMs spent half their week writing Jira tickets, answering small engineering questions, and triaging minor bugs. Autonomous agents now handle those mechanical steps directly. Ramp built a suite of internal agents like Glass, Inspect, Review Buddy, Testo, and Gadget to absorb that operational overhead.

This shift creates a mechanical bottleneck problem. Charles compares building software to Formula 1 racing. If your pit crew changes tires in two seconds instead of eight, your next delay isn't the tire change. It is your fueling rig, your cornering speed, or your race strategy. In product organizations, when engineers build features twice as fast with AI, the new slowdowns appear in discovery, high-level quality checks, and commercialization.

“Us as product leaders, we need to obsess a little bit less about the product that we're delivering and a little bit more about the factory that helps us build products faster,” Charles notes. In practice, that requires PMs to choose a distinct lane rather than acting as generalist coordinators.

The Three AI-Era Product Manager Archetypes

Track 1: The Factory PM (Technical Track)

A technical product manager dedicated to building the internal software factory, finding organizational bottlenecks, and shipping tools and agent pipelines that allow engineers and AI to build customer-facing products faster.

Track 2: The Tastemaker (The Driver)

A product leader who holds the steering wheel, sets the product vision, and maintains an uncompromising bar for product design, user taste, and high-craft execution that AI cannot replicate.

Track 3: The General Manager (GM Track)

A product manager whose scope expands across marketing, sales, growth, and operations to manage holistic business outcomes and cross-functional P&L delivery rather than just feature launches.

When This Works (and When It Doesn't)

This framework works when product teams actively automate their discovery, review, and deployment pipelines. If your engineering team generates code with AI assistants, separating internal tooling from high-craft product design stops PMs from becoming human bottlenecks.

It fails in early-stage teams with fewer than five people. At that scale, splitting product management into three separate tracks creates unnecessary coordination drag. A seed-stage founder must act as the factory engineer, the tastemaker, and the commercial GM all at once. Specialization becomes valuable only after an organization reaches enough product volume that pipeline efficiency dictates company velocity.

What to Do With This

Audit your current product team this week to find out where your PMs spend their actual hours.

Take your team's calendar and ticket logs from the last fourteen days. Categorize every PM task into three buckets: internal tooling and workflows (Factory), UI polish and product definition (Tastemaker), or go-to-market distribution and revenue operations (GM).

If more than thirty percent of their time sits outside these three categories on routine ticket updates, manual test verification, or status syncs, replace those tasks with automated scripts or direct engineer-to-agent workflows. Then, assign each PM to own one primary archetype based on their strengths.