How to Keep Your IT Customers When Things Don't Go According to Plan

If you've spent any length of time running an IT business, you'll know that however good your products, services and people are, occasionally things won't go according to plan.

A product fails, a delivery is late, a software problem affects a customer, a service doesn't perform as expected, a supplier lets you down or somebody simply makes a mistake. When you're providing complex technology products and services, some problems are inevitable. What matters is what happens next.

During the years my fellow co-founders and I were building our IT business, I dealt with plenty of difficult customer situations. Some involved products or services we supplied directly, while others involved manufacturers, suppliers or other parts of a complicated supply chain that we didn't completely control.

I've been in situations where a customer was extremely unhappy and we couldn't immediately fix the underlying problem. I've even been on the brink of losing a customer because of something that had gone wrong. Those situations aren't pleasant, but they taught me something important: customers don't only remember what went wrong. They remember how you behaved when it went wrong.

Handled badly, a problem can damage a relationship you've spent years building. Handled well, I've found that sometimes the relationship can actually become stronger.

Take Ownership of the Problem

When something goes wrong, it's very easy to explain why it isn't your fault. The manufacturer hasn't delivered, the software provider has a problem, a third-party service has failed or somebody further down the supply chain has made a mistake.

Those things may all be completely true, and the customer may eventually need to understand what has happened. But they're rarely the best place to start because, from the customer's perspective, they bought the solution from you.

One of the most useful things you can do is therefore take ownership of helping them through the problem, even when you don't have complete control over the cause. That doesn't mean accepting responsibility for something you genuinely haven't done. It means taking responsibility for what you can do next.

Investigate the problem, speak to the supplier, escalate it, look for alternatives and find a workaround if one exists. Most importantly, make it clear to the customer that somebody is taking responsibility for moving things forward.

Communicate Before the Customer Has to Chase You

This was probably one of the most important lessons I learned.

When you don't yet have an answer, there's a temptation to wait until you have something useful to tell the customer. I found that doing the opposite was often much better. There were occasions when I would phone a customer every day during a serious problem, even when there wasn't a significant development to report.

The conversation might effectively have been: “We haven't resolved it yet, but here's what we've done today, here's what we're doing next and I'll update you again tomorrow.”

Imagine being the customer on the other side of the problem. Their system isn't working properly, a project has been delayed or their own customers or employees are being affected. If they hear nothing from you, uncertainty grows. They start wondering whether you're working on it, whether somebody has forgotten or whether they need to chase you again.

Proactive communication removes some of that uncertainty. The customer might still be unhappy about the problem — and quite rightly — but at least they know somebody is dealing with it.

Don't make an unhappy customer chase you for an update.

Be Honest About What You Know

There's another temptation when dealing with a difficult customer situation, and that's to offer reassurance by promising something you don't really know you can deliver.

You want to make the customer feel better, so it's very easy to say, “It should be fixed tomorrow.” But if you don't really know that, tomorrow may arrive and the problem still isn't fixed. You now have two problems: the original issue and a customer whose confidence in what you're telling them has been damaged.

I learned that being honest was usually far more effective. If you don't know when something will be resolved, say so. Explain what you do know, what you don't know and what you're doing to find out.

You can still be positive and reassuring without making promises you can't control. Trust isn't built by pretending everything is okay. Sometimes it's built by being prepared to say: “I don't have the answer yet, but we're working on it and I'll keep you informed.”

Understand the Customer's Problem, Not Just Your Problem

This is particularly important in technology businesses because, when something technical goes wrong, it's natural for us to focus on the technical problem. A server has failed. Software isn't behaving correctly. Hardware hasn't arrived. A network connection is down. An integration has stopped working.

That's our problem. But what's the customer's problem?

Perhaps their warehouse can't dispatch orders, their engineers can't access the information they need, their sales team can't process something, a project deadline is at risk or their customers are now complaining to them.

Understanding that wider impact changes the conversation. Instead of simply talking about what has failed technically, you can start asking what you can do to reduce the impact while the underlying problem is being resolved.

Sometimes a temporary workaround isn't technically elegant, but if it helps the customer keep operating, it can be extremely valuable. That requires you to understand the customer's business, not simply the technology you've supplied.

Don't Disappear When the Conversation Gets Difficult

It's easy to speak to customers when everything is going well. The real test often comes when it isn't.

