Case Study · Sony Professional Services Europe

Lifecycle marketing and PrimeSupport revenue on Eloqua

Sony Professional Services Europe wanted to scrap siloed email activity and build a marketing automation first operation. Together we centralised campaign execution, built a full videographer lifecycle journey and automated PrimeSupport renewals in Eloqua, with revenue you could tie directly back to the canvas.

Sony Professional Services Eloqua lifecycle program.

Client background

Sony Professional Services Europe lead the way in AV and IT solutions for media, broadcast, sports, theatre, healthcare and enterprise. They operate across multiple product lines, each with its own commercial models, partners and buying cycles.

Historically, each product line behaved like its own small company. Different email platforms, different creative agencies, different lists and different processes. It got work out of the door, but it was messy, hard to measure and almost impossible to scale.

The CMO made a deliberate decision to wipe the slate clean and rebuild. Almost the entire marketing department was let go. New senior marketers were brought in to wield a small number of specialist agencies, with Eloqua at the centre and marketing automation as the default way of working.

At a glance

  • Industry: Professional AV and IT
  • Focus: Lifecycle marketing and warranty revenue
  • Key work: Videographer lifecycle and PrimeSupport
  • Platform: Eloqua + Salesforce
  • Award: Oracle Markie winner for lead nurture

The challenge

Sony needed to move from one shot, campaign based thinking to true lifecycle marketing. The vision was:

  • centralise campaign execution through a single Eloqua agency
  • standardise creative, templates and processes across product lines
  • build a full lifecycle journey for videographer customers across a two year camera life
  • tie email automation directly to Salesforce data and warranty dates
  • create a PrimeSupport renewal sequence that plugged revenue leaks at end of life

They did not just want more email. They wanted a machine that could generate and protect revenue in a way the business could see and believe.

My approach

I approached this as both a DevOps problem and a lifecycle design problem. First fix the way work flows into Eloqua so execution is reliable. Then build lifecycle programs on top of that foundation.

Part 1

Campaign execution playbook

We built a ticketing based intake model that standardised briefs, QA, approvals and deployment methods. Every send followed the same pattern and every asset lived on named, reusable Eloqua templates.

Part 2

Videographer lifecycle program

Using a two year assumed lifecycle for professional cameras, I designed a three phase nurture journey that mirrored how videographer customers behave across ownership, usage and upgrade cycles.

Part 3

PrimeSupport revenue catch net

For customers who did not upgrade, we built an automated PrimeSupport sequence that used the same data to sell extended warranty through the original dealer, capturing revenue that would otherwise evaporate.

The videographer lifecycle journey

The flagship initiative was the videographer lifecycle program. It treated every new camera sale as the start of a two year story, not a one off transaction.

Phase 1

Getting started

Immediately after purchase, customers received a sequence of onboarding emails focused on practical help. Product information, setup guides, educational videos and invitations to user forums that matched their segment.

Phase 2

Mid lifecycle

After the initial onboarding, contacts moved into a steady state relationship. They received regular newsletters with tips, case studies and content tailored to the type of videography work they were doing.

Phase 3

End of lifecycle and upgrade

Around three months before the two year mark, the journey shifted into upgrade mode. Emails highlighted the limitations of the current model, showcased new features in the latest generation and positioned Sony as the obvious upgrade path.

Behind the build: technical view

Technically, the Sony work was a proper lifecycle engine, not a pretty canvas. It relied on data discipline, correct purchase dates and clean object relationships rather than just clever email copy.

Tech Insight 1

Lifecycle anchored on purchase data

The engine used purchase dates from Salesforce and supporting CDO data to calculate where a contact sat in the two year life of their camera and which phase of the journey they belonged in.

Tech Insight 2

Standardised templates and campaign flows

Emails, landing pages and campaigns ran on standard templates. That meant we could maintain speed and quality across multiple business lines without reinventing the wheel each time.

Tech Insight 3

Ticketing driven DevOps for campaigns

A ticketing system, not unlike what I advocate today, handled campaign requests, SLAs, approvals and QA. It gave us a clear audit trail and dramatically reduced the risk of mistakes.

Tech Insight 4

PrimeSupport logic on the same data spine

PrimeSupport renewals used the same underlying data as the upgrade journey. Warranty dates and product details drove both upgrade messaging and extended warranty offers with no duplication.

Tech Insight 5

Closed loop reporting in Salesforce

Revenue attribution for the lifecycle program flowed into Salesforce. Campaign performance was reported where commercial teams already worked, which helped secure buy in and recognition.

Tech Insight 6

Oracle Markie level quality

The lifecycle program went on to win an Oracle Markie for best lead nurture. That does not happen if the technical foundation is flaky. It happens when content and architecture line up correctly.

What I would build today

If I rebuilt the Sony approach today, the principles would be the same but the tooling and patterns would be more modern.

Today 1

Event based lifecycle

I would move from time based phases to an event based model, using behavioural triggers, product usage signals and service events as drivers alongside purchase date.

Today 2

Deeper integration into service workflows

PrimeSupport and lifecycle communications would be tied directly into service cases and dealer activity. That would turn campaigns into a visible extension of customer operations, not a separate track.

Today 3

More granular audience modelling

There is huge potential in segmenting by project type, equipment mix and usage pattern. Modern data tooling would make that segmentation more precise and easier to maintain.

Impact

  • Campaign execution centralised on Eloqua with a clean process and SLA model.
  • Standard templates and QA significantly reduced send errors and rework.
  • The videographer lifecycle program became an Oracle Markie winning nurture.
  • PrimeSupport automation captured revenue from non upgraders via extended warranty.
  • The combined programs generated significant additional, fully attributable revenue every month.
  • The lifecycle pattern was rolled out to other Sony product areas after proving itself.

In my words

Sony were a joy to work with. They were brave enough to tear down their old way of working and commit to a proper lifecycle approach. The videographer and PrimeSupport programs were not just good looking canvases, they were engines that produced measurable revenue month after month.

- Greg Staunton

Want lifecycle campaigns that actually move revenue, not just open rates

If you want to centralise execution, build real lifecycle journeys and plug revenue gaps with smart automation, I can help you design and build the kind of programs that win awards and stand up to commercial scrutiny.