Case Study

How Cloudinary Replaced Track-Based Planning with a 2026 Product Strategy and Grew Activation 40% in Four Months

60 days of leadership alignment and a Context Day, then three months with the Growth team to show it in shipped experiments.

Client
Cloudinary
Engagement
Strategy + Growth pilot
Timeline
5 months
Year
2026

40%+

Day-7 activation lift, four months, experiments only

4

2026 strategic pillars aligned across Image, Video, and Assets

1

Context Day, PM and R&D leadership in one room

3x

Experimentation velocity over the Growth team’s pilot baseline

Client context

Cloudinary is an API-first image and video platform. Teams integrate it to upload, transform, optimize, and deliver visual media at scale — in websites, mobile apps, and commerce workflows — without running their own media infrastructure.

The product org mirrors that platform split: Image, Video, and Assets are separate lines, each with its own PMs, roadmaps, and metrics. Neta, SVP Product, together with her product directors and the VP of Product Operations wanted strategic alignment, fast.

The local maximum problem

Cloudinary needed a 2026 product strategy the leadership team could use when teams prioritised work. Planning still ran in tracks. Each product line optimised its own metrics while the combined product confused users — the classic “local maximum problem”.

Self-serve growth was another significant challenge. Product teams shipped features, but adoption depth, retention, and conversion for self-serve users were below the bar Cloudinary set for itself.

Engagement

RE.FOCUS came in with a two-phase approach: 60 days to align leadership and the wider product org on one 2026 strategy, then three months with the Growth team to turn one pillar into shipped experiments and a measured outcome.

Results

  • Day-7 activation grew more than 40% over the pilot period through experiments only — no engineering investment outside the Growth team
  • Four 2026 strategic pillars aligned and documented, shared across Image, Video, and Assets
  • Experimentation velocity tripled versus the Growth team’s baseline before the engagement
  • One Context Day replaced months of fragmented alignment meetings