Bharat Distributed Ledger (BADAL) for accelerating trusted commerce in India

India has made rapid progress in digitisation of the economy in the last decade becoming a world leader in identity systems, digital payments and tax, and a new data sharing and empowerment framework. However, many deep-rooted issues still exist, such as extending true financial inclusion; formalisation and creating a higher trust economy, that is essential for growth of mostly small businesses.

In this blog post, we look at innovations in blockchain, distributed ledger and other technologies such as zero-knowledge proofs as potential solutions to build a stronger fabric for the economy for decades ahead. The unique opportunity India has is to boost commerce by enhancing trust, thereby culminating the transformation already underway through existing building blocks of digital identity, payments and data sharing to boost commerce. Unlike many other countries, faster and interoperable payments or reducing the dominance of private money are solved problems for India; the missing piece is to digitise commercial contract enforcement, which on the other hand is a solved problem for developed countries. Lack of adequate contract enforcement caused by contracting parties having different versions of the truth; due to data systems that don’t interoperate reduces trust and creates friction for economic growth. Solution requires connecting the goods and services ledger to the money ledger, so that contracts of any kind become binding promises that can be executed programmatically. Using technology to solve this trust problem is a unique opportunity for India.

BADAL (also happens to be a word for Cloud in local language), a techno-legal solution in the form of “Distributed Ledger for Privacy-preserving Trustful Commerce; is proposed as an interoperable fabric underlying a future programmable economy across large and small businesses to create high trust economy.

We also look at the emergence of Central Bank Digital Currency (CBDC) which is one of the core money applications of this framework and global backdrop in Annexure. There are many other use cases being proposed from land records to decentralised clinical trials for blockchain and allied technologies in different areas of government and business¹ likewise, that can be implemented in BADAL.

First of all, why is trust important?

Trust is the basic glue that connects strangers and promotes economic activity. Money is the basic economic institution in a society building that trust². However, trust builds slowly due to a combination of various factors such as the nature of institutions (political and legal) and the level of formalisation. While formalisation of even small businesses is increasingly addressed by the successful rollout of GST for India, formalisation of trust still remains elusive. At a core fundamental level, trust is a public good that creates friction-free commerce and is a recipe for rapid economic growth.

There is a high correlation between the level of trust in society and GDP per capita³. A study conducted by World Value Survey attempted to measure the level of trust in a country by recording the positive responses received to the question ‘most people can be trusted’. It found that countries with high GDP per capita such as Sweden, Norway and Netherlands recorded high levels of trust exceeding 60% determined in this manner as the graphic below shows.

Douglass C. North, Nobel laureate in economics⁴, found that ‘the inability of societies to develop effective, low-cost enforcement of contracts is the most important source of both historical stagnation and contemporary underdevelopment.’ The Union Minister of Finance and Corporate Affairs has rightly acknowledged the role of the “Hand of Trust”⁵when presenting the Economic Survey of 2019-20.

In societies like India, with limited ability to efficiently enforce routine civil or property contracts, businesses tend to restrict working with those similar to them based on caste, religion etc. (called associational activity) where there is an implicit social and moral enforcement mechanism or with members who have clearly demonstrated reputation in the past (usually the large or the older players). In both these situations, the economic benefit that a new firm can bring with new ideas or new techniques will be muted as its absorption is slower. Similarly, a new player will find it very difficult to compete with incumbents even if such players are economically more efficient. Economist Olson⁶ showed that associational activity is often more detrimental than favourable for an emerging economy. So we need better ways to break this trust logjam. Trust in the money system in India is comparatively high, as promises tend to be kept with sufficient legal backing and can be digitised with e-mandates or automated payments/ collections; but the same is not the case for goods (or services) ledger, leaving room for delays cascading into a logjam resulting in low trust. This is often felt in day to day life by citizens not getting routine services despite advance payment or small businesses not getting paid despite having supplied goods. Delays, defaults and disputes can become the norm if parties have different versions of the truth.

Every economic activity is thus like a mini-contract with one side on the money ledger (payment from party A to B) and the other side, on the goods/services ledger (from B to A) between counterparties, and can be converted into an electronic contract that automatically executes on both ledgers subject to interoperability. To assure the performance of contracts, the money ledger and the goods/ services ledger need to be connected in a way that is scalable, privacy-enhancing, non-repudiable and programmable. This enables a contract agreed between parties becomes a commitment, and fulfilment is guaranteed by code through the electronic contract. Assuring performance of contracts is critical for a country that is seeking to grow through startup activity, not just in tech but other sectors too.

Currently, litigants lose nearly ₹ 50,000 crores annually in wages or business lost which comes to 0.5% of the country’s GDP, because of litigation, an indication of how expensive litigation can be. The majority of civil disputes in courts are related to recovery of money (30.2 per cent) and land-or property-related matters (29.3 per cent) As reported in the 2016 survey carried out by DAKSH. Common reasons for dispute are different versions of the truth of contracting parties, prior to contract (past) or during the performance of contract (future). Having the same truth and programmability inherent in electronic contracts is a boon in this regard.

In an earlier blog, we have explored the benefits of adapted blockchain technologies to solve the problem of SME financing in India with a related post by global experts⁷. We build further on that and believe that India can harness recent advances associated with blockchain technology to enable trust between unrelated parties by combining the best of the scalable and centralized legacy world with a secure and private decentralized world. This can benefit the real economy vastly along with the financial world.

Innovations in distributed ledger technologies and BADAL

Distributed Ledger technology can help in two ways – first by being able to verify past performance before one party strikes a deal with another, and second, by being able to enforce a contract in most situations as performance unfolds in future. Thus, building trust about the past as well as the future.

We thus imagine a fabric based on the following basic principles to help create and grow a large number of applications to record economic activity even while reconciling with other activities and past data and help inject a level of trust by creating a reliable, immutable record of trusted data records and programmable contracts

Single platform to allow standards bodies and organisations to publish their schemas, and reuse other schema elements in composing workflows
Fully privacy-preserving capabilities to allow participants to publish relevant zero-knowledge proofs which do not require private data to be shared beyond the participating entities
A programmatic contracts capability that can help automatically carry out the relevant tasks as agreed on without any further manual intervention

By connecting a new digital money ledger (such as Central Bank Digital Currency, or stablecoins) with the new goods & services ledger, we envisage a boost to trust across economy and commerce. As such, BADAL is the first such framework we are aware of globally, uniquely suited to India’s needs, opportunities and strengths.

We have discussed the early version of this in detail in an earlier open-source document⁸. BADAL is thus a privacy supporting, trust enhancing mechanism of coordinating economic activity, and information recording and sharing. Originally this group started out of a process to explore the domain around and figure out the appropriate model to support CBDC, support data sharing between participants, and coordination and automation of event-based standing instructions across events in the goods and services ecosystem and/or money flow.

We then reviewed exciting developments in related areas first to understand their relevance given India’s unique needs. Blockchain technologies generally are seen to enable unrelated parties to trust each other and transact without depending on a central institution or intermediary. These technology innovations are around three key areas:

Maintaining immutability and integrity of data across the distributed ledgers of parties.
Governance mechanisms, especially for decentralised networks
The programmability of such transactions to allow automatic execution.

Public blockchain technologies like Bitcoin and Ethereum, on the other hand, are based on a philosophy of distrust of centralised institutions like Central Banks and are designed for unrestricted access and decentralised decision-making. But they have had to develop new approaches to contend with a few challenges, especially given the huge growth off late that see further wor:

The enormous consumption of resources to establish ‘proof of work’ that limits efficiency and scalability, leading to newer approaches
Exposing all transactions on these networks that generally do not allow sensitive data to be private on the key layer, is as critical for confidential business data as it is for personal data
Rise of many networks that are not interoperable with each other or with the mainstream economy, though some bridges do exist
May have ability to operate outside banking conduits and regulatory frameworks that challenges government’s sovereignty and financial stability through greater oversight has been coming recently

Research on amending throughput, reducing costs and enhancing privacy/auditability/KYC compliance has been ongoing at a rapid pace, especially over the last couple of years.

Despite these unresolved issues, Public blockchain-based tokens, so-called cryptocurrencies, NFTs etc have become an unregulated asset class, especially amongst the young rapidly given the ease of use, creating concerns on possible misuse as well as potential opportunities. We were also part of the recent consultation of the Parliamentary Committee on Finance on ‘Cryptoassets: Opportunities and Challenges’ and had shared with them some of our ideas above in our submission here⁹.

Various solutions have been employed to address some of these challenges:

Permissioned blockchains, such as Hyperledger Fabric and Corda, allow only trusted parties to participate. Corda uses Notaries for verifying transactions. Such solutions have been successfully used in finance, supply chain, property rights, healthcare, education and e-governance
Zero-knowledge Proofs (ZKPs) allow proving/verification of specific aspects of data without actually making the data public

BADAL builds on the above primitives and is offered as an open and interoperable platform to enable money ledgers such as CBDC/stablecoin along with applications relevant for finance and commerce. This can be designed as a permissioned network relying upon a few regulated entities, and interoperable to ensure that its benefits are widespread and at much lower costs than permissionless systems. It consists of a private ledger that holds sensitive user data with access restricted to participating entities only, and a public ledger that contains notarised zero-knowledge proofs about transactions between users. It supports different schemas (configurations) that enable usage across different use-cases.

This programmability coupled with immutability akin to electronic contracts, allows applications in BADAL to be used to leapfrog the trust logjam, without diluting sovereign privileges of control of money given India’s stage of development. BADAL will thus establish provenance that helps establish credibility and reputation of transacting parties, proof of title/ownership of goods and assets, proof of the history of transactions including promises made and ambiguously defined and fulfilled; automatic execution of terms of contracts along with privacy as a fundamental right.

Historically, monetary accounting has solved for only one side of this metaphorical coin- the monetary value. All monetary systems denote a money value to any transfer of goods or services. BADAL, being a ledger that can record value in any domain, solves for the non-monetary aspect of the transaction. Integrated with electronic contracts for a variety of applications, BADAL will enable digital claims on non-monetary assets, including new age asset classes such as crypto assets, NFTs, where claims can be financialized and liquidated. An inherent promissory layer can be enabled into the current transaction mechanism. This extends to all data types, from land records to hospital quality service quality etc, rather than just transactions involving money and goods/ services.

The ability to connect any of the data types across domains can give rise to massive amount of efficiency gains with automated execution thanks to new data from machines like cars, consumer durables like refrigerators or health wearables coming from advances in IoT (Internet of Things), 5G, Imagine a use case of automated crop insurance with sensors that monitor weather from a satellite in space to moisture in soil etc. and deliver claim benefit to the farmer with zero friction in real-time.

One of the biggest problems BADAL could solve at bottom of the pyramid is financial inclusion in India. This is not only in the form of increased monetary transactions through it, but also the ability for MSME’s to gain cheaper credit. This is a possibility as MSME’s will find it easier to prove their liquidity and income to banks and other lenders due to the monetary traceability the system will provide. An increased ability to prove financial stability will lead to greater leverage for borrowers and more systemic trust for lenders. This increase in the systemic trust will not only lead to an increase in credit creation but catalyse an increase in money velocity in India as a whole.

