Freelancer or software company: which should you hire?
For a small, well-defined job with a short life, a good freelancer is usually enough. If the software will run for years, needs several kinds of expertise or costs you money when it stops, a software company carries less risk. The real difference is not price but whether the work depends on one person.
The answer to "freelancer or software company?" depends on the size of the project and how critical it is to your business. A freelancer is a developer who works for themselves rather than for an employer. A software company supplies several developers, testing, design and project management, and a legal entity is the other party to your contract. Either can deliver good work. What differs is what happens when something goes wrong: if a freelancer falls ill, takes another job or becomes unreachable, your project stops. In a company, someone else usually knows the code even if one person leaves.
Ask yourself a few things. Is the software the backbone of your business or a side tool? Who will maintain it in a year? Who will hold the source code and user data? If you have no clear answers, start by splitting the work into a small discovery phase.
Which option suits which level of project risk?
The table below compares typical situations. The boundaries are not exact; the point is to see which risk stands out.
| Situation | Better fit | Main risk to watch |
|---|---|---|
| Brochure site, one-off small change | Freelancer | Keep the access credentials yourself |
| Small plug-in or script for an existing tool | Freelancer | Undocumented work is hard to maintain |
| Prototype or idea test | Freelancer or small team | Quality drops if a prototype goes live |
| Customer-facing app that takes payments | Software company | Downtime and security flaws cost revenue |
| Integration with several systems | Software company | Testing and environments need a team |
| Business software handling personal data | Software company | Confidentiality duties must be in writing |
| Core system used for years | Software company | Ongoing maintenance and shared knowledge |
When does a freelancer genuinely make sense?
To be fair, looking for a company for every job can be needless expense. A freelancer is a good choice when:
- The job is small and clear: You can describe it in a few sentences, and the delivery date and acceptance criteria are fixed.
- Continuity is not needed: The software serves a campaign, an event or a short period of use.
- The skill is narrow: You want deep knowledge of one technology and no team coordination.
- Someone technical is on your side: A person in your team can supervise the work and review the code.
When these hold, a freelancer can be both fast and flexible. What is usually missing is a fallback plan, which the questions below help you build.
Which 8 questions should you ask before choosing?
Whichever side you pick, ask for written answers to these before you accept a quote:
- Have you delivered something similar, and can you show me a working live example?
- Who will look after the project when you are unavailable?
- Whose account will hold the source code, database and server access?
- How will bug fixing and maintenance work after delivery, and what is the response time?
- Can you issue invoices, and who exactly will be the party to the contract?
- How will you transfer the code and the economic rights in the software to me?
- If you will access personal data, what do you commit to on confidentiality and security?
- What will testing, acceptance and staged payment look like?
The quality of the answers often tells you more than the price of the quote. Vague answers suggest the work will later fall back on you. For the general logic of choosing a supplier, see our guide on how to choose an AI development supplier; most of that checklist applies to any software job.
What should the contract say?
You should take legal advice, but you can check yourself whether the following topics appear in the contract.
Economic rights and source code. Computer programs count as works under Law No. 5846 on Intellectual and Artistic Works. Under Article 52, contracts on economic rights must be in writing and the rights concerned must be listed separately. Saying only "the software will be delivered" may not be enough; the contract should state who keeps rights such as use, reproduction and modification. Settle this with a freelancer and a company alike.
Contract for work. The Turkish Code of Obligations (Law No. 6098) defines a contract for work as one where the contractor undertakes to produce a work and the client undertakes to pay for it (Art. 470). If the delivery is defective, the client has a choice of remedies such as withdrawing from the contract, a price reduction or free repair (Art. 475). Once the work is accepted, the contractor's liability can be limited (Art. 477), so do not run acceptance testing casually. The type and consequences of a contract depend on its actual wording; having a lawyer read it should be considered.
Personal data. If the developer or company will touch customer, employee or patient data, the Personal Data Protection Law (KVKK, Law No. 6698) may apply. Article 12 says that where personal data is processed on a controller's behalf by another person, the controller is jointly responsible with that person for the security measures. You may therefore need to put confidentiality and security duties in writing when you give a developer access to data. Using anonymised data instead of real data in test environments is also a sensible safeguard.
What should you check for security and maintenance?
Software shows its value in the years after delivery, not on the day. Ask about:
- Secure development practice: NIST's Secure Software Development Framework (SSDF) is a widely used reference. You can ask a supplier to describe a process along similar lines.
- Backup and handover plan: Is the code repository in your account? Could another developer take the project over within a reasonable time?
- Documentation: Are setup steps, environment details and architecture collected in a short document?
- Maintenance agreement: Are security updates and bug fixes covered, and is the response time written down?
A freelancer can meet most of these, provided the contract says so and the access stays with you. Companies often have some of them as standing processes, but ask for written confirmation anyway.
Example: how do the two options look side by side?
For example, a logistics company with 30 staff wants a mobile app for drivers to upload delivery photos, plus a server side that feeds the accounting system. This scenario is entirely hypothetical.
With a freelancer, one developer builds both the mobile and server parts. The first version comes quickly. But the code sits only on that person's laptop and the server access is tied to their account. Six months later the developer moves to another job, and the company must explain everything again to someone new. When the accounting integration fails, it is unclear who will look at it.
With a company, mobile, server and testing work are split between different people, and a project manager is the single contact. The start is slower and more structured, but the code sits in the company's own repository, defects are logged and a maintenance agreement exists. If an unbroken delivery record is critical to the business, the second option is safer. If the same company only wanted a brochure page, a freelancer alone would be enough.
A middle path also exists: build a prototype with a freelancer or small team, then hand over to a company for go-live and maintenance. That only works if the prototype code is transferable and documented.
What are the common mistakes?
- Looking only at price: The lowest quote often becomes the most expensive once maintenance and handover costs are added.
- Leaving access with the developer: Domain, server, app store account and code repository should be opened in your name.
- Starting without a contract, or with a one-page agreement: If scope, delivery, acceptance and rights are not written down, you have little to rely on in a dispute.
- Skipping the transfer of economic rights: The law requires a written transfer listing the rights separately; neglecting it can limit your freedom to modify the software.
- Handing over the whole job at once: Splitting it into stages and paying each after an acceptance test reduces risk.
- Leaving a critical system unmaintained: Software that nobody owns after delivery turns into a security hole over time.
How Hatson Tech helps
Hatson Tech is a software and AI company based in Ankara. The first meeting and the discovery phase are free; in discovery we settle the scope, the risks and the team structure that suits you. We do not publish fixed prices, and each quote is prepared for the actual scope of work. Where needed, we can run models on your own servers.
For web, mobile and business systems, see our custom software development solutions. If you are deciding between an off-the-shelf product and building your own, our guide on whether to buy or build AI may also help.