Your Software Agency Uses Subcontractors: What to Check
What should you check when a software development agency subcontracts?
Check who will do the work, who will supervise it, what they can access, and whether your agency remains responsible for delivery. Ask for written terms covering disclosure, approval rights, intellectual property, confidentiality, replacement and handover. Subcontracting can be a reasonable delivery choice when those responsibilities stay clear.
Start with a direct question: “Which parts of this project will people outside your company deliver?” Then ask the agency to show how the arrangement will work on your project.
Who is actually doing the work?
Ask the agency to distinguish its employees, independent contractors and any other businesses involved. A statement such as “we use our trusted network” does not tell you who will build your product or handle your information.
Request a short delivery roster showing each person's role, employer or contracting business, responsibilities and expected involvement. Include anyone reviewing code or handling releases, even if they will not attend your meetings.
You do not need personal details unrelated to the project. You do need enough information to understand who is involved and assess the arrangement.
Clarify whether subcontractors can delegate work again. If another business may bring in its own suppliers, decide whether the same disclosure and approval process must apply throughout that chain.
For the wider selection process, use these questions to ask a software development agency.
What disclosure and approval rights should you request?
Agree on the approval process before work starts. Distinguish approval of the initial arrangement from approval of later changes.
A practical starting point is written approval for a new subcontracting business, a material change in its scope, or access to sensitive information. For routine staffing changes within an approved team, you may prefer notification and an agreed review process.
Choose the level of control that fits your project. Requiring approval for every minor reassignment may create work without giving you useful oversight.
| Area | What to agree | Evidence to request |
|---|---|---|
| Initial disclosure | Which outside parties will work on the project | Delivery roster and scope |
| Changes | Which changes require notice or approval | Written change process |
| Further subcontracting | Whether another layer is permitted | Approval terms covering further delegation |
| Sensitive access | Which roles can access which systems or information | Access list |
| Rejection or replacement | How concerns will be resolved | Replacement and escalation process |
Also ask what happens if you decline a proposed subcontractor: who supplies an alternative, whether delivery dates change, and how any additional cost is agreed.
Who remains accountable for delivery and supervision?
Your contract should identify the agency as responsible for the agreed work, including work it delegates. Ask for this responsibility to cover defects, missed acceptance criteria and coordination between contributors.
Then separate accountability from daily supervision.
Who assigns work? Who answers technical questions? Who reviews changes? Who decides that a feature is ready for you to accept? Request a named agency lead for these duties and a backup contact.
Avoid an arrangement where you discover that managing the subcontractor has become your job. Direct conversations with a specialist can be useful, but the agency should still coordinate delivery and resolve disagreements.
Ask to see the proposed review process. It should identify a reviewer for subcontracted work and explain how defects return to the person responsible. Our guide to code review practices for small teams covers questions you can use here.
How should intellectual property ownership be handled?
Ask for a clear contractual route from every contributor's work to the rights promised to you. Do not treat a verbal statement that “you own the code” as a complete answer.
Have your legal adviser review how the agency's agreement with you fits its agreements with subcontractors. Ask them to check:
- Which deliverables are covered, including code, designs, documentation and tests.
- Whether contributor agreements support the rights the agency promises you.
- When the agreed assignment or licence takes effect.
- What happens if the agency and subcontractor have a payment dispute.
- Which pre-existing materials or third-party components are excluded.
- What rights you receive to use, modify and maintain those excluded materials.
Distinguish custom project work from tools or components the supplier already had. Request an exceptions list and the relevant usage terms before accepting them.
Receiving source files and receiving the necessary rights are separate acceptance questions. Check both; who owns the source code in outsourced development covers the wider ownership question.
What confidentiality and access controls should apply?
Ask the agency to show how confidentiality obligations reach everyone who may see your information. Define the information covered, permitted uses, restrictions on further sharing, incident reporting, and return or deletion at the end of the engagement.
Then review actual access. A confidentiality agreement should sit alongside a practical access plan.
Request individual accounts, permissions limited to assigned work, and a record of who approves access. Ask the agency to use test data wherever practical and to justify any need for live customer information.
Your access checklist should cover:
- Source code and design files.
- Customer and business information.
- Hosting, billing and release permissions.
- Credentials and other secrets.
- Copies held on devices or outside the agreed workspace.
- Removal of access when a person leaves.
Decide who checks that removal happened and what evidence you receive. For broader questions to raise, see data security in modern applications.
What happens if the subcontractor leaves?
Plan for a contributor becoming unavailable, being replaced, or ending their relationship with the agency.
Ask the agency to keep current work in an agreed repository and maintain enough documentation for another developer to continue. Agree where designs, tests, setup instructions and delivery decisions will be recorded.
Request a replacement process that covers the required skills, handover responsibilities, approval steps and treatment of onboarding costs. Ask who handles support while the replacement gets familiar with the product.
Check control of essential accounts too. Prefer arrangements where your organisation controls its product accounts and grants access to the delivery team.
A useful continuity question is: “If this contributor became unavailable today, what could the next developer access and run?” Ask for a demonstration at an agreed milestone.
What would a workable arrangement look like?
Consider an illustrative project in which an agency subcontracts a specialist to build a reporting feature.
The agency discloses the specialist's business and scope before work begins. You approve that scope. The specialist receives access to the relevant code and sample data, while the agency's technical lead reviews the work.
The agency remains responsible for the feature's acceptance criteria and fixes. Your legal adviser checks the ownership and confidentiality terms. Code, tests and setup notes are delivered to the agreed repository as work progresses.
If the specialist leaves, the agency supplies a replacement under the agreed process.
Use this example to test a proposal: can the agency explain each equivalent step for your project?
What common mistakes should you avoid?
Treating all subcontracting as a reason to reject an agency. Assess the proposed people, controls and responsibilities. Employment status alone does not answer your delivery questions.
Approving a business without defining its scope. Record what it may do and what access that work requires.
Accepting reassurances without supporting terms. Ask where the contract records ownership, confidentiality and delivery obligations.
Leaving handover until the final invoice. Review working code and documentation during delivery.
Keeping tighter control than you can administer. Choose approval rights you can use consistently, with a clear response process.
If your agreement is primarily for staff augmentation, define supervision separately: you may be choosing to direct contributors yourself. Make that division explicit.
What should you ask before signing?
Use this final checklist:
- We know which outside parties will contribute.
- We have agreed what requires disclosure, notice or approval.
- The agency's delivery and supervision duties are written down.
- Ownership terms and exceptions have been reviewed.
- Confidentiality obligations cover the people involved.
- Access has an owner, a defined scope and a removal process.
- Replacement, handover and support responsibilities are clear.
Resolve gaps in the proposal and agreement before relying on them during delivery.
Frequently asked questions
Should every subcontractor need my approval?
Choose approval rights around meaningful changes: a new supplier, different responsibilities or sensitive access. Agree how routine staffing changes will be handled.
Do I need a separate contract with the subcontractor?
Ask your legal adviser whether the proposed contract structure gives you the rights and protections you need. If you contract directly with the subcontractor, clarify how that changes the agency's responsibilities.
What if the agency refuses to disclose subcontracting arrangements?
Explain the information you need to assess delivery, ownership and access. If the agency cannot provide it or offer a workable alternative, treat the proposal as unresolved before signing.