HFS Research asked 202 large-enterprise leaders in 2026 whether they intended to change their IT service provider or delivery model. Ninety percent said yes. The same survey found those providers scoring highest on their value proposition and lowest on innovation.

A consultancy earns its next engagement mostly in the months after the current one ends, not during the program itself. That goes against how most delivery teams see the relationship: a clean go-live gets treated as the thing that wins the next contract, when it only clears the bar for consideration. What happens in the months afterward is what actually decides the outcome.

What Clients Remember

People don’t remember a six-month program as an even average of its weeks. They remember its high points and its ending, and weight both far more heavily than everything in between.

A single visible stumble, such as a slipped go-live date, a migration error a business user hits, or an escalation that reaches someone senior on the client side, gets recalled as a defining feature of the project. The final steering committee, the final invoice, and the formal close-out meeting disproportionately impact the perception of the success of the project.

The individuals involved get remembered too, more than the firm they worked for.

A client’s operations team credits the specific consultants who sat with them through a difficult cutover. An end-of-project survey score, gathered while the program is still fresh, says very little about how that same client will describe the relationship six months later, once only the peaks and the ending remain in memory.

The Months Nobody Owns

A consulting engagement runs on constant contact: workshops, status calls, steering committees, sometimes daily stand-ups. Then the main work goes live, and that contact usually drops dramatically. This is a cliff edge built into how SAP consulting gets scoped and billed, unlike a retainer, which never switches off.

In practice, the first one to three months after go-live tend to be the most fragile stretch, when a single phone call or email can still hold things together. By six months, the client has moved on to other priorities, unless problems keep occurring. 

Only deliberate contact prevents that drift. Plenty of the accounts a consultancy loses were with clients who were perfectly happy with the delivered work: satisfaction alone doesn’t hold a relationship together once the formal reason for talking has gone. 

One explanation shows up repeatedly in analysis of professional-services client relationships: often, nobody inside the firm is formally responsible for the relationship once delivery ends. The account manager has moved to new prospects, the delivery lead to the next program, and the client is left with no one assigned to them.

What the Board Is Watching

HFS Research’s data points to why: most SAP programs still get judged, day to day, against IT milestones: the go-live that is on-schedule, the code count, and the system uptime in the first weeks.

The client’s own board asks a different question, and it asks it later.

Business metrics and processes including released working capital, a shorter month-end close, or a supply chain that can flex are the terms HFS’s research found a board cares about, and they don’t show up until six to eighteen months after go-live. That delay between finishing the technical work and the business result becoming visible makes it harder for a client to justify bringing the same firm back quickly.

Most SAP transformation contracts are still priced fixed-fee or time and materials, with nothing built in that forces anyone to check the work against the original business case once the system is live.

ISG’s 2026 research found U.S. enterprises increasingly restructuring their SAP programs into phases with defined value checkpoints, driven largely by large-scale ecosystem changes such as the 2027 deadline for SAP’s older maintenance support.

The Trust Equation, and the Variable That Moves Fastest

The ‘trust equation,’ a framework from the consulting-advisory literature, breaks client trust into three things that build it: credibility, reliability, and how close the relationship actually feels, divided by how much the consultancy appears to be looking after its own interest. Scope extended, upselling that shows up right when the client is vulnerable, billable hours protected over the client’s own need: a client notices this faster than any single technical mistake.

How a serious problem gets handled matters more than whether it happened at all. Telling a client about a slipped deadline before they find out elsewhere is different from being caught out, and it’s the kind of peak moment a relationship gets judged months later. A vague reassurance costs more than an honest account of the risk, because when the gap between what was promised and what happened becomes apparent, it is interpreted as a broken promise rather than a disappointment.

The Unwritten Verdict

A steering committee sponsor isn’t the only person forming an opinion, and a consultancy that treats them as the whole relationship misses most of what actually decides the next contract.

At least four or five people typically weigh in: the sponsor, the steering committee, the client’s IT staff running the system day to day, the end users, and increasingly procurement or vendor management.

The IT staff and end users, in particular, form a verdict in conversations the consultancy never hears, long after the delivery team has packed up and gone. That verdict goes further than it might seem, between customer employees and staff at other potential clients: regional SAP user groups give client-side staff a channel to compare notes on consultancies with peers at other companies, outside anything the consultancy controls.

