https://www.reddit.com/r/business/comments/1j7zgsh/whats_your_biggest_fear_when_hiring_a_freelancer/
created by lemfreewill on 10/03/2025 at 14:09 UTC
1 upvotes, 8 top-level comments (showing 8)
I asked my co-founder what the biggest issue we might face when it comes to getting a freelancer for our mvp and he talked about commitment.
I thought that was a given considering, we're gonna get freelancers but what other issues do you think might come from this? Should we just get a full-time developer instead?
Comment by Significant-Jump-466 at 10/03/2025 at 14:16 UTC
1 upvotes, 0 direct replies
I am available to fulfill your these requirements
Comment by Tiny_Arugula_5648 at 10/03/2025 at 14:23 UTC
1 upvotes, 1 direct replies
the navity of saying commitment level about a contractor building an mvp is a redflag.. Hire yourself an experienced fractional CTO consultant who can help you navigate this. The mistakes you'll avoid will more than pay for their fee. LinkedIn and your network is your best tool for finding them, not some gig website.
Even better is proof your business idea without building anything.. most MVPs fail, be smarter and don't waste the time or money. Lots of huge companies started out testing their idea on other platforms. Building something should be a response to unblocking a known opportunity, not as a means to test your guesses, expectations, hopes and dreams.. this is the point where you resist the urge to go "but our app will do X, there's no way to test that without building", I assure you you won't feel that way after your 2nd or 3rd failed mvp when you've wiped out your savings.. don't underestimate the phrase "fail fast", 6 months of building something is not failing fast..
Best of luck.
Comment by Big_Cryptographer_47 at 10/03/2025 at 14:24 UTC
1 upvotes, 0 direct replies
commitment? people quit, and move jobs all the time haha/
Its about incentivization for a freelancer.
I've had more success with freelancers than partners / full time.
The reason is, is because, in order for them to get paid again, they have to do a good job the first time.
Unfortunately, 99% of full time employees do the bare minimum to not get fired. Freelancers however, need to prove themselves to you every single time you hire them on a project - so you hire them again in the future.
Read Shape Up by Basecamp, and hire a developer to build something in a 6 week cycle. Every 6 week cycle is a project, in which you pay them a flat fee to finish up the work.
Another thing with freelancers, don't pay hourly. Pay a project rate. This means you need to clarify every single thing you need done prior to hiring them on the project. But, that means they'll be incenvvitized to get it done quicker. If you pay them hourly, they're incentivized to work slow.
Comment by deecassian at 10/03/2025 at 14:37 UTC
1 upvotes, 1 direct replies
Commitment is definitely a real issue. A freelancer might build your MVP and bounce, leaving you looking for other freelancers to help with fixes if he/she isn't available.
If you hire multiple freelancers, your codebase could turn into a Frankenstein mess with no clear structure.
If you’re not planning to bring in a full-time dev soon, at least make sure everything is well documented, I still do that even with the developers I get from rocketdevs. No issues with them yet, but I can't be too careful.
Comment by No-Understanding5609 at 10/03/2025 at 14:46 UTC
1 upvotes, 0 direct replies
Dm me, I’m a native to the us and won’t screw you over, i have had previous start ups my self in the past and know how important every dollar is.
Comment by YahenP at 10/03/2025 at 14:54 UTC
1 upvotes, 0 direct replies
I think you asked the question from the wrong angle.
Hiring a freelancer always has only one goal - saving money. Freelancing exists only because it is always cheaper than hiring an employee. Hence the further calculation.
Take the cost of an employee for a project and the cost of a freelancer for a project. The difference is the amount of savings. If the risks exceed this amount, then you need to hire an employee, if not, then a freelancer is the best choice. Always consider that freelancing is a 50% chance of success or failure. On average, this is how it works out in the industry.
Comment by magnumix at 10/03/2025 at 20:15 UTC
1 upvotes, 0 direct replies
- Can you **trust** this freelancer to actually do the development work.
- Can you **trust** this freelancer to actually deliver the work.
- Can you **trust** this freelancer to commit to do the work in a timely manner.
- Can you **trust** this freelancer to stick around and ensure things are working post delivery.
The list goes on....
From another perspective. I have worked as a freelancer, and I would categorize potential clients in one of two categories.
1. Category One: I'm paying a premium for the freelancer's superior knowledge and experience because by the time I hire someone and train them to get to where I need them to be will be too late for my project;
2. Category Two: freelancers are so much less expensive than hiring someone full time, why wouldn't you hire a freelancer?
The worst experiences came from those in category number two. They often paid the least and demanded the most. They more often had unreasonable delivery timelines, they listened to suggestions the least, or they didn't realize they actually still have to provide instructions on what they actually wanted done. They have this 'vision' in their head, and they don't really know how to communicate it. So expectations never matches reality, and they are perpetually frustrated at you.
Comment by Significant-Jump-466 at 10/03/2025 at 14:15 UTC
1 upvotes, 1 direct replies
When hiring a freelancer developer, common concerns include inconsistent communication, lack of accountability, and potential delays in delivery. While freelancers offer flexibility, a full-time developer may provide greater commitment and alignment with your project goals, especially for an MVP. Consider your budget, timeline, and long-term needs before deciding.