An unhappy customer conversation can be uncomfortable, particularly when you don't yet have the answer they want. But that's precisely when visibility matters. I've always believed that if a customer has a serious problem, somebody needs to be prepared to stand in front of them — metaphorically or literally — and have the difficult conversation.

Listen to their frustration, resist the temptation to become defensive and try to understand what they're experiencing before focusing the conversation on what happens next. You might not be able to make the problem disappear immediately, but you can make sure the customer doesn't feel that you have disappeared.

There is a wider leadership lesson here too. As an IT business grows, the owner shouldn't be the only person capable of having these conversations. Developing people who can listen, think and take responsibility is part of building a stronger team. I explore that further in How Better Leadership Conversations Can Reduce Owner Dependency in an IT Business.

Once It's Fixed, Learn From It

Resolving the immediate problem shouldn't necessarily be the end of the story. Once the pressure has gone, there's an opportunity to step back and ask: what can we learn from this?

Could we have spotted the problem earlier? Could we have communicated more effectively? Was there too much reliance on one supplier? Do we need a better escalation process? Was important information sitting in one person's head? Does something need documenting? Could the customer have been given an alternative more quickly?

This is where a difficult customer experience can contribute to building a stronger business. The objective isn't to create a company where nothing ever goes wrong — I'm not sure such a business exists. It's to create one that learns when things do go wrong.

Make Sure the Customer Relationship Belongs to the Business

There's another lesson I can see more clearly looking back at our own business journey.

For many years, I personally held some very important customer relationships. Some went back a long way, and those relationships were valuable to the business. But if the owner is the person who has to step in whenever an important customer has a problem, that creates another issue: owner dependency.

You may have retained the customer, but you've also reinforced the idea that the relationship ultimately depends on you.

As our business developed, it became increasingly important for customer relationships to extend beyond the founders. Other people needed the knowledge, authority and confidence to look after customers and deal with difficult situations themselves.

That doesn't mean the owner should never become involved. There will always be situations where that's appropriate. But a strong IT business shouldn't need its owner to personally rescue every important customer relationship.

Customers need to trust the business, not just the person who owns it.

This is one of the reasons reducing owner dependency can be so important when you're building a stronger and more resilient business. I've explored that in more detail in How to Reduce Owner Dependency Before Selling Your IT Business.

Strong Customer Relationships Matter When You're Preparing for a Future Exit

If you're considering selling your IT business at some point in the future, customer relationships take on another significance.

A potential buyer isn't simply acquiring a list of company names. They'll want to understand the quality and durability of the revenue those customers generate. They'll also want to understand risks such as customer concentration, contracts, recurring revenue and how dependent important relationships are on particular individuals.

If your biggest customers have been with the business for years, have strong relationships with several members of your team and continue buying because they value the company rather than simply their relationship with you, that's very different from a customer base held together personally by the owner.

And those relationships are built over time. They're built when things are going well, of course, but they're also built — and sometimes tested most severely — when things don't go according to plan.

A Problem Can Become a Moment of Trust

I've been on the brink of losing a customer because of a problem. At the time, it certainly didn't feel like an opportunity.

But by taking ownership, looking for solutions, communicating regularly and being honest about what was happening, we managed to retain the relationship. That experience stayed with me.

You can't guarantee that every customer will stay. Sometimes a problem will cause a relationship to end regardless of what you do. But you can control how you respond: take ownership, communicate before they chase you, be honest, understand the impact on their business, stay visible when the conversation becomes difficult and, once it's resolved, learn from what happened.

Because customers remember when things don't go according to plan. But they also remember the people and businesses that stepped up when they did.

If you're beginning to think about preparing your IT business for a potential future exit, customer quality and concentration are two of the areas explored in my Exit Readiness Focus Framework, alongside areas such as recurring revenue, leadership, financial visibility, processes and owner dependency.

DOWNLOAD THE EXIT READINESS FOCUS FRAMEWORK

No email address. No sign-up. Just a practical place to start.

Build a stronger business now. Give yourself more choice later.

Leave a Reply

Your email address will not be published. Required fields are marked *

This field is mandatory

This field is mandatory

This field is mandatory

There was an error submitting your message. Please try again.

Security Check

Invalid Captcha code. Try again.

Information icon

We need your consent to load the translations

We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.