The Implementation Gap (Post 5 of 8)
A good customer selection process catches most of the accounts that would have struggled in delivery, by screening for fit before the contract is signed. It doesn’t catch all of them. Some accounts look like a good fit on paper and reveal a problem only once work actually starts: a stakeholder who wasn’t visible during the sales cycle turns out to be the real decision-maker and is skeptical of the whole project, or the technical environment turns out to be messier than anyone described, or the champion who drove the purchase quietly leaves the company in week three. Selection is a filter applied before the relationship starts. It was never going to catch everything, and pretending otherwise leaves delivery with no playbook for the accounts that slip through.
What happens next in most companies is that the implementation team absorbs the problem and tries to push through without raising it, because a hard question about an already-signed account feels like admitting failure, or like second-guessing a decision that’s already been made. Most importantly, no one wants to compromise a sale. That instinct is understandable and it’s usually the wrong call. An account that’s genuinely struggling to implement well doesn’t get better because everyone declined to name the problem out loud. It gets worse, more expensive, and harder to recover from the longer it goes unaddressed. Eventually, if not addressed, it could result in churn.
What Selection Can’t See From the Outside
Some of the clearest signals that an account is going to be difficult only become visible once a team is working inside it. A stakeholder map that looked complete during the sales cycle turns out to be missing the person who controls the budget for anything beyond the initial purchase. A technical environment that was described accurately but incompletely turns out to have a dependency nobody mentioned because nobody on the customer side thought to mention it. A champion whose enthusiasm carried the deal through procurement turns out to have oversold the initiative internally, and half their own team is resistant to a change they never bought into.
None of these are failures of the selection process. They’re the kind of thing that simply isn’t visible from outside the account, and the honest response is to build a way of noticing them early and acting on what’s noticed, rather than treating selection as though it should have been infallible.
The Signals Worth Escalating
A handful of patterns are worth treating as a trigger for a real conversation rather than something to work around and hope it resolves on its own. A stakeholder who consistently doesn’t show up to working sessions, especially one who was described as critical during the handoff, is signaling something about how seriously the initiative is being taken internally on the customer’s side. A customer who keeps pushing back on scope in ways that suggest they misunderstood what they bought, rather than isolated requests, is signaling a sales-cycle misalignment that will keep resurfacing until it’s addressed directly. A technical requirement that surfaces mid-project and would meaningfully change the effort required is signaling that the original scope was built on an incomplete picture, and pretending the original timeline still applies helps no one.
Any one of these on its own might be noise. A pattern of them, especially in the first few weeks, is a signal worth acting on rather than absorbing.
Having the Conversation Before It Becomes a Support Ticket
The reason to escalate early isn’t to look for reasons to walk away from accounts. It’s that the range of options gets narrower the longer the problem goes unaddressed. Caught in week two, a misaligned scope is a rescoping conversation, uncomfortable but manageable, and usually one that improves the relationship because it shows the customer the vendor is paying attention. Caught in week ten, the same misalignment is a crisis, the relationship has already absorbed weeks of frustration on both sides, and the eventual outcome is often a support escalation, a discount nobody budgeted for, or a customer who technically implements but will never renew.
Most companies don’t lack the judgment to see these signals. They lack a defined process for acting on them, which means every consultant has to individually decide whether raising a concern is worth the discomfort of appearing to flag a problem on an account leadership already considers a win. Building an explicit escalation path, covered in more detail later in this series, removes that individual burden and makes surfacing early signals the normal, expected behavior rather than an exception that requires unusual courage.
NextPeak Studio helps growth-stage SaaS companies build the judgment and process to catch struggling implementations early, before the cost of the problem outgrows the cost of the conversation. If your team is absorbing warning signs without raising them on accounts everyone agreed were a good fit, this is where that pattern usually starts.

