We also launched a similar service in the past like 3-4 years back and trust me it doesn't work as you think. The problem is with the product-market fit. It is very hard to find the right people for your service and the fierce competition from all the major players makes it even harder.
If you are truly involved in the service then don't wait for the people to find and reach out to you, instead try to find the right audience and reach out to them. I know it is tougher than saying. We've tried it but unfortunately, it didn't work as we planned and that's why we shut it down after just 6 months.
Nevertheless, at least try it first. All the best.
Good to know that you had a try at this. Thanks for the insights. True, I agree on the part that finding PMF is the biggest challenge and on the other hand the distribution part.
Unless, we find and do better than the other players in atleast one aspect such as quality or pricing, it would not be straightforward.
We have been working for the last few weeks on building TinyApps.
A lot of us have come across situations where in we want to offload some of our work but at the same time we don't want to take the pain of finding developers, agencies and the cost that comes with it. This would help in focusing on our core work and at the same time get some bandwidth.
So, we are launching a platform where in you can post your tasks which could be just a bug fix, a simple infrastructure setup using terraform, a dashboard in react or anything related to software development for a fixed tiny price similar to the price of a coffee.
"A task which can be completed in few days i.e less than a week is generally a tiny task. It could be a bug fix, a simple crud app, a server setup etc. Ofcourse if you have something which takes more time or are not sure, don't hesitate to proceed, that becomes a medium tiny task or a big tiny task :-)"
That's not tiny. Tiny is 1-2 hours work. Tiny is something like changing a hardcoded text string in a codebase or changing something in a properties file.
True, I agree on that. Just that I used the same wording of the app to refer to the task. Tiny ideally is very small.
Might be I should change it given I will be adding additional pricing tiers as well.
Setting up the env probably eats into your margins.
Whenever I onboard a new contractor, they bill me 4+ hours just to get the thing to run on their machine and understanding the code base.
I'm curious if you're constantly having different devs, this overhead for each dev makes it less appealing on both sides of the table.
I also had someone (who I gave paid trial "tiny task") steal my codebase and post the code publicly on github to pretend to use in job interviews. Ever since then, I try to minimize the number of contractors I allow access to my source code.
How do you prevent the subcontractors from doing this?
True, any new task even though how tiny it might be, needs few hours to understand and get the local environment up.
The onboarding of a new client requires some effort even if the same devs remain the same. So in the long run it comes down to niching down to specific workflows which are profitable and which is nothing but PMF.
Given, most of the devs who I work with are from my network, the real challenge of confidentiality issues are a bit too early now. But at some point an NDA and his recent work ratings are some factors which could help in avoiding those issues. But again nothing is foolproof.
I tried to create a similar service a couple of months ago but it didn't take off. Good luck to you.
I think it needs a lot of trust before people can start posting on our platform. For example- Upwork has built the reputation for that. So, bootstrappers like ourselves can't survive that period. I think that's the reason for my failure while creating that platform.
Small suggestion: you are calling it upwork but no signups for devs is a real bummer. If you aren't ready to take outside devs yet, at least put a waiting list where devs can put their email and other info to be contacted later.
Yes, am offloading it to dev's in my network. The onboarding of freelancers needs other workflows to be setup such as payments etc before which I want to get some traction.