← All articles

·4 min read

In-House Developer, Freelancer or Software Agency: Which Fits a Small Business?

Match the option to how long the work lasts, how many skills it needs and who will manage it day to day.

Hire in-house when software is a permanent, daily part of the business and you can manage a technical employee. Use a freelancer for a small, well-defined task in one skill. Engage a software agency when the project needs several skills, a delivery process and continuity if one person leaves.

Key takeaways

  • The duration of the work matters more than the hourly rate.
  • Count the skills the project needs. One person rarely covers design, development, testing and operations.
  • Someone must manage the work. Decide who before choosing.
  • Ask each option the same question: what happens if this person is unavailable for a month?

How do the three options compare?

QuestionIn-house developerFreelancerSoftware agency
Best fitOngoing product work for yearsA contained task in one skillA project needing several skills
Skills coveredOne person's skillsOne person's skillsDesign, development, testing and project management
Who manages the workYouYouThe agency, with your decisions
Cost shapeSalary, benefits, equipment and hiring timeHourly or per taskProject price or monthly capacity
Start timeWeeks to months to hireOften daysOften days to weeks
Continuity riskHigh if the only developer leavesHigh if the freelancer becomes unavailableLower when the agency documents work and can replace a team member
Knowledge of your businessDeepest over timeLimited to the taskGrows over the engagement and should be documented

Which option fits three fictional businesses?

Online retailer. The website and order system change every week and drive most revenue. A permanent developer who learns the business is justified, possibly with an agency for larger projects.

Accounting firm. The firm needs one report added to an existing tool that already works. The task is small, the skill is specific and the acceptance test is clear. A freelancer with references for that tool fits.

Clinic group. The group wants a patient intake system connected to its scheduling software. It needs workflow design, web development, an integration, testing and training. No single person covers all of that, so an agency or a product team fits.

What does each option cost beyond the rate?

  • In-house: recruiting time, benefits, equipment, software licences, training and the manager's time. If the developer is the only technical person, also plan for code review and backup.
  • Freelancer: your time writing requirements and testing, plus the risk of rework if the freelancer leaves before handover.
  • Agency: a higher rate that includes project management and testing. Ask what is included so you can compare fairly.

What should you ask before deciding?

  1. Will this work continue after the first release, and for how long?
  2. Which skills does the project need, and who covers each?
  3. Who on our side will answer questions and approve work every week?
  4. Who will own the source code, accounts and documentation?
  5. What happens if the person or team becomes unavailable?

The source code and handover checklist covers question 4 in detail. If you are comparing agencies that use an offshore team, see how to evaluate a Canadian software partner with an offshore engineering team.

Discuss a software project with Wizy.

Frequently asked questions

Is a freelancer always cheaper than an agency?

The hourly rate is usually lower. The total can be higher if you spend many hours managing the work, or if the work must be redone after a handover fails. Compare the full cost of reaching a tested, documented result.

Can a small business combine these options?

Yes. A common pattern is an agency for the first build and an in-house person or a smaller support agreement afterward. Agree on documentation and handover at the start so the transition is possible.

When does hiring a first developer make sense?

When there is enough ongoing work to fill the role for years and someone who can set priorities and review the work. Without both, a single developer can become a single point of failure.

Who should own the code under each option?

In all three cases the business should confirm in writing that it owns the code, has administrator access to the repository and hosting accounts, and receives documentation. Ownership terms vary by contract, so check before work starts.