Posted on

iSPIRT Playgrounds Coda

As you may have heard from us or read about in our publications, iSPIRT takes the long view on problems. We call ourselves 30 year architects for India’s hard problems. The critical insight to a 30-year journey of success is that it requires one to be able to work with and grow the ecosystem, rather than grow itself. An iSPIRT with more than 150 volunteers would collapse under its own weight. Instead we work tirelessly to build capacity in our partners and help them on their journeys. We remain committed to being in the background, taking pride in the success of our partners who are solving for India’s hard problems.

However, many people think we’re trying to square a circle here. Why would anybody, that too, folks in Tech jobs who get paid tremendously well, volunteer their time for the success of others? 

The motivation for volunteering is hard to explain to those who have not experienced the joy volunteering brings. Our story is not unique. Most famously, when the Open source movement was taking root, Microsoft’s then CEO, Steve Ballmer, called Open Source “cancer”.

We have published all of our thinking on our model as and when it crystallised. However, we realised a compendium was needed to put our answers to the most commonly expressed doubts about iSPIRT in one place. This is that compendium for our volunteers, partners, donors and beyond.

1. What is iSPIRT?

a) iSPIRT is a not-for-profit think tank, staffed mostly by volunteers from the tech world, who dedicate their time, energy and expertise towards India’s hard problems.

b) iSPIRT believes that India’s hard problems are larger than the efforts of any one market player or any one public institution or even any one think-tank like ourselves. These societal problems require a whole-of-society effort. We do our part to find market players and government entities with the conviction in this approach and help everyone work together.

c) In practical terms, this means that the government builds the digital public infrastructure, and the market participants build businesses on top of it. We support both of them with our expertise. We have iterated this model and continue to improve and refine this model.

d) To play this role we use our mission to align with the Government partners, Market partners and our own volunteers. We believe those who have seen us work up close place their trust in us to work towards our mission. Our long-term survival depends on this trust. All our actions and processes are designed to maintain this trust, and so far if we have any success at all, it can only be seen as a validation of this trust.

2. What is our volunteering model?

a) Anyone can apply to be a balloon volunteer, and we work with them to see if there is a fit.

b) The ideal qualities of a volunteer are publicly available in our Volunteering Handbook, the latest one was published in December 2017.

c) We require every volunteer to declare their conflicts, and ask them to select a pledge level. This pledge level determines their access to policy teams and information that can lead to potential conflict of interest. For every confirmed volunteer, we make available this pledge level publicly on our website.

d) We are often asked what’s in it for our volunteers. We let all our volunteers know this is “No Greed, No Glory” work. Wikipedia is maintained by thousands of volunteers, none of them get individual author credits. What volunteers get is the joy of working on challenging problems a sense of pride in building something useful for society a community of like-minded individuals who are willing to work towards things larger than themselves

e) There are not too many people who would do this for no money, but it does not take a lot of people to do what we do. All of this is given in much greater detail in our Volunteer Handbook.

3. How does iSPIRT decide the initiatives it works on?

a) We have seen success due to the quality of our work and the commitment to our mission. We only take on challenges related to societal problems where technology can make a difference.

b) Even within those problems, our expertise and focus is in solving the subclass of problems where the hard task of coordination between State and Market, between public infra and private innovation is crucial to the task at hand.

4. How does it work with State and Market partners

a) On the hard problems we select in #3 above we assemble a team of volunteers. These volunteers outline a vision for the future. We begin by sharing this vision in multiple forums and creating excitement around them. Examples of these forums are: 

  1. 2015: Whatsapp moment of India. Nandan Nilekani presentation on the future of finance and many articles written about it
  2. 2016: Startup India Launch – Jan 2016 13th. India Stack unveiled as part of official program of Digital India (Public event)
  3. 2017: Cash Flow Lending – DEPA launch 2017 August – Carnegie India Nandan Nilekani and Siddharth Shetty Presentation
  4. Many different public appearances by Pramod Varma, Sharad Sharma, Sanjay Jain, Nikhil Kumar
  5. 2019: Siddharth Shetty explaining AA at an event at @WeWork Bangalore
  6. 2019 Sahamati Launch with a presentation by Nandan Nilekani and representatives from MeiTY, SEBI, multiple Bank CEOs, and AA entrepreneurs.

b) On market partners

i. We work with any market partner who shows conviction towards the idea, and are willing to commit their own resources to take the vision forward. Previous and current partners include banks, startups, tech product and service companies. These early adopter partners form part of our Wave 1 cohort. 

ii. We dive deeper with this wave 1 cohort and iterate together to build on the “private innovation” side of the original vision with their feedback. This is developed with the mutual commitment to sharing our work in the public domain, for public use, once we have matured the idea. We work with them and iterate till we surface a MVP for wider review.

iii. At iSPIRT, we don’t like mission capture. There are no commercial arrangements between iSPIRT and any individual market participants. 

iv. We never recommend specific vendors to any of our partners.

v. New infrastructure/ new frameworks often require the creation of a new type of entity. We engage with these through domain specific organizations such as Sahamati for Account aggregators, as an example.

vi. After Wave 1 partners co-create an MVP, we open up for wider public review and participation. We make public all of our learnings to help the creation of Wave 2 of market participants.

vii. The mental model you should have for iSPIRT Vision/Wave 1/ Wave 2 is those of Alpha/closed Beta/public Beta in the tech world.

c) On government partners

i. We work together with any government partners who show conviction towards the idea, and are willing to commit their own resources to take the vision forward. Previous partners have been RBI, NPCI, MeiTY, TRAI, etc.

ii. We dive deeper with these partners and iterate together to build on the “public infrastructure” side of the original vision with their feedback. As part of the government process, many authorities have their own process to finalize documents, etc. Many of these involve publishing drafts, APIs etc. for feedback, and potential improvement from market participants. We publish the work we do together and invite public comments. Examples: UPI Payment Protocol; MeITY Electronic Consent Artefact; ReBIT Account Aggregator specifications

iii. We only advise government partners on technology standards and related expertise. 

iv. There are no commercial arrangements between iSPIRT and government partners, not even travel expenses.

v. We never recommend any specific market players for approval towards any licenses or permissions. Both iSPIRT and our partners would suffer greatly if this process was tarnished.

  1. With UPI we did not recommend any individual PSPs for inclusion in the network. This was entirely RBI and NPCI prerogative.
  2. Similarly for AA, RBI alone manages selection of AAs for approvals of licenses.

vi. We also respond to public comments wherever they are invited. The following are some examples of our transparent engagement on policy issues.

  1. iSPIRT Public Comments & Submission to Srikrishna Privacy Bill
  2. iSPIRT Public comments to TRAI Consultations
  3. Support to RBI MSME Committee Report
  4. Support to RBI Public Credit Registry Report

5. How does iSPIRT make money?

a) iSPIRT’s expenses includes a living wage for some of its full-time volunteers, travel expenses and other incidental expenses related to our events. This is still a relatively small footprint and we are able to sustain entirely on donations.

b) These donations come from both individuals and institutions who want to support iSPIRT’s long-term vision for India’s hard problems. Sometimes, donor institutions include our market partners who have seen our work up close.

c) Partnerships do not require donations. We engage with many more market partners who are NOT donors than donors who are market players.

6. How does iSPIRT protect against conflict of interest?

We see two avenues of conflict of interest, and have governance mechanisms to protect against both

a) First is Donor Capture. We try to structure donation amounts and partners such that we are not dependent on any one source of funds and can maintain independence

i. We maintain a similar separation of concerns as do many news organizations with their investors.

ii. Our volunteers may have a cursory knowledge of who our donors are. However, this knowledge makes no difference to their outcomes.

b) Second is Volunteer conflicts, where they may get unfair visibility or information to make personal gains.

i. We screen for this risk extensively in the balloon volunteering period.

ii. We have hard rules around this that are strictly enforced and constantly reminded to all our volunteers in all our meetings.

iii. For volunteers who need advice whether a potential interaction could constitute conflict we provide an easy avenue through our Volunteer Fellows Council. The council will advise on whether there is conflict and if yes, how to mitigate it.

iv. To prevent a “revolving door” situation, we require that volunteers from the policy team leaving to continue their careers in the industry undergo a “cooling-off” period.

To volunteer with us, visit: volunteers.ispirt.in

The post is authored by our core volunteers, Meghana Reddyreddy and Tanuj Bhojwani. They can be reached at [email protected] and [email protected]

Posted on

COVID19 strikes cash flow lending for small businesses in the country

Many ongoing industry efforts to bring cash flow lending to life for MSMEs are now on hiatus

COVID19 strikes cash flow lending too

At iSPIRT, with our long-cherished dream of democratising credit in this country, we advocated for and built public infrastructure to enable market players to offer cash flow based lending solutions to small businesses. 

Pre-COVID: We argued that small businesses needed this new breed of products because they were unable to access formal credit otherwise.

During-COVID: As we process, accept and adapt to our new reality as a country, we realise small businesses need something much more urgently than cash flow based solutions from the market – they need rescue and stimulus packages from the government to survive the health and economic distress brought on by COVID19. 

Post-COVID: When the lending cycle picks up again in the market (and we will watch it diligently!) we will revive our efforts to bring cash flow based lending products to the market. For now, we are putting these efforts on a hiatus. This is because we think there’s a while for “Post-COVID” to come and many uncertainties are unfolding every day. So for now, we want to wear a “During-COVID” hat for the foreseeable future. 

This is disappointing for many parallel efforts that were underway in the market

Since July last year, after the U.K. Sinha chaired expert committee on MSMEs submitted its report to the RBI, many parallel efforts including Sahay, revamping of TReDS, PSB59, etc. by different market players were underway to bring cash flow lending ideas in this report to life. iSPIRT engaged with market players to design a digital public infrastructure first approach encapsulated in Sahay. The government was supportive of all of these, highlighting the importance of MSMEs within the economy.

