Professional Services Partnership & Account Growth

Larger and more complex accounts routinely needed something outside the standard product: a custom configuration, a non-standard install, a scoped exception. That work sat with a separate Professional Services function, but the accounts themselves still lived inside Customer Success. The partnership existed to keep those two views of the same customer connected instead of handed off cold.

Custom requests arrived through Customer Success first, because that was the relationship the account already trusted, and then had to be re-explained to Professional Services from scratch. Scoping conversations happened without the operational history that would have made them faster and more accurate, and quotes went out that did not reflect what the account had actually asked for or what had already failed. Customers experienced the handoff as a reset, not a next step.

• Bring the operational history into the scoping conversation before the quote is drafted, so the proposal answers the actual problem instead of a secondhand summary of it.
• Treat a custom request as a relationship moment, not just a transaction. The account is deciding whether to trust the company with something bigger, not only buying a configuration.
• Sit in on the consultation rather than relaying notes. Detail gets lost in the second telling, and the account can tell the difference.
• Look for the upsell and cross-sell that the original request implies, rather than quoting only what was literally asked for.
• Plan implementation before the quote is signed, not after, so delivery timing is a commitment instead of a guess.
• Treat account growth as a long-term measure, not a per-request outcome. The value of the partnership shows up over several cycles with the same account, not in a single quote.

1. 01

   A standing coordination channel

   A direct working relationship with Professional Services that started informally and became a recognized path for any account with a need outside the standard offering.

2. 02

   A shared scoping practice

   Joining solution scoping conversations directly, bringing the account's operational history and prior interactions into the room instead of leaving Professional Services to start from the request alone.

3. 03

   Quote preparation support

   Helping shape quotes so they reflected the full scope of what an account needed, including options the account had not explicitly asked for but had a clear use for.

4. 04

   Customer consultation involvement

   Taking part in consultations for custom and complex requests, so the account had continuity between the person who knew their history and the person designing the solution.

5. 05

   Implementation planning input

   Working through delivery sequencing and timing alongside Professional Services, so a signed quote came with a realistic plan rather than a separate project to figure out later.

6. 06

   An account growth lens

   Using the partnership as a channel for upselling and cross-selling grounded in what an account had already shown it needed, and tracking those accounts over time rather than treating each request as a one-off.

• Gradually absorbed portions of the Professional Services workflow for the accounts already inside Customer Success, reducing handoff friction for the account.
• Improved the accuracy of quotes by grounding them in operational history rather than a restated request.
• Surfaced upsell and cross-sell opportunities that a request-only view of the account would have missed.
• Became a reference point for how Customer Success and a specialized delivery function could share ownership of a growing account without either side losing visibility.

This partnership was never formally assigned. It grew because it was faster and more accurate for the account to work through one continuous relationship than through a handoff, and Professional Services noticed that before I made the case for it. The part I would do earlier is write the shared scoping and consultation habits down as a repeatable practice, rather than letting them live in a working relationship that depends on the same two people staying in the same roles.

• Customer Operations
  Order Operations Architecture →

  An operating model for orders: one rule that settles ownership, a split-intake work design, and a decision tree an associate can run in the moment.

• Customer Operations
  Customer Journey Operating System →

  A complete communication architecture spanning purchase through long-term customer success, designed as an operating system rather than a set of messages.

• Customer Operations
  VIP and Gifting Program Charter →

  A charter for high-touch outreach: who qualifies, what is offered, who owns each stage, what could go wrong, and how success is measured before anything is sent.