A new operating model separates long-term product maintenance (handled by Product Owners) from initial development. For new features, a temporary "swarming" team of Program Managers (strategy) and Product Ops (execution/tools) is assembled, creating a flexible, expert-driven approach to innovation.

Sales leader John McMahon explains that while perpetual licenses offered years to fix issues, today's consumption-based models can see customers churn in a week if they don't see immediate value. This demands an intense focus on rapid value realization.

SaaS playbooks for sales, marketing, and success were designed for annual product changes. AI-native products iterating every 30 days require a complete organizational rethink, as old go-to-market motions cannot keep pace with the product's rapid evolution.

The transition to a subscription service allowed Adobe to implement a data-driven operating model. This shifted product development from internal debates won by the "loudest voice" to decisions based on real-time customer usage data, empowering product managers and reducing internal conflict.

The marketing team at Adobe actively uses all new software, a practice called "Adobe on Adobe" or "Customer Zero." This process provides invaluable, real-time feedback to engineers, ensures product quality, and gives sales and marketing teams deep product knowledge and credibility with clients.

A new organizational model is emerging where companies create small, agile teams comprising a senior expert, an engineer, and a marketer. Empowered by AI tools, these pods can develop and launch new products in a week, a task that once required large teams and over six months.

In AI-native companies that ship daily, traditional marketing processes requiring weeks of lead time for releases are obsolete. Marketing teams can no longer be a gatekeeper saying "we're not ready." They must reinvent their workflows to support, not hinder, the relentless pace of development, or risk slowing the entire company down.

Instead of large, multi-year software rollouts, organizations should break down business objectives (e.g., shifting revenue to digital) into functional needs. This enables a modular, agile approach where technology solves specific problems for individual teams, delivering benefits in weeks, not years.

The transition from an internal tool to a commercial SaaS product is not just a business model change. For Spresso, it required 18 months of focused engineering to make the platform leaner and cut customer deployment time from four months to less than four weeks.