Cash Flow Lending – The idea whose time will come

This slow down in the momentum is obviously disheartening for many iSPIRT volunteers and to all the market players we were working with. Months of hard work may not come to life in the next quarter or two. But these same months of hard work were possible only because we saw ourselves as architects with a 10-20 year horizon to solve India’s hard problems.

Cash Flow lending is a powerful idea to democratise credit in our country. It’s time will come, and come soon. Right now, we need to pace ourselves to our new realities and revive the energy again when lending picks up in this country.

About the Author: Meghana is a core volunteer and orchestrating our efforts in Democraticising credit at iSPIRT. She can be reached at [email protected]

Posted on

The future of ‘civic’ technologies after COVID-19

In 1973, the British economist Ernst Schumacher wrote his manifesto “Small is Beautiful”, and changed the world. Schumacher’s prescription — to use technologies that were less resource-intensive, capable of generating employment, and “appropriate” to local circumstances — appealed to a Western audience that worried about feverish consumption by the ‘boomer’ generation. Silicon Valley soon seized the moment, presenting modern-day, personal computing as an alternative to the tyranny of IBM’s Big Machine. Meanwhile, in India too, the government asked citizens to embrace technologies suited to the country’s socio-economic life. Both had ulterior motives: the miniaturisation of computing was inevitable given revolutions in semiconductor technology during the sixties and seventies, and entrepreneurs in Silicon Valley expertly harvested the anti-IBM mood to offer themselves as messiahs. The government in New Delhi too was struggling to mass-produce machines, and starved of funds, so asking Indians to “make do” with appropriate technology was as much a political message as it was a nod to environmentalism.

And thus, India turned its attention to mechanising bullock carts, producing fuel from bio-waste, trapping solar energy for micro-applications, and encouraging the use of hand pumps. These were, in many respects, India’s first “civic”, or socially relevant technologies.

The “appropriate technology” movement in India had two unfortunate consequences. The first has been a celebration of jugaad, or frugal innovation. Over decades, Indian universities, businesses and inventors have pursued low-cost technologies that are clearly not scaleable but valued culturally by peers and social networks. (Sample the press coverage every year of IIT students who build ‘sustainable’ but limited-use technologies, that generate fuel from plastic or trap solar energy for irrigation pumps.) Second, the “small is beautiful” philosophy also coloured our view of “civic technologies” as those that only mobilise the citizenry, out into farms or factory floors. Whether they took the form of a hand pump, solar stove or bullock cart, these technologies did little to augment the productivity of an individual. However, they preserved the larger status quo and did not disrupt social or industrial relations as technological revolutions have historically done. 

Nevertheless, there has always been a latent demand in India for technologies that don’t just mobilise individuals but also act as “playgrounds”, creating and connecting livelihoods. When management guru Peter Drucker visited post-Emergency India in 1979, Prime Minister Morarji Desai sold him hard on “appropriate technology”. India, Drucker wrote, had switched overnight from championing big steel plants to small bullock carts. Steel created no new jobs outside the factory, and small technologies did not improve livelihoods. Instead, he argued, India ought to look at the automotive industry as an “efficient multiplier” of livelihoods: beyond the manufacturing plant, automobiles would create new sectors altogether in road building and maintenance, traffic control, dealerships, service stations and repair. Drucker also pointed to the transistor as another such technology. Above all, transistors and automobiles connected Indians to one another through information and travel. Drucker noted during his visit that the motor scooter and radio transistor were in great demand in even far-flung corners, a claim that is borne by statistics. These, then were the civic technologies that mattered, ones that created playgrounds in which many could forge their livelihoods. 

The lionisation of jugaad is an attitudinal problem, and may not change immediately. But the task of creating a new generation of civic technologies that act as playgrounds can be addressed more readily.  In fact, it is precisely during crises such as the ongoing COVID-19 pandemic that India acutely requires such platforms.


Consider the post-lockdown task of economic reconstruction in India, which requires targeted policy interventions. Currently, the Indian government is blinkered to address only two categories of actors who need economic assistance: large corporations with their bottom lines at risk, and at the micro-level, individuals whose stand to lose livelihoods. India’s banks will bail out Big Business, while government agencies will train their digital public goods — Aadhaar, UPI, eKYC etc — to offer financial assistance to individuals. This formulaic approach misses out the vast category of SMEs who employ millions, account for nearly 40% of India’s exports, pull in informal businesses into the supply chain and provide critical products to the big industries.

To be sure, the data to identify SMEs (Income Tax Returns/ GSTN/ PAN) exists, as do the digital infrastructure to effect payments and micro-loans. The funds would come not only from government coffers but also through philanthropic efforts that have gained steam in the wake of the pandemic. However, the “playground” needs to be created — a single digital platform that can provide loans, grants or subsidies to SMEs based on specific needs, whether for salaries, utilities or other loan payments. A front-end application would provide any government official information about schemes applied for, and funds disbursed to a given SME.

Civic technologies in India have long been understood to mean small-scale technologies. This is a legacy of history and politics, which policymakers have to reckon with. The civic value of technology does not lie in the extent to which it is localised, but its ability to reach the most vulnerable sections of a stratified society like India’s. The Indian government, no matter how expansive its administrative machinery is, cannot do this on its own. It has to create “playgrounds” — involving banks, cooperative societies, regulators, software developers, startups, data fiduciaries and underwriting modellers — if it intends to make digital technologies meaningful and socially relevant.  

Please Note: A version of this was first published on Business Standard on 17 April 2020

About the author: Arun Mohan Sukumar is a PhD candidate at the Fletcher School, Tufts University, and a volunteer with the non-profit think-tank, iSPIRT. He is currently based in San Francisco. His book, Midnight’s Machines: A Political History of Technology in India, was published by Penguin Random House in 2019

Posted on

The history of technology is about to change radically. India must seize the moment

There are no atheists in foxholes, and there appear to be no capitalists in a global pandemic either. The head of Honeywell’s billion-dollar GoDirect Trade platform, which uses a permission-based blockchain to buy and sell aviation parts, declared on March 20 that American corporations had a “walled-garden” approach to data. “They need to start sharing data, a huge paradigm shift”, said Lisa Butters. Only a couple of weeks ago, Honeywell had been defending the virtues of a permission-based system, saying enterprises “needed some constraints to operate in”. 

What a difference a few days can make. 

Historically, the aviation industry has been one of the most secretive among ‘Big Tech’ sectors, with its evolution tied intimately to the Second World War, and the US-Soviet Cold War rivalry that followed soon after. Concerns around China’s theft of aerospace IP was among the foremost drivers behind the Obama administration’s negotiation of the 2015 agreement with China to prohibit “economic espionage”. It is the ultimate “winner-takes-all” market — but Boeing, its lynchpin, has now approached the US government for an existential bailout. Honeywell’s call for a “paradigm shift” is proof that the sector is not thinking just in hand-to-mouth terms. The aviation sector may get a lifeline for now, but as an industry forged by a global war, it knows more than most that a transformational moment for technology is upon it, which needs to be seized. 

As the economist Branko Milanović has highlighted, the correct metaphor for the Covid-19 pandemic and ensuing crisis is not the Great Recession of 2008, but the Second World War. To win WWII, and retain its military superiority, the United States pioneered technology complexes that placed innovation at the trifecta of a university lab, government, and market. (The blueprint for this model was drawn up in 1945 by Vannevar Bush, founder of Raytheon and director of the Office for Scientific Research and Development, and presented to the US government. The document was titled, “Science: The Endless Frontier”.) This was by no means a Western endeavour alone. Several countries, including India, followed suit, trying to perfect a model of “organised science”. In India, the Council for Scientific and Industrial Research was the totem for this effort and created a centralised network of national labs. The primary difference between Western models and ones in developing countries like India was the role of the state. In the US, the state retained regulatory agency over the process of technological innovation, but gradually ceded into the background as the Boeings, Westinghouses, GEs, Lockheed Martins, and IBMs took over. In India, the state became both the regulator and purveyor of technology. 

India’s attempts to create “national champions” in frontier technologies (think Hindustan Antibiotics Ltd, Electronics Corporation of India Ltd, Defence Research and Development Organisation, etc) failed because the state could not nimbly manufacture them at scale. Even as India pursued “moonshots”, those businesses in the United States that were incubated or came of age during the Second World War began to occupy pole positions in their respective technology markets. Once those markets matured, it made little sense for America to continue creating “organized” technology complexes, although research collaborations between universities and the federal government continued through the National Science Foundation. The banyan-ization of the internet and Silicon Valley — both seeded by generous assistance from the US Department of Defence — into a market dominated by the FAANG companies affirms this shift.

In the wake of the Covid-19 pandemic, however, the tables are turning. The United States is not only shifting away from “moonshots” but also pivoting towards “playgrounds”, settling on a model that India has perfected in the last decade or so.

The United States has often sought to repurpose private technologies as public utilities at key moments in its history. Communications technology was built and moulded into a public good by the American state. It was US law that enabled patent pooling by Bell Labs in the 19th century, leading to the creation of a “great new corporate power” in telephony. A few decades into the 20th century, American laws decreed telephone companies would be “common carriers”, to prevent price and service discrimination by AT&T. Meanwhile, both railroads and telecommunications providers were recognised as “interstate” services, subject to federal regulation. This classification allowed the US government to shape the terms under which these technologies grew. IT is precisely this template that Trump has now applied to telehealth technology in the US. Tele-medicine services could not previously be offered across state lines in the US, but the US government used its emergency powers last week to dissolve those boundaries. And on March 18, President Trump invoked the Defence Production Act, legislation adopted during the Korean War and occasionally invoked by American presidents, that would help him commandeer private production of nearly everything, from essential commodities to cutting-edge technologies. 

