We are a company, so we have an obvious interest in this question. Even so, plenty of jobs are better served by one good freelancer. Here is how we would decide.
When a freelancer is the better choice
- The job is small and clear: a landing page, a change to an existing app, one integration.
- You can judge the work, or you have a technical friend who can.
- You need one skill, and you are happy to manage the work directly.
- Your budget would not cover a team’s overheads, and the project does not need them.
The real risks are availability and concentration. Freelancers get ill, take other work or move on. If only one person understands your product, that risk stays with you for as long as the product exists.
When a company is the better choice
- The project needs design, mobile, back end and testing together.
- The app has to keep working for years, with OS updates, store rules and staff changes along the way.
- You need cover: someone else who can pick up the work if a person is away.
- You do not have the time or knowledge to manage the work yourself, and want someone accountable for delivery.
The real risks are cost, and a junior team doing the work after a senior team sold it. Ask who will work on your project, and ask to speak to them.
A rough guide by size
These are rules of thumb and not quotes. Size is easier to compare than price, since prices vary widely by country.
- About a month of one person’s work or less: one freelancer and one small, clear goal. Prove the idea before anything else. Tools such as FlutterFlow or an AI builder can be reasonable for a demo.
- Two to four months with one or two people: a strong freelancer, a small team or an offshore company can all work. Judge them on the plan they give you. Do not judge on price alone.
- Several roles for six months or more, or a long product life: a company, or a small team of people who already work together.
Any budget should include money for after launch: allow for yearly OS and store updates.
Marketplaces such as Fiverr and Upwork are a third route, for either a freelancer or a company. They keep a public record of past orders and offer payment protection, which is useful on a first job.
What protects you either way
- Write down what the first release does, and what it does not do.
- Pay in milestones tied to working software you can test.
- Keep the code repository and store accounts in your own name. See who owns the code.
- Start with a small paid first step, then decide on the rest.
- Ask for a build you can install, every week or two.
Questions that reveal more than a portfolio
- What would you leave out of my first version?
- What is most likely to go wrong on this project?
- Who works on it each day, and who covers when they are away?
- How would I move to another team if I needed to?
If you would like our view on your project, including whether you need a company at all, send us a few sentences.