When hiring a freelancer, should I lump together related tasks or spread them out?


I'm building a web app that will require API integration with numerous platforms like Flickr, Tumblr, etc. It's relatively straight forward stuff--I just need to allow users to import their various subscriptions into my web app. But I'm literally planning to integrate with over a dozen APIs/platforms. Should I lump together these tasks as one big project (on a site like guru.com or freelancer.com) or should I divide each gig into chunks?

Once a developer has integrated one API with my app, it should be relatively easier to integrate additional APIs. But I'm afraid one big project will unreasonably drive up my costs.

What's the best way to go about this?

Outsourcing Developers Web App

asked Dec 21 '12 at 07:24
357 points

2 Answers


Put it all together for the purpose of finding someone. You don't want 12 different programmers working on your software, that would be a nightmare to manage and would require you to train 12 people.

As for actually doing the work once you find someone, break it down to small tasks and give them one at a time.

As for the price, I would find someone to work on an hourly rate instead of paying a fixed price if possible. That way you can always quit after one integration if you aren't happy with them and get someone else to continue on.

answered Dec 21 '12 at 20:57
Joel Friedlaender
5,007 points
  • Paying by the hour is a good idea. I didn't think of that. – Richard 10 years ago


Why not define a single api and use a service like zapier for integration? Here is a list of products / services that can exchange info.

Depending on your product, this may open up additional channels.

answered Dec 21 '12 at 08:11
Jim Galley
9,952 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Outsourcing Developers Web App