Invoking the law is one thing, executing it is another. Rather than strong-arming businesses, the Trump administration is now trying to bring together private actors to create multiple “playgrounds” with an underlying public interest. The Coronavirus Task Force was the first of its kind. The Task Force brought together Walmart, Google, CVS, Target, Walgreens, LabCorp and Roche, among others to perform singular responsibilities aimed at tackling the coronavirus pandemic. Walmart would open its parking lots for testing, Google would create a self-testing platform online, Roche would develop kits, LabCorp would perform high-throughput testing, and so on. The COVID-19 High-Performance Computing Consortium, created on March 23, is another such playground. It includes traditional, 20th-century actors such as the national laboratories but is doubtless front-ended by Microsoft, IBM, Amazon and Google Cloud. The Consortium aims to use its high computational capacity to create rapid breakthroughs in vaccine development. Proposals have been given an outer limit of three months to deliver. 

In some respects, the United States is turning to an approach that India has advanced. To be sure, we may not currently be in a position to develop such a playground for vaccine R&D and testing at scale. But India is well-positioned to create the “digital playgrounds” that can help manage the devastating economic consequences of the Covid-19 epidemic. There is a universal acknowledgement that India’s social safety nets need to be strengthened to mitigate the fallout. One analyst recommends “a direct cash transfer of ₹3,000 a month, for six months, to the 12 crores, bottom half of all Indian households. This will cost nearly ₹2.2-lakh crore and reach 60 crore beneficiaries, covering agricultural labourers, farmers, daily wage earners, informal sector workers and others.” The same estimate suggests “a budget of ₹1.5- lakh crore for testing and treating at least 20 crore Indians through the private sector.” 

The digital public goods India has created — Aadhaar, UPI and eKYC — offer the public infrastructure upon which these targeted transfers can be made. However, cash transfers alone will not be enough: lending has to be amplified in the months to come to kickstart small and medium businesses that would have been ravaged after weeks of lockdown. India’s enervated banking sector will have meagre resources, and neither enthusiasm or infrastructure to offer unsecured loans at scale. “Playgrounds” offers private actors the opportunity to re-align their businesses towards a public goal, and for other, new businesses to come up. Take the example of Target, which is an unusual addition to the Coronavirus Task Force, but one whose infrastructure and network makes it a valuable societal player. Or Amazon Web Services in the High-Performance Computing Consortium, which has been roped in for a task that is seemingly unrelated to the overall goal of vaccine development. 

If digital playgrounds are so obvious a solution, why has India not embraced it sooner? None of this is to discount the deficit of trust between startup founders and the public sector in India. Founders are reluctant to use public infrastructure. It is the proverbial Damocles’ sword: a platform or business’ association with the public sector brings it instant legitimacy before consumers who still place a great deal of trust in the state. On the other hand, reliance on, or utilisation of public infrastructure brings with it added responsibilities that are unpredictable and politically volatile. To illustrate, one need only look at the eleventh-hour crisis of migrating UPI handles from YES Bank in the light of a moratorium imposed on the latter earlier this month. On the other hand, the government retains a strong belief that the private sector is simply incapable of providing scalable solutions. In most markets where the India government is both player and regulator, this may seem a chicken-and-egg problem, but c’est la vie.

Nevertheless, there are milestones in history where seemingly insurmountable differences dissolve to reveal a convergence of goals. India is at one such milestone. A leading American scientist and university administrator have called the pandemic a “Dunkirk moment” for his country, requiring civic action to “step up and help”. By sheer chance and fortitude, India’s digital platforms are poised to play exactly the role that small British fishing boats played in rescuing stranded countrymen on the frontline of a great war: they must re-imagine their roles as digital platforms, and align themselves to strengthen the Indian economy in the weeks to come. 

Arun Mohan Sukumar is a PhD candidate at the Fletcher School, Tufts University, and a volunteer with the non-profit think-tank, iSPIRT. His book, Midnight’s Machines: A Political History of Technology in India, was recently published by Penguin RandomHouse.

Posted on

When one door closes…

An inspiring effort in response to COVID-19

Last Tuesday, for the first time in recorded history, India pulled the emergency brakes on all of the complex interactions that make up the economy and society of 1.3 Billion Indians.

We’re going to see a lot more cascading effects of bringing almost all economic activity to a sudden and near-complete stop. Some of those effects are already visible and others will reveal themselves over time. One thing that’s easy to predict is that this disaster, like most others, will affect Bharat more than it does India.

However, at iSPIRT, we remain impatient optimists for Bharat. It does not suffice for our volunteers to simply predict the future; we want to help create it. When the lockdown hit, we could immediately see that the country’s messy supply chains would be hard-pressed to disentangle essential services from non-essential ones. On the very first day of the lockdown itself, you may have seen videos or news about the police using their lathis on innocent essential service providers like doctors.

This is undeniably tragic, but at its heart is an information and social trust issue inherent in India. When you distil the problem, it comes down to how does the administration identify those travelling for essential-services vs those who are not. Consider this, Swiggy and Zomato alone – who only work on the last mile of one category of food – claim to have a fleet of close to 500,000. For the entire supply chain, even restricted to essential items only, will require authorisations for millions of people and another few million vehicles.

So today, we’re announcing the release of an open-source tool called, ePass. ePass is a tool to help the administration issue digital lockdown passes. These e-Passes are secure and can be verified when needed. iSPIRT got this solution going from zero to launch in less than 4 days. In the following interview, Tanuj Bhojwani speaks with Sudhanshu Shekhar, who led the effort to build the tool and Kamya Chandra, who helped liaison with the Karnataka administration.

Tanuj Bhojwani: Hey Sudhanshu, let’s start with what e-Pass is?

Sudhanshu Shekar: Sure, so the objective is to make sure that those who are on the road providing essential services or regular citizens seeking them can face minimal friction from the authorities.

We imagine a simple 4-step flow

  1. Individuals, such as you or me, or businesses providing essential services, can apply for a pass.
  2. The administration sees these requests digitally, and can authorise them from the backend, either manually or via automated rules.
  3. People can download their digitally signed passes on their devices
  4. The on-ground personnel, such as the police, can verify the curfew pass is valid by scanning it.

We’ve built tools for each part of that flow.

When we started working with the administration, they gave another great suggestion. If the beat officers could provide pre-authenticated “tokens” – like a gift-code, we could make this process even more convenient for some essential service providers. For example, they could distribute tokens to all the informal businesses in a mandi in one go, helping bring the supply-chain back online that much faster.

Tanuj Bhojwani: And you’ve made this open-source. How can a local administration use this?

Kamya Chandra: Everything is a configuration. The administration will have to decide who the approving authorities are. An admin dashboard allows bulk uploads, approvals, tracking statistics of issued passes, etc. It also allows them to configure timings, the validity of the pass, which identity fields are required, etc.

And finally, they have to instruct their beat officers to download the verification app and use it.

Tanuj Bhojwani: so the local government hosts this themselves?

Sudhanshu Shekar: Yes, the governments need to host this themselves, either directly or through a service provider. As iSPIRT, we have only provided the code and will not be providing any managed services. Even the code is open-sourced for others to use and remix as they see fit.

Tanuj Bhojwani: iSPIRT doesn’t work with the Karnataka administration normally, so how did this all happen? How did the team come together?

Sudhanshu Shekar: Sharad called me at 8 pm Tuesday or Wednesday? Maybe it was 8 in the morning. I’m no longer sure. What’s a day anyway? *laughs*

Kamya Chandra: I want to interrupt here and say I am super impressed by Sudhanshu and the rest of the team. No matter how little sleep they got, they didn’t let it affect their judgement or mood. Their decisions were always geared towards what’s the best that’s needed.

Sudhanshu Shekar: Thank you. We’re all just doing what we can.

But basically, on Monday, as Karnataka started enforcing curfew, we realised that people are going to need curfew passes. We started kicking around the idea on Monday, but there was no team. The next night the PM announced a nation-wide lockdown. We knew this was going to be a problem everywhere.

On Wednesday, the Karnataka administration also got in touch with Sharad asking for a similar solution, and they made it clear they need the solution in two days.

Sharad called and said, “I’m going to ask you about something, and you’re going to want to do it, but be really sure and think about it. This is a hard project and has very tight timelines. Everybody will understand if you say no”.

Sharad was right, I did want to do it, so I said yes and immediately got to work. I reached out to several friends and iSPIRT volunteers for help and a few – namely Mayank, Manish, Vibhav, Mohit and Ashok – agreed to help. It was easy to convince everybody, given the importance of fighting COVID. Manish has a few friends in China and was very aware about the seriousness of this situation. We quickly agreed on the basic product outline and started working. Wednesday was a flurry of activity and we got frequent reviews done with the Administration.

We realised we needed an admin console for the police to manage pass issuance. None of us was really an expert in building front-end applications and therefore, I started making calls trying to find an expert. Through referrals, I managed to reach Vishwajeet at 12 pm. I spoke to him about the project, its importance and the strict timelines. I told him we’d fail without him!

Tanuj Bhojwani: So you called a guy you’ve never met and asked him to deliver a complex task, on a ridiculous deadline for no pay nor any certificate or recognition. How did he respond?

Sudhanshu Shekar: He called his office to take a holiday. Vishwajeet sat down, worked for 15 hours straight, and delivered before time!

Kamya Chandra: *laughs* I want to add that this team, which did not know each other, did sleep shifts – including Vishwajeet, who became a volunteer that afternoon. I remember Sudhanshu taking turns with the devs to sleep at night in 2-hour batches just to keep the engine going. I’d run demos with the administration for feedback in the morning, while they all got a little shut-eye. From afternoon, they’d repeat another day and night of development.

Tanuj Bhojwani: Wow, that’s a lot of effort, and what sounds like very little sleep! What was happening on the police end, Kamya? 