In a subsequent blog post, we will detail the potential use cases; as well as preliminary design of a prototype of one sample use case that is being built currently.

BADAL fabric supporting India Stack could boost digital India

India has pioneered transformations in Identity, Payments, and Data empowerment (these building blocks are popularly called the India Stack) through a techno-legal approach. These address friction of doing business, information asymmetry, and distributed systems. Breakthroughs along the way were public platform (identity), public protocols and standards, and techno-legal approaches to solving big societal problems.

Some examples of this:

Aadhaar enabled e-KYC has significantly reduced the onboarding cost for finance companies and utilities from ~Rs 1500 to as low as Rs10/¹⁰. This lower KYC cost has helped in expanding the reach of government initiatives like PMJDY and similar massive private rollouts like Jio.
Unified Payments Interface (UPI) has led to an explosion of digital wallets and payment technologies that reduce transaction friction. India has logged more real-time online transactions¹¹ than China and USA in 2020.
The recent launch of the Account Aggregator (AA) model (based on Data Empowerment and Protection Architecture, DEPA) allows the controlled sharing of private financial data by citizens with various financial institutions to get the best deals. This is a global first and in some sense, an export of a truly global standard¹² from India.
Open Credit Enablement Network (OCEN) is creating a way to democratise access to credit, to the level of making it accessible to a street vendor for small sums. These public goods prevent any large player from monopolising the data ecosystem and at the same time reduce the cost of providing service. For instance, microloans as small as Rs.300 can be availed on GeM-SAHAY leading to true inclusion at the bottom of the pyramid.

These techno-regulatory concepts are now being considered for adoption by several countries across the world. Overall, India is arguably ahead of most countries in adopting technology for promoting financial inclusion as well¹³.

The next building block now is the trust layer through BADAL, ensuring every commitment is met and every contract is enforceable, boosting transparency and growth over the next decade. Trust permeates through all three ends of this triangle as identity is the ‘who’; and data and payment relate to ‘what’ of commerce. In BADAL, identity and data sharing can be achieved without diluting privacy to enable trusted payments (& commerce).

Annexure: CBDC Developments

While BADAL provides fabric to money or goods ledgers, we describe CBDC in detail here, given its importance. Money was traditionally issued by the sovereign (through a Central Banker) and circulated in the economy through layers of banking intermediaries. With the advent of permissionless public blockchains, some of which also seek to portray themselves as alternate currencies, the sovereigns have taken note and introduced their own variant as a public good to protect the financial stability of the nation-states. This sovereign/state-issued digital currency is popularly known as Central Bank Digital Currency (CBDC).

Central Banks have been increasingly researching and in some cases developing prototypes of CBDC since 2017 as per a survey¹⁴ by the Bank for International Settlements (BIS). 86% of the world’s central banks¹⁵ are studying CBDCs actively. Sweden has finished its phase-1 pilot for CBDC called e-Krona in April 2021¹⁶. China published its plan for a CBDC retail pilot called e-CNY in July 2021 and has already put this in production apparently timed ahead of the Winter Olympics that will be hosted this year. This seems to already cover a fifth of the population ¹⁷. The USA is evaluating its own CBDC¹⁸; has been considering a regulatory framework for Stablecoins and has come out with a detailed report titled ‘Money and Payments: The U.S. Dollar in the Age of Digital Transformation in January 2022¹⁹’. In India, RBI is actively studying the benefits of CBDC²⁰.

fig: Central bank’s work on CBDC advances further

While there are different types of CBDCs such as wholesale/ retail and account-based/ token-based, ultimately a payment using CBDC can be immediately settled. This is akin to using paper money and unlike a cheque or money transfer between bank accounts that require a process of clearing and settlement adding to inefficiency and costs. CBDC can potentially thus leapfrog depending upon the development of existing banking systems in different countries.

Advanced Economies (AEs) and Emerging Markets and Developing Economies (EMDEs) have different motivations for issuing CBDC to end-users (via Retail CBDC) and financial institutions (via Wholesale CBDC), illustrated in the diagram below.

fig: Motivations for issuing a retail CBDC

In countries like China²¹ and Sweden²², a significant part of money moves digitally on private networks and central bankers are losing visibility and control of money flows. Both countries are moving quickly towards the launch of a retail CBDC.
China is also possibly viewing its CBDC as a tool to emerge as a global reserve currency²³ like the USD. China was also home to some of the largest mining pools²⁴ that spend enormous electricity on cryptocurrency. In this backdrop, China has recently banned crypto-mining and private cryptocurrencies.
In the USA, payments are expensive due to its legacy system of banking. This has led to a burst of digital payment options, the latest being ‘stablecoin assets’ (digital currencies backed by real assets like US dollar, treasuries, etc) that also compete with their money-market funds. Stablecoin assets have crossed $100 billion 25 in market value and are a popular choice to transact in Decentralised Finance (DeFI). DeFi is a parallel financial system evolving around crypto-assets. DeFI is not subject to transparency and compliance required in the conventional financial world at this point in time. As DeFi becomes big and interacts with the conventional financial world, there is a growing systemic risk arising from failure or fraud in DeFi. The US Government, therefore, wants to regulate some aspects of DeFI²⁶ and may thereby bless some stablecoins and crypto-assets as explicitly permitted financial products. Earlier in 2015, Bitcoin was determined to be a commodity²⁷ by some authorities there. The US Fed has also begun a consultation process towards design choices and feasibility of CBDC implementation.

Indian perspective

In India, the focus of policy has rightly been on promoting financial inclusion to formalise the economy and drive economic growth. One important factor which drives the usage of unregulated informal value transfer systems is the lack of banking facilities and corresponding amenities for managing money, which leaves rural communities without alternatives other than a person-to-person method of transferring monetary value. Even though India has seen a significant increase in the number of bank accounts created, Reserve bank data still highlights little improvement in account usage and institutional borrowings, which feeds into the broader issue of financial inclusivity.

Initiatives like Pradhan Mantri Jan-Dhan Yojana (PMJDY) opened doors to big change. UPI has been very successful as a payment mode but still needs underlying bank accounts to transact and thus depends on the banking system & its motivation to provide access to the poor. The PMJDY scheme announced in 2014 has increased the number of adults with bank accounts to 43.47cr ²⁸ (~46% of 93.55cr adults with an Aadhaar²⁹). Despite this headway, there is still a lot to be achieved. The Financial Inclusion Index (FI) recently launched by RBI shows that India is at 53.9 on March 21 (vs 43.4 in March 2017) – a little more than halfway towards complete financial inclusion (FI of 100)³⁰. Presently, the banking system acts as the main gateway to financial inclusion as the banking system is the main distributor of cash. Hence, various government programmes (like PMJDY) rely upon banks for financial inclusion, despite those being not remunerative for banks. The accounts also have various restrictions on the number of debits/withdrawals to ensure low cost.

Even with the existence of such low-cost bank accounts, the poor do not have an incentive to use a bank account regularly as they do not save enough to use the bank account as a store of value. They use these accounts mainly to collect remittances and withdraw cash at ATMs as bulk of their transactions is in cash, not leaving a visible money trail that in turn makes financial inclusion difficult. Cash in circulation in India even now is Rs 29.38 trillion³¹ (~14.9% of estimated GDP for 2020-21 32) despite the availability of these cheaper accounts, demonetisation in 2017 and the subsequent formalisation of the economy with GST, RERA, etc.

