Kainos vs BJSS (CGI): full comparison for 2026
Quick verdict
Kainos (4.2/5) edges ahead of BJSS (CGI) (4.0/5) overall. Kainos is the better choice for UK government digital services, Workday programmes. BJSS (CGI) is the stronger option for NHS and government programmes, large onshore delivery. The right choice depends on your project size, budget, and required tech stack.
Kainos vs BJSS (CGI): head-to-head summary
| Criterion | Kainos | BJSS (CGI) |
|---|---|---|
| Founded | 1986 | 1993 |
| HQ | Belfast, United Kingdom | Leeds, United Kingdom (owned by CGI) |
| Team size | 3,000+ | 2,000–2,500 |
| Rating | 4.2 / 5 | 4.0 / 5 |
| Primary differentiator | Combined government digital delivery and Workday partnership, listed on the LSE | Large UK onshore delivery capacity, now backed by CGI's global network |
| Pricing model | Time and materials, fixed price, framework call-offs | Time and materials, fixed price, managed service |
| Min. engagement | Not published | Not published |
| Primary tech stack | Java, .NET, AWS | Java, .NET, AWS |
| Industries served | Public sector, Healthcare, Financial services, Commercial enterprises | Public sector, Healthcare, Financial services, Retail, Energy |
Kainos vs BJSS (CGI): overview
Kainos
Kainos was founded in Belfast in 1986 and is listed on the London Stock Exchange. In the year to March 2026 it reported revenue of £431.1m, up 17%, and a workforce of 3,216 after adding 420 people, a rebound from a 2024/25 restructuring that cut staff by 7%. It runs three divisions: Digital Services, Workday Services and Workday Products. Its government work spans departments such as the Home Office and NHS bodies, delivered from the UK and Ireland.
BJSS (CGI)
BJSS was founded in Leeds in 1993 and grew into one of the UK's largest independent technology consultancies before CGI completed its acquisition in February 2025. The deal brought about 2,400 BJSS staff into CGI and took CGI's UK headcount past 8,500. BJSS teams are being merged into CGI's metro-based UK operating model. UK clients get the scale and governance of a global group, with nearshore capacity now available through CGI centres such as Portugal.
Services and capabilities: Kainos vs BJSS (CGI)
| Capability | Kainos | BJSS (CGI) |
|---|---|---|
| Custom software development | ✓ | ✓ |
| Mobile app development | ✗ | ✗ |
| Cloud & DevOps | ✓ | ✓ |
| Data & AI | ✓ | ✓ |
| Legacy modernisation | ✓ | ✗ |
| Embedded & IoT | ✗ | ✗ |
| Dedicated team model | ✗ | ✗ |
| Fixed-price projects | ✓ | ✓ |
Tech stack comparison: Kainos vs BJSS (CGI)
| Framework / platform | Kainos | BJSS (CGI) |
|---|---|---|
| .NET | ✓ | ✓ |
| Java | ✓ | ✓ |
| Python | ✓ | ✓ |
| React | N/A | N/A |
| AWS | ✓ | ✓ |
| Azure | ✓ | ✓ |
| Kubernetes | ✓ | ✓ |
| Embedded | N/A | N/A |
Pricing comparison: Kainos vs BJSS (CGI)
| Criterion | Kainos | BJSS (CGI) |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Fixed project, Time and materials | Fixed project, Managed service, Time and materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Kainos vs BJSS (CGI)
| Dimension | Kainos | BJSS (CGI) |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Public sector, Healthcare, Financial services | Public sector, Healthcare, Financial services |
| Best use cases | A government department needs a GOV.UK service built and run., An NHS body wants a digital patient service delivered onshore. | An NHS trust needs a national-scale digital service., A bank wants a large onshore team with independent testing. |
| Typical project type | Fixed project | Fixed project |
Kainos vs BJSS (CGI): pros and cons
| Kainos | |
|---|---|
| + | Belfast-based delivery costs less than London while staying UK-based |
| + | Public reporting gives buyers verified financials and headcount |
| + | Very familiar with UK public-sector procurement frameworks |
| - | Little offshore capacity, so rates do not compete with nearshore vendors |
| - | Workday business takes a growing share of leadership focus |
| - | The 2024/25 restructuring shows exposure to swings in public-sector spending |
| BJSS (CGI) | |
|---|---|
| + | Long record on large NHS and government programmes |
| + | CGI ownership adds financial stability and access to nearshore centres |
| + | Strong testing and quality engineering practice |
| - | Acquired by CGI in 2025, and integration into CGI's model may change account teams and processes |
| - | Large-consultancy pricing and governance are heavy for small projects |
Who should choose Kainos?
A typical fit: a government department needs a GOV.UK service built and run.
Combined government digital delivery and Workday partnership, listed on the LSE. Minimum engagement is not publicly disclosed. Works best with clients in Public sector, Healthcare, Financial services, Commercial enterprises.
Who should choose BJSS (CGI)?
A typical fit: an NHS trust needs a national-scale digital service.
Large UK onshore delivery capacity, now backed by CGI's global network. Minimum engagement is not publicly disclosed. Works best with clients in Public sector, Healthcare, Financial services, Retail, Energy.
Decision matrix: Kainos vs BJSS (CGI)
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Kainos |
| You need a large dedicated team for an ongoing programme | Check each company's engagement model |
| Your budget is at the lower end | Compare: Kainos (Not published) vs BJSS (CGI) (Not published) |
| You need specialist depth in a specific vertical | BJSS (CGI) |
| 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: Kainos vs BJSS (CGI)
| Use case | Kainos fit | BJSS (CGI) fit | Winner |
|---|---|---|---|
| A government department needs a GOV.UK service built and run. | Strong | Limited | Kainos |
| An NHS body wants a digital patient service delivered onshore. | Strong | Limited | Kainos |
| An NHS trust needs a national-scale digital service. | Limited | Strong | BJSS (CGI) |
| A bank wants a large onshore team with independent testing. | Limited | Strong | BJSS (CGI) |
| 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 | Strong | Strong | Both equally |
Verdict: Kainos vs BJSS (CGI)
Kainos (4.2/5) is the stronger overall choice for most Software Development Outsourcing projects. Combined government digital delivery and Workday partnership, listed on the LSE.
BJSS (CGI) (4.0/5) is worth a look in a scenario like this: a bank wants a large onshore team with independent testing. If your situation matches that, BJSS (CGI) is a competitive option.
Related comparisons
Kainos vs BJSS (CGI) FAQ
Is Kainos better than BJSS (CGI)?
Kainos (4.2/5) scores higher overall, but "better" depends on your use case. Kainos's strongest advantage: belfast-based delivery costs less than London while staying UK-based. BJSS (CGI)'s strongest advantage: long record on large NHS and government programmes.
How do Kainos and BJSS (CGI) differ in pricing?
Kainos uses time and materials, fixed price, framework call-offs pricing. BJSS (CGI) uses time and materials, fixed price, managed service pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Kainos or BJSS (CGI)?
BJSS (CGI) 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 Kainos and BJSS (CGI)?
Kainos's primary differentiator is: combined government digital delivery and Workday partnership, listed on the LSE. BJSS (CGI)'s primary differentiator is: large UK onshore delivery capacity, now backed by CGI's global network. They also differ in team size (3,000+ vs 2,000–2,500), minimum engagement (Not published vs Not published), and primary industries served (Public sector, Healthcare vs Public sector, Healthcare).
Verify all details directly with each company before making a decision.