Kamya Chandra: Honestly, I went in with a negative impression of the police and administration – because all you see are videos of people being beaten. However, I was very impressed with the few people I was working with. They were very knowledgeable about the challenges they were going to face operationally. Also, it was obvious they were doing their best. The first call I got from them was at 11.45pm!

They made time for our demos, gave excellent, considered feedback on all of it that has definitely helped the product. For example, we added a quick and easy way to verify the ID alongside the QR, so that it can work even if the beat policeman verifying does not have a smartphone.

All of this was happening by a remote team in lockdown. I was in Delhi talking to officers in Karnataka. Other than Sudhanshu, I’ve never met any of the other volunteers! In every other organisation, this kind of a crisis response doesn’t happen as smoothly even if the team knows each other. Anywhere else, it would have been near impossible if the team didn’t know each other.

Tanuj Bhojwani: Oh! I assumed they were all from Bangalore?

Sudhanshu Shekar: No.

 Mayank is in Bundi, a small town in Rajasthan. Kamya is in Delhi. I’m in Indiranagar, Bangalore. Ashok, our design guy, is in Koramangala and Mohit – I have no idea where he stays – I have never met him *everyone laughs*

Kamya Chandra: Knowing everyone’s location is harder, we still don’t know full names! One of the volunteers who helped us test the security of the product was Sasi Ganesan. I spelt his first and last name wrong in the first email I sent to him! He still helped though. On the 4th day of working together, I needed everyone’s last names, I still only knew Sudhanshu’s and Sasi’s!

Compared to the places I’ve worked before, I was surprised to see Pramod send an email with such savage truths. That’s a great example of how radical candour works, why it is in direct opposition to corporate culture.

Tanuj Bhojwani: *laughs* What were the “savage truths” in this email?

Kamya Chandra: To be fair to Pramod, it was more surprising than savage. Pramod said DO NOT GO LIVE (in bold and underline) until security and related aspects weren’t complete. The contents weren’t particularly shocking, but that he sent it to all of us – including people he barely knew. There was no secrecy or pretending to be bigger than we are. All our failures were also publicly available to a team we’ve never worked with before or met. It’s quite a unique experience.

Sudhanshu Shekar: Yeah, we were planning on going live on Friday, and we knew we needed to do security testing before we went live. Pramod’s email was a good one, and all fair asks about security, usability and data retention. He connected us to another iSPIRT volunteer, Sasi Ganesan for help. Ten hours before the scheduled launch, Sasi wrote back with a list of tasks we must do BEFORE we go live. This Thursday night email doubled our todo list. Thankfully, we were able to pull in Bharat, Sireesha and a few others from Thoughtworks to help close these tasks But at the time it felt brutal, we realised this was going to be a very hard few hours.

Kamya Chandra: Yeah, I think this is around the time Rohit started helping us enhance our UX. To me, this email was a clear indication of the high bar every iSPIRT volunteer must meet. Tight timelines or urgent needs are not enough to excuse sloppiness. I am glad we have senior volunteers such as Pramod to keep the bar high.

Tanuj Bhojwani: But I believe this story has a twist?

Kamya Chandra: Well, we did the demos in time, and everyone seemed very impressed. Unfortunately, the Karnataka administration decided to go with someone else. Their decision to go with someone else was disappointing for us.

However, they are policymakers making scale decisions. They probably had to keep many balls in the air and have redundancy. It’s good they have backup plans for backup plans.

They handled it with grace and were very kind about it. They sent a thank you and a commendation letter to each of our volunteers. One of the senior lady officers asked me – do you only take techies? I do not have a computer science degree, but I want to volunteer!

I told her I was an economist too and that she should definitely volunteer.

Sudhanshu Shekar: For me, the toughest part was when I heard the news that our work won’t be going live on Friday like I had promised all these guys. I was really sad. For about an hour, I tried to fight the decision, but then I realised that I would have to do the difficult thing and break the bad news to a bunch of volunteers who’ve slept less than 6 hours total in the last 72 hours.

What happened next is what surprised me the most about this whole thing.

All of them – every single one – took it so well! They all said something to the effect of working on a solution with other volunteers felt better than not working on one and worrying about the lockdown.

I thought this is the end of the line, but it was they who cheered me up and suggested we should open-source it. I was hoping to tell the volunteers to get some rest. Instead, these guys were so passionate that they worked for a couple more days to complete the documentation, which is why we were able to launch ePass today!

Tanuj Bhojwani: Wow. That’s quite a lot of team-spirit for a team that has never even met! So what happens now that this is open-source? How do you expect it will get traction?

Kamya Chandra: The decision to open-source paid off! Even though Karnataka didn’t take ePass, the officers messaged their batchmates and told them about what the volunteers did.

Sudhanshu Shekar: Now, we have demos scheduled with several other state governments as well as a few national ministries. We think this could be live in at least a couple of places soon.

Tanuj Bhojwani: That sounds like a fairy tale ending. Do you have any advice for anyone who is reading this and wants to volunteer?

Kamya Chandra: I used to work at the World Bank in DC, and we were trying to implement national-level digital systems in many countries. When we had technical challenges there, I was often told to get on a video call with iSPIRT volunteers for guidance and inputs. The more I interacted with them, the more I realised there is magic here to learn from. So I gave up my diplomatic passport and got on a plane to Bangalore!

So my advice is that you should try volunteering even if you’re many, many oceans away!

Sudhanshu Shekar: *laughs* I have a more straightforward test than Kamya’s for those who want to volunteer. These are also the three reasons I volunteer.

First, Societal Impact. You feel useful because you get to work on something that genuinely helps people.

Second, exposure to a wide variety of topics – such a different set of problems – you don’t exactly stick to your lane. Hence, you also meet people with very diverse backgrounds and work experiences. Because my peers are not age-bracketed with me, I feel like there are many lessons that I usually would’ve learned in ten years of my career, I’ve learned already at iSPIRT. 

Third, you draw energy from others’ passion. It’s just amazing to go to work with people like this every day. I’ve realised iSPIRT is a self-selecting group – it’s only the people who seek to find it, find it. It is not easy to be a volunteer, because the environment is open and the volunteers are self-driven, people will clearly be able to see if you can walk the talk. When you have people respected in a system not for who they are, but what they do, it is magical for everyone.

Tanuj Bhojwani: That is very true. Thank you for the chat!

Like Sudhanshu says, Volunteering at iSPIRT is hard and definitely not for everyone. However, if one or more of these reasons resonate with you, you should read the volunteers handbook to learn more about balloon volunteering.

Posted on

Union Budget 2020: A Good Start That Needs Swift and Decisive Action


 “Words can inspire but only action creates real change.” 

Presenting the second Union Budget, the Finance Minister asserted that entrepreneurship has always been the strength of India and proposed a number of measures and policy changes to help boost the Indian startups. The Budget was a step in the right direction, but these are just baby steps for an economy that needs giant leaps to become an innovation hub. 

We are also hopeful that the investment clearance and advisory cell will go a long way in strengthening the startup environment and improve the ease of doing business within our community. The proposed 5-year deferment of tax payments on ESOPs by startup employees in the Union Budget, we believe, is a step in the right direction. However, it does not satisfactorily address the complete concerns and other pain points that have been plaguing the startup ecosystem. 

Firstly, the ESOP taxation change, in its current form, applies only to around 200 startups recognised by the IMB (Inter-Ministerial Board), thereby, severely restricting its scope. It is only fair that all DPIIT-registered startups enjoy the benefits of the proposed changes equally. Secondly, we strongly believe that ESOP taxation must be revised as per global norms, else, it would become an ineffective tool of talent acquisition and retention. 

We also require cohesive measures towards improving the ease of doing business and strengthening the overall ecosystem. To ease the working capital crunch faced by startups, a lowering of TDS rates on payments to DPIIT registered startups and MSMEs is necessary. To enable greater rupee capital participation, allowing universities and public trusts to invest in Alternative Investment Funds (AIF) will make a considerable impact. Achieving tax parity between listed and unlisted securities, which at present vary significantly, will enable startups to attract greater investments. The provision of R&D benefits for companies will help spur innovation and startup activity in India, enabling a structural shift in the economy towards building high-value capabilities. 

We believe that more cross-cutting measures across industries are necessary and so is the reduction of frictions between the businesses and government players. This will help us to cover more ground in fulfilling the mission of making India a high-value, innovation economy. 

Overall, Union Budget 2020 does reflect the Government’s keenness in improving the ease of doing business but considering that the lofty goals we have set out to achieve, good intentions and keenness do not suffice. These must be augmented with robust policy changes, as well as, swift and decisive action to strengthen and accelerate the startup ecosystem. 

India is at a crossroads and must decide how she is going to traverse the next decade and champion the change the world needs. It reminds one of Robert Frost, “Somewhere ages and ages hence:

Two roads diverged in a wood, and I—I took the one less travelled by,

And that has made all the difference”

Posted on

Union Budget 2020 – iSPIRT Recommendations

India is among the top startup ecosystems in the world with home to 50,000+ startups and 3,500+ funded startups growing at a rapid pace at 30 per cent. While the future outlook of the Indian startup ecosystem is definitely promising, further accelerated growth can happen only if the government introduces more startup-friendly policies, other than the existing support under ‘Startup India’.

With Budget 2020 less than two months away, the startup ecosystem is hoping to get a major boost with respect to the following measures:

  • Improve ease of doing business for startups.
  • Attract domestic and foreign investors.
  • Increase working capital flow for startups.

iSPIRT has made a 13-point recommendation list for Budget 2020 with respect to the above-mentioned measures:

1. Remove the TDS payment for DPIT registered Startups

Currently, payments to DPIT registered startups are subject to Tax Deduction at Source (TDS) of 10% under section 194J. It takes at least 1-2 years for startups to get refunds after filing of their returns, which blocks their working capital for that time period. 

