Ability to filter out service team posts
- Thread starter SpartanMight
- Start date
- Status
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.
Maybe a s-team post tag? Could either have it be public or privately shown. Either say it lets you filter out service team posts.
I just want to say the some service teams are not as bad a you make them out to be. for example, my goal with my service team is connect ten different online markets together, this improves the quality of each of the market and shows the best of them. It helps offer services across platforms the may otherwise be unavailable. Many other teams like Timeless have their own goal and aren't here to simply "mooch of" other peoples work. Many teams come with a goal in mind and have the intention of making the market (and many others) a better to place. It simply isn't fair to generalize and say that all teams should be "branded".
Last edited:
Of course the service team owner disagrees.. lame
Banned forever. Reason: Ban Evading (Vexaros)
I disagree. Your service team isn't the future and 95% of service teams are annoying and to be frank pretty horrible. Service teams aren't here to make the market a better place. They are here to make money.
oi bruv
The general idea of a service team isn't bad, but of course, it targets one group of customers.
Many experienced developers don't have the ability to negotiate, or don't have the experience and trust required for them to get the client influx they want. Even if a service team takes a huge cut (the one I manage takes a whopping 30%, largest on the market from what I've seen), that doesn't necessarily mean that it's a scam or a big steal.
Let's remember the fact that companies (that are super similar to service teams in the way they function) give you a fixed salary that is often 5x less than what they earn off you. This is the likes of IBM, Google, Microsoft, etc. They usually don't get people screaming "they are stealing money, etc", because people are used to it and IBM, Google, and Microsoft does a good job serving its clients.
This ends to a single result: Current service teams are bad because of the service.
What I've seen myself:
Why does it happen?
How can it be solved?
NOTE:
I've said this as a "service team" owner. It's your decision if you believe my arguments or consider them wrong.
Many experienced developers don't have the ability to negotiate, or don't have the experience and trust required for them to get the client influx they want. Even if a service team takes a huge cut (the one I manage takes a whopping 30%, largest on the market from what I've seen), that doesn't necessarily mean that it's a scam or a big steal.
Let's remember the fact that companies (that are super similar to service teams in the way they function) give you a fixed salary that is often 5x less than what they earn off you. This is the likes of IBM, Google, Microsoft, etc. They usually don't get people screaming "they are stealing money, etc", because people are used to it and IBM, Google, and Microsoft does a good job serving its clients.
This ends to a single result: Current service teams are bad because of the service.
What I've seen myself:
- Absolutely no customer care. Really poor support, experience, and CV. Anything that is more technical (eg: Development) usually leads to ghetto solutions. Bad long-term, not good for enterprise.
- Similar poor strategies. Get as many freelancers as you can, no matter their capabilities and get them to work on as many projects as possible. If a client gets poor support and asks for a refund, point him to your TOS. If he's still angry, give his product (along with his idea) on sale to "recuperate money" - if that isn't scammy enough.
- Absolutely no privacy - Share a project you need to be done, all those 50 unexperienced freelancers chosen in a whim get to know what you're doing. Large network? No problem, now everyone knows your plans.
- No user choice - Think a freelancer is not ready for his job? Bad luck, you can't change that. Most service teams don't allow absolutely any user choice to the client until the project is already public.
Why does it happen?
- Poor manager experience. Looked around several service teams. Most of the team leaders are not experienced as a freelancer and are not ready to lead a team.
- Bad hiring process - Get as many as you can != get the best service out there. Fewer and better-trained means happier freelancers (more work for them) and happier clients (more experienced freelancers).
- The idea that anybody can start a service team and earn a % of somebody's work for free. Sad to announce, it's more than that. It means money put in advertising, time put in hiring, PR, negotiating deals, convincing people to try your team, etc.
So many people think in that idea that it puts a huge black spot on the entire niche.
How can it be solved?
- Better customer care.
- No more douchy TOS making clients steer away from your product. Money-back guarantee if the project doesn't end up good.
- Better freelancer experience.
- Privacy for our projects.
NOTE:
I've said this as a "service team" owner. It's your decision if you believe my arguments or consider them wrong.
Last edited:
Our current thread prefixes definitely are flawed but making a small temporary fix like the one you have proposed won't really fix the underlying issue of the limitations of thread prefixes. We are developing a proper thread filtering system very soon which will be significantly better, but until then you'll just have to wait a few more weeks for that to be finished and implemented.
Denied, thanks for the suggestion
Denied, thanks for the suggestion
- Status
