About

I have spent my career leading the work that happens after software is sold.

Professional Services. Delivery operations. Customer Success. Partner programs. Post-acquisition integration. The work has changed titles, but the operating problem has stayed consistent: customer value depends on what happens after the deal closes.

Background

Trevor MacTaggart

Professional Services and Delivery executive with more than 20 years of experience helping software companies scale customer-facing operating models.

Across leadership roles at BlackLine, Rimilia, VersaPay, Strongpoint, Ceridian / Dayforce, and NetSuite, Trevor has worked at the intersection of Professional Services delivery, customer confidence, revenue predictability, cross-functional operating discipline, partner-led growth, and executive-level problem solving.

He has led large delivery teams, owned a $5M+ services P&L, built global delivery frameworks, standardized services operations, designed certification and enablement programs, improved Sales-to-Delivery coordination, and served as a senior escalation point for strategic customer accounts.

Customer Growth & Delivery brings that experience into a focused advisory practice for software companies that need to improve their post-sale system.

50-word bio

Trevor MacTaggart is a Professional Services and Delivery executive who helps software companies improve the post-sale system connecting implementation, customer value, retention, and growth. His experience spans BlackLine, Rimilia, VersaPay, Strongpoint, Ceridian / Dayforce, and NetSuite, including services P&L ownership, delivery model design, partner success, and post-acquisition integration.

20+ Years in software services leadership
$5M+ Services P&L ownership
Global Delivery framework design
PS · CS · Support · Partners Cross-function depth

Why This Practice Exists

The customer problem is often wider than the function that first feels it.

A renewal issue may be treated as a Customer Success problem.

A frustrated customer may be treated as a Support problem.

A project overrun may be treated as a Professional Services problem.

A weak partner may be treated as a channel problem.

In many cases, those are connected symptoms of a post-sale system that has not been designed for the company's current stage.

This practice exists to help leaders look across that system, define the few changes that matter most, and install a more reliable operating model.

Selected Experience

Where the operating experience was built

BlackLine

  • Led North American Professional Services following acquisition-related integration
  • Owned a $5M+ services P&L
  • Designed and implemented a standardized delivery framework
  • Partnered with Sales, Product, and Engineering leadership on readiness, handoffs, and customer adoption
  • Used data and AI-assisted insight to improve delivery planning and risk identification

Rimilia

  • Established and led Professional Services, Support, and Customer Success in North America
  • Built a cross-functional delivery cadence
  • Recovered strategic customer relationships through direct executive engagement

VersaPay

  • Scaled Professional Services during rapid growth
  • Introduced standardized delivery lifecycle management across 50+ active projects
  • Designed services pricing, packaging, and delivery models that supported Sales

Strongpoint

  • Built and led Partner Success
  • Designed partner onboarding and enablement programs
  • Contributed to approximately $0.7M in partner-influenced revenue

Ceridian / Dayforce

  • Consolidated six Professional Services groups into a single governed organization
  • Built PMO structure, common delivery standards, and management visibility
  • Increased billable training revenue by 33% through better operating discipline

NetSuite

  • Led international consulting teams delivering ERP and eCommerce programs
  • Owned delivery economics and forecasting
  • Built service methods, SOW governance, and post-acquisition integration routines

Working Style

Practical, structured, and grounded in operating reality.

The work is designed to be useful to senior leaders and credible to the teams who will live with the outcome.

Clear diagnosis

Start by locating the actual operating problem before proposing any change. Symptoms are not diagnoses.

Usable deliverables

A bias toward outputs that leaders and teams can act on — not abstract recommendations that sit in a slide deck.

Implementation reality

Respect for what it actually takes to make a new operating model work inside a real company with real constraints.

Start the Conversation

Discuss your post-sale operating problem.

A working session is a practical first step. No commitment required — just a focused conversation about what is happening and what may be worth examining.