2. Harmonise the Tax Rate and Holding Period between Listed and Unlisted Securities of Startups 

The higher holding period and higher tax rate disincentivise investments into startups from Indian sources. Globally, no such differentiation exists.

This recommendation seeks:

  • Reduction of the holding period for unlisted securities to 12 months from the current 24 months.
  • Levy of a lower tax rate of 10% on the sale of unlisted securities.
  • Removal of the “superrich” surcharge of 25%/37% on the sale of unlisted securities.

3. Change in the taxation of ESOPs for Startups:

The existing definition of Rule 3(8)(iii) of the Income Tax Rules, 1962 does not take into consideration the discrepancies in the determination of ‘Fair Market Value’.

The new recommendation seeks amendment to this rule as as per Rule 11UA(1)(c)(b), provided such fair market value shall not be less than the exercise price.”

4. Clarification on the February 19th, 2019 DPIIT circular on “Angel Tax” with regard to Form 2

This circular states that the exemption lapses in the case the startup has or will invest or conduct any of the activities below for a period of 7 years after investment, inter alia:

  • Make capital contributions to other entities, 
  • Make investments in shares and securities, 
  • Give loans and advances (except in the case of lending startups

The recommendation seeks an amendment to this notification

  • Extend the “business model” test applicable to all the other investments mentioned in Form 2 to all points mentioned therein
  • Allow Startups to make Loans and Advances in the ordinary course of business provided that the PAN of the recipient is reported
  • Allow startups to invest into shares and securities and make capital contributions provided that such downstream investments do not make further investments into any of the other points listed in Form 2

5. Allow for AIF expenses to be capitalised/passed-through

Expenses of an AIF can add up to up to 25%-30% of its corpus during the lifetime of a scheme, making a large chunk of the fund is a “dead-loss”.

The new recommendation seeks AIF expenses to be capitalised as the Cost of Acquisition or allowed to be set off against the income.

6. Classification of securities held by AIFs as Capital Assets by amending section 2(14) of the Income Tax Act, 1961.

There is still friction between the startups, investors and income tax department with respect to taxation of short-term gain from the sale of securities under AIF.

The new recommendation seeks an amendment to Section 2(14) as “any securities held by a Foreign Institutional Investor or AIF which has invested in such securities in accordance with the regulations made under the SEBI. 

7. Pass-Through Status for CAT III AIFs

Unlike CAT I and CAT II AIFs, CAT III AIFs do not have pass-through tax status, rendering their income to be taxed at the maximum marginal rate for their income earned, regardless of the tax status of the underlying investor.

The new recommendation seeks an amendment to Section 115UB and Section 10(23FBA) by including CAT III AIFs.

8. Allow Universities and Public Trusts to invest in AIFs

Currently, investments are allowed in SEBI registered Mutual Funds or notified Mutual Funds set up by a public sector bank or a public sector financial institution.

The new recommendation seeks an amendment to this section to include ‘Units of an Alternative Investment Fund registered with the Securities and Exchange Board of India”

9. Notify all SEBI registered AIFs as “long-term specified assets” under section 54EE

Section 54EE was introduced on April 1, 2016, to give capital gains exemption of Rs 50 lakhs for any gains invested into “long-term specified assets”, defined as “a unit or units, issued before the 1st day of April 2019, of such fund as may be notified by the Central Government in this behalf”

So far, the Central Government hasn’t notified any such funds, so no tax-payer has been able to avail of this benefit.

The new recommendation seeks issuance of a Central Government notification to notify all SEBI registered AIFs as “long-term specified assets” under section 54EE and announce measures to extend this to April 1, 2025.

10. Time-bound response from the Inter-Ministerial Board (IMB) and allowing all startups to reapply

The IMB has not been effective yet in timely responses to startups.

The new recommendation proposes DPIIT to issue a notification stating that:

  • IMB will respond in 60 days from the date of submission by the Startup.
  • Startups who were denied IMB recognition prior to February 19th, 2019 can re-apply for IMB recognition once again under the new criteria.

11. Exempt Software product Companies from Softex

Software product exporters are required to file SOftex form to report the inward remittance on export invoices in convertible foreign currency. However, Software products have a publicly listed MRP/List price and hence do not require any valuation.

The new recommendation seeks RBI to exempt software product companies from filing Softex and create a separate category of Purpose code for disposal of inward remittances by authorised dealers.

12. Creation of aHSN code for Software Product Startups

Under the GST regime, all IT Software has been treated as “Service”.  Yet, there exists HSN codes and SAC codes both. 

It is recommended that an HS code classification for specific categories can be issued using the last 2 digits (first 6 Digits being defined under international system). 

13. R&D Credits for Software Product Companies 

As startups and young software product companies don’t have taxable profits, they are unable to take advantage of current R&D tax benefits that involve setting off R&D expenses against taxable profits. To overcome this limitation, they should be allowed a deferred tax credit for up to 7 years after the R&D investment.

You can read about Budget Representation 2020 in detail here.

Posted on

#8 Call for Volunteers: Designing Digital Infrastructure for Healthcare at National Scale

Why Healthcare?

Interacting even briefly with the healthcare system reveals the issues that plague the sector in India: a severe shortage of high-quality doctors, nurses, or medical supplies (and a lack of information on where the best are); misdiagnoses or late diagnoses; overcrowding and long waits in public hospitals; overpriced and over-prescribed procedures and in private hospitals; a complicated insurance claim system; and significant gaps in health insurance coverage. Those who have worked on trying to improve the healthcare system know the systemic challenges: misaligned incentives in care delivery, a lack of health data to coordinate care, low state capacity, and the political battles between states and the Centre. Yet not one of us is spared bouts of illness or other health incidents over our lifetime. We have no choice but to work with this system. And when it doesn’t function effectively, the largest effects are felt by the poorest: productivity losses and income shocks caused by health issues have a way of spiralling individuals on the cusp of economic well being back into poverty. 

Designing for high quality, affordable, and accessible healthcare in India is a challenging societal problem worth solving, with huge potential spillover benefits.

iSPIRT in Healthcare

At iSPIRT, we have started to develop an approach to dealing with complex societal problems at national scale. Our work on India Stack and financial inclusion taught us that public digital infrastructure can create a radical transformation in social outcomes when designed with a regulated and shared back-end that enables a number of (sometimes new!) private players to innovate on the front end to deliver better services. After all, innovative companies like Uber or Amazon are built on digital infrastructure: the TCP/IP Internet protocol and GPS systems that were both funded by public research. iSPIRT targets societal challenges by setting an ambitious target that forces us to think from first principles and innovate on the right digital public goods – which then catalyses a private ecosystem to help reach the last mile and solve the challenge at scale.

Over the last three years, members of our Health Stack team have been thinking deeply about how to design for a radical transformation in healthcare outcomes. We have developed a trusted working relationship with the National Health Authority and the Ministry of Health to better understand their operations and the issues at play. Our approach to addressing the challenge is evolving every day, but we’ve now developed a hypothesis around a set of building blocks that we believe will catalyse the health system. These blocks of digital infrastructure will, we hope, improve capacity at the edges of the system and realign institutional incentives to solve for long term holistic healthcare for all. 

Health Stack Digital Building Blocks Overview (Work in Progress!)

Some further teasers to our approach are included in the attached writeup which provides an overview of some of the more mature building blocks we hope to implement in the coming year. 

We’re striving for an end state of healthcare that looks something like this (cut by population type on the left):

These ideas were presented by the team recently to Bill Gates in a closed-door meet last month (who said he was excited to see what we could accomplish!)

We need your help!

To help shape our ideas and make them a reality, we need more volunteers — particularly those with the following expertise:

  1. Technical Experts (e.g. microeconomists or engineers): We have a few building blocks with broad design principles that need fleshing out – for instance, a Matching Engine to between individuals and doctors/hospitals. If you are a microeconomist (especially if you have thought about bidding/auction design for a matching engine, and more generally want to solve for misaligned incentives in market structure) or you’re a techie interested in contributing to solve a problem at a national scale, please reach out! Prior expertise in healthcare is not a prerequisite. Also, if you’ve looked through the document and find a block where you think your technical expertise could help us build, certainly let us know. 
  2. Current and Future HealthTech Entrepreneurs: Often, a successful health tech startup requires some public infrastructure to be successful. For instance, a powerful rating and recommendation app need a trusted electronic registry of doctors and hospitals providing core master data. Many of our Health Stack modules are designed to catalyse private sector participation and market potential for better products and services, which in turn produce better outcomes for individuals. If you are interested in helping design public infrastructure that your company could use or are a potential health tech entrepreneur interested in learning more about the ecosystem by building for it, please let us know!
  3. Healthcare Policy/Program Implementation Expertise: Field experience in healthcare delivery is invaluable – it gives us a true sense of the real challenges on the ground. If you’ve worked in delivering healthcare programs before with government, a non-profit, the private sector, an international organisation, or philanthropy and have ideas on what’s needed for an improvement in the sector at national scale, we’d love to hear from you. 
  4. Market making/ Health Stack Evangelisation: Any technology is only as good as its adoption! As some building blocks of the health stack get implemented, we are looking for volunteers who can help evangelise and drive its adoption.

India’s potential in the health sector is tremendous – partly because we have an opportunity to redesign not just the technology foundation (which is a near-greenfield) but also the market structure. With the right team, we hope to orchestrate an orbit shift in the quality and affordability of healthcare across the country.  

To volunteer, please reach out to [email protected] and [email protected] 

Posted on

Announcement: iSPIRT Foundation & Japan’s IPA to work together on Digital Public Platforms

Information-technology Promotion Agency, Japan (IPA), Japan External Trade Organization (JETRO), and the Indian Software Product Industry Roundtable (iSPIRT) have shared common views that (i) our society will be transformed into a new digital society where due to the rapid and continued development of new digital technologies and digital infrastructure including digital public platforms, real-time and other data would be utilized for the benefit of people’s lives and industrial activities, (ii) there are growing necessities that digital infrastructure, together with social system and industrial platforms should be designed, developed and utilized appropriately for ensuring trust in society and industry along with a variety of engaged stakeholders and (iii) such well-designed digital infrastructure, social system and industrial platforms could have a great potential to play significant roles to improve efficiencies of societal services, facilitate businesses, realize economic development and solve social issues in many countries. 

Today, we affirm our commitment to launching our cooperation and collaboration through the bringing together of different expertise from each institution in the area of digital infrastructure, including mutual information sharing of development of digital infrastructure, in particular, periodic communication and exchange of views to enhance the capability of architecture design and establishment of digital infrastructure. We further affirm that as a first step of our cooperation, we will facilitate a joint study on digital infrastructure, such as (i) the situation of how such digital infrastructures have been established and utilized in India, Japan and/or other countries in Africa or other Asian regions (the Third Countries) as agreed among the parties, (ii) how the architecture was or can be designed for digital infrastructure as a basis for delivering societal services in the Third Countries and (iii) what kind of business collaboration could be realized, to review and analyze the possibility of developing digital infrastructure in the Third Countries through Japan-India cooperation. We may consider arranging a workshop or business matching as a part of the joint study to figure out realistic use cases.

Our cooperation is consistent with the “Japan-India Digital Partnership” launched between the Ministry of Economy Trade and Industry, Government of Japan and the Ministry of Electronics and Information Technology, Government of India in October 2018. We will work closely together and may consider working with other parties to promote and accelerate our cooperation if necessary.

For any clarification, please reach out to [email protected]

Posted on

A Great Leap Forward to Transform Fintech: Data Empowerment

India is one of the first nations in the world to kick off Open APIs for consented financial data sharing. And nobody’s heard about it! 

Dear Kickass Financial Product Managers and (current & future) Fintech Entrepreneurs,

Amidst the usual flurry of sensational headlines, you may have missed a quiet announcement a few weeks ago that marked a monumental shift: RBI became the first central bank globally to publish a common technology framework – including detailed APIs – for consent driven data sharing across the entire financial sector (banking, insurance, securities, and investment).

This is a gamechanger for the industry.

Out of context, yet another circular with a good deal of jargon is an easy thing to gloss over. But it turns out this effort is actually a global first: although the UK, EU, Bank of International Settlements (BIS), Canada, and others have begun thoughtful public conversations around Open Banking (e.g. through that famous BIS report making the case, initiatives like PSD2, conferences, and various committees), India is one of the first nations in the world to actually make it a market reality by publishing detailed technical API standards — standards that are quickly being adopted by major banks and others across the financial sector in the country without a mandatory requirement from RBI. It’s not just the supposedly cutting edge banks of Switzerland, the UK, or the US driving fintech innovation: the top leadership of our very own SBI, ICICI, IDFC First, Bajaj Finserv, Kotak, Axis, and other household names have recognised that this is the way forward for the industry, and are breaking through new global frontiers by actually operationalising the powerful interoperable technology framework. Not only are they adopting the APIs, some are also starting to think through the new lending and advisory use cases and products made possible by the infrastructure. We think many new fintech startups should also be considering doing the same.

Why do the APIs Matter?

The world is focusing heavily on data protection and privacy – and rightly so. Securing data with appropriate access controls and preventing unauthorised third-party sharing is critical to protecting individual privacy. But to a typical MSME, portability and control of their data is just as critical as data security to empower them with access to a stream of new and tailored financial products and services. For instance, if an MSME owner could share trusted proof of their business’ regular historic GST payments or receivables invoices digitally with ease, a bank could now offer regular small ticket working capital loans based on demonstrated ability to repay (known as Flow-based lending) rather than just loans backed on collateral. Data sharing can become a tool for individual empowerment and prosperity by enabling many such innovative new solutions.

Operationalising a seamless and secure means to share data across different types of financial institutions – banks, NBFCs, mutual funds, insurance companies, or brokers – requires a common technology framework for data sharing. The published APIs create interoperable public infrastructure (a standard ‘rails’) to be used for consented data sharing across all types of financial institutions. This means that once a bank plugs into the network as an information provider, entities with new use cases can plug in as users of that data without individually integrating with each bank. Naturally, the system is designed such that data sharing occurs only with the data owner’s consent — to ensure that data is used primarily to empower the individual or small business. The MeiTY Consent Framework provides a machine-readable standard for obtaining consent to share data. This consent standard is based on an open standard, revocable, granular (referring to a specific set of data), auditable, and secure. Programmable consent of this form is the natural next innovation of the long terms and conditions legalese that apps typically rely on. RBI has also announced a new type of NBFC – the Account Aggregator – to serve as a consent dashboard for users, and seven new AAs already have in principle licenses. 

The Data Empowerment and Protection Architecture (DEPA) – in one image

In many other nations, market players have either not been able to come together to agree on a common technical standard for APIs, or have not been able to kick off its adoption across multiple competing banks at scale and speed. In countries like the US, data sharing was enabled only through proprietary rails – private companies took the initiative to design their own infrastructure for data sharing which end up restricting players like yourselves from innovating to design new products and services which could benefit people on top of the infra. 

What other kinds of innovative products and services could you build? 

Think of the impact that access to the Google Maps APIs allowed: without them, we would never have seen startups like Uber or Airbnb come to life. Building these consented data sharing APIs as a public good allows an explosion of fintech innovation, in areas such as:

  • New types of tailored flow-based lending products that provide regular, sachet sized loans to different target groups based on GST or other invoices (as described above). 
  • New personal financial management apps which could help consumers make decisions on different financial institutions and products (savings, credit, insurance, etc.) based on historic data and future projections. This could also branch out into improved wealth management or Robo advisory. 
  • Applications that allow individuals to share evidence of financial status (for instance, for a credit card or visa application) without sharing a complete detailed bank statement history of every transaction

…and many others, such as that germ of an idea that’s possibly started taking shape in your mind as you were reading.

In summary

This ecosystem is where UPI was in mid-2016: with firm, interdepartmental, and long term regulatory backing, and at the cusp of operationally taking off. UPI taught us that those who make a bet on the future, build and test early (PhonePe and Google were both at the first ever UPI hackathon!), and are agile enough to thrive in an evolving landscape end up reaping significant rewards. And just as with UPI, our financial sector regulators are to be lauded for thinking proactively and years ahead by building the right public infrastructure for data sharing. RBI’s planning for this began back in 2015! They have now passed the innovation baton onto you — and we, for one, have ambitious expectations.

With warmest regards,

iSPIRT Foundation

I’m Pinging A Few Whatsapp Groups Now, What Else Should I Send Them To Read? 

For any further questions or queries, please reach out to [email protected] and [email protected]

Posted on

Bharat Calling In Bay Area

In the first week of October, around Dussehra, a bunch of Indians gathered in the Bay Area. The setting had nothing to do with Dussehra, it had more to do with whether they would be spending their next Dussehra while settled in India or in the Bay Area.

iSPIRT conducted two sessions around opportunities emerging in India, spurred by new digital public goods that are going to create a Cambrian explosion of new software products.

The startup activity in India over the past few years has been noted by Silicon Valley and the attendees had a keen interest to discuss what has been happening on the ground.

There were two primary tracks to the discussion:

  • how India has changed in the past decade or so and 
  • what factors have contributed to that radical change

The largely held view of the ecosystem among those gathered was of the 2008 – 2014 period, when the majority of them were last in India, studying or working.

The concerns raised about starting up were around ease of doing business and culture at the workplace but the consensus was that things are improving in these regards.

The keywords that came up to describe the factors causing the change in India were Jio, Modi and so on. However, the fascinating point to learn for all was about the rise of digital public goods and how they are fundamentally changing the market playground in India.

Many had heard of UPI (Unified Payment Interface) and rightfully so, credited Government for it but what awed everybody was how it came about with the effort of a bunch of volunteers believing in the idea of open-source public good and making India a ‘Product Nation’.

Everyone agreed that a new growth journey lies ahead for India, created by factors such as the rise of internet users, internet penetration with Jio, high data consumption and user education that comes along with it. However, it will get catalysed further when coupled with digital public goods.

UPI has been a success story and it crossed more than a billion transactions last month and had overtaken global volume of American Express months back! A number of successful companies like JusPay and PhonePe capitalised on UPI and similar opportunities now lie ahead with :

We dived into specifics of all these to discuss myriad product opportunities that will emerge, enabling new success stories.

This will further be enabled by :

  • Talent that is more agile and honed to operate in an ambiguous startup environment. This has turned around in the past few years, while a lot of talent was tuned to work in a corporate environment earlier.
  • More access to seed capital as more startup operatives have gained wealth and experience in the past few years
  • And parents are more supportive of the idea to join a startup or start one!

Capitalising on all these would need a new entrepreneur archetype that operates from first principles thinking to dig deep in the market and create viable products and business models taking advantage of unique local factors.

Volunteering with iSPIRT can act as a good channel to understand the market better, to get involved with understanding and building digital public goods that are shaping the times ahead in the country.

It’s the forum to engage with peers that help you learn more about yourself, discover your flow that brings joy and contribute towards a public good.

One attendee summed up the takeaway beautifully –

“In the US, I have created a professional career and learnt lessons by building on top of platforms in the West. Now, there are similar opportunities to build on top of platforms and participate in Indian playground. If I get to become an iSPIRT volunteer, I can not only build on top but also help build the very platforms that are driving India forward.

In my own backyard, I have the local know-how to build for India and should act on it, instead of watching Chinese and Western apps put their stake from Kashmir to Kanyakumari.”

To know more about emerging public goods, iSPIRT Foundation and know our volunteering model, check out www.ispirt.in and write to [email protected]

We would like to thank Jaspreet from Druva, Anand Subbarayan from Lyft for hosting us, Hemant Mohapatra from Lightspeed Partners for helping with the setup and our local volunteer Pranav Deshpande.

Posted on

Indian Software Product Registry – All That Product Companies Need to Know

Earlier this year, National Policy on Software Products was rolled out to create a robust, participatory framework to bring together industry, government and academia on a common platform to make India as a global hub for software products development. This is a much-needed initiative to provide holistic and end-to-end support to the Indian software product ecosystem. The registry is the first step among many towards solving the real problems of the industry and nurturing the software product companies. If done right, this initiative will have immense potential and far-reaching impact to benefit the industry.

Under this policy, one of the key initiatives is the set-up of the Indian Software Product Registry (ISPR) through industry ownership. It is a collaborative platform which will act as national coordination, facilitation and inter-connected centre for all activities related to the Indian software product ecosystem.

The main purpose of this policy is to focus towards the promotion of Indian software products which are defined as under for implementation:

  • Indian Company: As per sub-section 26 of section 2 of the Income Tax Act, 1961, “Indian company” means a company formed and registered under the Companies Act, 1956 or Companies Act, 2013,  provided that the registered office or, as the case may be, principal office of the company, corporation, institution, association or body in all cases is in India.
  • Indian Software Product Company (ISPC):  An ISPC is defined as an Indian company in which 51% or more shareholding is with Indian citizen or person of Indian origin and is engaged in the development, commercialisation, licensing and sale /service of software products and has IP rights over the software product(s).

ISPR aims to create a platform to enable discovery of Indian Software Product Companies and their products while simultaneously giving automatic access to the Government e-Marketplace (GeM) platform. This will enable the government to identify Indian companies as part of their buying process. However, more work on specific allocation of government buying and redeveloping of RFP’s in government for products will also be initiated so that the government can finally buy Indian products.

Secondly, by listing on exchange on ISPR will enable MEITY to get a better understanding of the industry so that specific product-related interventions like recurring payments for SaaS companies, credits for R&D to enable Indian companies to invest in research and development, and facilitation of Indian software product industry for providing fiscal incentives, if any, at a later stage among others will also be achieved.

Thirdly, ISPR will also enable Indian Software Product Companies to list their products here and connect to buyers across the world. Since this is a government-backed platform, it provides a high level of trust and authenticity in the global market. 

Indian Software Product Companies can register here.  For any more queries, please feel to reach out on [email protected].

Posted on

The Global Stack: A Manifesto

In 1941, soon after he had secured an unprecedented third term as President of the United States, Franklin D. Roosevelt mobilised the US Congress to pass the Lend-Lease Act. Its context and history are storied. British Prime Minister Winston Churchill famously wrote to FDR requesting material assistance from the United States to fight Nazi Germany — “the moment approaches when we shall no longer be able to pay [to fight the war]”. FDR knew he would not get the American public’s approval to send troops to the War (Pearl Harbor was still a few months away). But the importance of securing the world’s shipping lanes, chokepoints, manufacturing hubs and urban megalopolises was not lost on the US President. Thus, the Lend-Lease Act took form, resulting in the supply of “every conceivable” material from the US to Britain and eventually, the Allied Powers: “military hardware, aircraft, ships, tanks, small arms, machine tools, equipment for building roads and airstrips, industrial chemicals, and communications equipment.” US Secretary of War Henry Stimson defended the Act eloquently in Congress. “We are buying…not lending. We are buying our own security while we prepare,” Stimson declared.

The analogy is not perfect, but FDR’s Lend-Lease Act offers important lessons for 21st century India’s digital economy. Our networks are open; our public, electronic platforms are free and accessible to global corporations and start-ups; our digital infrastructure is largely imported; and — pending policy shifts — we believe in the free flow of information across territorial borders. India has made no attempt, and is unlikely in the future, to wall off its internet from the rest of the world, or to develop technical protocols that splinter its cyberspace away from the Domain Names System (DNS). While we have benefited immensely from the open, global internet, what is India doing to secure and nourish far-flung networks and digital platforms? The Land-Lease Act was not just about guns and tanks; a quarter of all American aid under the programme comprised agricultural products and foodstuff, including vitamin supplements for children. The United States knew it needed to help struggling markets in order to build a global supply chain that would serve its own economic and strategic interests. Indeed, this was the very essence of the Marshall Plan that followed a few years later.

In fact, India’s digital success story itself is a creation of global demand. When the Y2K crisis hit American and European shores, Indian companies stepped up to the plate and offered COBOL-correction ‘fixes’ at competitive rates. In the process, Western businesses saved billions of dollars — and Y2K made computing ubiquitous in India, which in turn, added great value to the country’s GDP. 

Therefore, there are both security-related concerns and economic consequences that should prompt India to develop “digital public goods” for economies across Asia, Europe and Africa. Can India help develop an identity stack for Nigeria — a major source of global cyberattacks — that helps Abuja mitigate threats directed at India’s own networks? Can we develop platforms for the financial inclusion of millions of undocumented refugees across South and Southeast Asia, that in turn reduces economic and political stress on India and her neighbours when confronted with major humanitarian crises? Can we build “consent architecture” into technology platforms developed for markets abroad that currently have no data protection laws? Can we nurture the creation of an open, interoperable and multilateral banking platform that replaces the restrictive, post-9/11, capital controls system of today with a more liberal regime — thus spurring financial support for startups across India and Asia? Can India — like Estonia — offer digital citizenship at scale, luring investors and entrepreneurs who want to build for the next billion, but do not have access to Indian infrastructure, markets and data? These are the questions that should animate policy planners and digital evangelists in India. 

The Indian establishment is not unmindful of the possibilities: in 2018, Singapore and India signed a high-level agreement to “internationalise” the India Stack. The agreement has been followed up with the creation of an India-Singapore Joint Working Group on fintech, with a view towards developing API-based platforms for the ASEAN region. As is now widely known, a number of countries spanning regions and continents have also approached India with requests to help build their own digital identity architecture. 

But the time has come to elevate piecemeal or isolated efforts at digital cooperation to a more coordinated, all-of-government approach promoting India’s platform advancements abroad. The final form of such coordination may look like an inter-ministerial working group on digital public goods, or a division in the Ministry of External Affairs devoted exclusively to this mission. Whatever the agency, structure or coalition looks like within government, its working should be underpinned by a political philosophy that appreciates the strategic and economic value accrued to India from setting up a “Global Stack”. In 1951, India was able to successfully tweak the goals of the Colombo Plan — which was floated as a British idea to retain its political supremacy within the Commonwealth — to meet its economic needs. Working together with our South Asian partners and like-minded Western states like Canada, we were able to harvest technology and foreign expertise for a number of sectors including animal husbandry, transportation and health services. India was also able, on account of skilful diplomacy, to work around Cold War-era restrictions on the export of sensitive technologies to gain access to them.

That diplomacy is now the need of the hour. The world today increasingly resembles FDR’s United States, with very little appetite to forge multilateral bonds, liberal institutions, or rules to create effective instruments of global governance. It took tact and a great deal of internal politicking from Roosevelt to pry open the US’ closed fist and extend it to European allies through the Lend-Lease Act. India, similarly, will need to convince its neighbours in South Asia of the need to create platforms at scale that can address socio-economic problems common to the entire region. This cannot be done by a solitary bureaucrat working away from some corner of South Block. New Delhi needs to bring to bear the full weight of its political and diplomatic capital behind a “Global Stack”. It must endeavour to create centripetal digital highways, placing India at the centre not only of wealth creation but also global governance in the 21st century.

The blog post is authored by Arun Mohan Sukumar, PhD Candidate at The Fletcher School at Tufts University, and currently associated with Observer Research Foundation. An edited version of this post appeared as an op-ed in the Hindustan Times on October 21, 2019.

Posted on

A Day at Startup Bridge – Crafting Strategic Partnerships

For our most recent Startup Bridge Salon on May 9th, we had planned for sixty 1-1 strategic partnership meetings between 11 B2B startups and 35+ US corporates. In the weeks leading up to the event and the week post-event, we clocked 115 meetings. Read more to learn about the event & program, and how you can participate or get involved. 

 I got 10 meetings with decision makers through StartupBridge which is worth 1000 business cards at a trade show. (Raviteja, CEO @Moengage, May 2019)

I made 18 connects out of which 11 are of extremely high value. (Aditya, CEO @FirstHive, May 2019)

History of StartupBridge, M&A/PSP Connect

In 2013-14 the M&A Connect (and Business Exchange BEX) program was established as part of iSPIRT’s Market Catalyst pillar to help solve the problem of extremely low “exits” to “investment” ratio for startups in India. Strong “exits” are healthy markers of a mature startup ecosystem, closing the cycle of capital flows. The program consisted of developing a strong match between the global corporates interested in acquisitions (buy-side) and Indian startups (sell-side). 

The initial problem was a discovery issue where Indian startups were not on the radar of these potential acquirers. The M&A connect program activated the India radar, by engaging the buy-side to collect deep virtual mandates, and use it to match and make warm connects with the sell-side, at times hand-holding the connect process to several favorable outcomes. 

In this program, we found that our startups were not effective at pitching their story to a potential acquirer. This resulted in a few aborted connections. Additionally, it became clear that the path to an effective M&A lay in facilitating potential strategic partnerships (PSP), which if nurtured has the potential to blossom into investments or acquisitions. Strategic partnerships can surface in the form of technology or GTM/distribution level enfgagement between startups and larger corporates. It can open several doors instantly, making distribution easier, revenue growth faster and gives the startup multiple options.

The M&A Connect program morphed into PSP Connect (Dec 2016 onwards) and the program goals moved from pure M&A to building strategic partnerships. iSPIRT partnered with TiE leaders in Silicon Valley to create the Startup Bridge India initiative (SBI), where many buy-side companies were invited to meet and explore strategic level engagement with highly curated sell-side startups. 

The Startup Bridge Approach

Over the last 3 years, the SB team, iSPIRT volunteers and TiE partners, have helped B2B SaaS/enterprise startups refine their air-game, and engage in partnership discussions with high conversion outcomes. 

We have connected 45 startups to Fortune 1000 corporations and in the process catalyzed $200M+ of value in terms of PSP (potential strategic partnership), customers and M&A. (Manu Rekhi, Inventus Capital & Startup Bridge)

The key value proposition is to help startups scale revenue by 10x in 2 years through meaningful PSP connects with decision-makers at global Fortune 1000. In turn, these corporations leverage SB to engage with highly curated startups to get access to technology and product gaps. 

We are effectively the bridge over the chasm that most startups struggle with, and the potential disruption that many corporates are worried about.

Startup Selection

Did you know that ~50% of Unicorn enterprise startups in the Silicon Valley have an Indian founder or co-founder and had origins or back-offices in India? 

Our stringent startup selection process is essential for matching the “Who in India” with the “Who in USA”. Data from the program over the years have shown that the startups which stood to leverage the program effectively and benefited the most were in the ARR range of $500K to $5M. Hence SB’s high-level criteria for inducting B2B enterprise/SaaS startups into the program focus on a) having a global product-market fit, preferably in the US, with b) a strong footprint & revenue (~$1M ARR), and c) bringing deep technology, high revenue potential and/or a high growth momentum. 