In addition, the cost of handling cash by the central bank and commercial banks (currency printing, operating currency chests, logistics of moving currency, ATM operations, etc.) has been estimated to be ~Rs 21,000 cr (Rama Bijapurkar) and ~1.7% of GDP ( (Visa Inc., 2016). High adoption of CBDC can help in reducing this cost while creating enormous amounts of data and enabling policymakers to diagnose and regulate better. At a later stage, CBDC can also be used for targeted monetary policy actions when its impact on the financial system is well understood. Experts are concerned that CBDC may result in the disintermediation of the financial system. This risk can be mitigated by following design principles set out by the Bank for International Settlements (BIS)³³ (i) “do no harm” to monetary and financial stability; (ii) coexist with cash and other types of money in a flexible and innovative payment ecosystem; and (iii) promote broader innovation and efficiency.

CBDC inherently provides an alternative to cash to directly reach a customer and can complement the banking network to make adoption quicker. By providing a digital alternative to cash will enable building verifiable money trails that can lead to greater financial inclusion by private players providing customised health, insurance, investment & education products in compliance with privacy laws. In the financially excluded segments, CBDC, being a form of central bank currency, is likely to be well trusted and be adopted easily.

The blog post is co-authored by Sanjay Phadke, Dhananjay Nene, Sharad Sharma, Navin Kabra, R Barve, K Babel, V Agarwal, K Gokarn, Kalyan Narguru, Shashank B, Arun Maharajan, Karan Sirdesai, P Sahu, P Rao, A Kulkarni, Krishna Iyer, V Nene and A Lath.

If you have any queries or comments, please contact us at [email protected].

06/06/202012/06/2020

NHS Open House on PHR & Doctor Registry #3: Summary And Next Steps

On 6th June, we marked the third open house discussion of the National Health Stack (NHS). At the beginning of the session, iSPIRT volunteer Sharad Sharma offered a brief recap of the NHS and painted a roadmap for future developments in this initiative (including timelines, agendas, and future open house sessions). Sharad also discussed the content of the most recent open house session, in which Kiran Anandampillai explained the concept of the electronic registry system. After reiterating the vision for the NHS and the registry system, Sharad passed the floor to iSPIRT volunteer Vikram Srinivasan to dive into the registry APIs.

As a refresher, the electronic registry system is a mechanism for managing master data about different entities in the healthcare ecosystem. In today’ session, Vikram focused on the doctor registry. As the name suggests, the doctor registry will contain information about the doctors licensed to practice in India.

The doctor registry has the following design principles:

Self maintainability: Doctors should be able to enrol themselves and update their own data

Non-repudiable: The data in the registry should be digitally signed by a relevant attester (such as a State Medical Council) so that it can independently be verified by anybody

Layered access: There should be a clear demarcation between public and private data in the registry, with only consent-based access to private data (eg. a doctor’s name and registration status should be public, but mobile number and photo should be private)

Extensible schema: The data in the public registries should be as minimal as possible, allowing private players to build their own extensions around the core schema

Open APIs: The data in the registries should be available via open APIs

Incentive aligned: The registry must enable convenient use cases so that doctors have an incentive to keep it up to date (eg. doctors can use their registry profile to electronically sign prescriptions, insurance claims etc. or doctors can use their registry profile to streamline and digitize the process of renewing their medical licenses)

After discussing the design principles behind the registry, Vikram dived straight into the details of the doctor registry APIs, which can be broken into the following categories:

Enrollment APIs: These APIs allow doctors to enrol in the registry and update their data

Consented APIs: These APIs allow a doctor to authenticate themselves, share their data/profile, and electronically sign documents

Search APIs: These APIs are used to access the registry to query a doctor’s public data or search for any other publicly available information

After covering these topics at a high level, Vikram released the API specifications for the Consented APIs and the Search APIs. The Swagger documentation for the same can be found here. The enrollment APIs will be released during next week’s open house session.

Upon completing his walkthrough of the doctor registry APIs, Vikram handed the floor over to our volunteer Siddharth Shetty. In the beginning of his segment, Siddharth answered the community’s technical questions around the NHS. Here are the questions he answered:

Is it mandatory to use the Open Source Project Eka codebase that has been published for the Consent Manager, API Bridge, and Gateway?
In case of the Schema Standardization, during the 1st schema-less phase, are HIPs allowed to share data formats like JPEG, PDFs etc?
Can the consent manager give the health locker (as an HIU) a standing consent to keep pulling the user’s information from various HIPs on an ongoing basis i.e. bypass the consent manager for future requests
Can the API bridges be configured such that instead of just sending the links to the information based on a request from an HIU (health locker in this case), the information can be sent such that it can be copied into the health locker?
Will the consent artifacts be encrypted between parties using any asymmetric key mechanism which will be valid between the services?
Is there any defined/recommended timeout for the data transmission from HIU – Bridge – CM- HIP and then HIU – HIP?

These were all great questions, and hopefully Siddharth’s answers helped clarify any doubts. If anybody wishes to ask any other questions around the NHS, please send them in to [email protected] with the subject line “NHS Questions”. Siddharth will continue answering the community’s technical questions during next week’s session (business-related questions will be answered in subsequent sessions).

To close off the open house discussion, Siddharth laid out the different working groups in the NHS ecosystem. Since the NHS is an open, public ecosystem, it is crucial for industry players and interested citizens to contribute to its development and pitch in with their feedback, knowledge, and engagement. Here are the working groups that are currently being formed:

Technical Architecture Group: Responsible for working on open technical problems such as circuit breaker flows and time-out mechanisms. Also responsible for extensions and changes to the tech architecture

Data Dictionary Group: This working group deals with moving away from the current schema-less architecture towards a standardized data vocabulary (leveraging existing medical schema projects and also coming up with new ideas relevant to the Indian context)

Pilot Group: This group is comprised of people who have already started building on the NHS components (or would like to start building on the components).

Ecosystem Incentives Group: This group is looking at the incentive structures that power the NHS ecosystem (monetary and otherwise)

Any readers who are interested in learning more or joining these working groups are invited to reach out to [email protected]. A complete recording of the 6th June’s open house discussion can be found below

During next week’s session, we will be covering the Personal Health Records system (PHR), particularly as it relates to hospitals, and we will also be diving deeper into the Doctor Registry Enrollment APIs.

Readers are advised that next week’s NHS open house discussion will take place from 11:30 am – 12:30 pm on Saturday, June 13th.

The registration form for next week’s session can be found here.

24/05/202024/05/2020

iSPIRT Open House Sessions on NHS: Summary & Next Steps

Yesterday afternoon, we hosted our first Open House Session in partnership with Swasth Alliance on the National Health Stack (NHS). For those unfamiliar with this infrastructure, it is helpful to picture the NHS as a multi-layer cake designed to elevate the capacity of the Indian healthcare ecosystem.

At the base layer is a set of generic building blocks. These building blocks, which include bank accounts, digital identities, and mobile numbers, form the basic rails needed to identify, transact with, and communicate with individuals and businesses. Many components of IndiaStack – such as eSign and DigiLocker – leverage and augment these building blocks.

The next layer of the NHS is the ‘plumbing layer’. This layer contains fundamental pillars needed to enable simple, intelligent, and secure healthcare solutions. The three main pillars of the NHS plumbing layer are electronic registries, a personal health record framework, and a claims engine. A brief summary of these pillars is provided below:

Electronic Registries: these registries allow for efficient discovery and authentication of doctors, hospitals, and other healthcare providers
Personal Health Records System (PHR): a system that allows individuals to enjoy a longitudinal view of all their healthcare data and exercise granular control over how this data is stored and accessed
Claims Engine: a software engine that reduces the cost of processing insurance claims, enabling insurers to cover more kinds of healthcare procedures, such as preventive checkups, walk-in consultations, and other low-cost but high-value procedures that are currently excluded from Indian insurance policies

The third layer of the NHS is an augmentation layer which is intended to utilize the three pillars of the NHS to bring greater efficiency to the Indian healthcare ecosystem. The doctor: patient ratio in this country is relatively low, and cannot be changed overnight.

Having said that, increasing the efficiency of each doctor would have a similar effect to increasing this doctor: patient ratio. The augmentation layer of the NHS is designed to drive up doctor efficiency through the use of technology. Examples of this kind of technology could include a matching engine to pair patients with the most relevant doctor, or a system to help doctors securely and remotely monitor the bio-markers of their patients. Unlike the plumbing layer, the augmentation layer of the NHS is not close to completion, but we do envisage the augmentation layer playing an important role in the ascent of Indian healthcare quality. Both the plumbing layer and the augmentation layer are designed as open, standardized interfaces. These layers serve as digital public infrastructure accessible to public and private entities wishing to build atop them.

That brings us to the fourth and final layer of the NHS: the application layer. This layer comprises all the government and private sector applications that aim to serve the diverse needs of Indian patients. The first three layers of the NHS exist so that the innovators and change-makers of the fourth layer are optimally empowered to organize, access, and process the data that they need to deliver the best service to their users.

The first session on the NHS followed this schedule and published the entire webinar on our official Youtube channel:

An introduction to iSPIRT and our values
An overview of the NHS
A deep-dive into and demonstration of the PHR pillar of the plumbing layer
A question-answer session with the audience

The objective of the session was to drive awareness of the NHS components, objectives, timelines, and design philosophies. We want participants from all walks of healthcare to be engaged with the NHS and take part in building it.

In keeping with this objective, we will be hosting weekly open house sessions to keep diving deeper into the National Health Stack. The next such event will take place on Saturday (30th May) at 11:30 am. The focus of this second session will be on another pillar of the plumbing layer – the electronic registry system. More specifically, the session will focus upon the doctor registry.

Readers who wish to learn more about the NHS are encouraged to share this post and sign up now for the session below or click here.

Readers may also submit questions about the NHS to [email protected] We shall do our best to answer these questions during next Saturday’s open house discussion.

About the Author: The post is co-authored by our volunteers Aaryaman Vir, Siddharth Shetty and Karthik K S.

Further Reading

National Health Stack by NITI Aayog: https://niti.gov.in/writereaddata/files/document_publication/NHS-Strategy-and-Approach-Document-for-consultation.pdf
Holistic Health Leapfrog: https://pn.ispirt.in/towards-a-holistic-healthcare-ecosystem/
What does the Health Stack mean for you? https://pn.ispirt.in/what-does-the-health-stack-mean-for-you/
Federated Personal Health Records: https://pn.ispirt.in/5-what-is-the-federated-phr-component-of-the-health-stack/
Data Empowerment & Protection Architecture: https://www.youtube.com/watch?v=mW__azI8_ow
Care Intermediaries: https://pn.ispirt.in/7-healthcare-leapfrog-but-where-is-the-problem/
Personal Health Record Specifications: https://projecteka.github.io/content/documentation.html
Open Health Services Network Specifications: https://developers.beckn.org/Healthcare

21/05/202022/05/2020

iSPIRT Open House Discussion on National Health Stack [Virtual]

The National Health Stack is a set of foundational building blocks that will be built as shared digital infrastructure, usable by both public sector and private sector players.

Healthcare delivery in India faces multiple challenges today. The doctor-patient ratio in the country is extremely poor, a problem that is exacerbated by the uneven distribution of doctors in certain states and districts. Insurance penetration in India remains low, leading to out-of-pocket expenses of over 80% (something that is being addressed by the Ayushman Bharat program). Additionally, the current view on healthcare amongst citizens as well as policymakers is largely around curative care.

Preventive care, which is equally important for the health of individuals, is generally overlooked. The leapfrog we envision is that of public, precision healthcare. This means that not only would every citizen have access to affordable healthcare, but the care delivered would be holistic (as opposed to symptomatic) and preventive (and not just curative) in nature. This will require a complete redesign of operations, regulations, and incentives – a transformation that, we believe, can be enabled by the Health Stack.

iSPIRT Foundation in partnership with Swasth Alliance is hosting an Open House Discussion on the following building blocks of the Health Stack

Doctor Registry
- The ability for doctors to digitally authenticate themselves and share their electronic credentials with a third-party application such as a telehealth provider
Personal Health Record (PHR) System
- The ability for every Indian to be empowered with control over their health data such that they can share it with trustworthy clinical providers to access a digital service
Open Health Services Network
- A unified health services network that comprises of a common set of protocols and APIs to allow health services to be delivered seamlessly across any set of health applications, doctors, and providers.

The virtual session will be from 11:30 AM to 1:00 PM on Saturday 23rd May.

To confirm your participation and receive the virtual link, please click here.

Recommended Reading

National Health Stack by NITI Aayog: https://niti.gov.in/writereaddata/files/document_publication/NHS-Strategy-and-Approach-Document-for-consultation.pdf
Holistic Health Leapfrog: https://pn.ispirt.in/towards-a-holistic-healthcare-ecosystem/
What does the Health Stack mean for you? https://pn.ispirt.in/what-does-the-health-stack-mean-for-you/
Federated Personal Health Records: https://pn.ispirt.in/5-what-is-the-federated-phr-component-of-the-health-stack/
Data Empowerment & Protection Architecture: https://www.youtube.com/watch?v=mW__azI8_ow
Care Intermediaries: https://pn.ispirt.in/7-healthcare-leapfrog-but-where-is-the-problem/
Personal Health Record Specifications: https://projecteka.github.io/content/documentation.html
Open Health Services Network Specifications: https://developers.beckn.org/Healthcare

07/05/202013/12/2023

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:

2015: Whatsapp moment of India. Nandan Nilekani presentation on the future of finance and many articles written about it
2016: Startup India Launch – Jan 2016 13th. India Stack unveiled as part of official program of Digital India (Public event)
2017: Cash Flow Lending – DEPA launch 2017 August – Carnegie India Nandan Nilekani and Siddharth Shetty Presentation
Many different public appearances by Pramod Varma, Sharad Sharma, Sanjay Jain, Nikhil Kumar
2019: Siddharth Shetty explaining AA at an event at @WeWork Bangalore
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.

With UPI we did not recommend any individual PSPs for inclusion in the network. This was entirely RBI and NPCI prerogative.
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.

iSPIRT Public Comments & Submission to Srikrishna Privacy Bill
iSPIRT Public comments to TRAI Consultations
Support to RBI MSME Committee Report
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]

19/06/201910/07/2019

#6 Healthstack session at LetsIgnite

We had the chance to conduct a discussion on the National Health Stack during the LetsIgnite event organized by the LetsVenture team on 15th June at the Leela Palace. The audience comprised of early stage healthcare startups along with angel investors and venture capitalists having keen interest in healthcare investments. Some notable attendees included Dr. Ramesh (senior cardiologist, MD Endiya Partners) and Mr. Mohan Kumar (Partners, Norwest Venture Partners).

Sharad Sharma (co-founder, iSPIRT), Dr. Santanu Chatterjee (Founder, Nationwide Primary Care), Dr. Ajay Bakshi (Founder Buddhimed Technologies, ex-India CEO Parkway Pantai) and Arun Prabhu (Partner, Cyril Amarchand Mangaldas) had been invited to lead the session, which was moderated by Anukriti Chaudhari and Priya Karnik, both core volunteers at iSPIRT championing the health stack initiative.

