Who is Pramod Bhasin?
Pramod Bhasin helped build the operation within GE that became Genpact. Its origins include a 1997 back-office pilot for GE Capital. His story is a case of building a venture inside a larger institution before the business developed a wider independent identity.
- Founder profiled
- Pramod Bhasin
- Company or institution
- Genpact
- Reading lens
- Technology services
Source starting point: Genpact: the company’s journey from its 1997 pilot ↗. Full sources and context appear below.
Not every founder begins outside an established organisation. Genpact’s history starts with a pilot inside GE Capital in 1997, focused on improving back-office operations. Pramod Bhasin, identified by ICRIER as Genpact’s founder, had worked across GE’s international businesses and led GE Capital in Asia and India.
From internal work to a service
Genpact’s published timeline describes its emphasis on process efficiency and the development of Lean and Six Sigma methods. It later became an independent company and listed in New York in 2007. The founding chapter highlights the commercial potential of a capability first developed for an internal customer.
A process needs context
An efficient sequence of tasks is useful only if it serves the right outcome. A services business must understand exceptions, handovers and the customer’s wider operation. Repeating a process in a new organisation often requires adaptation, even when the underlying method is familiar.
The founder lens
Our reading of Bhasin’s story is to look within established work for capabilities that solve a broader problem. A team may be doing something valuable before it has named that activity as a business. The next step is to determine which parts can travel to a new customer and which depend on the original setting.
Find the assumptions supplied by the original customer
An internal team can depend on shared systems, informal access and knowledge of how its organisation works. Those advantages may disappear when the same capability is offered externally. A founder should identify which parts of the service are repeatable and which rely on the original environment. New customers need a clear scope, an onboarding process and a way to assess delivery. Improving a process also requires understanding why it exists; making an unnecessary step faster is different from removing the need for it. The useful business story follows that transition from local expertise to a service with responsibilities another organisation can confidently understand.
The decision and its trade-offs
An internal customer can provide access and a defined problem, but also hide assumptions that an external customer would question. The operating challenge is to make a process measurable and transferable. A service that works because a few people know the parent organisation well may need substantial redesign before it can serve a broader market.
How to investigate the operating model
Document the incoming work, decision rules, exceptions and handovers in one process. Measure completion quality as well as speed. Then ask which steps depend on informal access to the original customer. Those dependencies identify where a growing service organisation needs clearer interfaces, training or escalation paths before taking on unfamiliar clients.
Evidence and context
An internal venture benefits from a different resource and customer environment than a startup beginning independently. Its history offers useful operational questions, but does not provide a universal launch template.
Put the idea to work
Use these questions to investigate the idea in your own context.
- List the systems and knowledge supplied by the original organisation.
- Define what a new customer must provide before work begins.
- Measure whether the process solves the customer’s underlying need.
A closer look
What is distinctive about an internal venture becoming independent?
It must translate a capability developed for one setting into a proposition others can buy and use. The Genpact profile examines that organisational transition rather than presenting efficiency methods as a guaranteed result.
What should a founder investigate in the Genpact story?
Compare repeatability, error recovery and transfer to new customers. A successful pilot proves less than a process that keeps working across settings.
Sources & editorial note
This profile draws on the public sources below. Company and founder accounts describe their own perspective. Our analysis, questions and takeaway are editorial interpretation. This is not an original interview or a sponsored feature.
See our editorial standards or request a correction. For a useful comparison, read N. R. Narayana Murthy: the Infosys founder story. Explore the founder topic guides for connected reading paths.


