The products in the suite grew separately, each with its own team and delivery pressure. To ship their first versions on time, two of them left shared flows for later: company registration, user invitations, and related setup work were handled outside the product while each team focused on its core. That worked for a while. Then the suite started needing a shared layer underneath its products.
That layer became a product, even if it did not start as one. It began as a working prototype built by a development lead running an agentic engineering system. My role at the start was light: define behavior, set limits, answer product questions, and let the system move inside that frame.
Once there was something tangible on screen, the questions changed. They were no longer only about behavior. They became product questions: what is this, who is it for, what should it own, and where should it stop. That is where I stepped in as product manager.
This was still a product, even if no customer bought it directly.
The customer might never operate this layer the way they operate the visible tools, but a bad experience here can still damage the relationship. Registration, access, invitations, permissions, and account setup are not background details when they decide whether a customer can start using the suite cleanly.
The work became less about directing every task and more about designing the conditions for speed to stay useful. If product tried to control every decision, it would become the bottleneck. If product stepped away, the work could drift. The operating model had to sit in the middle: clear scope, clean boundaries, decisions made at the right level, and enough structure for the agentic system to keep building without losing direction.
That also changed how I worked as a product manager. I started using Claude to keep planning, PRDs, roadmap structure, and user stories closer to the pace of the build. What began as a way to keep up with one fast-moving product became a reusable product workflow, later standardized for product teams across the company. The full system belongs in its own case.
The same question is now showing up in UX/UI. A designer joined to shape the experience around these shared flows, and the boundary needs to be drawn again: what can be made repeatable enough for the system to execute, and what still needs human judgment because it carries the customer experience.
That is the work behind this platform: turning a shared operational need into a product while learning how product management changes when strategy has to keep pace with an agentic build.
Not by controlling everything. Not by stepping out. By designing the boundaries where both can work.