The context was set by an interactive talk by Sharad who began by giving a glimpse of the underlying philosophy of the iSPIRT Foundation – the idea of building public goods as digital technology stacks which can be leveraged by private players to serve Bharat. . Sharad described societal change in India being a Jugalbandi between digital public infrastructure, market participants and policy makers to achieve the same. He mentioned how the India Stack was changing the face of fintech in India and that the Health Stack could do the same for healthcare. The audience was more than startled to hear that a day prior to the session, the number of UPI transaction in India were already one-sixth of what MasterCard had done worldwide. ( UPI has only been around for 33 months! ). Sharad then went on to explain the different layers of the Health Stack comprising National Registries, standardised health information flows, an insurance claims management software built upon a standard Policy Markup Language and a gamifier policy engine. He didn’t miss reminding the audience that the Health Stack was being built to solve for the healthcare needs of ‘Bharat’and not the privileged 30 million Indian families already being well-served by the healthcare conglomerates in urban areas.

With the context in place, Anukriti took over to give a background of the healthcare landscape in India. India struggles with a 1:1600 doctor to patient ratio with more than 60% of doctors and hospitals concentrated in urban regions. To add to that, the public expenditure for healthcare is just 3.9% of our annual GDP (compared to 18% in the US) and it’s not surprising that most deaths in public healthcare facilities happen because of poor quality of care. Health insurance penetration barely touches 20% with OOP expenditure dominating the healthcare spending in India. With a huge underserved population, the need of the hour is to leap-frog to scalable solutions that can reach the masses instead of incremental linear growth solutions to address the Indian healthcare challenges. The different layers of Health Stack make it much easier for innovators (both public and private) to develop radical solutions.. While funding in healthcare startups has increased over the last 5 years, it still significantly lags behind areas like fintech, e-commerce, ed-tech, etc. Moreover, the bulk of healthtech investments have been focused on the consumer tech sector. Anukriti ended her views with a futuristic optimism regarding the innovations that Health Stack could open, to make healthcare truly affordable, accessible and high quality.

We were fortunate to have Dr. Santanu and Dr. Bakshi give insights about the Health Stack with their on-ground experiences in healthcare spanning over decades. Dr. Santanu mentioned that for primary care, the national registry of care providers was very fundamental to ascertain ‘which stakeholder provides what’ given that almost every provider is somewhere involved in primary care. On top of that, he stressed about the need for Artificial Intelligence backed clinical support systems that seamlessly integrate with the doctor’s workflow. This is of particular relevance for rural healthcare settings wherein, despite various efforts, there aren’t enough doctors to setup shops in villages . A standardized health information layer, along with data transfer mechanisms, could be the driving force for this. He was, however, wary of how well standard insurance schemes would work for primary care as the insurance business model falls apart given that almost everyone needs access to primary care at some point or the other. Priya resonated with his views and further suggested that for ‘Bharat’, micro insurance policies could be the key mechanism to drive insurance adoption at the consumer level. Such a system could potentially be facilitated by a claims engine platform build upon a standard policy markup language to ‘almost-automate’ (auto-adjudicate) the claims addressal process.

Dr. Bakshi contended that for a stable society, healthcare and education are a must, as the former secures our ‘today’ while the latter secures our ‘tomorrow’. Having worked as the CEO of three major hospital chains in India, he accepted (without an iota of political correctness) that as a nation, we have failed miserably in providing either. Healthcare is a social good and nowhere in the world has it been solved by private players alone (given the way private incentives are aligned). The public sector in India hasn’t stepped up which is the reason that private players dominate the quality healthcare delivery which could lead us (or is perhaps already leading) to following the footsteps of the US. This is an alarming trend because in the short and medium term, India cannot afford to outsource the entire healthcare delivery to private players. Dr. Bakshi remarked that to set things on the correct track, the Health Stack is a very important initiative and congratulated the iSPIRT team for working ardently to make it happen. He however suggested all stakeholders to be privy of the fact that while fintech transactions are linear (involving the payer and the recipient), a healthcare ‘transaction’ involves multiple aspects like the doctor’s opinion, investigation, drugs, nurses, ward boys and many other layers. This underlying multidimensionality would make it difficult to replicate an India Stack kind of model for the healthcare setting. At the core of the healthcare transaction lies the ‘doctor-patient’ interaction and it is imperative to come but with some common accepted standards to translate the healthcare lingo into ‘ones and zeroes’. He lauded the health information flows of the Health Stack for being a step in the right direction and mentioned that in his individual capacity, he is also trying to solve for the same via his newly launched startup Buddhimed Technologies.

With two stalwarts of healthcare sitting beside her, Anukriti grabbed the opportunity to put forth the controversial concept of ‘doctors being averse to technology’ which could possibly be a hindrance for Health Stack to take off. Dr. Santanu and Dr. Bakshi were quick to correct her with the simple example of doctors using highly technical machines in providing treatments. They coherently stated that doctors hated Information Technology as it was forced upon them and suggested that IT professionals could do a better job by understanding the workflows and practical issues of doctors and then develop technologies accordingly. This is an important takeaway – as various technologies are conceptualized and built, doctors should be made active participants in the co-creation process.

The idea of a common public infrastructure for healthcare definitely caught the attention of both investors and startup founders. But amidst the euphoria emerged expected murmurs over privacy issues. That was when Arun Prabhu, the lawyer-in-chief for the session, took the lead. He reiterated Dr. Bakshi’s point of the doctor-patient relationship being at the core of the healthcare transactions. Such a relationship is built upon an element of trust, with personal health data being a very sensitive information for an individual. Thus, whatever framework is built for collating and sharing health information, it needs to be breach proof. Arun cited the Justice Srikrishna report to invoke the idea of consent and fiduciaries – a system wherein individuals exercise their right to autonomy with respect to their personal data not by means of ownership (which in itself is an ambiguous term), nor by regimes of negligence or liability but by the concept of a coherent consent mechanism spread across different stakeholders of the healthcare value chain. Moreover, the consent system should be straight-forward and not expressed via lengthy fifty page documents which would make it meaningless, especially for the India 2 and India 3 population. Lastly, he mentioned that just like physical and tangible assets have certain boundaries, even data privacy can have certain realistic limitations. If an information point cannot be specifically identified or associated with a particular individual but can have various societal benefits, it should be made accessible to relevant and responsible stakeholders. Thus, while it is imperative to protect individual health data privacy, there should be a mechanism to access aggregated anonymized health data. There is tremendous value in aggregating large volumes of such data which can be used for purposes like regional analysis of disease outbreaks, development of artificial intelligence based algorithms or for clinical research. Priya added that such a system was inherent in the Health Stack via the Population Health Analytics Engine and the framework for democratisation of aggregate data.

Overall, the session amalgamated various schools of thought by bringing together practitioners, CEOs, CIOs, lawyers, startups and investors on one common discussion platform. This was perhaps an example of the much-needed Jugalbandi that Sharad had mentioned about. A public good is conceptually ‘by the stakeholders, for the stakeholders and of the stakeholders’. This necessitates its active co-creation instead of isolated development. Needless to say, multi-way dialogue is the DNA of such a process. Staying true to that philosophy, we look forward to conducting many such interactive sessions in the future.

Ravish Ratnam is part of the LetsVenture Team – a platform for angel investing and startup fundraising.

He can be reached on [email protected]

20/05/201922/05/2019

Drones, Digital Sky, Roundtables & Public Goods

This is a guest post by Dewang Gala and Vishal Pardeshi (Pigeon Innovative).

Unmanned Aerial Vehicles(UAV’s)/ Drones have been making a buzz all over the world. Drones in the past have been looked at as a threat in various countries. The public perception towards drones has been very different in the past and has been changing over the past few years when people have been able to see the real benefits that this technology can offer. However, there is a need for a regulatory body to avoid the misuse of drones.

India is one of the key markets where the future growth of drone technologies is likely to emerge. India’s drone market expected to grow $885.7 mn and drones market in the world will reach $16.1 billion by 2021. Thus this market will create lots of employment opportunities and help our nation’s economy grow. Just like how the Information technology sector flourished in India increasing its contribution to the Indian GDP from 1.2% in 1998 to 7.7% in 2017, the Indian drone industry shows a similar promise.

How can drones contribute to the public good in India?

Previously, drones were an area of interest for defense sector only, but in past decade drones have been able to come into the public and commercial space where they have been able to take high definition photos, map a large area in a short time, calculate crop health, spray pesticides, inspect man-made structure which would be difficult or unsafe while doing it traditionally, play a crucial role during natural calamities to save lives, deliver goods and medicines.

Countries like Rwanda have allowed a full network of drones in their airspace which has helped save lives with the delivery of medical supplies. The company operating there initially had a huge challenge to convince people that the drones were meant for good and the company did not have the intention to spy on them. Once the people of Rwanda saw that these drones could save lives, a whole network of drones emerged across the country. Imagine the impact it would create across different industries in India if we accept and embrace this technology and have regulations in place for its safe usage. The upsurge of new drone-based innovative companies is a positive sign of India heading towards becoming a global leader in this field.

India is a high potential market, still entrepreneurs and businessman in this sector experience oblivion. This is because a few years back drones were completely banned in India as a perceived threat and now steps have been taken in Drone regulation 1.0 to get the industry moving forward. Though there are many roadblocks for the regulations to be in full force as it tries to bring together multiple agencies, the good part of it is that government understands that they lack the necessary skills set to create regulation and is willing to take help from the existing players to contribute in making the regulation more robust and user friendly.

What can be the public goods in the drone industry and why do we need them?

Paul A Samuelson is usually credited as the first economist to develop the theory of public goods. But what exactly is public goods?
A good which is:

Non-excludable – it is costly or impossible for one user to exclude others from using a good.
Non-rivalrous – when one person uses a good, it does not prevent others from using it.
Indivisible – one cannot divide public goods for personal use only.

Traffic lights, roads, street lights, etc. are examples of public goods. With the seamless possibilities that drones can offer, it makes sense to have public goods defined for this sector.

Imagine a future where airspace is accessible to everyone, where we have defined drone ports and air corridors which will allow smooth and safe operation of the drones. A lot of industries can benefit from it. Creating public goods will also allow more people to participate in the system thus increasing the size of the pie. If everybody in the system starts feeling comfortable with the operation of drones in the open skies then we could fundamentally transform the way we do things.

Who should be responsible for creating public goods?

Although classical economic theory suggests public goods will not be provided by a free market. But in a market like India, where the market is neither free nor regulatory, groups of individuals or organization can come together to voluntarily help government bodies to provide public goods in this market. For example, DigitalSky platform is a software initiative developed by the joint effort of iSPIRT and the government, working towards creating an online platform for registration of drones and obtaining permission for its operation, with a vision of making it paperless and presence-less.

There is tremendous scope for innovation and improvement in this sector. In the case of public goods, no firms will find it profitable to produce these goods because they can be enjoyed for free once they are provided and they cannot prevent this from happening. To provide these goods then, we either rely on governments or private organizations which volunteer to work on these issues.