PSP Wishlist

Karthik & Vinod discuss their key partnerships approach

On the buy-side, it is critical to engage corporates who can enable the 10x growth for these startups. Most startups see partnerships as tactical like with a reseller, system integrator (SI), channel/OEM partner… A strategic partner goes beyond tactical value. A startup can explore and collaborate with a PSP to accelerate its strategy in the emerging focus area. In return, the PSP provides a rocket boost to the startup’s customer acquisition, distribution, branding, and/or a holistic product strategy. Having such a partner can also significantly impact startup valuation.

As a startup, you need to think about a PSP early in the game at the ‘Flop’ and not at the ‘Turn’. You need time to develop a PSP and you need to start early. (Vijay Rayapati, Nutanix, Jul 2018)

If you think of the value chain of your customers, their vendors, integrators, solution & platform providers, a strategic partner may lie above you and your peers, and a level or two above your target customer. Often high growth customers can transform into strategic partners. We help the startups think through their PSP wishlist and make relevant recommendations.

Startup Air Game

Pitching to a PSP company is very different from the pitching to a customer or to an investor. A well-articulated pitch can make a difference between a yawn and a wow! A great startup pitch highlights their Mission, problem statement, their solution & approach, the product/platform overview, key metrics & traction, unit economics of growth & acquisition, testimonials, market size & drivers, and finally their ask. 

