The choice is not good versus bad; it is what you must own and what you can buy. This article separates core work from context work, compares cost shape, continuity, knowledge transfer and governance, and gives you a decision checklist before you sign.
The decision between an in-house team and an agency is rarely settled by slogans. One side says an internal team is the only way to own the product; the other says an agency is faster and cheaper. Both exaggerate. The practical question is which part of the work gives you a real advantage when you own it, and which part you can buy without losing anything.
The question sharpens in Saudi Arabia when an organisation builds its first digital platform with a small team. Hiring engineers, designers and product leads takes time, the roles rarely arrive together, and an agency starts faster but eventually leaves. The wrong decision does not show up on the first invoice. It shows up a year later: a system nobody can maintain, an internal team still waiting for a hire that never closed, or an agency that walked out with the knowledge.
Core work and context work
Core work is what makes your product different: the way you understand the customer, the rules that govern the service, and the decisions about what gets built and what does not. That work should not be handed over completely, because handing it over means handing over the ability to differentiate. Context work is what the company needs in order to operate but does not compete on: hosting, test automation, standard integrations, design-system implementation, and deployment pipelines.
The test is simple. If the capability disappeared tomorrow, would the customer notice? If a competitor could buy the same capability the same way, would it still be an advantage? If the answer is no, it is a candidate for buying. The common mistake is to invert the equation: keep everything in-house until the team becomes the bottleneck, or hand product judgement to an agency and then hold it responsible for outcomes it never helped define.
The shape of cost, not the number
Comparing a monthly salary with an agency day rate is misleading. An internal team carries recruitment, training, tools, desks and management, the cost of idle time between projects, and the cost of turnover. An agency carries those costs inside its price, but you pay for a defined scope and you can stop. A fair comparison adds up total cost over the same period, including management time, recruitment and delay.
The hidden cost in both models is knowledge. An internal team without documentation depends on one person; an agency without a structured handover leaves you paying twice to learn what it built. Ask where knowledge lives before you ask for a price: who can use it six months from now, and what remains if the person leaves or the contract ends?
| Line | In-house team | Agency | Hybrid |
|---|---|---|---|
| Control over priorities | Direct, but limited by team capacity | Set by the contract and scope | Your decision, shared delivery |
| Start | Waits for hiring and setup | Starts quickly after signature | Starts with the agency, transitions gradually |
| Continuity | Depends on people who may leave | Depends on a team that may be reassigned | Documented and duplicated |
| Cost shape | Salaries, equipment, management | A price covering scope and operations | Higher at the start, less committed later |
| Domain knowledge | Built over time | Arrives with the team, leaves with it | Stays with the decision owner |
| Scaling up and down | Slow | Flexible | Flexible around a stable core |
| Intellectual property | Inside the company | A clause that must be written | A clause that must be written |
| Security and access | Carried entirely by you | Needs controls and access handover | Shared with explicit boundaries |
| Best use | A long-lived product in a deep domain | A bounded first release or rare capability | Build first, then operate in-house |
Hiring lead time and continuity
A role is not a person, and a team is not a role. Even when you hire a strong first engineer, you still need a product lead who understands the domain, a security owner, and someone to manage suppliers. Those roles do not arrive on one day. A good agency gives you a complete team from week one, but the continuity of that same team is not guaranteed unless it is written into the contract.
Ask the agency who will work on the project by name. Will they stay from kickoff to handover? What happens if the account manager changes or the lead engineer leaves? Ask the internal team the opposite question: what happens if the only person who knows how to deploy the system is ill? Continuity is not a personality trait. It is a system of documentation, role rotation and review.
Knowledge transfer is the deliverable
If you choose the agency, delivery does not end with a link. Ask for repository access from day one, written design decisions, a runbook that explains deployment and recovery, and transition sessions where your team sits at the keyboard rather than in the back row. Make a reverse demo a condition: your team runs the system and explains it while the agency watches and corrects.
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Intellectual property is a legal clause, but it is also an engineering one. Make sure code, designs, content, the domain and cloud accounts transfer to you at handover. Review access: who holds production keys, who can deploy a change, and how access is removed when the contract ends. These questions protect the company more than any promise of partnership.
Governance that protects either model
Either model fails without one owner of the decision. Appoint a product owner with authority to order priorities, record decisions in one place, and tie each stage to acceptance criteria that can be tested. In the agency model, review outcomes rather than hours, and ask for an independent code review if you have nobody to review. In the internal model, budget for performance, security and maintenance, not only features.
McKinsey's study of 300 listed companies found that top-quartile performers on its design index grew revenue 32 percentage points faster over five years. The study does not prove that design alone causes growth, but it does mean product and design judgement is not an administrative cost to defer. If that is your core work, it belongs close to whoever decides how the business runs.
The hybrid that usually works
For many Saudi organisations the realistic model is not a hard choice between inside and outside. Keep the product owner, the domain expert, the operations owner and the security owner in-house. Start the build with an agency, then move operation and continuous development to an internal team that forms in parallel. Set the transition date at the start, and let hiring run ahead of the agency's exit rather than behind it.
When does in-house win outright? When the product is long-lived, the domain is deep, change is continuous, and you can build and retain a team. When does the agency win outright? When the scope is bounded, the need is a rare capability or a fast first release, and hiring would take longer than the build. The decision is not permanent; review it every year against scope and capability.
The decision checklist before you sign
Do not start comparing two proposals before you answer these lines. Each one changes the model, not only the price. Also review technical consulting, and the earlier post on choosing a software company in Saudi Arabia, which explains how to read proposals before you sign.
The core capability: define it in one sentence, and write down what cannot be handed to an outside party.
The decision owner: appoint the product owner and whoever owns priority order, and name them in the contract.
Intellectual property: write an explicit clause for code, designs, content and the domain.
Early access: require the repository and accounts from day one, not at handover.
The team by name: ask who will work, how long they stay, and who backs up each critical role.
The transition pack: agree the documents, the reverse demo and the walkthroughs before the build starts.
Security and access: set permission controls and the plan for removing them at the end of the contract.
Exit: put the transition date and the exit plan in the contract, not after it ends.
Frequently asked questions
Is an in-house team always cheaper? No. A salary is not the full cost. Add recruitment, training, management, tools, idle time and turnover. An agency may cost more in a given month and less for a bounded scope, because it does not carry a permanent obligation.
Can an agency build our core product? It can execute the build, but the judgement, the rules and the customer understanding should stay with you. If you hand over the judgement too, you are renting your advantage rather than owning it.
How do we protect knowledge when the contract ends? Through access, documentation, a reverse demo and a written exit plan. Put those clauses in the contract and test them during the project, not after it.
What is the first in-house hire? A product owner who understands the domain and owns the decision, then an engineering lead. A delivery team without a decision owner produces speed without direction.
Can we start with an agency and hire later? Yes, and it is a common model. Run hiring in parallel with the build, and begin the transition well before the agency leaves.
Sources
- McKinsey: The Business Value of Design — 300 listed companies, and top-quartile revenue growth 32 percentage points faster over five years.
- Rasad technical consulting — how we review scope, team and risk before a build.
- Choosing a software company in Saudi Arabia — reading proposals and checking the team.
- Rasad's published price bands — the figures this article works from.
- SDAIA: Personal Data Protection Law — enforceable since September 2024, and what it means for whoever holds the data.
Cover image: Shixart1985, CC BY 2.0, via Wikimedia Commons.