The growth in India’s drone market would be primarily driven by the proactive initiative of existing players who will lay the foundation of this market in India. Thus DICE and iSPIRT have taken an initiative and are spreading awareness through round table sessions.

Round table sessions organized by DICE and iSPIRT serve as a platform where drone based entrepreneurs come together and think towards growing this industry by creating a model that benefits everyone in the system. The aim is to create a win-win situation in B2B and B2G.

The round table primarily serves two purposes:

To enable strategic partnerships between companies and encouraging companies to contribute to public goods.
Bridging the gap between the companies and the government.

Behavioral economics suggests that individuals can have motivations other than just money.

For example, People may volunteer to contribute to local flood defenses out of a sense of civic pride, peer pressure or genuine altruism.

Even if we have a narrow self-interest point of view we have to understand that voluntarily helping government bodies in tackling and solving the issues in drone rules and regulation will in turn help this market to flourish. And companies or individual contributors will have an underlying first mover advantage. So it’s important to act proactively to help the government to create regulation on your futuristic business model. It’s our job to demonstrate government that business can be done safely with a minimum amount of agreeable risk. Working together will not only accelerate the pace at which the regulations are implemented but also ensure that India takes away a big slice of the $100bn drone market. [5]

How does the future look like?

If you have ever seen the cartoon “The Jetsons” from the 1990’s you can already imagine what the future could look like. We are in an era where we can clearly automation and AI takes over mundane and laborious tasks at an exponential rate. The computers around us today are becoming powerful with each day. It can be witnessed that today it has become much easier to survive and it isn’t hard to survive as it used to be back in the days. We are not too far from the singularity where machine intelligence surpasses human intelligence. Thus we should have an environment where we can ensure that the technology is exploratory and exploitation is avoided.

Technology doesn’t happen on its own, people work together to make those imaginations/dreams a reality. We can already see Proof of concept (POC) of drone deliveries, drone taxis, and other futuristic applications. Who knows what else could we have with us in the next decade. Imagine a future where you would own your own personalised autonomous flying vehicle which takes you to your desired place with just the press of a button. You would have mid-air fueling stations which would enable you to drive without having ever to touch the land. Millions of smaller sized drones would be able to deliver products within minutes just like the internet today delivers information. Drones would become smaller and smaller and nanotechnology will enable us to overcome the limitations we see in drones today. Many other applications will rise up as we start working towards.

If you have any suggestions/solutions/ideas on how the system can be made better you can definitely become a part of iSPIRT / DICE India and write to us on [email protected] or [email protected] and also become a part of the round table.

04/02/201905/02/2019

A Platform is in the Eye of the Beholder

The distinction between whether you are building a platform or a product should be made primarily to align your internal stakeholders to a particular strategic direction, as we learned in the recent iSPIRT round table.

[This is a guest post By Ben Merton]

“So are we a platform, or are we a product?” I said last month to my co-founder, Lakshman, as we put the finishing touches to our new website.

We’d been discussing the same question for about a year. The subject now bore all the characteristics of something unpleasant that refuses to flush.

However, the pressure had mounted. We now had to commit something to the menu bar.

“I think we’re a product.”

“But we want to be a platform.”

“Okay, let’s put platform then…But isn’t it a little pretentious to claim you’re a platform when you’re not?”

Eventually, we agreed to a feeble compromise: we were building a platform, made up of products.

Job done.

At least, that is, until #SaaSBoomi in Chennai last month.

Manav Garg, who has considerably more experience than both me and Lakshman at building platforms, put up the following slide:

Product = Solving a specific problem or use case

Platform = Solving multiple problems on a common infrastructure

“Here we go again”, I could hear Lakshman say to himself after I Whatsapped him the image.

“That’s his definition. It doesn’t have to be ours,” he replied tersely, “What does he mean by ‘use case’, anyway?”

“I don’t know.”

I’m in awe of the entrepreneurs who seem to bypass these semantic quandaries.

You know, the ones who say stuff like “Stop thinking so much. Just sell stuff. Make customers happy.”

For me, these are the type of questions I need to chew over for hours in bed at night.

I was therefore excited to be invited to the iSPIRT round table at EGL last week, where the topic of discussion was “Transform B2B SaaS with #PlatformThinking”. The roundtable was facilitated by iSPIRT mavens Avlesh Singh, Shivku Ganesan & Sampad Swain.

It takes a lot to get 20 tech founders & their leaders to travel after work from all over the city to sit in a room for three hours with no alcohol. Fortunately, the organisers had promised a lot. The topic description was:

“Enable a suite of products, high interoperability, and seamless data flow for customers. This peer-learning playbookRT will help product to platform thinkers develop an effective journey through this transformation” was the topic description.”

The meeting was governed by Chatham House rules, meaning we can’t discuss the name or affiliation of those involved.

However, along with our founder mavens of large, well-known Indian technology businesses, there were 15 or so less illustrious but equally enthusiastic founders (& their +1s), including myself.

The discussions started with an overview of the experiences and lessons that had been learned by some of those who had successfully built a platform.

“We define a use case as a configuration of APIs…” the founder of a cloud communication platform started. This was going to be interesting.

“Why did you define it that way?” I asked.

“Based on observations of our business.”

I began to understand that the term ‘use case’ was being used differently by platform and product companies.

“A use case of a platform is usually tangential but complementary to the core business. A use case for a product is something that just solves a problem,” someone clarified, guaranteeing me a slightly more restful night.

As the discussions continued, it also became clear that there were a large number of possible markers that distinguish a platform from a product, but there was no agreement on the exact composition.

To resolve the impasse, we listed out the names of well-known technology companies to build a consensus on whether they were a platform or a product.

Suffice to say, we failed to reach any consensus. The conversation went something like this:

“Stripe?”

“Platform.”

“Product.”

“A suite of products.”

“AirBNB?”

“A marketplace.”

“A marketplace built on a platform.”

Etc etc

Even companies that initially appeared to be dyed-in-the-wool platforms like Segment and Zapier eventually had someone or the other questioning the underlying assumptions.

“Why can’t they be products?” murmured voices of dissent at the back of the room.

This was going nowhere. A few people sought solace from the cashew nuts that had been placed on conference table in front of us.

“Does the customer care whether you’re a product or a platform?” someone said.

Finally, something everyone could agree on. The customer doesn’t care. Your product or platform just needs to solve a problem for them.

“Then why does any of this matter at all?” became the obvious next question.

“I found it mattered hugely in setting the direction of the company, especially for the engineering and design teams,” the Co-Founder of a large payment gateway said.

“And investors?”

“Yes, of course. And investors. However, I think the biggest impact that our decision to build a platform had on my business was in the design more than anything else,” he explained, “For the engineering team, it was just a question of ‘we need this to integrate with this’. But the UX/UI and the…language… needed to be thought about very carefully because of this decision.”

“So, in effect, the platform/product debate is primarily a proxy for the cultural direction of the company?”

“Exactly.”

Logically, therefore, the only way you can really understand whether a company is a platform or a product is to have an insight into the direction its management wishes to take it.

A company might appear to be a product from the outside but, since it intends to evolve into a platform, it needs to start aligning its internal stakeholders to this evolution much earlier.

“So, a startup like mine should call itself a platform even if we are years away from actually being one?” I asked cautiously after I had enough time to process these insights.

“Yes,” was the resounding, satisfying response that virtually guaranteed me a full night’s sleep.

“And when should the actual transition from product to platform happen?”

“Well, Jason Lemkin says it should happen only when your ARR reaches USD 15m-20m, but that’s just another of those rules that doesn’t apply in India,” the co-founder of a marketing automation software said.

“The important thing is that this transition – when it does happen – is very hard for businesses,” he continued, “There is a lot of risk, but it opens up new revenue streams, helps you scale and build a moat. We hugely benefited from our decision to become a platform, but it was tough.”

It’s unlikely that we completely resolved the product vs platform debate for all founders. However, I feel that all of us came away from that meeting with a deeper insight into the subject.

Ultimately, whether you’re building a product or a platform will depend on your perspective. Most companies lie somewhere in between.

Where does your company lie on this sliding scale? And if that makes you a platform vs. a product, does it make any difference to the way you think?

We want to thank Techstars India for hosting the first of the roundtables on this critical topic.

Ben Merton

Ben is a Co-Founder of Unifize, a B2B SaaS company that builds a communication platform for manufacturing and engineering teams. He is also a contributor for various publications on business, technology and entrepreneurship, including the Wall Street Journal, the Financial Times and Business Standard. You can follow him on LinkedIn here, and Twitter here.

Featured Image: Source: https://filosofiadavidadiaria.blogspot.com/2018/01/o-principio-mistico-da-verdadeira-causa.html

04/10/201810/10/2018

AI/ML is not Sexy

One would think that the new sexy in the startup capital of the world is self-driving cars, AI/ML… I got news for you! AI/ML (esp. Machine Learning) is not listed in Gartner’s hype cycle for 2018.

Source: https://commons.wikimedia.org/wiki/File:Hype-Cycle-General.png

This was corroborated on my recent trip to the valley and the US east coast, where I met several investors, founders, corp dev and other partners of the startup community. It was evident that the AI/ML hype which peaked in 2016 & 2017 is no longer considered a buzzword. It is assumed to be table stakes. What you do with AI/ML is something everyone is willing to listen to. Using AI/ML to solve a high-value B2B SaaS problem is Sexy! (Gartner trends for 2018).

As the hype with AI/ML settles down, B2B startups across the globe are discovering the realities of working the AI/ML shifts for SaaS. Many AI tools & frameworks in the tech stack are still evolving and early pioneers are discovering constraints in the stack and creatively building workarounds as they build their products.

Many entrepreneurs are watching from the sidelines the unfolding of the AI/ML hype, wondering on many valid questions like these (and more):

Q: Do I have to stop what we are building and jump onto the AI bandwagon? No.
Q: Are the AI/ML resources mature & stable to build better value products? No, they are still evolving.
Q: Do I need expensive investments in constrained resources? No, not until you have a high-value problem to solve.

B2B SaaS startups go through 2 key struggles. How to find market-fit and survive? And how to stay relevant and grow. And if you don’t evolve or reinvent as the market factors change, there are high chances for an upstart to come by and disrupt you. The iSPIRT entrepreneur playbooks look to help entrepreneurs get clarity on such queries and more. Our goal is to help our startups navigate such market shifts, stay relevant and grow. Our mini roundtables Playing with AI/ML are focused on WhyAI for SaaS discussions in multiple cities. If you or a startup you know may benefit do register

The MiniRT Agenda

Seeding & creating an active discussion on Why AI/ML? What is the higher order value being created? How to identify the value & opportunities to leverage AI? How to get started with an AI playground (if not already running)? How to think of data needs for AI/ML investments, How to address the impact on Product & Business… Insights from these sessions are meant to help refine our approach & readiness to leverage AI/ML for building higher order value products. And in doing so building a vibrant community focused around navigating this shift.

Upcoming PlaybookRTs on AI/ML