I thought I knew my pitch and had the details at my fingertips. But then I started getting really valuable, thought-out feedback…I had to focus on pitching to partners, not customers. (Pallav Nadhani, FusionCharts, Dec 2016)

Mentor feedback sessions during the boot camp

It takes 100 hours per startup to articulate their value proposition into a pitch deck of only 10 crisp slides. The initial hours creating & refining their pitch deck with assigned mentors. It is followed by a day-long boot camp before the event where they are grilled through their pitches by the SB team, startup & corporate mentors from the industry, and successful entrepreneurs.The multiple rounds of feedback not only cover their proposition, but also helps weave in the founders’ story, and develop their stage presence, and tonality. Post boot camp they work on the critical feedback with their individual mentors, sometimes even redefining their models & assumptions, and final dry runs with the SB team. The results at every SB event have been astounding 7-min founder pitches amazing every attending corporate and industry leader. 

Tapesh and his amazing 7-minute “technicolor” pitch deck

PSP Virtual Mandates & Exclusive Connects

Vamshi 1-1 connects over the roundtable.

We have found that startups require 2 points of support for effective partnership outcomes. First, crafting warm connects based on virtual mandates. Second, prime focus on shepherding the startup-partner conversations on a rolling basis. The unmet need is to have 1-1 connects with the right person on common ground.

