In this guide 6 sections
Hire a freelancer for a small, well-defined job with one clear owner on your side, such as a brochure site. Hire a software company when the work needs design, testing, several skills and someone still answerable a year after launch. Price matters less than what happens when the builder leaves.
A freelancer suits small, clear work
A freelancer is often the right call. A booking form, a Shopify theme tweak, a link between your shop and your Tally export: each is one person’s job, done faster than a team could manage. You speak to whoever writes the code.
Trouble starts when the job grows. One person has one set of skills. A tidy back end can sit behind clumsy screens. Nobody reviews the work.
Be frank about size. If the whole job fits on one page and will hardly change, hire one person from Upwork, a referral or a local contact. Ask if they hold a full time job elsewhere. Moonlighting is common and exclusivity is rare.
- One page of requirements that will not shift
- A single website or one system, not several linked ones
- A result you can click through and judge yourself
- No hard date tied to a launch event or an audit
A company brings a team and a routine
A software company puts several roles on one job. A designer, a developer, a tester and a project manager who chases the rest. If one falls ill, the sprint carries on.
That routine is what you pay for: code review, a staging link for you to test, release notes, and a person who answers when invoicing breaks. Some firms skip all of it. Ask for a sample sprint report before signing.
Expect more questions in the first month. A decent team asks about your barcode scanner, your thermal printer and your month-end before it writes a line. It keeps a Trello board you can read. This feels slow. It saves rework.
What changes at handover
Handover is where the two options part ways. A freelancer’s knowledge often sits in one head. Ask where the Git repository lives, who owns the hosting account, and who controls the nameserver settings that decide where your domain points on the day something breaks.
Put the repository, the domain, the SSL certificate renewal and the app store listing in your name from day one. Companies must do this too. It is simply easier to check when one person registered everything through GoDaddy on a personal email, and harder to fix afterwards.
A company can hand over a README, a recorded walkthrough and a named second engineer. A freelancer can match that. Only if you ask. Write it into the agreement before the first payment, not after the last.
- Source code in a repository you own
- Hosting, domain and Play Console accounts in your name
- A README on how to run and deploy it
- Named people who can fix it if the builder disappears
Who looks after it six months later?
Software needs care after launch. Servers want patching, a payment gateway changes its webhook format, and a phone update quietly breaks the camera screen that your delivery staff use all day. Someone must answer when the app stops at ten at night.
Some freelancers take new clients and go quiet. Others stay for years and are excellent. You cannot tell which at the start. Write the support terms down either way.
A company usually sells a monthly support plan. Read what it covers and what it leaves out. Check how quickly it must answer a fault that stops billing, because effort without response times is not much of a promise. Watch for lockin through custom hosting you cannot move.
How to decide this week
Write the job on one page. List the users, the main tasks and the systems it must talk to. Then count the skills: screen design, back end, mobile build, testing, hosting. Be honest about it.
One skill and one owner on your side? Offer a freelancer a small paid trial. Three or more skills, or invoicing that stops whenever the software stops? Talk to two companies, and ask each how it would cover a developer falling ill in the middle of a release.
Send the same page to everyone. Compare the questions they ask back, not just the figure at the bottom. Then book one reference call with a past customer of your top pick.
Freelancer or company scoring sheet
A one-page worksheet with two columns, freelancer and company, and eight rows: job size, skills needed, deadline, testing, handover, support after launch, cost of delay and your own time. You score each row from one to five, circle the three that matter most to your business, and read the totals against those.
Open a blank worksheet to printQuestions owners ask
Is a freelancer always cheaper than a company?
Not always. The first invoice is often lower, but you may pay later for rework, missing tests or a second person to take over. Compare the cost over the first year, including support.
Can I start with a freelancer and move to a company later?
Yes, if the code is tidy, documented and sitting in an account you own. A new team will read it before taking it on. Ask the freelancer to keep short notes.
What if my freelancer stops replying?
Check that you hold the repository and hosting logins. With those, another developer can pick the work up. Without them you may have to rebuild from scratch, and that is why ownership comes first.
Should I ask a company for references?
Yes. Speak to a customer with a similar job and ask what happened when something went wrong. Behaviour under pressure reveals more than a sample screen.