Ciklum vs Thoughtworks: full comparison for 2026
Quick verdict
Ciklum (4.1/5) edges ahead of Thoughtworks (3.9/5) overall. Ciklum is the better choice for large dedicated teams with a London contract. Thoughtworks is the stronger option for complex modernisation, engineering culture change. The right choice depends on your project size, budget, and required tech stack.
Ciklum vs Thoughtworks: head-to-head summary
| Criterion | Ciklum | Thoughtworks |
|---|---|---|
| Founded | 2002 | 1993 |
| HQ | London, United Kingdom | Chicago, United States (UK offices) |
| Team size | 3,000–4,500 | 10,000+ |
| Rating | 4.1 / 5 | 3.9 / 5 |
| Primary differentiator | London headquarters with a long history of large dedicated teams in Ukraine and Central Europe | Thought leadership in software practice, backed by a large global delivery network |
| Pricing model | Dedicated team, time and materials, managed service | Time and materials |
| Min. engagement | Not published | Not published |
| Primary tech stack | Java, .NET, Python | Java, Kotlin, TypeScript |
| Industries served | Financial services, Retail, Healthcare, Media, Travel | Financial services, Retail, Public sector, Healthcare, Media |
Ciklum vs Thoughtworks: overview
Ciklum
Danish entrepreneur Torben Majgaard started Ciklum in 2002 in Kyiv. It is now headquartered in London's Shoreditch and employs around 4,000 people. Its investors have included Horizon Capital, a fund associated with George Soros, and Dragon Capital, but current ownership is not publicly documented. Delivery is concentrated in Ukraine and Poland, plus the Czech Republic since its 2021 acquisition of Prague-based CN Group.
Thoughtworks
Thoughtworks was founded in Chicago in 1993 and has had a significant UK presence for decades. Apax Partners took it private in a deal valued at about $1.75bn that closed in late 2024, after a NASDAQ listing in 2021, and the transaction came with job cuts affecting about 6–7% of its 10,500 staff. It is known for its Technology Radar and for shaping agile and continuous-delivery practice. It has delivery centres in India, China, Brazil and elsewhere, but UK engagements usually lean on senior onshore consultants.
Services and capabilities: Ciklum vs Thoughtworks
| Capability | Ciklum | Thoughtworks |
|---|---|---|
| Custom software development | ✓ | ✓ |
| Mobile app development | ✗ | ✗ |
| Cloud & DevOps | ✓ | ✓ |
| Data & AI | ✓ | ✓ |
| Legacy modernisation | ✗ | ✓ |
| Embedded & IoT | ✗ | ✗ |
| Dedicated team model | ✓ | ✗ |
| Fixed-price projects | ✗ | ✗ |
Tech stack comparison: Ciklum vs Thoughtworks
| Framework / platform | Ciklum | Thoughtworks |
|---|---|---|
| .NET | ✓ | N/A |
| Java | ✓ | ✓ |
| Python | ✓ | N/A |
| React | ✓ | N/A |
| AWS | ✓ | ✓ |
| Azure | ✓ | ✓ |
| Kubernetes | N/A | ✓ |
| Embedded | N/A | N/A |
Pricing comparison: Ciklum vs Thoughtworks
| Criterion | Ciklum | Thoughtworks |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Dedicated team, Managed service, Time and materials | Time and materials, Team extension |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Ciklum vs Thoughtworks
| Dimension | Ciklum | Thoughtworks |
|---|---|---|
| Best company size | Startup to mid-market | Enterprise |
| Best industries | Financial services, Retail, Healthcare | Financial services, Retail, Public sector |
| Best use cases | A retailer needs a 30-person e-commerce team., A healthcare firm wants a managed QA and testing service. | A bank wants to break up a core monolith., A retailer needs to rebuild its platform and change how teams work. |
| Typical project type | Dedicated team | Time and materials |
Ciklum vs Thoughtworks: pros and cons
| Ciklum | |
|---|---|
| + | London HQ makes contracting simple for UK buyers |
| + | Twenty years of experience running large remote teams |
| + | Several delivery countries spread location risk |
| - | Ownership has changed hands between investors several times, and the current cap table is not public |
| - | A large Ukrainian workforce means continuity plans need review |
| - | Mid-sized clients may find the sales process heavy |
| Thoughtworks | |
|---|---|
| + | Very strong senior consultants and engineering practices |
| + | Global delivery network for blended teams |
| + | Well suited to modernisation programmes that need cultural change |
| - | Taken private by Apax in 2024 alongside a restructuring that cut 6–7% of staff |
| - | Premium pricing, especially with senior UK consultants |
| - | Overkill for straightforward builds |
Who should choose Ciklum?
A typical fit: a retailer needs a 30-person e-commerce team.
London headquarters with a long history of large dedicated teams in Ukraine and Central Europe. Minimum engagement is not publicly disclosed. Works best with clients in Financial services, Retail, Healthcare, Media, Travel.
Who should choose Thoughtworks?
A typical fit: a bank wants to break up a core monolith.
Thought leadership in software practice, backed by a large global delivery network. Minimum engagement is not publicly disclosed. Works best with clients in Financial services, Retail, Public sector, Healthcare, Media.
Decision matrix: Ciklum vs Thoughtworks
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Both offer fixed-price models |
| You need a large dedicated team for an ongoing programme | Ciklum |
| Your budget is at the lower end | Compare: Ciklum (Not published) vs Thoughtworks (Not published) |
| You need specialist depth in a specific vertical | Ciklum |
| You want engineers added to your own in-house team | Thoughtworks |
| Your product includes hardware, firmware or connected devices | Neither; consider an embedded specialist |
Use case fit: Ciklum vs Thoughtworks
| Use case | Ciklum fit | Thoughtworks fit | Winner |
|---|---|---|---|
| A retailer needs a 30-person e-commerce team. | Strong | Limited | Ciklum |
| A healthcare firm wants a managed QA and testing service. | Strong | Limited | Ciklum |
| A bank wants to break up a core monolith. | Limited | Strong | Thoughtworks |
| A retailer needs to rebuild its platform and change how teams work. | Limited | Strong | Thoughtworks |
| 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 | Limited | Both equally |
Verdict: Ciklum vs Thoughtworks
Ciklum (4.1/5) is the stronger overall choice for most Software Development Outsourcing projects. London headquarters with a long history of large dedicated teams in Ukraine and Central Europe.
Thoughtworks (3.9/5) is worth a look in a scenario like this: a retailer needs to rebuild its platform and change how teams work. If your situation matches that, Thoughtworks is a competitive option.
Related comparisons
Ciklum vs Thoughtworks FAQ
Is Ciklum better than Thoughtworks?
Ciklum (4.1/5) scores higher overall, but "better" depends on your use case. Ciklum's strongest advantage: london HQ makes contracting simple for UK buyers. Thoughtworks's strongest advantage: very strong senior consultants and engineering practices.
How do Ciklum and Thoughtworks differ in pricing?
Ciklum uses dedicated team, time and materials, managed service pricing. Thoughtworks uses time and materials pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Ciklum or Thoughtworks?
Ciklum 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 Ciklum and Thoughtworks?
Ciklum's primary differentiator is: london headquarters with a long history of large dedicated teams in Ukraine and Central Europe. Thoughtworks's primary differentiator is: thought leadership in software practice, backed by a large global delivery network. They also differ in team size (3,000–4,500 vs 10,000+), minimum engagement (Not published vs Not published), and primary industries served (Financial services, Retail vs Financial services, Retail).
Verify all details directly with each company before making a decision.