I went from first discussion into pricing in one week with a Fortune 10 company.  Getting in front of the decision maker is all the difference. As a founder/CEO I can close the sale without the long drawn out sales process. (Sanjoe Jose,  CEO @Talview, May 2019)

Bringing PSP companies into our network, we connect with key profiles within the company on their build-buy-partner outlook. This helps in surfacing several latent areas of focus for partnerships, investments or acquisitions. Constructing the virtual mandate out of these relations is key to recommending a high-potential match between the startups and corporates. 

All startup bridge sessions and introductions are curated and by invite-only. 

Exclusivity made the quality of event and connections even more important. I attended because of an impressive amount of my peers from other Fortune 1000 companies. (Rahul Kamath, VP Oracle, May 2019)

Impact to Date

The stringent startup curation criteria ensure high potential innovation & growth partnerships for corporates. The intense boot camp and mentoring hours help startups develop highly effective positioning in the market. The latent virtual mandates enable effective match-making resulting in extremely relevant growth opportunities for the startups.

If I had to do this on my own each of these connections would have taken 8-12 weeks of effort.

Though these events get significant attention & traction, the goal of the SB program is to deliver these connections on a rolling basis. Here are some stats and anecdotes across the years:

  • 19 out of the 45 startups in the SB cohorts have grown 10x in the past 2 years.  
  • 749 connections to decision-makers have been made to-date with >$200M of value creation in terms of partnerships, customer purchases, and M&A. 
  • 121 PSP connections from the May 9th event and beyond.  
  • 3 exits and 1 more on the way.
  • Focus on quality and value creation has resulted in consistent high NPS 56-81. This focus on quality is the core principle of this community lead effort and the hallmark of success so far. 

What can you do?

Shifting from its pro-bono, volunteer-run orbit, Startup Bridge is transforming into a mature, scalable global program. By broadening the corporate network reach beyond Silicon Valley, and expanding support to startups of Indian origin regardless of domicile, the program is poised to benefit startups and corporates at scale. Upcoming SBDays are being planned for New York, Bay Area, Japan. Startup Bridge continues to be mission-driven, helping fill a critical gap in strategic partnership building for Indian origin startups. 

If you are a startup or would like to refer a startup to be part of the SB program please fill the partnership application form. Alternately you could email us at [email protected]. 

If you are a corporate exec and/or can help us with decision-makers (CXOs, EVP/SVP, GM), or key influencers (VP/Director of Partnerships, Corporate Development) please email us at [email protected]. 

[This post could not have been possible without inputs from the SB Team & iSPIRT volunteers, Dipty Desai, Jibin Jose, Manu Rekhi, Raju Reddy, Sharad Sharma, Sijo George, Rajan Thiyagarajan, Vrushali Malpekar, and volunteers from the previous Startup Bridge/PSP Connect program.  Also, personal thanks to all the volunteers, mentors, and the participating startups for making the SB Salon on May 9th successful.]

Some more photos from the salon

Whatfix pitch by Khadim

Vivek pitching iZooto

Predera’s pitch by Vamshi

Vishal on Seclore

Side 1-1 with Flex

Hitachi giving feedback on Startup Bridge

Workday commenting on Startup Bridge

Ashish with Israeli Panel

Side 1-1 with Salesforce

Peer networking

Corporate Attendees

Corporate Attendees

Nimesa at boot camp – pitch feedback

Moengage at boot camp – stage presence feedback

Posted on

Fireside Chat: Vinod Khosla and Nandan Nilekani in Conversation with Sharad Sharma

Join us for a conversation with Vinod Khosla and Nandan Nilekani. Together with Sharad Sharma, our fireside chat host, they will talk about what it means to be an entrepreneur in India today and how these entrepreneurs can solve the hardest problems of India.

Vinod Khosla and Nandan Nilekani are arguably two of the most influential thinkers and innovators of our time when it comes to transformation, entrepreneurship, and large scale impact. Born within 6 months of each other, both graduated for IITs, created iconic companies, become billionaires in the in aprocess and continue to innovate and transform the world.

What better opportunity than to hear these icons of industry at a fireside chat discussing the most intriguing aspects of startups, entrepreneurship, digital transformation and India’s growth towards a multi trillion dollar economy.

About Mr. Vinod Khosla

Vinod Khosla is the founder of Khosla Ventures, a premier Silicon Valley venture capital firm, and a member of the 2018 Midas List. His firm, Khosla Ventures, invests in a wide variety of startups ranging from Healthcare, Sustainable Energy, Food/Agriculture to Space, AI and Robotics. He co-founded Sun Microsystems in 1982 after which he spent 18 years at venture capital firm Kleiner Perkins Caufield & Byers before launching his own fund.

About Mr. Nandan Nilekani

Nandan Nilekani is the co-founder of tech giant Infosys and currently back as a non-executive chairman affecting a remarkable turnaround. In 2009, he was made a Cabinet Minister and Chairman of UIDAI – India’s mammoth National ID project – Aadhaar.  After Aadhaar, Nandan has actively supported India’s digital transformation through the IndiaStack initiatives in payments, digital locker, eSignature and other services. Nandan has also backed startups in the India ecosystem.

About Mr. Sharad Sharma

Sharad Sharma is the co-founder of iSPIRT and has worn many hats as CEO of Yahoo India R&D, Chair of NASSCOM Product Forum and as intrapreneur at AT&T. He is a passionate evangelist and an active investor in the software product ecosystem in India.

When?

2nd of August, 2019 from 18:00 – 19:30 hrs.
Venue to be disclosed. 

How to participate?

You can be a part of this Fireside Chat by registering here. Confirmed participants will be intimated by the 28th of July via email. 

Please note, due to limited seating at the venue we will not be able to accommodate everyone who applies.