In the DACH market, that verdict now includes something new. ISG’s 2026 research found German enterprises tightening governance over their SAP programs, demanding clear audit evidence and a defined split of responsibility between the client, the hyperscaler, and the service provider. A consultancy’s governance behavior counts toward that judgment now too, alongside whether the system actually works.

The consultancies that manage this well keep each of these groups informed in a way tailored to them, rather than sending one update broadcast to all of them.

In general, a sponsor wants outcomes framed in business terms, IT staff want technical transparency and early warning when something goes wrong, and users mostly want evidence that somebody listened to them and proof that the new system makes their working life easier. Who hears about a problem first, in what order, and how fast, deserves the same amount of thought as the outcome framing does.

The stakeholder maps that hold up are the ones kept current through the project, rather than filed away after kickoff. Do that, and a key client-side team member’s move to a new role, inside the client or at a different employer, becomes a lead for new work, provided the relationship was actually kept up after their part in the project ended.

Why the Best Sellers Often Lose Their Own Clients

Strong new-business performance and client retention don’t have to trade off against each other.

From outside, the pattern looks like a question of where attention and reward get allocated inside the firm, more than any inherent tension between sourcing new opportunities and relationship management.

Where a commercial culture rewards new wins visibly (a signed contract is celebrated, or a bonus is paid) account growth can end up tracked with far less visibility, and delivery teams get staffed, evaluated, and moved onto the next sale the moment a project closes. Left unaddressed, that gap can open up account after account, rather than staying an occasional oversight.

That doesn’t stay hidden for long in a market as networked as SAP consulting. Former clients and the consultants who served them turn up in the same user-group conversations, the same LinkedIn threads, sometimes the same next employer. A firm known for winning new logos while quietly losing its old ones gets noticed by exactly the people whose opinion decides the next contract.

Repeat engagements also work as a visible signal to other potential clients of how the relationship actually performed, which gives them a value beyond the revenue they represent on their own.

What the Firms That Keep Clients Actually Do

Account development starts while the engagement is still running, not in its final weeks. The strongest firms schedule carefully structured reviews that run alongside formal project governance rather than replacing it, timed to match the client’s own planning cycle instead of a fixed date on the consultancy’s calendar.

They usually feature data the client has already seen, so the conversation covers strategy rather than repeating a status report. They also ask a harder question than most firms manage: where is this engagement falling short, from the client’s side, right now.

Contact continues through the quiet stretch between engagements too, and it carries something the client can actually use, not a thinly disguised sales call. The firms getting this right keep updates as transparent as the situation allows. When something genuinely goes wrong, honest, visible correction does more for the relationship than pretending nothing happened.

The same firms treat a strong relationship as something to draw on. They ask for a reference. They propose a joint case study, or a session co-presented at a user-group event. A satisfied client who never gets asked to vouch for the firm represents value nobody collected, and this kind of activity can be beneficial to both parties.

Turning Goodwill Into a System

Four practices distinguish the firms described above, and each one sits with a manager or a practice lead rather than an individual consultant.

They name a relationship owner separate from the delivery lead, with an actual handover conversation at the point an engagement closes.

They build a contact cadence, one month, three months, six months after go-live, into the engagement plan itself, rather than leaving it to whoever happens to remember.

They send someone back to check the original business case against what the system actually delivered, instead of treating technical acceptance as the finish line.

They give account growth the same internal visibility as a new-logo win, reflected in commission design and in what gets reported to leadership.

One more practice belongs in the same picture: tracking, for every major client, roughly where they sit on their own SAP path: stabilizing a recent go-live, planning a second rollout, weighing a cloud migration, or looking at a new product area.

A firm that tracks this brings the next piece of work to the client’s attention. A firm that doesn’t waits for an invitation to bid once the client has already started calling around.

A short check makes the pattern visible either way. Take any client the firm delivered for in the last two years. Name the person who owns that relationship today. Ask whether the client could name them too. Then ask whether anyone at the firm could say, with any confidence, where that client sits on their own SAP roadmap right now.

IgniteSAP works with a number of SAP consultancies on optimizing their talent pipeline, matching practices with consultants who bring the depth a role needs now, and the capacity to grow as part of their organization. If that kind of staffing support would help your practice, contact us on LinkedIn.