I’ve never seen a Q2C implementation fail because the technology didn’t work.
I’ve seen dozens fail because the sales team refused to use the new quoting process. Because finance didn’t trust the billing system. Because operations couldn’t figure out how to fulfill orders differently. Because the executive sponsor got reshuffled and nobody cared about the initiative anymore.
The technology is the easy part. People are the hard part.
This is something SIs consistently underestimate. You can have a perfect Revenue Cloud configuration, flawless integrations, and processes that are theoretically superior to what you had before. If your organization isn’t ready to change how it works, the system fails.
Why Q2C Creates More Friction Than Other Implementations
Q2C touches almost every function in an organization. It rewrites how revenue gets recognized. It changes how sales creates and manages quotes. It dictates how orders flow through operations. It determines when and how finance recognizes revenue and closes the books.
This breadth of impact is why change management is so critical, and why it’s consistently underestimated. Most implementations treat it as a side activity: a few training sessions before launch, a user guide, maybe a center of excellence to handle post-launch questions. The real work of getting people to change behavior gets deferred until after go-live. By then, you’re fighting adoption problems rather than preventing them.
The Three Groups That Resist
Sales resists new quoting workflows.
Sales is measured on closing deals. They have a process that works, even if it’s cumbersome. They have workarounds for edge cases. A new CPQ system is asking them to think differently about something they’ve been doing for years.
The resistance usually sounds like: “This is too slow. We can’t quote customers as fast as before.” Sometimes this is a real system problem. More often it’s the friction of learning something new combined with a system that wasn’t designed with the actual sales workflow in mind.
The fix isn’t better documentation. It’s involving top salespeople in the design process. Let them see the system before go-live. Let them identify where it slows them down and address those issues before launch. Have them champion the system to peers. Sales reps trust other sales reps more than they trust IT or implementation consultants.
Finance doesn’t trust the numbers.
Your finance team has been running month-end close the same way for years. They know which numbers to audit, where to look for issues, how to reconcile discrepancies. A new Q2C system is producing numbers via logic they can’t easily inspect, from a system they’ve never worked in.
The skepticism is usually well-founded. They’re responsible for accurate financial reporting. They should be skeptical of a system handling their data for the first time. “Trust the system” is not a satisfying answer for a controller who will sign off on financial statements.
The fix is giving finance genuine visibility into how the system works, not just theoretical documentation. Run the new system in parallel with the old one for a quarter. Let finance validate the numbers match. Let them build trust incrementally rather than flipping a switch on day one.
Operations is confused about what changed.
Order fulfillment just got more complicated. Orders are coming in differently. Data fields are different. The ERP integration is different. Operations teams often get the least change management attention because they’re viewed as execution, not stakeholders. “The system will tell you what to do” is not sufficient when you’re trying to fulfill orders correctly.
The fix is involving operations in the design phase, showing them exactly how their workflow changes, and providing hands-on practice with realistic scenarios before go-live. Then having implementation team members available for the first month to troubleshoot in real time.
The Framework That Actually Works
Secure executive sponsorship that’s genuinely engaged. You need a P&L owner who cares about the outcome and is willing to have hard conversations with functional leaders who aren’t adopting. A sponsor who approves the budget but delegates everything else isn’t enough. The sponsor needs to be visible, to publicly acknowledge the change management challenge, and to personally address resistance when it emerges.
Build a cross-functional implementation team. Your implementation team should include a real decision-maker from sales, finance, and operations, not coordinators who have to check with their boss on every call. These people become your advocates and your problem-solvers when resistance emerges in their functions.
Tell a different story to each function. Finance wants to hear about accurate revenue recognition and faster closes. Sales wants to hear about faster quoting and cleaner deal hygiene. Operations wants to hear about fewer exceptions and less manual intervention. These are all true. Tell the right version to each audience, framed around what they care about.
Build skills before go-live, not after. Two-hour training sessions the week before launch don’t produce adoption. People forget. They haven’t practiced with their own data. Effective training is role-specific, hands-on in a sandbox environment with realistic scenarios, and involves multiple sessions over several weeks. The goal is competence, not familiarity.
Plan for a messy first month and staff accordingly. The first month post-launch will surface edge cases, unexpected exceptions, and integration behaviors that weren’t fully tested. This is normal. Plan for it. Have implementation team members available to monitor and troubleshoot. Build a support model that knows the system, not just generic IT support. Create clear escalation paths for issues that require configuration changes.
Measure adoption and address gaps directly. Track which users are engaging with the system and how. When you see adoption gaps, don’t wait for them to self-correct. Go find out what’s wrong. Sometimes it’s a system issue. Sometimes it’s a process issue. Sometimes it’s a training gap. Sometimes it’s deliberate resistance that requires senior leadership engagement. Know which one you’re dealing with before deciding how to respond.
The ROI of Getting This Right
The organizations that invest in change management launch into momentum, not chaos. People use the system because they understand why it matters and they’ve been part of shaping it. The first quarter post-launch is productive, not a firefight. The system generates the business value it was designed to generate.
The organizations that skip change management spend 18 months trying to drive adoption of a system that launched a year ago. They absorb the cost of an implementation plus the opportunity cost of a system nobody fully uses.
Change management isn’t exciting project work. But it’s where your implementation either succeeds or fails, and it’s worth every dollar you put into it.
I work on Revenue Cloud and Q2C implementations at Slalom. Connect with me on LinkedIn if you want to talk through the organizational side of your implementation.