Endava vs Version 1: full comparison for 2026
Quick verdict
Endava (4.5/5) edges ahead of Version 1 (3.9/5) overall. Endava is the better choice for large UK programmes, payments and banking, nearshore at volume. Version 1 is the stronger option for oracle and Microsoft estates, public-sector managed services. The right choice depends on your project size, budget, and required tech stack.
Endava vs Version 1: head-to-head summary
| Criterion | Endava | Version 1 |
|---|---|---|
| Founded | 2000 | 1996 |
| HQ | London, United Kingdom | Dublin, Ireland (UK offices including Birmingham) |
| Team size | 10,000+ | 3,000+ |
| Rating | 4.5 / 5 | 3.9 / 5 |
| Primary differentiator | UK headquarters and governance with more than 10,000 engineers in lower-cost nearshore locations | Managed services for Oracle, Microsoft and AWS estates with Indian and Spanish delivery |
| Pricing model | Time and materials, managed service, outcome-based contracts | Managed service, time and materials, fixed price |
| Min. engagement | Not published | Not published |
| Primary tech stack | Java, .NET, AWS | Oracle, Microsoft Azure, AWS |
| Industries served | Financial services, Payments, Retail, Media and telecoms, Healthcare | Public sector, Financial services, Healthcare, Utilities |
Endava vs Version 1: overview
Endava
Endava is the largest UK-headquartered company on this list built around nearshore delivery. It reported 11,479 staff at the end of June 2025, and the UK supplied 33% of revenue in the final quarter of that fiscal year. Delivery centres in Romania, Moldova, North Macedonia, Serbia, Bulgaria, Argentina and elsewhere let it staff large programmes at below-London cost. Headcount fell from 12,085 a year earlier, which reflects softer demand across the IT services market.
Version 1
Version 1 was founded in Dublin in 1996 and has been majority-owned by Swiss investor Partners Group since July 2022, in a deal reported at around €800m. It had more than 3,200 staff by 2023 and opened a Birmingham hub with 500 planned jobs, plus UK acquisitions such as Automation Logic. Much of its UK work is Oracle, Microsoft and AWS managed services for public-sector bodies. Delivery comes from Ireland, the UK, Spain and India.
Services and capabilities: Endava vs Version 1
| Capability | Endava | Version 1 |
|---|---|---|
| Custom software development | ✓ | ✓ |
| Mobile app development | ✗ | ✗ |
| Cloud & DevOps | ✓ | ✓ |
| Data & AI | ✓ | ✓ |
| Legacy modernisation | ✓ | ✓ |
| Embedded & IoT | ✗ | ✗ |
| Dedicated team model | ✓ | ✗ |
| Fixed-price projects | ✗ | ✓ |
Tech stack comparison: Endava vs Version 1
| Framework / platform | Endava | Version 1 |
|---|---|---|
| .NET | ✓ | ✓ |
| Java | ✓ | ✓ |
| Python | ✓ | N/A |
| React | N/A | N/A |
| AWS | ✓ | ✓ |
| Azure | ✓ | ✓ |
| Kubernetes | ✓ | N/A |
| Embedded | N/A | N/A |
Pricing comparison: Endava vs Version 1
| Criterion | Endava | Version 1 |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Dedicated team, Managed service, Time and materials | Managed service, Fixed project, Time and materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Endava vs Version 1
| Dimension | Endava | Version 1 |
|---|---|---|
| Best company size | Enterprise | Startup to mid-market |
| Best industries | Financial services, Payments, Retail | Public sector, Financial services, Healthcare |
| Best use cases | A UK bank needs 50+ engineers for a multi-year core platform programme., A payments company wants a managed service covering development, testing and support. | A public body needs Oracle E-Business Suite support and migration., A utility wants Azure managed services. |
| Typical project type | Dedicated team | Managed service |
Endava vs Version 1: pros and cons
| Endava | |
|---|---|
| + | Public-company reporting gives buyers audited figures on headcount, revenue and client concentration |
| + | A UK board and London HQ simplify contracting and data-protection discussions for UK buyers |
| + | Delivery from several countries spreads risk if one location is disrupted |
| + | Long payments and banking track record with UK and European institutions |
| - | Headcount dropped about 5% in the year to June 2025 as demand softened |
| - | Smaller projects can get less senior attention than flagship accounts |
| - | Day rates are higher than those of smaller Central European vendors |
| Version 1 | |
|---|---|
| + | Strong in Oracle and Microsoft environments common in UK public bodies |
| + | Indian and Spanish delivery lower costs on managed services |
| + | Private-equity backing has funded UK expansion |
| - | Majority-owned by Partners Group since 2022, so an eventual sale or exit is likely |
| - | Product-style bespoke development is less central than managed services |
Who should choose Endava?
A typical fit: a UK bank needs 50+ engineers for a multi-year core platform programme.
UK headquarters and governance with more than 10,000 engineers in lower-cost nearshore locations. Minimum engagement is not publicly disclosed. Works best with clients in Financial services, Payments, Retail, Media and telecoms, Healthcare.
Who should choose Version 1?
A typical fit: a public body needs Oracle E-Business Suite support and migration.
Managed services for Oracle, Microsoft and AWS estates with Indian and Spanish delivery. Minimum engagement is not publicly disclosed. Works best with clients in Public sector, Financial services, Healthcare, Utilities.
Decision matrix: Endava vs Version 1
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Version 1 |
| You need a large dedicated team for an ongoing programme | Endava |
| Your budget is at the lower end | Compare: Endava (Not published) vs Version 1 (Not published) |
| You need specialist depth in a specific vertical | Endava |
| You want engineers added to your own in-house team | Neither lists team extension; ask about dedicated teams |
| Your product includes hardware, firmware or connected devices | Neither; consider an embedded specialist |
Use case fit: Endava vs Version 1
| Use case | Endava fit | Version 1 fit | Winner |
|---|---|---|---|
| A UK bank needs 50+ engineers for a multi-year core platform programme. | Strong | Limited | Endava |
| A payments company wants a managed service covering development, testing and support. | Strong | Limited | Endava |
| A public body needs Oracle E-Business Suite support and migration. | Limited | Strong | Version 1 |
| A utility wants Azure managed services. | Limited | Strong | Version 1 |
| You need hardware, firmware or IoT work in the same contract | Limited | Limited | Both equally |
| You want a fixed-price first phase before a longer engagement | Limited | Strong | Version 1 |
Verdict: Endava vs Version 1
Endava (4.5/5) is the stronger overall choice for most Software Development Outsourcing projects. UK headquarters and governance with more than 10,000 engineers in lower-cost nearshore locations.
Version 1 (3.9/5) is worth a look in a scenario like this: a utility wants Azure managed services. If your situation matches that, Version 1 is a competitive option.
Related comparisons
Endava vs Version 1 FAQ
Is Endava better than Version 1?
Endava (4.5/5) scores higher overall, but "better" depends on your use case. Endava's strongest advantage: public-company reporting gives buyers audited figures on headcount, revenue and client concentration. Version 1's strongest advantage: strong in Oracle and Microsoft environments common in UK public bodies.
How do Endava and Version 1 differ in pricing?
Endava uses time and materials, managed service, outcome-based contracts pricing. Version 1 uses managed service, time and materials, fixed price pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Endava or Version 1?
Endava is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each company before shortlisting.
What are the main differences between Endava and Version 1?
Endava's primary differentiator is: UK headquarters and governance with more than 10,000 engineers in lower-cost nearshore locations. Version 1's primary differentiator is: managed services for Oracle, Microsoft and AWS estates with Indian and Spanish delivery. They also differ in team size (10,000+ vs 3,000+), minimum engagement (Not published vs Not published), and primary industries served (Financial services, Payments vs Public sector, Financial services).
Verify all details directly with each company before making a decision.