IR35 Compliant Software Development UK: Choose Your Engagement Model

By Sahil Chaudhary · Last updated 15 Oct 2026

UK business owners, founders, CTOs, and procurement teams face a persistent challenge: how to scale software development capabilities without inadvertently inheriting significant tax liabilities under the off-payroll working rules, commonly known as IR35. The decision to build in-house, hire individual contractors, or engage a dedicated development team carries distinct implications for compliance, risk, and your project’s ultimate success.

TL;DR: Navigating IR35 requires careful consideration of your chosen engagement model. While in-house employment is IR35-exempt and individual contractors carry high client-side risk, engaging a dedicated development team under a Statement of Work (SOW) often provides a robust, IR35-compliant solution for UK businesses seeking external expertise.

Key takeaways

• IR35 compliance is a critical factor when choosing how to staff software development projects in the UK.
• The responsibility for determining IR35 status shifted to the client for medium and large UK businesses in 2017/2021.
• Engagement models like dedicated development teams, structured via a Statement of Work, can significantly mitigate IR35 risk for the client.
• Beyond IR35, UK GDPR, DPA 2018, and robust supplier due diligence remain essential for any software development partnership.
• Proper contractual agreements and clear project scopes are vital for ensuring outside-IR35 status where applicable.

The UK's IR35 Challenge for Software Development

Since the reforms to the off-payroll working rules (IR35) were implemented in the public sector in 2017 and extended to the private sector in 2021, UK organisations have grappled with the complexities of engaging external talent. For medium and large businesses, the onus shifted from the individual contractor to the client to determine the employment status for tax purposes. This change has created a significant hurdle for founders and engineering leaders keen to access specialist skills without incurring unexpected tax penalties or administrative burdens.

The pain point is tangible: a slower time-to-hire for critical roles, increased burn rate due to inflated contractor costs, or worse, the risk of HMRC investigations and substantial back-dated tax liabilities. This isn't merely a compliance exercise; it directly impacts your ability to innovate and grow. Understanding the nuances of IR35 is therefore paramount when deciding how to acquire software development expertise for your next project.

Understanding IR35: Employee vs. Contractor Status in the UK

At its core, IR35 seeks to identify 'disguised employment' – situations where a contractor effectively works like an employee but bills through a limited company to gain tax advantages. HMRC applies a series of tests to determine status, focusing on three key areas:

• Control: Does the client dictate how, when, and where the work is done, or does the contractor have autonomy?
• Mutuality of Obligation (MOO): Is there an obligation for the client to offer work and for the contractor to accept it? A genuine contractor relationship typically lacks this.
• Personal Service: Must the individual personally perform the work, or do they have a genuine right to send a substitute?

HMRC's online Check Employment Status for Tax (CEST) tool is a starting point, but its output isn't legally binding and often struggles with complex scenarios. Many businesses find it doesn't fully capture the nuances of modern software development engagements.

Inside IR35 vs. Outside IR35: What it Means for Your Project

If an engagement is deemed 'inside IR35', it means the contractor is considered an employee for tax purposes. The fee-payer (often the client or an agency) must deduct income tax and National Insurance Contributions (NICs) at source via PAYE. This effectively removes the tax advantage of contracting.

Conversely, an engagement 'outside IR35' signifies a genuine business-to-business relationship. The contractor's limited company is responsible for its own tax and NICs. For medium and large clients, a Status Determination Statement (SDS) must be issued, clearly outlining the IR35 status and the reasons for that determination. This SDS must be passed down the supply chain.

Engagement Models and Their IR35 Implications for UK Businesses

The choice of how you engage software development talent profoundly impacts IR35 risk. Here’s a breakdown of common models:

In-house Employment: The Simplest, Most Costly Path

Hiring permanent staff offers the most straightforward IR35 position: none. Your employees are unequivocally inside PAYE. However, this comes with significant costs beyond salary, including employer National Insurance contributions (currently 13.8% on earnings above the secondary threshold), pension contributions, recruitment fees (often 15-25% of annual salary), benefits packages, and the administrative burden of HR. Additionally, notice periods can impact project agility, and the UK tech talent market remains competitive for senior roles, leading to lengthy time-to-hire.

Individual Contractors (Staff Augmentation): High Flexibility, High IR35 Scrutiny

This model involves engaging individual contractors, often through an agency, to augment your existing team. While offering flexibility and rapid access to specialist skills, it presents the highest IR35 risk for the client. Because these individuals often integrate closely with your team, use your equipment, and follow your processes, their working arrangements frequently resemble employment.

For any medium or large UK business, you are responsible for issuing an SDS. If HMRC deems the status incorrect, the liability for unpaid tax and NICs falls on your organisation. Mitigating this requires extremely clear contractual terms, a genuine right of substitution, and ensuring the contractor maintains a high degree of autonomy over how they deliver their work, not just what they deliver.

Dedicated Development Teams (Statement of Work): Mitigating IR35 Risk

Engaging a dedicated development team, such as those offered by Krapton, operates on a fundamentally different principle: you are contracting for a service, not for individual labour. Under a Statement of Work (SOW), the supplier (Krapton IT Consultancy Ltd) takes responsibility for delivering specific project outcomes or features. The supplier determines the employment status of its own engineers, and the client's contract is with the supplier entity.