6-Oct (Chennai) 10 am – 1 pm – MiniRoundTable on WhyAI for B2B SaaS – Shrikanth Jagannathan, PipeCandy Inc
18-Oct (Bangalore) 6 pm – 8 pm – MiniRoundTable with Dr Viral Shah on AI/ML Tools & discuss your ML/DeepLearning challenges
27-Oct (Delhi/Gurgaon) 2 pm – 6 pm – MiniRoundTable on WhyAI for B2B SaaS, Adarsh Natarajan, CEO & Founder – Aindra Systems
TBD (Bangalore) – MiniRoundTable on WhyAI for B2B SaaS, (based on registered interest)
TBD (Mumbai) – MiniRoundTable on WhyAI for B2B SaaS, (based on registered interest)

The AI+SaaS game has just begun and it is the right time for our hungry entrepreneurs to Aspire for the Gold, on a reasonable level playing field.

Click to Register for the AI/ML Playbooks Track.

Please note: All iSPIRT playbooks are pro-bono, closed room, founder-level, invite-only sessions. The only thing we require is a strong commitment to attend all sessions completely and to come prepared, to be open to learning & unlearning, and to share your context within a trusted environment. All key learnings are public goods & the sessions are governed by the Chatham House Rule.

Image source: https://commons.wikimedia.org/wiki/File:Hype-Cycle-General.png

Interesting Reads

The slow, light touch of AI in Indian Saas

05/07/201805/07/2018

The Second 20 Confirmed Batch at #SaaSx5

2 days to go for #SaaSx5 and we are reaching our limits for this year. I had missed a few folks in the first batch of 50 announced, so including them along with the next 20+ (in no particular order).

There will be one last list sent out tomorrow of confirmed participants. Really excited about the sessions which are shaping up at #SaaSx5

04/07/201805/07/2018

The First 50 Confirmed Companies at #SaaSx5

We are almost there. Only 3 days for #SaaSx5.

For people who are have attended earlier SaaSx I don’t need to tell this, but for all those who are attending the event for the first time – SaaSx is an informal event for knowledge sharing by SaaSprenuers for SaaSprenuers. This is why we have it on the beach for the last 3 years. 🙂

If you don’t know what this is about, SaaSx5, iSPIRT Foundation flagship event for software entrepreneurs of India, is being held in Chennai on 7, July 2018 (Saturday). SaaSx has been instrumental in shaping Global Software from India in the last 3 years. This year the theme is to help SaaS entrepreneurs setup for growth over the next 1-2 years.

So the first 50 confirmed list #SaaSx5 companies is here. It has been a slog for us going through all the applications we received, especially the initial drive to set extremely fair criteria and process. Listening to feedback from earlier SaaSx this year we decided to allow Founder and +1 (from their leadership team). Having a tag team we believe is extremely helpful to the founders in learning, assimilating and taking it back to their teams. This also meant that given the small limited space we had to be strict in our curation to ensure most SaaS product startups had an opportunity.

By the time this post goes live many other invites will have been sent and confirmed. We will continue to announce the companies finalized as we go along, so they can start preparing for the amazing sessions.

There are still spots, so if you have not registered or confirmed your invite (check your email), please do it quickly.

saasx5

In no particular order, here are the first 50 (based on their confirmations).

[Update: Next 20+ also announced]

All confirmed participants will receive further information in their mailboxes.

Looking forward to an amazing #SaaSx5!

Thanks to our many behind the scenes volunteers who have been tirelessly working on getting us this far and continuing on. Thanks to Chirantan & team from Software Suggest for crafting this post.

01/06/201809/06/2018

SaaSy bear SaaSy bear what do you see?

I see 3 shifts critical for me!

Taking a line from the popular Brown Bear children’s book, I believe that our SaaS startups have a real opportunity to leverage some leading shifts in the global SaaS evolution. While there are many areas of change – and none less worthy than the other – I am highlighting 3 shifts for SaaS (tl;dr) which our entrepreneurs can actually work with and help change their orbit:

Market shifts with AI/ML for SaaS to build meaningful product & business differentiation,
Platform Products shift to transform into a multi-product success strategy,
Leveraging Partnerships for strategic growth and value co-creation.

Some background

I joined iSPIRT with a goal to help our community build great global products. I believed (and still do) that many entrepreneurs struggle with the basics of identifying a strong value proposition and build a well thought out product. They need strong support from the community to develop a solid product mindset & culture. My intent was to activate a product thinkers community and program leveraging our lean forward playbooks model.

I had several conversations with community members & mavens on playbooks outcomes and iterating our playbook roundtables for better product thinking. I realized that driving basic product thinking principles required very frequent and deeper engagement with startups. But our playbooks approach model – working in a distributed volunteer/maven driven model – is not set up to activate such an outcome. Through our playbooks model, our mavens had helped startups assimilate best practices on topics like Desk Sales & Marketing, something that was not well understood some years back. This was not a basic topic. The power of our playbook RTs was in bringing the spotlight on gaps & challenges that were underserved but yet highly impactful.

As a product person, I played with how to position our playbooks for our entrepreneur program. I believe our playbooks have always been graduate-level programs and our entrepreneurs are students with an active interest to go deep with these playbooks, build on their basic undergraduate entrepreneurship knowledge, and reach higher levels of growth.

The product thinking and other entrepreneurial skills are still extremely relevant, and I am comforted by the fact that there are many community partners from accelerators like Upekkha to conclaves like NPC and event-workshop formats like ProductGeeks which are investing efforts to build solid product thinking & growth skills.

As the SaaS eco-system evolves, and as previous graduate topics like desk sales & marketing are better understood, we need to build new graduate-level programs which address critical & impactful market gaps but are underserved. We need to help startups with meaningful & rapid orbit shifts over the next 2-3 years.

Discovering 3 Shifts for SaaS

Having come to this understanding I began to explore where our playbooks could continue to be a vibrant graduate-level program and replicate our success from the earlier playbooks. Similar to an entrepreneur’s journey, these three shifts became transparent through the many interactions and explorations of SaaS entrepreneurs.

Market Shift with AI/ML for SaaS

There is no doubt that AI is a tectonic shift. The convergence of big data availability, maturity of algorithms, and affordable cloud AI/ML platforms, has made it easy for SaaS startups to leverage AI/ML. During a chance roundtable learning session on Julia with Dr. Viral Shah & Prof Alan Edelman, it was clear that many entrepreneurs – head down into their growth challenges – were not aware of the realities behind the AI hype. Some thought AI/ML should be explored by their tech team, others felt it required a lot of effort & resources. The real challenge, however, is to discover & develop a significantly higher order AI-enabled value to customers than was feasible 2 years ago. While AI is a technology-driven shift, the implications for finding the right product value and business model are even greater.

As I explored the AI trend I saw a pattern of “gold rush” – build a small feature with rudimentary AI, market your product as an AI product… – making early claims with small changes which do not move the needle. It became clear that a step-by-step pragmatic thinking by our SaaS startups was required to build an AI-based leapfrog value proposition. This could help bring our startups to be at “par” and potentially even leap ahead of our global brethren. Here was an opportunity to create a level playing field, to compete with global players and incumbents alike.

To validate my observations, I did quick small research on SaaS companies outside of India on their approach with AI. I found quite a few startups where AI was already being leveraged intrinsically and others who were still trying to make sense. Investments varied from blogging about the AI trend, branding one as a thought leader, to actually building and delivering a strongly differentiated product proposition. E.g.:

Chargebee rivals Stripe & Recurly, are experimenting with ML for fraud detection and for predicting subscription cancellation.
InstaSafe (cyber security for cloud) rivals Centrify, OneLogin… have been researching AI for authentication & security.
SignEasy rival DocuSign acquired Appuri for integrating ML into their product value.
Nintex and AgilePoint are exploring how engaging ML bots will help understand and improve processes in the BPM space.

There are no successes, yet! Our startups like Eka, Wingify, FreshWorks, WebEngage… have all been experimenting with AI/ML, stumbling and picking themselves up to build & deliver a higher level of value. Some others are setting up an internal playground to explore & experiment. And many others are waiting on the shore unsure of how to board the AI ship.

How do we enable our companies to create new AI playgrounds to analyze, surface, validate and develop higher order customer values & efficiencies? To chart a fruitful journey with AI/ML there are many challenges that need to be solved. And doing it as a group running together has a better chance of success.

The AI+SaaS game has just begun and it is the right time for our hungry entrepreneurs to Aspire for the Gold on a reasonable level playing field.

Shift to Platform Products

As market needs change, the product needs a transform. As new target segments get added different/new product assumptions come into play. In both these scenarios existing products begin to age rapidly and it becomes important for startups to re-invent their product offerings. To deal with such changes startups must experiment and iterate with agility. They require support from a base “internal” platform to allow them to transform from a single product success strategy to scaling with multiple products strategy.

This “internal” base platform – an infrastructure & layout of technology components to interconnect data & horizontal functional layers – would help to build & support multiple business specific problem-solution products (vertical logics). The products created on such a platform provide both independent as well as a combined value proposition for the customers.

Many startups (Zendesk, Freshdesk, Eka, WebEngage…) have undertaken the painful approach of factoring an internal platform to transform their strategy & opportunity. Zoho has been constantly reinventing itself and launching new products on a common platform, some of which are upending incumbent rivals in a very short period of time. WebEngage transformed itself from a “tool” into an open platform product.

“As the dependency on our software grew, customers needed more flexibility to be able to use their data to solve a wide range of business problems…significant difference in the way we build products now. We have unlocked a lot of value by converting ourselves into an open platform and enabling customer data to flow seamlessly across many products.” – Avlesh Singh, WebEngage

The effort to build an internal platform appropriately architected to support growing business needs (many yet unknown) is non-trivial and requires a platform thinking mindset for increased business development. It must be architected to allow rapid co-creation of new & unique product values in collaboration with external or market platforms. This can help the startup be a formidable player in the growing “platform economy”.

Leveraging Potential Strategic Partnerships

A strategic partner offers 2 benefits for startups. First is the obvious ability to supercharge the startup’s GTM strategy with effective distribution & scale. How does one make a strategic partnership? Pitching to a strategic partner is very different from pitching to a customer or investor. PSPs look for something that is working and where they can insert themselves and make the unit economics even better.

“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

The second leverage with a partner is the ability to innovate in the overlap of the partner’s products & offerings and the startup’s product values. A good partner is always looking for startups which can co-create a unique value proposition and impact an extremely large customer base.

“…we still have only three four percent market share when it comes to customers. So if we have to participate we have to recognize that we are not gonna be able to do it alone we’re going to have to have a strategy to reach out to the entire marketplace and have a proposition for the entire marketplace…you need to (do it) through partnerships.” – Shikha Sharma, MD Axis Bank

Both these partnership intents if nurtured well can bring deep meaningful relationship which can further transcend scale into a more permanent model (investment, M&A…).

Working with the 3 Shifts of SaaS

While each shift is independent in its own importance, they are also inter-related. E.g. an internal platform can allow a startup to co-create with a partner more effectively. Partners are always interested in differentiated leading-edge values such as what is possible with leveraging AI/ML. Magic is created when a startup leverages an internal platform, to co-create a strong AI-enabled value, in the overlap & gap with potential strategic partners.

And that’s what I see

I see a vibrant eco-system of SaaS startups in India working on creating leading global products. Vibrancy built on top of the basic product thinking skills and catapulted into a new orbit by navigating the 3 shifts.

