Author: Rob Broadhead

  • When To Fire A Client

    When To Fire A Client

    Recent events have me thinking about the pros and cons of when to fire a client. It is often a difficult decision to make and even more complicated than accepting a contract or customer. The challenge in accepting a customer includes questions such as whether you can take on the additional work or the profitability of the work. Once you land a customer, you are used to that revenue and level of work. Yes, even if that work includes headaches.

    Unprofitable? Fire A Client

    While there are challenges to it, a client that is not profitable is the easiest to get rid of. There is a bottom line to consider and a black or white decision. The larger obstacle is deciding to get rid of a profitable client but a pain. We all know a customer like this. They do the ‘right” thing and pay bills on time. However, they constantly disrupt plans, cause us to stress, or give us steady fodder for complaints. First, let’s assume we are not merely whining. That is not only possible but is something I see more often than I want to admit. Yes, even when I am the none doing the whining. Next, we need to evaluate the cost of the stress or other negative impact.

    Is This self-inflicted?

    Once we have decided this is not about profit or paying bills, we need to assess the source of the stress honestly. In IT, there are many reasons for us to experience stress in a project. These include timeframes, deadlines, technology platforms, version hell, and normal interpersonal challenges. In my experience, the technology challenges are worth working through. You will see these with other customers. Better yet, a solution that reduces obstacles inherent to a technology platform is re-usable and can win future clients. The steps required for these solutions can be painful. However, the reward can be substantial and worth the temporary stress.

    While it takes two to tango, I have found that we can often place the majority of interpersonal challenges among customers and vendors on one side or the other. Let’s start with the case where we are the problem. This situation can arise when a project is outside of our skillset, goes beyond our resources, or is generally not to our liking. The quick solution in these cases might be termed as “suck it up, buttercup.” However, that may not be the best approach. While we all have some level of ‘grunt work” or other unpleasantness to handle as part of our job, that is not always required. When we have a customer taking us in a direction that does not suit us, it is worthwhile to send them to another vendor. Happy workers are more productive. Why waste our good workers on things that drain them without due cause. Profit is not enough. Make sure the overall benefit is there for any given project.

    They Are A Toxic Client

    The heading for this section is a bit harsh. A bad client is not necessarily toxic. Nevertheless, most bad clients have some toxicity in their company that makes them a challenge. The flaw may be in their communication, culture, or just an individual. We will leave the last option for last. When this problem is the client, it is worthwhile to assess how much pain and suffering they cause. Likewise, we need to assess any positives that may come from a successful project. Sometimes success in a bad situation can be a game-changer for our company’s success. On the other hand, a doomed project can sink an enterprise. We need to make sure we can overcome the challenges and be legitimately successful if we move forward.

    Do Not Be A Quitter

    I have known people to give up on marriages and long-term friendships over minor things, but not customers. It almost goes unsaid that we should not fire a client too hastily. In my experience, a customer is held on to longer than they should instead of the other extreme. That being said, a difficult project or situation is not enough to turn them away once we have started. The focus should be on whether or not the customer relationship can be successful. Likewise, there is some point where it has to be profitable to both parties. When you take a loss with a customer for no sound reason, then it is simply charity. Nevertheless, we should not walk away abruptly. Even a bad relationship deserves closure. Please find a way to transition them to self-sufficiency or another vendor that has a (preferably better) chance of success. You will not regret it.

    The Value Of Loyalty

    Before we wrap up these thoughts, I feel loyalty is worth a mention. Some situations go sour or bad over time, and those that experience bumpy roads or obstacles. A vendor that takes on those periods of challenge and sticks with their customers even in the bad times will often find rewards at the end. These rewards may not come from that difficult customer, but they do come. There are lessons learned and “brownie points” that we earn when we are known to be a vendor that cares about our customers. Think of major brands, and you will often find that sentiment buried somewhere in the branding. People buy from those they know, like, and trust. Trust is earned in the trenches, not through the easy times.

    A Way Forward

    All of these thoughts boil down to some steps you can take to assess whether to fire a client.

    • Is it us or them?
    • Can a solution be found that benefits both parties?
    • What are the benefits of staying as opposed to firing them?
    • How do we extract ourselves from the relationship with a minimum of damage and ill will?

    These may seem simple. However, each of the above bullet points can be very nuanced and complex.

  • The Cloud As A Launching Pad – Leverage The Cloud

    The Cloud As A Launching Pad – Leverage The Cloud

    I looked at the Parler-Amazon situation in a previous blog post as a cautionary tale. The focus was on the negative side of that situation and finding ways to avoid vendor lock-in. In this article, I will look at the positive side of that situation. Parler would likely not exist at all and definitely would not be the same if not for Amazon. This is a tale of how we can leverage the cloud to take our business to new heights.

    Leverage The Cloud To Plan Big

    In the past, technology required a lot of setup, configuration, negotiations, and then waiting for our order to be fulfilled. Those steps can be accomplished in minutes and provide us a solution at scale with cloud solutions. Yes, opening an Amazon account and getting through the verification steps may take a day or two. However, once we have that out of the way, we can build an enterprise system without a need to order servers or negotiate deals. We also can build a solution for our small business today that grows to support our enterprise tomorrow. Better yet, this is not something only Amazon provides. There are countless full-scale providers like Microsoft and Google and niche solutions like Salesforce, NetSuite, and so many others. We have the opportunity to start small and grow as big as our vision allow

    Scaled Technology

    In the Parler example, they started with a need for a platform that supported messages and profiles for a user base of maybe thousands. When that suddenly grew, they could leverage the cloud and instantly support that growth of server requirements. We could gloss right over that fact, but it would miss how critical SAAS and cloud solutions can be to organizations’ “overnight success.” That would ignore a history of businesses that were not ready for substantial growth, and they ended up folding instead of becoming a success. We can look back a few decades to the Internet boom of the late ’90s. There we find numerous examples of companies that bet big on marketing, got a hit, and then collapsed due to a lack of ability to support rapid growth.

    A Positive Focus

    It is easy to point to big organizations like Apple, Amazon, Microsoft, Google, and even IBM (remember them?) as behemoths that squash the little guys. On the other hand, part of their growth has come from the platform they provide to many of those same little guys. It is astounding how many companies have e-commerce capabilities and a way to connect to customers. That is often because of these giant companies and their offerings. Of course, the platforms will take their cut. For example, it is only fair that Apple should get a share of sales on the Apple store. We can argue about how much (or little) is “reasonable.” Nevertheless, that does not remove the fact that so many companies and individuals rely on these platforms to exist. That is where the previous warning against single vendor lock-in came from.

    Know Your Place

    Therefore, we often need these big vendor relationships to get our business off the ground. We are wise to be wary of the partnerships we put in place. However, we also can use them to think bigger than we have in the past. The promise of the cloud is a near-infinite ability to scale a solution that is designed right. Do not let that be ignored as you consider how to position your product or organization. We can paint these platforms as the next monopolistic wave. On the other hand, we are better served by finding ways to leverage what they provide. That allows us to get our own organization off the ground and on a solid footing.

  • Select Multiple Vendors For A Reliable Foundation

    Select Multiple Vendors For A Reliable Foundation

    Recent political events in the United States have seen organizations and people “canceled” or de-platformed. While one can look at these as situations a business should avoid at all costs (getting swept into politics), it is an excellent cautionary tale. The Achilles heel of many of these organizations is a reliance on a single vendor for a key facet of their business. No one provider will ever give you the flexibility of multiple vendors.

    Vendor Lock-in

    The concept of vendor lock-in is not new. However, it has gotten fuzzy in areas like Cloud computing and businesses that are “too big to fail.” The Parler example falls exactly in this zone. They relied on Amazon AWS for their data infrastructure and went dark when Amazon decided that there was a breach of the user agreement. Your thoughts on Amazon’s actions do not save the folks at Parler from making a critical mistake. They put all of their eggs in the Amazon basket. They had vendor lock-in even though I bet they never considered it as such.

    Yes, you can point to this as a case of letting politics guide a business. However, this could happen if Amazon sold off the AWS products, or even if someone at Amazon (or within your organization) hit the wrong switch. There are countless tales of sites that went down for a period of time because of spam-blocking or other automated processes triggered by a simple mistake. You do not have to be in the news to have something shut down your access to a product.

    Multiple Vendors And Disaster Recovery

    The whole purpose of creating a DR plan is to consider what happens if you lose a key vendor or resource for any reason. It could be a natural disaster, one of Public Relations, or any other reason. The point is to address the problem of losing that resource. A good disaster recovery plan considers these events and looks to multiple vendors and their locations. Some DR plans rely on the stability a cloud provider gives you. Amazon, Google, Microsoft, and other providers have multiple data centers spread across the globe with redundancies built to avoid downtime. In some cases, that is sufficient. We pay these vendors money to handle our DR headaches. However, that does lock us into those vendors when we choose only one.

    Cloud To The Rescue

    One of the benefits of cloud providers is that they allow us to scale up our usage. We can have a tiny server at minimal cost and powerful ones that are costly but drive our business. Thus, smaller businesses can get some of the Cloud’s enterprise features without a high cost up-front. This same benefit should lead us to look at multiple vendors, even with the smallest of businesses. This concept also extends out beyond our server needs. We can embrace the cloud to handle many of our needs. For most businesses, this includes things like payment providers, customer communications, billing, and payroll. Many vendors want you to rely on them and will even provide attractive packages. However, make sure you understand the risks involved.

    It Is Your Data

    First and foremost, make sure any vendor agreement includes a way for you to get your data. The Parler case included Amazon, stating they would allow access to the application data and even help Parler migrate off their platform. That may save the business from immediate death. Think of what would happen if you lost all of your financial or customer data. You should ensure that any licensing includes your ability to own your data and content. There should also be language that restricts a vendor from being able to leverage or use the same. Content platforms are famous for this, including many social networks. They have language that allows them to share or use your content to promote their platform. If you get paid for that usage, then that is good. However, you could find yourself effectively funding a vendor’s marketing campaign or at least providing essential content.

    Finally, make sure you test your access to data early and often. Exports and APIs are excellent tools. On the other hand, they can change and cause data loss or impact recovery times. You might also find that you need a tool or solution to do something with that data. If you can not afford to have the migration tools in place or it is not practical to migrate data regularly, at least ensure you have a reasonable estimate of the time and cost in a DR situation.