Why do techs complain about IT service platforms?

In Episode 67 of The Force Field Podcast I asked techs who work for web-based service platforms if they consider themselves contractors, vendors, commodities or customers. I brought this question up years ago in the now defunct OnForce forums and it was quite an interesting debate.

The platforms have become more established since then and after ten years of web-based entities like OnForce, there is almost a whole new generation of techs using them, so I thought it was a good time to bring up the topic again. I created polls and discussion topics in several social media venues, including one in the Force Field Forums. Once again, the results were, uh, interesting.

I was somewhat frustrated with the responses the first go-around on the old OnForce forums, simply because I was so sure of my convictions that it was almost inconceivable to me that anyone except some less informed employees of the platforms would disagree. I was wrong.

This time would be different, I told myself, based on years of complaints from some current and former platform techs who often found themselves on the short end of the stick when attempting to deal with these companies. These techs were frustrated with the perceived discriminatory policies and practices of the platforms, who seemed to clearly favor the "Buyers" or clients over the techs, particularly in regards to disputes between the two parties. So, I took up the topic again, this time on The Force Field.

I polled the techs and asked the following question: Are you a contractor, a vendor, a commodity or customer? I clearly defined each term, discussed each in detail and drew the seemingly obvious conclusion that techs who worked on service platforms were, indeed, all of the above. After all the complaining from techs about the issue and what I thought was an open-and-shut case, I expected almost unanimous agreement from the platform techs. I was wrong again. According to the polls and responses, a majority of techs only consider themselves contractors. Almost none of them also consider themselves customers!

As I said in the podcast, when you pay a fee on the platform, you are buying something from the platform. The techs pay to play on the platforms. This makes the techs customers of the platforms. As a customer, the tech has a right to be upset and complain when the platform they pay to play on does not treat them the same as they would a client on the other side of the platform. That is perfectly understandable. However, according to the comments and polls, the majority of platform techs don't consider themselves customers. If so, why are they complaining as if they are? That is what floored me.

Either you are a customer or you are not. If you don't think you are customer on the platform, you have no reason to complain about it when you aren't treated like one. It's that simple.

According to the feedback, these platform techs who complain that the IT service platforms don't treat them as well as they do the clients don't consider themselves worthy of such status. So, why do these techs complain at all?

It was all very puzzling. Then something occurred to me. I missed one very important concept and one very important term.

A good business should favor the customer. I stated this in the show. It's just good business. However, there is an important caveat to consider. The type of business we are discussing calls itself a platform.

A platform is defined as a raised, level surface on which someone or something can stand or perform. There are many different types of platforms, but they all do essentially the same thing. They provide a flat, level base or environment from which anyone or anything, or a combination thereof, can operate.

The key word here is level. Platforms are supposed to be level, with equal opportunity and access for everyone and everything that uses them. They aren't supposed to be tilted or skewed in one way or another in order to give everyone equal footing and an equal position on the platform. In business, that means everyone on the platform should be treated the same. However, that's not how the typical IT service platform operates.

It is no secret that many of the online IT service platforms and so-called "marketplaces" treat their clients or "Buyers" very differently than they do their techs. The clients are coddled and given every consideration of courtesy while the techs are generally treated as expendable extras. There is no conjecture on this one; it's a well documented fact. The buyers are well cared for, and the techs, well, except for a few favored fellows (or ladies), not so much. This has been a point of contention since the days of ComputerRepair.com over ten years ago, and one that is often discussed in various platform centric newsgroups and forums across the web, including The Force Field Forums.

When a company calls itself a platform, it sets the expectation that it will be a level playing field with no preference to any party in a transaction, and will have little, if anything to do with the transaction at all. They call themselves platforms, but are they? That is the real argument, and there are many technicians who work them who contend that these platforms are not level at all.

A platform that isn't level isn't really a platform by definition. This is why platform techs do not consider themselves customers, but some techs complain that the platforms treat them differently from the customers who are the clients. Their point? It's not about being treated like a customer, it's about paying to play on a level platform.

We'll discuss this further in a future episode of The Force Field.


#5 Why do techs complain about IT service platforms?Niamh 2015-11-26 16:09
this was an extremely good post.
#4 Why do techs complain about IT service platforms?Bruce 2015-02-03 22:40
Thanks for sharing your thoughts on why techs complain about.
#3 Why do techs complain about IT service platforms?Mittie 2014-11-28 16:59
Awesome article.
#2 Why do techs complain about IT service platforms?Antwan 2014-11-24 14:57
I would like to thank you for the efforts you have put in writing this.
#1 OwnerTom 2014-08-05 01:22
I have used many platforms for many years. When I first started, I would take service calls all the time. I was always in a rush and anxious to be the first to click "accept" so no other tech would get it before me.

After a few months, I realized that I could do a third of the work and make the same money. Techs frequently complain about the low rates. Here is my tip. Do NOT take them for a low rate. I never, at least 99% of the time, never take a call at the published rate. I always respond if I am able to do the call. However, I triple their published price. Yes, I triple it. Sometimes more. I had one the other day come up for $75. I sent a counter offer of $350. An hour later, I was at the service call. I was there for a total of one hour. That's it. $350 for one hour. I do this all the time. I don't make anymore than when I was taking all the calls, but I am not making any less either. I just work less. Sure, I have had a couple get mad at me for making such a high offer, but at the end of the day, I have made it so they need me more than I need them. When you get to that point, you control your prices. For me personally, I have a minimum of $150 for 99% of my calls and try to stay around $95 per hour. Though I do take some for $65 per hour every now and again.

What you have to remember is, these companies have service contracts with "service level agreements" in their contract. They have to meet a certain level of service or they take a hit on their contract. If you are the only candy store in town, you can charge what you want. If there is more than one candy store and all of them charge a premium for their services, well, the candy stores make a good living. So before you take that next call, bump it up. Try my method for a three month period and you will want to cook me a steak dinner and buy me a beer. Why not? You have a lot of free time now!

Add comment

Comments submitted by unregistered users will be held for review before they are approved.

Security code

Strict Standards: Non-static method modhdArticleHelper::getTheArticle() should not be called statically in /home/content/08/9890508/html/portal/modules/mod_articlemod/mod_articlemod.php on line 5

Strict Standards: Only variables should be assigned by reference in /home/content/08/9890508/html/portal/modules/mod_articlemod/helper.php on line 9

Free White Papers

The Force Field Podcast

Strict Standards: Non-static method modhdArticleHelper::getTheArticle() should not be called statically in /home/content/08/9890508/html/portal/modules/mod_articlemod/mod_articlemod.php on line 5

Strict Standards: Only variables should be assigned by reference in /home/content/08/9890508/html/portal/modules/mod_articlemod/helper.php on line 9

Listen to the latest episodes of The Force Field now!

The Force Field Podcast Badge
 Proud member of The TechPodcasts Network
2013 Top 100 Podcast Badges

Strict Standards: Non-static method modhdArticleHelper::getTheArticle() should not be called statically in /home/content/08/9890508/html/portal/modules/mod_articlemod/mod_articlemod.php on line 5

Strict Standards: Only variables should be assigned by reference in /home/content/08/9890508/html/portal/modules/mod_articlemod/helper.php on line 9