“Reading market shifts isn’t easy. Neither is making mindset shifts. Startups are made or unmade on their bets on market/mindset shifts. Like stock market bubbles, shifts are fully clear only in hindsight. At iSPIRT, we are working to help entrepreneurs navigate the many overlapping yet critical shifts.” – Sharad Sharma, iSPIRT

Through our roundtables, we have selected six startups as the first running group cohort for our AI/ML for SaaS playbooks (Acebot, Artoo, FusionCharts, InstaSafe, LegalDesk & SignEasy).

If you are hungry and ready to explore these uncharted shifts, we are bringing these new playbooks tracks for you.

Please let us know your interest by filling out this form.

Also, if you are interested in volunteering for our playbook tracks, we can really use your support! There is a lot to be done to structure and build the playbook tracks and the upcoming SaaSx5 for these shifts for SaaS. Please use the same form to indicate your support.

Ending this note with a sense of beginning, I believe that our startups have a real opportunity to lead instead of fast-follow, create originals instead of clones. They need help to do this as a running group instead of a solo contestant. It is with this mission – bring our startups at par on the global arena – that I am excited to support the ProductNation.

I would like to acknowledge critical insights from Avlesh Singh (WebEngage), Manav Garg (Eka), Shekhar Kirani (Accel Partners), Sharad Sharma (iSPIRT). Also am thankful for the support from our mavens, volunteers & founders who helped with my research, set up the roundtables, and draft my perspective with active conversations on this topic: Ankit Singh (Wibmo/MyPoolin), Anukriti Chaudhari (iSPIRT), Arvi Krishnaswamy (GetCloudCherry), Ganesh Suryanarayanan (Tata GTIO), Deepa Bachu (Pensaar), Deepak Vincchi (JuliaComputing), Karthik KS (iSPIRT), Manish Singhal (Pi Ventures), Nishith Rastogi (Locus.sh), Pallav Nadhani (FusionCharts), Praveen Hari (iSPIRT), Rakesh Mondal (RakeshMondal.in), Ravindra Krishnappa (Acebot.ai), Sandeep Todi (Remitr), Shrikanth Jangannathan (PipeCandy), Sunil Rao (Lightspeed), Tathagat Varma (ChinaSoft), Titash Neogi (Seivelogic), and many other volunteers & founders.

All images are credited to Rakesh Mondal

04/05/201825/05/2020

Understanding iSPIRT’s Entrepreneur Connect

There is confusion about how iSPIRT engages with entrepreneurs. This post explains to our engagement model so that the expectations are clear. iSPIRT’s mission is to make India into a Product Nation. iSPIRT believes that startups are a critical catalyst in this mission. In-line with the mission, we help entrepreneurs navigate market and mindset shifts so that some of them can become trailblazers and category leaders.

Market Shifts

Some years back global mid-market business applications, delivered as SaaS, had to deal with the ubiquity of mobile. This shift upended the SaaS industry. Now, another such market shift is underway in global SaaS – with AI/ML being one factor in this evolution.

Similar shifts are happening in the India market too. UPI is shaking up the old payments market. JIO’s cheap bandwidth is shifting the digital entertainment landscape. And, India Stack is opening up Bharat (India-2) to digital financial products.

At iSPIRT, we try to help market players navigate these shifts through Bootcamps, Teardowns, Roundtables, and Cohorts (BTRC).

We know that reading market shifts isn’t easy. Like stock market bubbles, market shifts are fully clear only in hindsight. In the middle, there is an open question whether this is a valid market shift or not (similar to whether the stock market is in a bubble or not). There are strong opinions on both sides till the singularity moment happens. The singularity moment is usually someone going bust by failing to see the shift (e.g. Chillr going bust due to UPI) or becoming a trailblazer by leveraging the shift (e.g. PhonePe’s meteoric rise).

Startups are made or unmade on their bets on market shifts. Bill Gates’ epiphany that browser was a big market shift saved Microsoft. Netflix is what it is today on account of its proactive shift from ground to cloud. Closer home, Zoho has constantly reinvented itself.

Founders have a responsibility to catch the shifts. At iSPIRT, we have a strong opinion on some market shifts and work with the founders who embrace these shifts.

Creating Trailblazers through Winning Implementations

We are now tieing our BTRC work to specific market-shifts and mindset-shifts. We will only work with those startups that have a conviction about these market/mindset-shifts (i.e., they are not on the fence), are hungry (and are willing to exploit the shift to get ahead) and can apply what they have learned from iSPIRT Mavens to make better products.

Another change is that we will work with young or old, big or small startups. In the past, we worked with only startups in the “happy-confused” stage.

We are making these changes to improve outcomes. Over the last four years, our BTRC engagements have generated very high NPS (Net Promoter Scores) but many of our startups continue to struggle with their growth ceilings, be it an ARR threshold of $1M, $5M, $10M… or whether it is a scalable yet repeatable product-market fit.

What hasn’t changed is our bias for working with a few startups instead of many. Right from the beginning, iSPIRT’s Playbooks Pillar has been about making a deep impact on a few startups rather than a shallow impact on many. For instance, our first PNGrowth had 186 startups. They had been selected from 600+ that applied. In the end, we concluded that we needed even better curation. So, our PNGrowth#2 had only 50 startups.

The other thing that hasn’t changed is we remain blind to whether the startup is VC funded or bootstrapped. All we are looking for are startups that have the conviction about the market/mindset-shift, the hunger to make a difference and the inner capacity to apply what you learn. We want them to be trailblazers in the ecosystem.

Supported Market/Mindset Shifts

Presently we support 10 market/mindset-shifts. These are:

AI/ML Shift in SaaS – Adapt AI into your SaaS products and business models to create meaningful differentiation and compete on a global level playing field.
Shift to Platform Products – Develop and leverage internal platforms to power a product bouquet. Building enterprise-grade products on a common base at fractional cost allows for a defensible strategy against market shifts or expanding market segments.
Engaging Potential Strategic Partners (PSP) – PSPs are critical for scale and pitching to them is very different from pitching to customers and investors. Additionally, PSPs also offer an opportunity to co-create a growth path to future products & investments.
Flow-based lending – Going after the untapped “largest lending opportunity in the world”.
Bill payments – What credit and corporate cards were to West, bill payments will be to India due to Bharat Bill Pay System (BBPS).
UPI 2.0 – Mass-market payments and new-age collections.
Mutual Fund democratization – Build products and platforms that bring informal savings into the formal sector.
From License Raj to Permissions Artefact for Drones – Platform approach to provisioning airspace from the government.
Microinsurance for Bharat – Build products and platforms that reimagine Agri insurance on the back of India Stack and upcoming Digital Sky drone policy.
Data Empowerment and Protection Architecture (DEPA) – with usage in financial, healthcare and telecom sectors.

This is a fluid list. There will be additions and deletions over time.

Keep in mind that we are trying to replicate for all these market/mindset-shifts what we managed to do for Desk Marketing and Selling (DMS). We focussed on DMS in early 2014 thanks to Mavens like Suresh Sambandam (KissFlow), Girish Mathrubootham (Freshworks), and Krish Subramaniam (Chargebee). Now DMS has gone mainstream and many sources of help are available to the founders.

Seeking Wave#2 Partners

The DMS success has been important for iSPIRT. It has given us the confidence that our BTRC work can meaningfully help startups navigate the market/mindset-shifts. We have also learned that the market/mindset-shift happens in two waves. Wave#1 touches a few early adopters. If one or more of them create winning implementations to become trailblazers, then the rest of the ecosystem jumps in. This is Wave#2. Majority of our startups embrace the market-shift in Wave#2.

iSPIRT’s model is geared to help only Wave#1 players. We falter when it comes to supporting Wave#2 folks. Our volunteer model works best with cutting-edge stuff and small cohorts.

Accelerators and commercial players are better positioned to serve the hundreds of startups embracing the market/mindset-shift in Wave#2. Together, Wave#1 and Wave#2, can produce great outcomes like the thriving AI ecosystem in Toronto.

To ensure that Wave#2 goes well, we have decided to include potential Wave#2 helpers (e.g., Accelerators, VCs, boutique advisory firms and other ecosystem builders) in our Wave#1 work (on a, needless to say, free basis). Some of these BTRC Scale Partners have been identified. If you see yourself as a Wave#2 helper who would like to get involved in our Wave#1 work, please reach out to us.

Best Adopters

As many of you know, iSPIRT isn’t an accelerator (like TLabs), a community (like Headstart), a coworking space (like THub) or a trade body. We are a think-and-do-tank that builds playbooks, societal platforms, policies, and markets. Market players like startups use these public goods to offer best solutions to the market.

If we are missing out on helping you, please let us know by filling out this form. You can also reach out to one of our volunteers here:

Chintan Mehta: AI shift in SaaS, Shift to Platform Products, Engaging PSPs

Praveen Hari: Flow-based lending

Jaishankar AL: Bill payments

Tanuj Bhojwani: Permissions Artefact for Drones

Nikhil Kumar: UPI2.0, MF democratization, Microinsurance for Bharat

Siddharth Shetty: Data Empowerment and Protection Architecture (DEPA)

Meghana Reddyreddy: Wave#2 Partners

We are always looking for high-quality volunteers. In case you’re interested in volunteering, please reach out to one of the existing volunteers or write to us at [email protected]

25/03/201807/04/2018

Are you ready to Jump with AI/ML? [Updated Session Dates]

[Update 6-Apr] New April Session Dates – Symposium RT is being scheduled on Saturdays for Bangalore & Chennai (21st & 28th April).

Playbooks for Electrifying SaaS and more.

This is what we call the fourth industrial revolution…And companies are really transforming and bringing all these new technologies to connect with their customers in new ways.
– Dreamforce 2017 Keynotes, Marc Benioff.

There is no doubt that Artificial Intelligence (AI), is one of the recent “tectonic” market shifts, creating a change in landscape, market, and opportunity. AI and Machine Learning (ML), now in its eternal spring, has a deep impact on SaaS evolution. While the incumbent companies like Salesforce, Zendesk, Workday, have all invested heavily in AI, also global challengers across many verticals from Sales, BPM, CRM… to Security are focused on building higher order efficiencies and automation through AI/ML.

Over the last few years, our Indian SaaS entrepreneurs trumped the global SaaS growth by leveraging mobile first as there was no baggage of desktop, reduced sales & onboarding cost by perfecting the art of Inside Sales & Inbound Marketing, and efficient after sales support & service by leveraging remote success representatives. Our SaaS Mavens helped disseminate these leverages by sharing the best practices & modeling internal flywheels & experimentations. Many SaaS entrepreneurs successfully assimilated and got a significant boost in their growth journey. These levers are now basic table stakes for most SaaS startups.

AI has no breakthrough success stories, but it is helping create a level playing field – especially for our Indian entrepreneurs – to compete with global players and incumbents alike. Startups willing to make the jump, adapt AI into their products & business models to create meaningful differentiation, will experience a strong wind in their sails to leapfrog over the players who don’t.

Our entrepreneurs have a rare opportunity to be early adopters & global trailblazers.

To take advantage of this our entrepreneurs ask very valid questions.

Q. Why & How should we entrepreneurs navigate this AI market shift?
Q. How should we, given that we are untrained in AI, grapple with the 360° impact of AI on product, business, and technology?
Q. What AI leverage can we develop without requiring expensive investments for constrained resources?

