The call lasted eleven minutes.

I remember the exact number because I checked my phone afterwards, trying to work out how a 14 month programme could be ended in less time than it took me to make my morning coffee.

The client's operations director was polite. Professional. He thanked me for our work, said the delivery had been strong and acknowledged the team had hit every milestone we'd committed to. Then he said they were going in a different direction.

I asked what we could have done differently. He paused - the kind of pause that tells you the person already has the answer but isn't sure you're ready to hear it and then he said: "Aman, we never really felt like you were on our side."

I had 47 status reports. 14 months of green dashboards. A signed acceptance certificate from their own technical team.

I had delivered the project. I had not delivered the relationship. And in enterprise technology, those are not the same thing.

We had a 22-person team split across three locations. The scope was a £1.1M platform migration for a financial services client - complex, regulated, politically sensitive. We ran 28 sprints over 14 months. We closed everyone on time or early. Defect rate at go-live: 0.3%, against an industry average of around 4%. The client's own QA team signed off on every release. We finished four days before the contractual deadline.

By any objective delivery measure, this was a success. The project management certification bodies would have used it as a case study.

After the call ended, I did something I had never done before. I went back through 14 months of client communication, every email thread, every meeting note, every informal message and I read it as if I were the client.

I found six things that should have been red flags. None of them were on my RAID log. All of them were visible in real time. I had looked at all of them and seen nothing.

🤔 QUIZ

Q: You are running a programme. Delivery is on track. The client has never formally complained. But over the past 6 weeks, you have noticed the following:

What is the most accurate interpretation of these three signals together?

A)  Everything is fine — no news is good news
B)  The client is busy internally, it has nothing to do with you
C)  One of these signals is a warning, the other two are probably coincidence
D)  All 3 together form a specific pattern that typically precedes a client relationship breakdown — and you have a narrow window to act

👉  Take a moment. The answer is at the end of this issue

After losing this client, I made a decision. I would keep tracking delivery metrics, but I would add a second layer of measurement that had nothing to do with scope, budget, or timeline. I called it the Relationship Health Check. It takes 15 minutes every two weeks and has flagged a relationship risk on every single programme I've run since.

✅  Fix 1: The Client Engagement Audit

Every two weeks, I answer five questions about the client relationship, not the delivery:

If I cannot answer 'yes' or 'positive' to at least 4 of those 5, I schedule a relationship call within the week not a status call. A conversation about how they are experiencing the engagement. Not the deliverables. The experience.

✅  Fix 2: The Invisible Stakeholder Map

On the programme we lost, the operations director who called to fire us was not the person we had been managing. We had been managing his deputy. The director, the person with actual authority over the renewal decision, had formed an opinion of us almost entirely from second-hand information.

I now build two stakeholder maps at the start of every engagement:

The second list is the one that matters. I built a specific communication plan for those people — a cadence of brief, business-level updates that reach them directly rather than being filtered through their deputies. Not delivery metrics. Business outcomes. What we have changed in their organisation. What problems we have solved that they care about?

✅  Fix 3: The 90-Day Relationship Conversation

Every 90 days, I now have one conversation with the most senior client contact that is explicitly not a status call. I call it the 'bigger picture' conversation and I open it the same way every time:

The answer to that question tells you three things simultaneously: whether the client can articulate the value you are delivering, whether they are invested enough in the outcome to have thought about it, and whether your framing of the work matches theirs.

On the programme we lost, I know with certainty that the operations director could not have answered that question. That is not his failure. That is mine. I never gave him the language.

Pick your longest-running active client engagement. The one where delivery feels smooth and you haven't worried about the relationship in a while. Now answer these three questions honestly:

If you hesitated on any of those 3: the relationship is more fragile than your dashboard suggests. Not because delivery is failing. Because delivery is all you've been managing.

⚡  1 tool:  Grain.xyz — records and transcribes client calls automatically. I use it specifically to re-read client language patterns over time. The pronoun shift from 'we' to 'the project' becomes visible in black and white

📊  1 number:  According to Bain & Company research, a 5% increase in client retention increases profits by 25–95%. The industry spends the vast majority of its management attention on acquisition and almost none on the relationship mechanics that drive retention.

💬  1 quote:  "People will forget what you said, people will forget what you did, but people will never forget how you made them feel." — Maya Angelou. I have never read a sentence that applies more directly to client delivery than this one.

If you’ve found the above information valuable, then hit the forward button on this email and share it with your network to help me grow.

or copy and paste this URL:
https://amansinghpro.beehiiv.com/subscribe

D — all 3 signals together

Any one of them in isolation is inconclusive. But all three together declining senior attendance, slower responses, and zero scope requests form a specific pattern that I now recognise immediately. It means the client has psychologically moved from 'invested partner' to 'managing an existing obligation'. They are not angry. They are not about to escalate. They are quietly preparing not to renew. That is the most dangerous client state because it generates no complaints for you to respond to.

The window to recover from this state is approximately 6–8 weeks. After that, the internal narrative has solidified and the decision is effectively made before the contract end date conversation even begins. The prompt fix is not a delivery action. It is a relationship call senior to senior, off the record, about how they are experiencing the engagement.

The operations director who called to fire us was not wrong to leave. We had delivered what was in the contract. We had not delivered what was underneath the contract, the confidence that we understood their business, not just their backlog. That we were on their side, not just on their payroll.

Most delivery leaders I know are excellent at managing projects. Far fewer are excellent at managing the human being at the other end of the engagement, who has to justify your existence to their own board every quarter.

The certification will never teach you that. The only thing that teaches you that is losing a client you thought you had earned.

One question before you go:

Until next Wednesday
Aman
www.amansingh.pro