Tech Update

Nandan Nilekani, a renowned technology leader and co-founder of Infosys, has stepped down as a general partner at Fundamentum Partnership, a venture capital firm he co-founded nearly a decade ago. Despite the change in title, Nilekani will continue to advise the firm, mentor portfolio company founders, and provide strategic guidance.

Nandan Nilekani's Legacy

Nilekani is one of India's best-known technology leaders, having co-founded Infosys and led the creation of Aadhaar, India's biometric identity system. He has also been a leading advocate of the country's digital public infrastructure, including the Unified Payments Interface (UPI), a real-time payments network used by hundreds of millions of Indians.

Fundamentum's New Fund

Fundamentum has launched its third fund, which aims to back eight to ten early-stage startups building consumer technology, fintech, and AI products. The fund will issue initial checks of about ₹100 crore (around $10 million) and has already begun deploying capital.

Investment Strategy

The fund expects to raise roughly half of its target from international investors, and the remainder from Indian institutions, family offices, founders, and the firm's partners. This balance reflects the evolution of India's venture capital ecosystem over the past decade, with Indian investors now playing a much larger role in domestic funds.

Key Features of Fund III

Backs early-stage startups building consumer technology, fintech, and AI products
Issues initial checks of about ₹100 crore (around $10 million)
Aims to raise roughly half of its target from international investors
Remainder of funds to be raised from Indian institutions, family offices, founders, and the firm's partners

Future Prospects

Technology teams are watching tech update closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.