Agency vs Freelancer vs In-House: Who Should Build Your Internal Tools
Three hiring models for internal software, compared on cost structure, risk, speed and what happens after launch.
By Osamah Aldoaiss · 17.11.2026
The short answer: for a company of 5 to 50 people building something that matters to the business, an agency is usually the best fit. You get design, development, testing and project management under one agreement, a delivery commitment, and no single person whose absence stops the work. Freelancers carry key-person risk, and an in-house developer needs a steady stream of work and a manager who can review their output, which most small companies cannot supply.
The mistake to avoid is choosing by hourly rate. The model that looks cheapest per hour is often the most expensive per working system.
What each model actually is
A freelancer is one person you engage directly, typically paid by the hour or the project. You get their skills and nothing else: no project management, no second pair of eyes, no cover when they are ill or busy.
An agency is a team engaged for a defined scope. You get design, development, testing and project management under one contract, with someone accountable for delivery and cover if any one person is unavailable.
An in-house developer is an employee. You pay salary, benefits and management time whether or not there is work, and in return you get continuity and availability.
Same-criteria comparison
| Criterion | Freelancer | Agency | In-house developer |
|---|---|---|---|
| Cost structure | Lowest hourly rate, but all coordination and rework cost lands on you. | Fixed project price or day rate for a whole team: design, build, testing and management included. | Fixed salary plus benefits, recruiting and management time, used or not. |
| Time to value | Fast to start, often within days. Speed depends on one person's availability. | A few weeks to mobilise, then steady delivery from a team working in parallel. | Slowest to start. Hiring takes months, then onboarding. |
| Flexibility | High. Easy to start and stop, but availability is not guaranteed. | Scope is agreed up front, with changes handled in the open. Can scale across skills as needs change. | High once hired. Priorities can shift daily, within one person's skills. |
| Maintenance burden | Falls back on you unless a retainer is agreed. Knowledge sits with one person. | Covered by a support agreement, with documentation as part of the work. | Handled internally. Strong for long-lived systems, if the person stays. |
| Lock-in | Key-person risk: the code and its context live in one head. | Lower key-person risk. You should still insist on owning the code, and we hand it over from day one. | Low contractual lock-in, but you depend on retaining the person. |
| Team required | You must manage the work and define the requirements. | A single point of contact on your side is usually enough. | A manager who can direct and review technical work. |
Choose a freelancer when
You have one small, clearly defined task, a technical lead of your own, and a tight budget. If that describes you, a freelancer is fine. Agree where the code will live and keep it in a repository you own.
Choose an agency when
An agency earns its day rate when the work crosses disciplines, when the system matters to revenue, or when nobody on your side can write the specification. You will recognise the situation:
- The last freelancer disappeared, or got busy, halfway through. You are left with half-finished code, no documentation, and a vague idea of what was agreed. Starting again costs more than the first attempt.
- You do not have a technical person. You know what the business needs but cannot judge whether a quote, an architecture or a delivered feature is any good. An agency translates your business problem into a specification and tells you what is realistic.
- The project needs several skills at once. A 30-person distribution company wants a customer portal with login, ordering and invoicing. That is design, backend, frontend, security and testing, which you would otherwise assemble from three hires or three freelancers who have never worked together.
- You have been burned by software that works on the demo. Testing, review and a second pair of eyes catch problems before your customers do.
- The system is central to revenue. One person being on holiday, ill or poached is an unacceptable risk when orders flow through it.
- You want one party accountable. When something breaks, one phone call gets it fixed, and nobody asks whose fault it was.
You are paying for coordination, accountability and redundancy. The result is usually cheaper than a failed project, and far cheaper than the second attempt.
Choose an in-house developer when
You have continuous work for a full week, every week, and someone who can supervise a developer. For a company under about 50 people that is rarer than it feels, and a single hire concentrates the same key-person risk as a freelancer, with recruiting time on top.
A combination often works best
These are not exclusive. A common pattern is for an agency to build the first version, with a part-time internal owner, who may not be a developer, running the system afterwards while the agency stays on a light support arrangement. What matters is that someone on your side owns the outcome and that you own the code. Both are how we work.
Decision checklist
If two or more of these sound familiar, an agency will pay for itself:
- You have no one in the company who can write a technical specification or review code.
- A previous freelancer or developer left work unfinished or undocumented.
- The project needs design, backend and frontend together, not one skill.
- The system will touch revenue, customers or compliance.
- You cannot tell whether a quote is reasonable.
- Your internal tools depend on whatever one person remembers.
- You would rather have a delivery date and one accountable party than manage individuals.
Book a short call and we'll tell you honestly if it won't.
FAQ
Isn't a freelancer much cheaper than an agency? Their rate is lower, but the total often is not. A freelancer needs more management from you, and mistakes caught late are expensive. For a task that is small and fully specified, a freelancer can come out cheaper; for anything with several moving parts, the gap tends to close once you count your own time and rework.
What if the agency disappears or we fall out? That is the risk you take with one freelancer, magnified, and the answer is the same at every model: own the repository and hosting accounts from the start, receive written documentation, and use standard technology. We work that way, so another builder can take over without starting from scratch.
Can't we just hire a developer? You can, and if you have a full week of varied technical work and someone who can review it, it is a good move. Below that you are paying a salary for idle time or asking one person to cover far too many skills, with a three-to-six-month hiring lead time before anything ships.
How do I avoid being locked in to whoever builds my software? Insist on owning the repository and hosting accounts from the start, on written documentation, and on standard, widely used technology. Those three conditions make switching builders realistic under any model.
Can I mix models? Yes. Many of our clients have us build the first version, then keep a light support arrangement or a part-time internal owner for the long run.
What should I ask before signing with any of them? Ask who owns the code, what is in scope, how changes are handled, what documentation you will receive, and what support looks like after launch. Vague answers to any of these are a warning sign.
Where BlackCard comes in
We are a small agency that builds business software, workflows, AI tools and dashboards for companies of 5 to 50 people. You get one accountable team, a first usable version in weeks, and a code repository you own from the first week. We write down what is in scope, keep the system documented, and stay available after launch. The first call is free and diagnostic: we listen to the problem and tell you what we would build and what it would take.
See how our business software work starts, read about our consulting service if you only need an independent view first, or book a short call and describe what you need built.