How do we enable our companies to create new AI playgrounds to analyze, surface, validate and develop higher order customer values & efficiencies?

AI Playbooks

Since adapting to the AI “tectonic” shift requires a new paradigm of thinking, we have launched a multi-step playbooks track focused on Playing with AI/ML for Indian entrepreneurs. In line with iSPIRT’s mission, our playbooks purpose is to help market players navigate market shifts. The goal is to bring the practitioner knowledge from AI Mavens – AI-first entrepreneurs who are further ahead in their AI journey – to the AI-hungry startups and help them perfect the model of working with AI, get traction towards a meaningful AI-enhanced value, and become trailblazers for the community. If you are an AI-hungry startup who has either taken the plunge with AI/ML but early in your journey, or are actively looking to leverage AI/ML for your current products, then following the stepped approach below may help:

Step 1 – Attend an AI/ML Symposium RT – Getting prepared with Why AI and How AI. In our first kickoff session on 10-Mar, we had great discussions on AI data maturity, what can drive your AI approach, and more with our AI Mavens and ten startups (read more).

Step 2 – A cohort of startups from step 1 will be taken through multiple AI/ML Playbook RT for How AI – deep dives on topics to help with structuring an internal AI playground, competency with data product management, product positioning & branding, business model shifts, and more.
• These playbook RTs will help the startups carve out a lean playground for rapid experimentation and analysis, with a 3-4 person team of a data PM, & engineers. The team, actively lead by the founder, runs regular sprints (business/product/engineering sprints) of experimentation and validation, and have review touchpoints at intervals with AI-Mavens and the cohort as a running group.
• There is also an optional Tech Training Lab to build internal ML competency with a multi-day workshop with Julia experts.

Four startups have been initially selected for the cohort for the step 2 AI playbook RTs (Acebot, FusionCharts, InstaSafe & LegalDesk).

SaaSx5 – June 2018

We are working to set up the 5th version of our marquee SaaSx to engage with the larger SaaS startup community. We will definitely focus on the impact of AI/ML on SaaS and have workshops based on our momentum of the playbooks track on various topics above. Date & details to be announced shortly.

The AI+SaaS game has just begun and it is the right time for our hungry entrepreneurs to Aspire for the Gold, on a reasonable level playing field.

Click to Nominate or Register a startup for the AI/ML Playbooks Track.

Dates & Venue

~~AI/ML Symposium RT #1 – 10th Mar (Sat) 2p – 5p Done~~ (read more)
AI/ML Symposium RT #2 – 21st Apr (Sat) 11a – 2p @ Bangalore TBD
AI/ML Symposium RT #3– 28th Apr (Sat) 10a – 1p @ Chennai TBD

May the force be with you!

* All iSPIRT playbooks are pro-bono, closed room, founder-level, invite-only sessions. The only thing we require is a strong commitment to attend all sessions completely, to come prepared, to be open to learning & unlearning, and to share your context within a trusted environment. All key learnings are public goods & the sessions are governed by the Chatham House Rule.

Featured image modified from source: https://www.flickr.com/photos/jedimentat/7557276684

23/03/201826/03/2018

First AI/ML Playbook Roundtable – Playing With the New Electricity

This is a Guest post by Krupesh Bhat (LegalDesk) and Ujjwal Trivedi (Artoo).

AI is seen as the new electricity that will power the future. How do we make the best of the opportunity that advancements in AI technology brings about? With this thought in mind iSPIRT conducted a symposium roundtable at the Accel Partners premises in Bengaluru on March 10th. Accel’s Sattva room was a comfortable space for 20+ participants from 11 startups. There were deep discussions and a lot of learning happened through subject matter experts as well as peers discussion. Here’s a quick collection of some pearls, that some of us could pick, from the ocean of the deep discussions that happened there.

Products that do not use AI will die soon. Products that use AI without natural intelligence (read common sense) will die sooner.

– Manish Singhal, Pi Ventures

Starting with that pretext, it isn’t hard to gather that AI is not just a promising technology, it is going to be an integral part of our lives in near future. So, what does it mean for existing products? Should everyone start focusing on how they can use AI? Are you an AI-first company? If not, do you need to be one? After all, it does not make sense to build the tech just because it appears to be the next cool thing to do. If you are building AI, can you tell your value proposition without mentioning the word AI or ML? have you figured out your data strategy? Is the need driven by the market or the product?

Before we seek answers we must clarify that there are two types of products/startups in the AI world:

First, an AI-first startup – a startup which cannot exist without AI. Their solution and business model is completely dependent on use of Artificial intelligence (or Machine Learning at least). Some examples of such startups in local ecosystem are Artifacia and Locus.sh.

Second, AI-enabled startup – startups with existing products or new products which can leverage AI to enhance their offering by a significant amount (5x/10x anyone?). Manish has a very nifty way of showing the AI maturity of such companies.

The session was facilitated by several AI experts including Manish Singhal of pi Ventures, Nishith Rastogi of Locus.sh, Shrikanth Jagannathan of PipeCandy, Deepak Vincchi of Julia Computing.

Maturity Levels of AI Startups

After a brief introduction by Chintan to set the direction and general agenda for the afternoon, Manish took over and talked about the various stages of AI based companies. Based on his interactions with many startups in the space, he said there are roughly four growth stages where different companies fall into:

Level 1 – No Data, No AI: An entity that solves a business problem and is yet to collect sufficient data to build a sustainable AI business. The AI idea will die down if the company fails to move to state 2 quickly. Business may be capturing data but not storing it.
Level 2 – Dark data, No AI: The company holds data but is yet to build solid AI/ML capabilities to become an AI company. There is a huge upside for such companies but the data strategy needs to be developed and AI capabilities are not mature enough to be considered as an AI/ML company.
Level 3 – Higher automation driven by data and AI: These are the companies that have built AI to make sense out of data and provide valuable insights into the data using AI/ML, possibly with some kind of human assistance.
Level 4 – Fully autonomous AI companies: These are the companies at the matured stage where they possess AI products that can run autonomously with no human intervention.

Manish also noted that most companies they meet as a VC are in level 1 and 2, while the ideal level would be 3 and 4. He noted that AI comprises of three important components: Data, Algorithm & the Rest of the System that includes UI, API & other software to support the entire system. While it is important to work on all three components, oftentimes, the data part doesn’t get enough importance.

Do You Really Need Artificial Intelligence?

A whole bunch of solutions are smart because they are able to provide additional value based on past data. These are not AI solutions. They are merely rule based insights. Nishith from Locus added that there is nothing really wrong with rule based systems and in a lot of cases AI is actually an overkill. However, there are two cases where it seems apt for startups to look at AI for their predicament:

Data is incomplete: An example of this is Locus who gets limited mapping for gps coordinates and addresses.
Data is changing constantly: A typical case was of ShieldSquare where bots are continuously evolving and improving and the system deployed to identify them also needs to learn new patterns and evolve with them.

It is important to have clarity on your AI model especially when you communicate with your internal teams. Figure out what is the core component of your product – AI, ML, Deep Learning or Computer Vision.

What’s Driving Your AI Approach?

There are two major driving forces that can help one in deciding whether to AI or not to AI.

PUSH: The internal force when decision can largely be taken if your business is sitting on a lot of useful data, may be as a side effect of your key proposition.
PULL: The external market driven force where clients expect or ask for it e.g chatbots. We are already observing that AI can be a great pricing mechanism.

However, take great caution when using Customer data or Derived data, it depends on legal agreement with clients and can get you into legal troubles if it violates any terms.

Is Your Data Acquisition Strategy in Place?

Anyone interested in AI should have a data acquisition strategy in place. Here are a few points that can help you get one in place:

- What data do you collect, How do you validate it, Clean it and store it for further analysis?
- Surveys and chatbots can provide a steady stream of data if built correctly
- Think of data as a separate entity (has its own lifecycle), it may help to think of it as a currency and plan how you would earn, store and utilise it
- Capturing location, user interaction data can be insightful. This may include the interactions user has committed and the ones they have not committed (deleted/skipped/hidden)
- It makes sense to invest time, resources and people to gather data properly
- Have a unified warehouse (can start with economical options like Google Analytics and AWS)

It is also important to give some thoughts on how you are using aggregate data across the platform. In case, if your AI model uses a combination of customer specific data and the sanitised aggregate data available in the platform (“Derived Work”), then you should make sure that you have the permission to use such data. Without such clarity, you may run into legal issues.

Deepak Vincchi explained how Julia Computing is emerging as the programming language of choice for data scientists. The platform can process 1.3 million threads in parallel and is used by large organizations to crunch data problems.

In all this was an extremely engaging 3 hours without break. Guiding the session with real examples by Nishith, Shrikanth and also shared learnings from Navneet and others really helped bring to life Why AI and How AI. This symposium is part of an AI playbooks track was aimed at kickstarting cohorts of startups ready to jump with AI and help them get traction with AI, more will emerge on this shortly.

—

10 startups attended this mini-roundtable session – Acebot, Artifacia, Artoo, FusionCharts, InstaSafe, Klove, LegalDesk, Rocketium, Rubique, ShieldSquare.

Thanks to volunteers Rinka Singh and Adam Walker for their notes from the session and Ankit Singh (Mypoolin/Wibmo) for helping coordinate the blog post & note

Featured photo by Matan Segev from Pexels https://www.pexels.com/photo/action-android-device-electronics-595804/

First of all, why is trust important?

Innovations in distributed ledger technologies and BADAL

BADAL fabric supporting India Stack could boost digital India

Annexure: CBDC Developments

Indian perspective

1. What is iSPIRT?

2. What is our volunteering model?

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

4. How does it work with State and Market partners

5. How does iSPIRT make money?

6. How does iSPIRT protect against conflict of interest?

How can drones contribute to the public good in India?

What can be the public goods in the drone industry and why do we need them?

Who should be responsible for creating public goods?

How does the future look like?

The MiniRT Agenda

The AI+SaaS game has just begun and it is the right time for our hungry entrepreneurs to Aspire for the Gold, on a reasonable level playing field.

Interesting Reads

I see 3 shifts critical for me!

Some background

Discovering 3 Shifts for SaaS

Market Shift with AI/ML for SaaS

Shift to Platform Products

Leveraging Potential Strategic Partnerships

Working with the 3 Shifts of SaaS

And that’s what I see

Playbooks for Electrifying SaaS and more.

This is what we call the fourth industrial revolution…And companies are really transforming and bringing all these new technologies to connect with their customers in new ways. – Dreamforce 2017 Keynotes, Marc Benioff.

AI Playbooks

The AI+SaaS game has just begun and it is the right time for our hungry entrepreneurs to Aspire for the Gold, on a reasonable level playing field.

Dates & Venue

This is a Guest post by Krupesh Bhat (LegalDesk) and Ujjwal Trivedi (Artoo).

Maturity Levels of AI Startups

Do You Really Need Artificial Intelligence?

What’s Driving Your AI Approach?

Is Your Data Acquisition Strategy in Place?

This is what we call the fourth industrial revolution…And companies are really transforming and bringing all these new technologies to connect with their customers in new ways.
– Dreamforce 2017 Keynotes, Marc Benioff.