This model significantly reduces the client's IR35 risk because the client is not the 'fee-payer' for individual contractors, nor are they determining the status of individuals integrated into their own team. The focus shifts to deliverables and project milestones, rather than hours worked by specific individuals. Contracts are typically under English law, providing clear legal recourse and intellectual property assignment. This approach allows UK businesses to access high-calibre engineering talent efficiently and compliantly.

Mitigating IR35 Risk When Hiring Software Talent

Beyond selecting the right engagement model, proactive measures are crucial for IR35 compliance:

• Clear Contracts: Ensure all contracts, especially for individual contractors, explicitly state terms that support an 'outside IR35' determination, such as a genuine right of substitution, absence of mutuality of obligation, and clear project deliverables rather than open-ended tasks.
• Robust Status Determination Statements (SDS): If engaging individual contractors, issue a detailed SDS and ensure the contractor (and any agency) agrees with it. Keep comprehensive records.
• Review Engagements Regularly: Employment status can evolve. Periodically review working practices to ensure they align with the initial IR35 determination.
• Seek Expert Advice: For complex cases, consult with specialist tax advisors. This article provides general information and is not legal or tax advice. Always refer to official HMRC guidance or a qualified professional.

When NOT to use this approach

While dedicated teams offer significant IR35 mitigation, they may not be the optimal choice for very small, ad-hoc tasks requiring minimal hours or highly specific, one-off consultations. For such scenarios, a pre-vetted, genuinely self-employed consultant with a clear, limited scope of work might be more suitable, provided a robust SDS is in place if your organisation is medium or large.

Beyond IR35: Additional UK Regulatory Considerations

IR35 is just one piece of the regulatory puzzle for UK businesses. When engaging any software development supplier, especially an international one, consider these critical factors:

• UK GDPR and Data Protection Act 2018: If your project involves processing personal data, ensure your supplier's practices comply with UK GDPR. For offshore teams, this means having appropriate international data transfer mechanisms in place, such as the ICO's International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses.
• Companies House Due Diligence: Always verify the legal entity of your supplier. Krapton IT Consultancy Ltd is registered in England and Wales (Companies House no. 17457035). This provides a layer of legal certainty and transparency.
• Sector-Specific Regulations: If you operate in a regulated sector, ensure your supplier understands and can adhere to specific compliance requirements. For instance, FCA-regulated financial services firms must consider Consumer Duty and operational resilience, while NHS suppliers need to comply with the Data Security and Protection Toolkit (DSPT) and potentially integrate with NHS login or FHIR UK Core standards.

Vetting a Software Development Supplier for UK Compliance

Your procurement team will appreciate a structured approach to vetting. Beyond technical capability, focus on compliance and risk management specific to the UK context:

1. Legal Entity & Registration: Confirm the supplier is a legitimate limited company registered with Companies House. Verify their registered office and ensure contracts are under English law.
2. Insurance Coverage: Request proof of Professional Indemnity, Public Liability, and Cyber Liability insurance. This protects your business against potential errors, data breaches, or third-party claims.
3. Intellectual Property (IP) Assignment: Ensure your contract clearly stipulates that all IP developed during the project is assigned to your UK company upon payment.
4. Data Security & Privacy: Demand clear policies and procedures for data handling, storage, and access, demonstrating compliance with UK GDPR and the Data Protection Act 2018.
5. Exit Strategy & Knowledge Transfer: A robust contract should include provisions for knowledge transfer and an orderly exit if the engagement concludes, ensuring continuity for your software assets.
6. Experience with UK Clients: While not a strict legal requirement, a supplier with a track record of working with UK businesses will better understand local market nuances and regulatory expectations.

For a comprehensive guide on selecting a partner, consider choosing a software development agency in the UK that prioritises these factors.

FAQ: IR35 and Software Development for UK Businesses

What is a Status Determination Statement (SDS)?

An SDS is a document issued by a client (for medium/large businesses) or an agency that formally states whether an engagement with an individual contractor is 'inside' or 'outside' IR35, along with the reasons for that decision. It must be passed down the supply chain.

How does IR35 affect a small UK start-up?

Small companies (as defined by the Companies Act 2006, meeting at least two of three criteria: turnover not exceeding £10.2m, balance sheet not exceeding £5.1m, or no more than 50 employees) are exempt from the client-led IR35 rules. For these businesses, the individual contractor remains responsible for determining their own IR35 status.

Can I use the CEST tool for an offshore dedicated team?

The CEST tool is designed to determine the employment status of an individual working for a UK client. For a dedicated development team engaged via a Statement of Work, your contract is with the supplier entity, not individual contractors. Therefore, CEST is generally not applicable, as the IR35 responsibility for the supplier's engineers lies with the supplier itself.

What is "mutuality of obligation" in IR35?

Mutuality of Obligation (MOO) refers to the reciprocal obligation for the client to offer work and for the worker to accept it. In a genuine contractor relationship, there should be no ongoing obligation for the client to provide work beyond the current project, and no obligation for the contractor to accept future work offers.

Ready to Build with IR35 Confidence?

Navigating the complexities of IR35 doesn't have to slow your project down. Krapton offers expert dedicated development teams and custom software development services designed to integrate seamlessly with your UK business while managing compliance effectively. If you're looking to hire software developers for a UK project and need an IR35-compliant solution, partner with Krapton and book a free consultation with Krapton today.