Monday, August 17, 2026 | 04:54 PM ISTहिंदी में पढें
Business Standard
Notification Icon
userprofile IconSearch

Tredence eyes Europe, GCC expansion to reduce US revenue dependence

The data analytics and AI firm is focusing on Europe and GCC markets, expanding beyond retail CPG and the US, while building partnerships and AI-led capabilities to drive growth

Rakesh Sancheti, Chief Growth Officer at Tredence.
premium

Rakesh Sancheti, Chief Growth Officer at Tredence.

Avik Das Bengaluru

Listen to This Article

Rakesh Sancheti, chief growth officer at data analytics and AI firm Tredence, says the company is looking to reduce its dependence on the United States for revenue. In an interview to Avik Das, he discusses the company's growth strategy, geographic diversification, and how it wants to create a differentiated offering in the GCC market. Edited excerpts:

Q: What are some of the pillars of growth that you have charted out as the growth officer?

Retail consumer packaged goods (CPG) has been our core where we have had an industry leading capability and growth which helped us raising funds in the first two rounds. I think we need to go outside of retail CPG and focus also on banking, financial services, healthcare, and life sciences where there is a huge amount of opportunity for data and AI. And with this whole agentic AI, we can solve a lot of new use cases and create disruption. So while we continue to grow and scale the retail CPG business, my mandate is to diversify further across verticals.
 
The second one is (that) we are very focused on our partnership. We have realised that to solve end-to-end problems for our customer and truly be a customer-first organisation, we need to come out of the technology stack and think of the end-to-end outcome. So the focus is also to diversify technology partnerships in the new world of AI. We are trying to leverage the world of hyperscalers, whether it’s a Google cloud, Snowflake, AWS, Microsoft, or Anthropic.
 
The third is more of a regional diversification because we can't be entirely North America-centric. So I work with our regional teams and am looking to expand in the Middle East and Europe.

Q: Since you talk about expanding in Europe, what proportion of your revenue will be from that geography in two years?

Currently, it is about 10-12 per cent with the US contributing about 75 per cent. In an ideal world, I would say the balance between US and non-US revenue should be about 70:30. We have already made progress with a lot of companies based in the UK, Benelux, Germany, and France. We are focusing on the huge industrial footprint in Germany and the Nordics. We (have) already had early success of acquiring (a) few clients, especially in the renewable energy sector. The reason we have created a separate business unit for Europe is due to these huge expectations. We aspire to grow almost five times in the next three years.

Q: How do you want to leverage the GCC business?

What we realise is almost half our customer base have invested heavily in GCC and they are mature ones working even with the IT services companies. But the new world order demands transforming their internal operations to deliver their AI mandate for their organisation. It requires a different skill set, operating models, and vendors. And when they look to set up their AI centre of excellence they need a partner who has the experience to co-build, co-design, co-innovate, and co-scale with them.

Q: How do you differentiate your offerings compared to system integrators?

We know that if GCC has to be successful, it has to be a co-delivery model. We have come up with a flexible and pod-based model. There are three types of pods - the first model is about co-building things together where the requirements are a little bit unknown. This is usually for GCCs with low maturity levels. The second model is where requirements are known, but they don't have the skill set and capacity. There almost 80 per cent of the work is owned by of us with the remaining with the product owners. And the third one is like a co-anchor where the requirements are very clear and the GCC wants to deploy the model at scale.