There has recently been emerging a new business model in the service team industry which I highly disagree with and believe will be detrimental to the market.
This suggestion is in full reference of this thread starting from post #5. - https://www.mc-market.org/threads/350815/
It was just a little debate between me and Cal on why I disagree to this scheme, but I’ll be paraphrasing some of my points from there to here to emphasise my suggestion.
This new business model which I highly disagree with is an ‘organisation’ owning multiple service ‘teams’ which are all linked together behind the scenes. What I mean by when they are linked together behind the scenes, is that in reality under the false facade that there are multiple ‘teams’, each of them are all run by the same exact singular team.
I don’t believe I should copy and paste my entire post hence I’ll just link it. But all my strongest points against this model can be found here - https://www.mc-market.org/threads/350815/#post-3067851
To reiterate some of the points in that post. Anyone can setup the infrastructure for this multi-service team organisation model. The fact there are already so many teams in circulation is because they are fairly easy to setup. Hypothetically speaking, I can open up 10 ‘teams’ myself and have 10 advertising threads in every section of MCM. But in reality, every single ‘team’ has the same freelancers and managers behind it. They are offering the exact same service with the exact same quality with the same freelancers across multiple ‘teams’. This is abusable and there are no rules to prevent this. The amount of multiple ‘teams’ for more exposure can potentially be limitless. If abused, the whole market will just be flooded.
If you think about it, this is just a very elaborate plan to advertise the same team over and over again. It may even be on grounds to infringe the duplicated threads rule. Yes, the branding may be different for each ‘team’, but they are all connected to one central team. If an ‘organisation’ owns 5 service teams, all 5 of those service teams will offer the same quality with the same freelancers and managers backing it.
Again, this is abusable and can get out of hand if enough people start doing this. I’d like to state that I’m not against service teams itself, but this sort of duplication tactic by hiding under the pretence of an ‘organisation’ for more exposure is just wrong.
We already have an ‘organisation’ called Slashy doing this - https://gyazo.com/f44ed3d8181f3571cc6f23ec40a64999
Now we have Above pulling a similar stunt with Prime and Avast (and they plan to add more). I would not be surprised in the future if more ‘organisations’ pop up where they will abuse this tactic for multiple threads in a section for more exposure.
To conclude, I suggest a rule to regulate such activities. I’m not sure exactly what should be restricted, and it would be great if you guys can suggest some ideas. My own solution would be that users should only be allowed to maintain a single service team (this could also apply to other businesses too possibly) at any given point. This is to prevent multiple rebranded duplicates popping up which will potentially flood the market.
This suggestion is in full reference of this thread starting from post #5. - https://www.mc-market.org/threads/350815/
It was just a little debate between me and Cal on why I disagree to this scheme, but I’ll be paraphrasing some of my points from there to here to emphasise my suggestion.
This new business model which I highly disagree with is an ‘organisation’ owning multiple service ‘teams’ which are all linked together behind the scenes. What I mean by when they are linked together behind the scenes, is that in reality under the false facade that there are multiple ‘teams’, each of them are all run by the same exact singular team.
I don’t believe I should copy and paste my entire post hence I’ll just link it. But all my strongest points against this model can be found here - https://www.mc-market.org/threads/350815/#post-3067851
To reiterate some of the points in that post. Anyone can setup the infrastructure for this multi-service team organisation model. The fact there are already so many teams in circulation is because they are fairly easy to setup. Hypothetically speaking, I can open up 10 ‘teams’ myself and have 10 advertising threads in every section of MCM. But in reality, every single ‘team’ has the same freelancers and managers behind it. They are offering the exact same service with the exact same quality with the same freelancers across multiple ‘teams’. This is abusable and there are no rules to prevent this. The amount of multiple ‘teams’ for more exposure can potentially be limitless. If abused, the whole market will just be flooded.
If you think about it, this is just a very elaborate plan to advertise the same team over and over again. It may even be on grounds to infringe the duplicated threads rule. Yes, the branding may be different for each ‘team’, but they are all connected to one central team. If an ‘organisation’ owns 5 service teams, all 5 of those service teams will offer the same quality with the same freelancers and managers backing it.
Again, this is abusable and can get out of hand if enough people start doing this. I’d like to state that I’m not against service teams itself, but this sort of duplication tactic by hiding under the pretence of an ‘organisation’ for more exposure is just wrong.
We already have an ‘organisation’ called Slashy doing this - https://gyazo.com/f44ed3d8181f3571cc6f23ec40a64999
Now we have Above pulling a similar stunt with Prime and Avast (and they plan to add more). I would not be surprised in the future if more ‘organisations’ pop up where they will abuse this tactic for multiple threads in a section for more exposure.
To conclude, I suggest a rule to regulate such activities. I’m not sure exactly what should be restricted, and it would be great if you guys can suggest some ideas. My own solution would be that users should only be allowed to maintain a single service team (this could also apply to other businesses too possibly) at any given point. This is to prevent multiple rebranded duplicates popping up which will potentially flood the market.
- Type
- Suggestion
- Status
- Implemented
Last edited:
