Company: AudienceView Year: 2019 Role: Director, Customer Support Pillar: Shared Services Leadership

Support Transformation &
M&A Integration

A simultaneous mandate: transform a broken support operation while leading the Customer Support and Corporate IT workstreams of a 254-person merger — with a 30-day integration target from deal close.

20→2P2 response target (days)
$8.1MRun-rate synergies
254NewCo headcount
30 daysIntegration target
L1→L3Certification built

Two Problems at Once

When I joined AudienceView in August 2018, the support operation had a P2 response time exceeding 20 days. Customers were waiting three weeks for a response to issues classified as significant but non-critical. The team had no formal tiering structure, no OLA framework with internal partners, and no knowledge base customers could self-serve from.

Within the first year, the Vendini acquisition was announced — deal signed May 13, 2019, closed May 27. I was assigned the Customer Support and Corporate IT workstreams of the integration, with a Day 30 target of June 11 for operational alignment across two organisations that had never worked together.

"Two mandates running in parallel: fix the existing operation and absorb another one. The only option was to move them forward together."

From 20 Days to a 2-Day Target

The support transformation had four components, each addressing a different failure point in the existing operation:

OLA Framework — built a formal Operating Level Agreement with the hosting team, defining internal response commitments for each issue severity. This was the missing layer between customer SLAs and internal accountability.
Skills Matrix & Tiering — introduced a structured L1→L2→L3 tiering model, defining what each level handled, when to escalate, and how to develop capability within the team. This created clarity and a career path that hadn't existed.
Self-Help Knowledge Base — built a customer-facing KB that deflected repeating tier-1 queries, reducing inbound volume on issues the documentation could resolve without agent involvement.
AudienceView University — an internal certification curriculum providing structured knowledge progression from onboarding through to advanced product expertise. New agents had a defined path; senior agents had a credential.

Response Time Targets

20+ daysP2 at baseline
15 daysShort-term target
10 daysMid-term target
2 daysEnd-state target

254 People, 30 Days

The AudienceView/Vendini integration had a tight timeline. Deal signed May 13, closed May 27, Day 30 target June 11. I led two workstreams — Customer Support and Corporate IT — responsible for org design, people mapping, process unification, and the communications that kept both teams informed without creating unnecessary anxiety.

Org design required mapping two distinct support structures — different tiering, different tooling, different escalation paths — onto a unified model that could serve both customer bases without a visible seam. This meant decisions about which processes survived, which were retired, and how the combined team would be structured going forward.

People mapping was the most sensitive element. Every role in both organisations needed to be assessed against the end-state NewCo structure. The goal was to communicate role clarity as early as possible, using honest information rather than corporate language that created more uncertainty than it resolved.

End-state headcount for the combined organisation was approximately 254, with run-rate synergies of ~$8.1M USD across the NewCo. Full integration target was December 1, 2019.

"The org design spreadsheet is a document. The conversation with your team about what it means — that's leadership."

Running Two Transformations in Parallel

The transformation and the integration reinforced each other. The OLA framework and tiering model we built for AudienceView became the template for the unified support operation post-merger. Starting the transformation before the merger closed meant we had a working model to absorb Vendini into rather than building from scratch under integration pressure.

Communication cadence matters more than communication content. During the integration, teams cared less about what was decided than about knowing that decisions were being made and they would be told. A regular, honest update — even when the update was "we don't have a final answer yet" — reduced anxiety significantly more than detailed memos published infrequently.

Knowledge base investment pays during disruption. The self-help KB we built before the merger closed absorbed the spike in customer queries that came during integration — queries driven by confusion about what the merger meant for their product and support experience. Having documented answers ready was the right call.

M&A IntegrationSupport Transformation Org DesignPeople Mapping OLA FrameworkTraining Programs KPI FrameworkKnowledge Base