Engineering Strategy — 2026

Last updated: 2026-02-09

Summary

This year, we are focused on the following priorities: acquiring and onboarding 50 ACCS and/or ACO customers; accelerating migration enablement; delivering AI-powered Product Innovation to customers; achieving total savings of $3.0M from run rate spend in H126; and reducing overall customer churn by 30% against H126 forecast.

If you are working on something does not directly support these goals, it is not a priority.

Goals in detail

1. Acquire and onboard 50 ACCS and/or ACO customers​

Make it significantly easier for Commerce customers to adopt ACCS and ACO.

Related initiatives:

What success looks like:

  • 20 go-live customers by Summit​
  • Deliver 3 ACCS features resulting from CDE engagements​
  • Deliver 3 ACO features resulting from CDE engagements

2. Accelerate migration enablement

Create a one-step migration path to migrate customers from PaaS to SaaS

Related initiatives:

What success looks like:

  • Reduction of ACS retention engagement cycle time from 8 to 5 weeks
  • Decrease customer migration cycle time average by 50%
  • Ability to successfully co-innovate with customers

3. Deliver AI Product Innovation to customers​

Delivery AI Product Innovations to Customers

Related initiatives:

What success looks like:

  • Deliver 4 Agentic AI Use Cases (Catalog Discoverability in LLMs, Brand Concierge, and UCP/ACP enablement, AI Coding Agent for App Builder)​
  • Co-innovate with 4 customers

4. Reduce overall customer churn by 30% against H126 forecast​

Delivery AI Product Innovations to Customers

Related initiatives:

What success looks like:

  • Retain 50% more ARR ($12M vs $8M actual) through ACS Retention program (achieved by tooling)
  • Achieve a 90% retention rate (vs 88% actual)​
  • Engage 75% of at-risk accounts with at least 2 product touchpoints

Explicit non-priorities

To be clear, this year we are not optimizing for:

  • Large, custom one-off solutions
  • Short-term speed at the cost of long-term maintainability
  • Manual processes that don’t scale

Why this matters now

  • With the launch of ACCS and ACO, we are at a critical inflection point to ensure customers successfully adopt next-generation services and transition away from legacy PaaS solutions.
  • Rapid innovation is now a necessity

How this connects to initiatives

Each major initiative exists to serve the strategy above.
On the initiative pages, you'll see:

  • Why the initiative exists
  • What changes and what stops
  • Which teams are impacted
  • How success is measured

If an initiative doesn’t clearly map back to this strategy, we should question it.

Questions or feedback

If something here feels unclear, conflicting, or unrealistic, that’s a signal we want to hear, please reach out to your Engineering Leader.

Strategy only works if it’s understood and challenged by the people doing the work.