Posted on

#5 What is the Federated PHR Component of the Health Stack?

PHR – Personal Health Record – is a mechanism to access a longitudinal view of a patient’s health history and be able to use it for different purposes. It is a component of the health stack:


It relies on two building blocks – (a) registries, to know the source of the data; and (b) health identifier, to know whom the data belongs to. Separating out the building blocks with each serving singular functions helps design a more scalable and sustainable system. We follow certain principles for both of these building blocks:

1. Registries are master databases with information about different entities in the healthcare ecosystem, for example, of hospitals, doctors, care beneficiaries, etc. There should be checks and balances built to ensure correctness of data (such as digital signatures, audit trails, etc.), and this information should be made accessible for different use cases (through open APIs, and consent). Opening access to this information will have a positive effect of increased demand, thus improving quality and leading to convergence towards singular sources.

2. Health identifier is a mechanism to integrate a patient’s health records. This identifier should incorporate the following features:

  • The identifier need not be unique. This means that a patient should have the ability to create multiple health identifiers for different health records – think of different digital folders for mental health cases and cancer cases (a common practice in the physical world).
  • The power to unify health records should lie with the patient. In the physical world, this would translate to the patient having the right to either keep two folders or merge them into one. The same should be allowed digitally.
  • Patients should be allowed to use any identifier to verify themselves. However, since we are creating an electronic system of health records, it is important that these be digitally verifiable – such as mobile number, email ID or Aadhaar.

3. Electronic consent, as specified by MeitY, is a mechanism to give consent electronically in a manner that follows the ORGANS Principles – Open, Revocable, Granular, Auditable, Notifiable, Secure.

_____________________________________________________________________

With these building blocks in place, we come to features of the PHR architecture:

1. Federated – instead of having a centralised repository of all health records, we propose a federated framework where data resides at the source of generation. This has many benefits – (i) ease of operations, as data is not stored with a single entity (ii) lower costs, as no additional repository is being built (iii) better security, as data is stored at different nodes; and (iv) patient empowerment, as data is being shared directly with the patient.

2. Schema level standardisation – we believe that only standardising the schema without enforcing codification standards (which require a significant behavioural shift) should be sufficient for a number of use cases. Since this standardisation is at an IT systems level, it only requires a one-time mapping and does not require any change in clinical workflows.

3. Health data access fiduciaries – these would be entities that would route the consent and data requests between information users and information providers. In doing so, they would play the role of privacy protection, consent management and user education.

4. Health data vault – this is an option for the patient to store his/ her records in a personal storage space. While most hospitals that capture data continue to store it for a long period of time,  an individual might still choose to store this information separately (for long-term access, trust-deficit between patient and provider, etc.). In such a case, the patient can request a copy of the record to be pushed to his/her health data vault.

_____________________________________________________________________

Proposed architecture:

Workflow:

Patient goes to a healthcare provider. At the time of issuance:

Option 1: patient shares mobile number/ email id/ aadhaar no.
1. Provider authenticates user using one of the digital identifiers
2. (a) Provider sends a link to patient for downloading the report. Patient can later link these records with his/ her HDAF; or
2. (b) Patient can sign up with HDAF and search for provider to link records

Option 2: patient shares HDAF ID
1. Provider links patient records to the HDAF

Post linkage, patient can approve requests from data consumers through the HDAF for different use cases.

_____________________________________________________________________

We believe that building PHR as a public good will enable interesting use cases to come to life, that would together improve the healthcare ecosystem. While we will continue our quest for these, we would love to receive feedback on our thinking! If you work in this space and have comments, or would like to understand how this could help your product, please drop me a line at [email protected].

Posted on

#4 Reimagining Cancer Care

In the last few months, I have had the opportunity to work closely with the National Cancer Grid – a network of 150+ cancer centres in India – and in the process, better understand the workflows involved in different medical processes and the requirements of medical professionals. I have closely observed care delivery, interviewed cancer patients and oncologists, learnt about current challenges and about initiatives being undertaken by NCG and other organisations to tackle them.

This blog post is an evolved version of an earlier post, where I had talked about the use cases of health data and the implementation of a PHR (Personal Health Record). Of these, I believe that the biggest use of health data will be in improving the quality of care in complex medical cases (either acute like surgical procedures, or chronic like cancer). In this post, I will use cancer care to exemplify this.

Core idea
Let us visualise a specific application for cancer care, with oncologists as its primary users. There are only around 1000 trained oncologists in India, so let’s assume that all of them are users of this application. Let us also assume that clinical data of all patients treated by these oncologists is conveniently accessible through this application (with due privacy and security measures). What will these users do now?

Expert consultation
I attended a Virtual Tumour Board run by the National Cancer Grid – a weekly remote consultation program run on Saturday mornings where teams of doctors voluntarily join to discuss well-documented cases and their potential treatment plans. VTBs are run separately for each speciality (like head & neck tumour, gynaecology, neurology, etc.), which means that it takes up to 4-6 weeks for one’s turn. Doctors usually do not have the luxury of such long waiting periods, and therefore turn to individual consultations which are often not documented, depend on informal connects and are sometimes made with incomplete data. Formalising this process and making it asynchronous can be of huge benefit to all medical professionals.

Care team collaboration

Complex medical procedures often involve a team of doctors and other medical professionals, working responsibly for a given patient. A significant percentage of all deaths due to medical negligence is caused by lack of communication between the care team members. The communication process today is paper-based and unstructured, leading to accidents that can, in fact, be prevented – especially with the growing use of IoT devices and voice-based inputs. (I saw one such application at Narayana Health being used by their ICU teams).

Performance evaluation

Lack of organised data, changing patient care-providers and long feedback loops make it difficult for medical professionals to monitor their performance. Can we empower them with tools to do so? Doctors today lack visibility on the outcome of the treatment given and rely on intuition, experience or techniques tested in developed countries for care delivery. Such a tool would not only help doctors improve their performance, but also improve the trust equation with their patients.

User Experience
There are three crucial elements for enabling a good user experience:

Data input – Most EHR systems require text input to be typed in by doctors. This makes it difficult to use. Other input techniques for automated data transcription like touch, voice, or other innovative methods for data capture will need to be explored. Additionally, interoperability across all systems and devices will be key in enabling access to all data.

Data interpretation – Sorting through a patient’s health records takes up a substantial amount of time of a physician, especially when the data is unstructured. Developing intelligence to sort the relevant records as per the case in question will significantly enhance the user experience of the product.

Safety and Privacy– All solutions should ensure complete privacy of patients. This could mean access controls, electronic consent, digital signatures, digital logs, tools for data anonymisation, etc. it might also be important to perform basic verification of users of the platform.

Value Discovery
The value of the platform will increase as more and more physicians become a part of it. For example, an endocrinologist might need to consult a cardiologist in a case of disease progression, or an ENT specialist might need to consult an oncologist to confirm a diagnosis. More importantly, the platform will also drive innovation, i.e., other use cases can be developed on top of it. For example, the expert opinions mentioned above can also be used for consulting patient remotely, pre-authorising claims, forming medical peer review groups, etc. Similarly, working care groups can also simultaneously enrol staff for upskilling (as practised today in an offline setting), and information about treatment outcomes can help guide better research.

Next steps
We remain on a quest to find use-cases for PHR since we believe technology pilots alone would not be enough to drive its adoption. In that context, we are looking for partners to experiment with this in different healthcare domains. If you are interested, please reach out to me at [email protected]!

Posted on

#3 What does the Health Stack mean for you?

The National Health Stack is a set of foundational building blocks which will be built as shared digital infrastructure, usable by both public sector and private sector players. In our third post on the Health Stack (the first two can be found here and here), we explain how it can be leveraged to build solutions that benefit different stakeholders in the ecosystem.

Healthcare Providers

  • Faster settlement of claims: Especially in cases of social insurance schemes, delay in settlement of claims causes significant cash-flow issues for healthcare providers, impacting their day-to-day operations. The claims and coverage platform of the health stack is meant to alleviate this problem through better fraud detection and faster adjudication of claims by insurers.
  • Easier empanelment: The role of facility and provider registry is to act as verified sources of truth for different purposes. This means a convenient, one-step process for providers when empanelling for different insurance schemes or providers.
  • Quality of care: The use of personal health records can enable better clinical decision making, remote caregiving and second opinions for both patients and medical professionals.

Insurers

  • Faster and cheaper settlement of claims: claims and coverage platform, as described above
  • Easier empanelment of healthcare providers: registries, as described above
  • Diverse insurance policies: In addition to the above benefits, the policy engine of the healthstack also seeks to empower regulators with tools to experiment with different types of policies and identify the most optimum ones

Researchers and Policymakers

  • Epidemiology: the analytics engine of the healthstack can be helpful in identifying disease incidence, treatment outcomes as well as performance evaluation of medical professionals and facilities
  • Clinical trials: a combined use of analytics and PHR can help in identifying requirements and potential participants, and then carrying out randomised controlled trials

How can it be leveraged?

While the healthstack provides the underlying infrastructure, its vision can be achieved only if products benefitting the end consumer are built using the stack. This means building solutions like remote second opinions using health data from healthcare systems, as well as developing standard interfaces that allow existing systems to share this data. In the diagram below, we elaborate on potential components of both of these layers to explain where innovators can pitch in.

If you are building solutions using the health stack, please reach out to me at [email protected]!

Posted on

An Afternoon With Don Norman In Bengaluru

Are you building products for the everyday user? Is it becoming harder and harder to manage complexity while maintaining usability? How do you design a sustainable system for a complex multi-stakeholder environment? How do you teach a user to use your product with good design? How do you reinvent an established business model in light of rapidly evolving markets and technological possibilities? How do you design a product to be truly human-centric?

If any of these questions sound relevant to you, here’s an opportunity to seek answers on 22nd February in Bengaluru! 

About Don Norman

Dr Don Norman is a living legend of the design world having operated in the field for over 40 years. He has been Vice President of Apple in charge of the Advanced Technology Group and an executive at both Hewlett Packard and UNext (a distance education company). Business Week has listed him as one of the world’s 27 most influential designers. Dr Norman brings a unique mix of the social sciences and engineering to bear on everyday products. At the heart of his approach is human and activity-centred design, combining knowledge of cognitive science, engineering, and business with design.

Presently, he is Director of the recently established Design Lab at the University of California, San Diego where he is also professor emeritus of both psychology and cognitive science and a member of the Department of Electrical and Computer Engineering. He is also the co-founder of the Nielsen Norman Group, an executive consulting firm that helps companies produce human-centred products and services.

ProgrammeTalk

Don will share valuable insights about his interactions with Indian people, products and experiences.

Fireside Chat

An informal discussion with Don about his learnings and experiences spanning his long and illustrious career.

How to participate?

We’re inviting engineers, product managers, designers and everyone else who is building for large scale impact.

If you would like to further your understanding of human-centric design and hear straight from the horse’s mouth, please register here by 18th February. (An invite will be sent out to selected participants by 21st February)

Posted on

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.

© Ben Merton 2018

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

Posted on

#2 Federated Personal Health Records – The Quest For Use Cases

Last week we wrote about India’s Health Leapfrog and the role of Health Stack in enabling that (you can read it here). Today, we talk about one component of the National Health Stack – Federated Personal Health Records: its design, the role of policy and potential use cases.

Overview

A federated personal health record refers to an individual’s ability to access and share her longitudinal health history without centralised storage of data. This means that if she has visited different healthcare providers in the past (which is often the case in a real life scenario), she should be able to fetch her records from all these sources, view them and present them when and where needed. Today, this objective is achieved by a paper-based ‘patient file’ which is used when seeking healthcare. However, with increasing adoption of digital infrastructure in the healthcare ecosystem, it should now be possible to do the same electronically. This has many benefits – patients need not remember to carry their files, hospitals can better manage patient data using IT systems, patients can seek remote consultations with complete information, insurance claims can be settled faster, and so on. This post is an attempt to look at the factors that would help make this a reality.

What does it take?

There are fundamentally three steps involved in making a PHR happen:

  1. Capture of information – Even though a large part of health data remains in paper format, records such as diagnostic reports are often generated digitally. Moreover, hospitals have started adopting EMR systems to generate and store clinical records such as discharge summaries electronically. These can act as starting points to build a PHR.
  2. Flow of information- In order to make information flow between different entities, it is important to have the right technical and regulatory framework. On the regulatory front, the Personal Data Protection Bill which was published by MeitY in August last year clearly classifies health records as sensitive personal data, allows individuals to have control over their data, and establishes the right to data portability. On the technical front, the Data Empowerment and Protection Architecture allows individuals to access and share their data using electronic consent and data access fiduciaries. (We are working closely with the National Cancer Grid to pilot this effort in the healthcare domain. A detailed approach along with the technical standards can be found here.)
  3. Use of information – With the technical and regulatory frameworks in place, we are now looking to understand use cases of a PHR. Indeed, a technology becomes meaningless without a true application of it! Especially in the case of PHR, the “build it and they will come” approach has not worked in the past. The world is replete with technology pilots that don’t translate into good health outcomes. We, in iSPIRT,  don’t want to go down this path. Our view is that only pilots that emerge from a clear focus on human-centred design thinking have a chance of success.

Use cases of Personal Health Records

Clinical Decision Making

Description: Patient health records are primarily used by doctors to improve quality of care. Information about past history, prior conditions, diagnoses and medications can significantly alter the treatment prescribed by a medical professional. Today, this information is captured from any paper records that a patient might carry (which are often not complete), with an over-reliance on oral histories – electronic health records can ensure decisions about a patient’s health are made based on complete information. This can prove to be especially beneficial in emergency cases and systemic illnesses.

Problem: The current fee-for-service model of healthcare delivery does not tie patient outcomes to care delivery. Therefore, in the absence of healthcare professionals being penalised for incorrect treatment, it is unclear who would pay for such a service; since patients often do not possess the know-how to realise the importance of health history.

Chronic Disease Management

Description: Chronic conditions such as diabetes, hypertension, cardiovascular diseases, etc. require regular monitoring, strict treatment adherence, lifestyle management and routine follow-ups. Some complex conditions even require second opinions and joint decision-making by a team of doctors. By having access to a patient’s entire health history, services that facilitate remote consultations, follow-ups and improve adherence can be enabled in a more precise manner.

Problem: Services such as treatment adherence or lifestyle management require self-input data by the patient, which might not work with the majority. Other services such as remote consultations can still be achieved through emails or scanned copies of reports. The true value of a PHR is in providing complete information (which might be missed in cases of manual emails/ uploads, especially in chronic cases where the volume and variety of reports are huge) – this too requires the patient to understand its importance.

Insurance

Description: One problem that can be resolved through patient records is incorrect declaration of pre-existing conditions, which causes post-purchase dissonance. Another area of benefit is claims settlement, where instant access to patient records can enable faster and seamless settlement of claims. Both of these can be use cases of a patient’s health records.

Problem: Claim settlement in most cases is based on pre-authorisation and does not depend solely on health records. Information about pre-existing conditions can be obtained from diagnostic tests conducted at the time of purchase. Since alternatives for both exist, it is unclear if these use cases are strong enough to push for a PHR.

Research

Description: Clinical trials often require identifying the right pool of participants for a study and tracking their progress over time. Today, this process is conducted in a closed-door setting, with select healthcare providers taking on the onus of identifying the right set of patients. With electronic health records, identification, as well as monitoring, become frictionless.

Problem: Participants in clinical trials represent a very niche segment of the population. It is unclear how this would expand into a mainstream use of PHR.

Next steps

We are looking for partners to brainstorm for more use cases, build prototypes, test and implement them. If you work or wish to volunteer in the Healthtech domain and are passionate about improving healthcare delivery in India, please reach out to me at [email protected].

Posted on

SaaS 3.0 – Data, Platforms, and the AI/ML gold rush

An impending recession, the AI/ML gold rush, Data as the new oil, SaaS Explosion…
The SaaS landscape is changing rapidly and so are the customer expectations!

18 months ago, I came across a message that India is a premier hub for global B2B SaaS, just like Israel is a hub for cybersecurity. At first, I did not think much of it, but after having interacted with many SaaS founders and observing their painful growth journey, I realized the potential in these words. Yet, a series of market shifts are changing the world order of SaaS putting at test India’s position as a premier hub for SaaS.

TL;DR

The SaaS 3.0 market shifts are changing how global customers perceive value from SaaS products:

  • Tools which provide higher levels of automation & augmentation are valued more.
  • Comprehensive solutions in place of single point products is a preference.
  • Interoperability across the gamut of systems is an expected norm.

Startups, you have to build your new orbit to solve for these evolving needs. First, focus on delivering a 5x increase in customer value through an AI-enabled proposition. Next, build your proprietary data pot of gold, which can also serve as a sustainable moat. Lastly, leverage platforms & partnerships to offer a suite of products and solve comprehensive customer scenarios.

Read more on how the convergence of market shifts are impacting SaaS 3.0.

Quick background

While the SaaS industry began over 2 decades ago, many say it is only now entering the teenage years. Similar to the surge of hormones which recently brought my teenage daughter face-to-face with her first pimple. And she is facing a completely new almost losing battle with creams and home remedies. In the same vein, convergence of several market shifts – technology, data, economics, geopolitics – combined with deep SaaS penetration is evolving the industry to a new era. This rare convergence – like the convergence of the nine realms in Thor Dark World – is also rapidly changing how customers perceive the capability of SaaS products.

Convergence #1 – SaaS penetration is exploding!

I learned from Bala at Techstars India that they received a record number of applications for their first accelerator program. 60% of these were building or ideating some form of B2B SaaS offering. It would seem to justify the message above, that SaaS in India has grown legs, building a true viral movement, replicating momentum. Yet in these large numbers, there is also a substantial ratio of repetitive products to innovations. Repetitive in say building yet another CRM, or mindlessly riding a trend wave such as chatbots. Without an increased pace of innovation beyond our existing successes, we cannot continue to be a premier hub.

In 2018 SaaS continued to be the largest contributor to cloud revenue growth at 17.8% (it was down from 20.2% in 2017). Competition is heating up in all categories of SaaS. 10 years ago, an average SME customer was using 2 apps, now it averages at 16 apps. 5 years ago, a SaaS startup had on average 3 competitors, now a SaaS startups averages at 10 customers right out the door. Many popular SaaS categories are  “Red Oceans”. Competing in these areas is typically on the basis of features or price, dimensions which are easy for any competition to catch up on. There is a need for startups to venture deeper into the sea and discover unserved & unmet customer needs in a “Blue Ocean” where they have ample opportunity to fish and build a sustainable moat.

AppZen started with an opportunity to build conversational chatbots for employees, helping them in an enterprise workflows on various aspects like sales & expenses, and several other companies are doing the same. But as they went deeper to understand the customer pains, they were able to identify an unserved need and pivoted, leveraging the same AI technology they had built, to solve for T&E expense auditing. Being a first mover to solve this problem, they are carving out leadership in this underserved space and is one of the fastest growing SaaS startups of 2018.

Convergence #2 – Impending recession in 2019/2020!

On average recessions come every four years and we are currently 9 years from the last recession. The war between the Fed vs the US govt on interest rates, the recent US govt shutdown on a frivolous $B wall, the tariff and trade war between the US and China, are all indicative reasons for an upcoming recession. In such an uncertain economy, customers experience reduced business activity and alter their behavior and preferences:

  • Customers will become crystal clear about satisfying their core needs versus nice-to-haves.
  • They will seek high automation tools to help not only cut costs but also to make strategic decisions for an upside.
  • Many will prefer a suite of tools instead of buying multiple single point products.
  • They will also slow down POC, investment, partnership activities.

In a way, this is mixed news. Companies often pursue low-cost digital products with SaaS being a natural choice. However, combined with the competitive SaaS landscape, businesses become very selective. To be recession-proof startups must:

  1. Collaborate and partner with other vendors to build a shared view of the larger customer scenarios. Innovate to share (anonymized) data/intelligence.
  2. Partner to deliver a comprehensive solution instead of solving for a gap. 
  3. Invest & experiment in building solid AI-enabled automation for improving efficiency and decision making.

E.g. Clearbit’s approach to provide API and allow customers to leverage the value it provides, by integrating with common platforms such as Slack or Gmail which customers frequently use. In this approach they are reducing app switching and embedding the niche usecase into the larger customer workflow environment.

Another e.g. Tact.ai is helping increase sales team efficiency and bring visibility of field data to the leadership team. They are not only solving the core salesforce data entry problem for field sales, but with better data in the system, businesses now get better visibility about sales activities and can take effective strategic decisions.

Convergence #3 – the AI/ML gold rush!

During the dot com & mobile rush in early 2000, I watched many a friend jump ship to build a startup. At that time the web was flush with rich content, but the mobile web was in its early growth and innovative ways to bring web content onto mobile phones were being explored. Automated conversion of HTML to WML was a hot topic. But the ecosystem conditions were not aligned for completely automated WML transformations. Several startups in this space including my friend’s startup shut for such reasons.

More recently in 2016-17 Chatbots were projected to be the next big thing and it too suffered from similar misalignment. Chatbots were the first attempt to bring AI/NLP for customer interaction. However, they lacked the depth of ecosystem conditions to make them successful. 

  1. Bots were treated as a panacea for all kinds of customer interactions and were blindly applied to problems. 70% of the 100,000+ bots on Facebook Messenger fail to fulfill simple user requests. This is partly a result of not focusing on one strong area of focus for user interaction.
  2. Bots were implemented with rule-based dialogues, there was no conversational design built into it. NLP is still in its infancy and most bots lacked data to provide meaningful interactions. They were purely a reflection of the level of detail and thought that went into the creation of the bots.

AI/ML, however, is suffering from the “hype” of an “AI/ML hype”. There is a considerable depth within the AI/ML ecosystem iceberg. Amazon, Google, Microsoft…OpenSource are continuously evolving their AI stack with higher and higher fidelity of tools & algorithms. You no longer need fancy degrees to work the AI tools and automate important customer workflows or scenarios. 

Yet it is easier said than done. Most startups on the AI journey struggle to get sufficient data to build effective ML models. Further, data privacy has increased the complexity of sharing data, which now resides in distant silos. While internal proprietary data is a rich source of patterns, often times it is incomplete. In such cases, entrepreneurs must innovate, partner, source to build complete data as part of their data collection strategy. A strong data collection strategy allows for a sustainable moat. 

AIndra multiplied 7000 stains into 7M data points by splitting into microdata records. DataGen a startup in Israel, is generating fake data to help startups train models. The fake data is close enough to real data that the use is ethical and effective. Startups like Datum are building data marketplaces using blockchain to democratize data access. 

As mentioned many of the AI tools are limited in their constraints. Meanwhile, getting familiar with the capabilities and limitations of the necessary tools will help form a strategy path to solving the larger customer scenarios. 

Tact.ai faced the constraint by the limitations of the Alexa API. However, instead of building their own NLP they focused on working around the constraints, leveraging Alexa’s phrase based recognition to iteratively build value into their product. During this time, they continue to build a corpus of valuable data which will set them up for high growth when the NLP stack reaches higher fidelity.

Solving for the Hierarchy of Customer Needs

The convergence of SaaS penetration, AI/ML, data & privacy, uncertain economy & global policies… the customer expectations are rising up the Maslow’s hierarchy of needs. SaaS 1.0 was all about digital transformation on the cloud. SaaS 2.0 focused on solving problems for the mobile first scenarios. In the SaaS 3.0 era, the customer expectations are moving to the next higher levels. They will:

  • Prefer comprehensive solutions in place of single point products.
  • Expect interoperability across the gamut of systems.
  • Need tools which provide higher levels of automation & augmentation.

For startups who want to fortify their presence in the SaaS 3.0 era :

  1. Begin with a strong AI value proposition in mind, regardless if it is AI-first or AI-second. Articulate the 5x increase in value you can deliver using AI, which wasn’t feasible without AI. 
  2. Build your proprietary data pot of gold. And, where necessary augment with external data through strategic partnerships. A strong data lever will enable a sustainable moat. 
  3. Leverage platforms & partnerships to offer a suite of products for solving a comprehensive customer scenario.

Remember it is a multi-year journey, Start Now!

 

I would like to acknowledge Ashish Sinha (NextBigWhat), Bala Girisabala (Techstars India), Manish Singhal (Pi Ventures), Suresh Sambandam (KiSSFlow), and Sharad Sharma (iSPIRT) who helped with data, insights and critical feedback in crafting this writeup. Sheeba Sheikh (Freelance Designer) worked her wonderful illustrations which brought the content to life. 

Interesting Reads

Posted on

#1 India’s Health Leapfrog – Towards A Holistic Healthcare Ecosystem

In July 2018, NITI Aayog published a Strategy and Approach document on the National Health Stack. The document underscored the need for Universal Health Coverage (UHC) and laid down the technology framework for implementing the Ayushman Bharat programme which is meant to provide UHC to the bottom 500 million of the country. While the Health Stack provides a technological backbone for delivering affordable healthcare to all Indians, we, at iSPIRT, believe that it has the potential to go beyond that and to completely transform the healthcare ecosystem in the country. We are indeed headed for a health leapfrog in India! Over the last few months, we have worked extensively to understand the current challenges in the industry as well as the role and design of individual components of the Health Stack. In this post, we elaborate on the leapfrog that will be enabled by blending this technology with care delivery.

What is the health leapfrog?

Healthcare delivery in India faces multiple challenges today. The doctor-patient ratio in the country is extremely poor, a problem that is further exacerbated by their skewed distribution. Insurance penetration 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.

How will this leapfrog be enabled by the Health Stack?

At the first level, the Health Stack will enable a seamless flow of information across all stakeholders in the ecosystem, which will help in enhancing trust and decision-making. For example, access to an individual’s claims history helps in better claims management, a patient’s longitudinal health record aids clinical decision-making while information about disease incidence enables better policymaking. This is the role of some of the fundamental Health Stack components, namely, the health registries, personal health records (PHR) and the analytics framework. Of course, it is essential to maintain strict data security and privacy boundaries, which is already considered in the design of the stack, through features like non-repudiable audit logs and electronic consent.

At the second level, the Health Stack will improve cost efficiency of healthcare. For out-of-pocket expenditures to come down, we have to enable healthcare financing (via insurance or assurance schemes) to become more efficient and in particular, the costs of health claims management to reduce. The main costs around claims management relate to eligibility determination, claims processing and fraud detection. An open source coverage and claims platform, a key component of the Health Stack, is meant to deal with these inefficiencies. This component will not only bring down the cost of processing a claim but along with increased access to information about an individual’s health and claims history (level 1), will also enable the creation of personalised, sachet-sized insurance policies.

At the final level, the Health Stack will leverage information and cost efficiencies to make care delivery more holistic in nature. For this, we need a policy engine that creates care policies that are not only personalized in nature but that also incentivize good healthcare practices amongst consumers and providers. We have coined a new term for such policies – “gamifier” policies – since they will be used to gamify health decision-making amongst different stakeholders.

Gamifier policies, if implemented well, can have a transformative impact on the healthcare landscape of the country. We present our first proposal on the design of gamifier policies, We suggest the use of techniques from microeconomics to manage incentives for care providers, and those from behavioural economics to incentivise consumers. We also give examples of policies created by combining different techniques.

What’s next?

The success of the policy engine rests on real-world experiments around policies and in the document we lay down the contours of an experimentation framework for driving these experiments. The role of the regulator will be key in implementing this experimentation framework: in standardizing the policy language, in auditing policies and in ensuring the privacy-preserving exchange of data derived from different policy experiments. Creating the framework is an extensive exercise and requires engagement with economists as well as computer scientists. We invite people with expertise in either of these areas to join us on this journey and help us sharpen our thinking around it.

Do you wish to volunteer?

Please read our volunteer handbook and fill out this Google form if you’re interested in joining us in our effort to develop the design of Health Stack further and to take us closer to the goal of achieving universal and holistic healthcare in India!

Update: Our volunteer, Saurabh Panjawani, author of gamifier policies, recently gave a talk at ACM (Association for Computing Machinery)/MSR (Microsoft Research) India’s AI Summit in IIT Madras! Please view the talk here: https://www.microsoft.com/en-us/research/video/gamifier-policies-a-tool-for-creating-a-holistic-healthcare-ecosystem/

Posted on

SaaSy bear SaaSy bear what do you see?

Shifts for SaaS - SaaSy Bear

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.:

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 

Posted on

A Look Back At How Startup India Has Eased The Journey Of Startup And Investors

image1

It’s been two years since the fateful 2016 budget which recognised “Startups” as a separate breed of companies unto themselves, demanding bespoke treatment from the government and authorities. The clarity brought forth helped quell the nerves of both companies and investors, who had to otherwise resort to exotic exercises, supplementary structures, and platoons of professionals to keep their entrepreneurial dreams alive.

As we all await with bated breath for the slew of reforms expected of the Finance Minister, it behoves us to see how far we’ve come and how much further we need to proceed so that a billion dreams may become a reality.

This article is the first part of a two-part series which explores how Startup India has eased the friction in the Startup ecosystem so far, from an investor’s perspective with the second part talking about the next step of reforms which would have a multiplier effect on the ecosystem.

Flywheel of Funding

More often than not, any coverage about fundraising covers the journey of startups and entrepreneurs and the travails of raising their multimillion dollar rounds. But there exists another dimension to this story, that of fund managers raising their own funds. A large section of the investor community was elated that the government recognised this oft-ignored story and created the Rs 10,000 Cr (USD 1.5 billion) Fund of Funds managed by SIDBI which invests into SEBI registered AIFs and Venture Capital Funds.

This approach seeks to galvanise an ecosystem through a flywheel effect, instead of gardening it via direct intervention. The 10,000 Cr corpus can help seed AIFs worth Rs 60,000 Cr in India, which when fully deployed, is estimated to foment 18 lakh jobs and fund thousands of Indian startups. By contributing a maximum of 20% of the corpus of a fund, many fund managers can hasten they fundraise and concentrate more on helping their portfolio companies raise, instead of competing with them.

The Fund of Funds has invested into 88 AIFs so far, thus galvanising more than 5,600 Cr (USD 873 million) worth of investments into 472 Startups.

Bringing back tax breaks, not a back-breaking Tax

The Government’s support of Indian investors found its way into the Income Tax Act, with several measures to incentivise investments into the Indian Startup ecosystem, such as:

  • Insertion of Section 54 EE, which exempts Long-Term Capital Gains up to Rs 50 lakhs provided it has been invested in the units of a SEBI registered AIF
  • Insertion of section 54GB, which exempts Long-Term Capital Gains of up to Rs 50 lakhs provided it been invested into the shares of a Startup which qualifies for section 80IAC
  • Clarifying that the conversion of debentures or preference shares to equity shares will not be considered as a transfer and thus subject to capital gains at the point of conversion (the entire Venture Capital industry is based on convertible debentures and preference shares and this move has settled long-standing disputes regarding the instruments of investments)
  • Issuing a notification that the dreaded angel tax will not apply to shares issued at a premium to domestic investors by those startups who qualify under the DIPP scheme (although the scope of this needs to be extended to rid the spectre of angel tax that haunts various investors and entrepreneurs)
  • Clarifying that the stance of the assessee in categorising the sale of listed securities held for more than 1 year as Capital Gains or Income from Business can’t be questioned by the taxman
  • Changing the definition of a capital asset to include any securities held by a Foreign Portfolio Investor, thus removing the friction arising from asset classification (a similar provision is sorely needed for domestic hedge funds and Category III AIFs)

Capital without Borders

The Startup India scheme over the past few years has rolled out the red carpet to foreign investors while rolling back the red tape. The success of this is evidenced by the percentage of funding foreign capital represents in the Indian startup ecosystem, which is 9 times higher than domestic capital investment.

Some of the initiatives include:

  • Liberalising Foreign Direct Investment into most sectors including financial services, single brand retail, pharma, media and a host of other sectors up to 100% in most areas
  • Abolishment of the Foreign Investment Promotion Board
  • Relaxation of External Commercial Borrowings (ECBs) for Startups for up to USD 3 million
  • Allowing for issue of shares for non-cash consideration to non-residents under the automatic route
  • Marshalling foreign investment into Indian entities primarily for the purpose of investing in other Indian entities has been brought under the automatic route as opposed to the previous government approval route
  • Dismantling the approval mechanism for the transfer of securities by a Foreign Venture Capital fund to an Indian resident
  • Moving most of the filings (FCGPR, FCTRS, etc) to an online window managed by the RBI (ebiz.gov.in)

Well begun is half done

The government’s efforts to improve life for Startups in investors have begun to bear fruit in tangible ways as evidenced by the reduction in the number of companies seeking to have a Delaware entity with Indian operations. The recent leapfrog in the “Ease of Business” rankings also stands testament to this.

The Government must now seek to consolidate all these gains and clarify its stance and the stance of the tax department on long pending issues which have been a bane to all startups. While we have miles to go before we sleep, we must look back and take note of what we’ve achieved before we seek to scale greater heights.

This post has been authored by Siddarth Pai of 3one4 Capital

Posted on

Build On IndiaStack – Venture Pitch Competition

Announcing ‘Venture Pitch Competition: #BuildOnIndiaStack’

Dalberg and iSPIRT invite applications from early-stage ventures that are tech-
based solutions leveraging the India Stack platform at the core of their business
model to bring financial or transactional services to the underserved in India.
Pitch to some of the leading investors and thinkers in the Indian start-up ecosystem,
including the Bharat Innovations Fund, Omidyar Network and Unitus Seed Fund.
Winners will spend an hour of 'Think Time' – a mentorship session with
technology evangelist Nandan Nilekani.

Who are we looking for?

We are open to all innovations that use the India Stack to unlock new business
models or reach previously underserved new customer segments across sectors
such as financial services, education, healthcare and others. Some core focus areas
for the competition may include digital lending and supporting activities, such as
alternative credit scoring; sector specific affordable digital finance services such as
health insurance or education loans; sector specific digital services such as skilling
and certification, property registration agreements, patient-centric healthcare
management; and SaaS platforms “as a service” that support the development of
other India Stack based innovations such as Digi-locker or e-sign providers.

 

Who is eligible?
All applicants should:
1. Meet the 3-point criteria: tech enabled, leveraging India Stack Platform and
serving the underservedBe

2. Be a part of two (minimum) to four (maximum) members team including the
founder of the companyBe early stage start-ups that have received only seed (or limited angel)

3. Be early stage start-ups that have received only seed (or limited angel)
funding, if at all

 
What is in it for you?
The investor group, comprising of Bharat Innovations Fund, Omidyar Network and
Unitus Seed Fund, is a network of investors and operators, entrepreneurs and
technologists, designers and engineers, academicians and policy makers, with the
singular mission to solve some of India’s toughest problems.

Through this event you have an opportunity to receive:

-Exclusive focus on tech innovations that leverage the India Stack platform
and have the potential to address the underservedFlexible

-Flexible, insight driven, funding of up to Rs. 8 lakhs for early stage, innovative
modelsStrategic

-Strategic business support, through their specialists to support investees in
their strategy and growthA chance to be a part of the India Stack ecosystem through partnerships,

-A chance to be a part of the India Stack ecosystem through partnerships,
pilots, workshops, conferences and network building exercises

Visit www.buildonindiastack.in and send your pitch now.

Posted on

Customer Purchasing Insights For eCommerce Software

SoftwareSuggest is an online software discovery & recommendation platform. We provide free consultation on software and help SMEs select the right software for their organization. As a part of our business, we collect customer requirements, which when analysed can serve the industry with deep insights. Our learning for the eCommerce industry are presented in this report.

Below mentioned are the major takeaways:

  • There has been a hike in the number of organisations opting for online eCommerce solutions for their business. According to our findings a whopping 80% of the total are first time users.
  • A good number of e-commerce software buyers are located in Delhi, Maharashtra and Karnataka region.
  • We discovered that organizations prefer buying SaaS based over installation based software. The data suggest 69% prefer SaaS based.
  • The spread and depth of functionalities of software is the most prominent factor influencing the purchase decision of the software buyers.

Let us have a look at the fascinating figures that we discovered.

1.Industries turning up to use eCommerce software

industries using ecommerce software

We found that 35% of the software requirement was from apparel industry and next position is occupied by food and grocery item business (i.e. 20%). Rest is shared by miscellaneous industry like electronics, footwear, etc.

2. From which state maximum requirement was generated?

According to our observation, maximum eCommerce software buyers are from Northern region with Delhi (16%) being the kingpin in the list. Next place is shared by Maharashtra (12%) and Karnataka (13%). It can be a good decision for eCommerce companies to invest their resources in these region.
state wise lead distribution

3. What do the users prefer- SaaS based vs Installation based?

There has been a drastic shift in the number of users who prefer using SaaS based software when compared to server based software. It has been found from our data that 70% users prefer SaaS based or online software over the server based software.

User preference- SaaS based v/s Server based

4. What all features a buyer looks for in eCommerce software?

Nowadays, software buyers look for the product which can help them facilitate their customers in smarter way. With the advancement in technology, they look for sundry features which are stated as follows:4

5. What is the preferred budget in which buyers purchase the software?

For SaaS based, it has been found that on an average 50% of software buyers look for an ecommerce software between ₹1000 to ₹3000 per month. Around 18% buyers are willing to spend ₹3000 to ₹7000 per month. Only 7% can spend above ₹10000.

budget criteria for SaaS based sofwtare

For server or installation based, it has been discovered that 80% of software buyers prefer buying in the budget range of ₹50,000 – ₹1,00,000. Around 10% prefer buying in ₹100000- ₹150000. Remaining can afford up to ₹150000 and above.

budget criteria for server based software

6. New users v/s Existing users

new user v/s existing users

Around 20% of the software buyers are the existing users who reach us due to following reasons:

  • They are not satisfied with the services provided by their software providers
  • Their software does not have the latest features and they want to upgrade their software

In regards with the changing market conditions, there has been a hike in the number of retailers opting for online stores for their business. We discovered that around 80% of the software buyers bought software for the first time.

7. What is an average number of products showcased by merchants using eCommerce software?

average number of products showcased by ecommerce merchants

The data which has been collected by our team revealed that 17% of merchants prefer showcasing around 100-200 products on their website. And 21% of merchants prefer showcasing between 200-1000 products. Only 8% showcase above 1500 products which is quite less.

8. Time taken to decide on ecommerce solution

Our findings suggest that for a large percentage of software buyers, it takes around 3 to 5 weeks to decide on a solution.

time to find ecommerce solution

9. Number of demos before buying a software

We found that maximum software buyers usually take around 3-4 demos to decide on a solution.

no. of demos before buying

10. Factors influencing purchase decision

A software buyer looks for multiple features before purchasing any software.The depth and spread of functionality of the software is one of major factors. Have a glimpse at the other factors.

factors influencing purchase decision

The report has been generated from the data being collected by SoftwareSuggest team.

You can give your valuable thoughts about the report in the comment section below.

Also, find the list of eCommerce software solution with software demo, comparison chart, and many other values to help yourself select the right software.

Posted on

List of 11 #Madeinindia Applicant Tracking Software

Applicant tracking systems are great for HR professionals and recruiters. Even though there are disputes about their effectiveness as they target keywords more than candidate skills, it greatly helps recruiters to minimize the size of talent preposition without wasting their precious time and energy. Statistically speaking, ATS has saved over 20% of companies’ precious time during the recruiting process. Moreover as per careerealism “75% of large companies uses ATSs to review a resume before a recruiter sees it”. By seeing the above stats you can easily analyze how ATS is a must for every organization in this highly competitive business scenario.Indian Applicant Tracking Systems

To simplify your talent pool acquisition, here is a list of some of the Top Indian Applicant Tracking Software (In no particular order):
Resumefox: It is an innovative and easy to use recruitment software that saves the hiring time and cost by a whopping 70%. Moreover, through its comprehensive modules an organization can simplify its recruitment process by a great deal. Here are some of its notable features.

  • It helps in building searchable resume databases with zero manual efforts.
  • Reformates multiple resumes at one go and has a strong duplicate resume detection system
  • Generates comprehensive and insightful reports in real time
  • Creates recruitment life cycle and offers detail analysis of employee until joining.

Price:

  • Lite: $699
  • Standard: $899
  • Enterprise: $1199

TalentRecruit:  TalentRecruit is an end-to-end solution that integrates and automates your entire recruitment processes. It helps your company grow by streamlining the recruitment process and reduces operational cost with increase in recruiter’s efficiency. It is highly customized so can fit in any organization. Some of its most enterprising features are:

  • Provides candidate screening and evaluation facility
  • Enrich with facilities such as candidate sourcing, resume management, tracking candidate progression, etc.
  • It provides advanced search algorithms to locate the right candidate.
  • Has an efficient and agile management of jobs and candidates in order to reduce the “Time to Hire”

Price: Rs 1000-1500/user/month

99ATS: It is a web-based recruitment system that helps organization to stream line and manage their recruitment process. Moreover it has easy migration and avoids resume duplication. Here are some perks :

  • Has built-in bulk email to reach out to maximum number of candidates.
  • Imports resumes one by one or in bulk from external resources and organizes with the applicant tracking system.
  • Has comprehensive and reliable social media integration which helps in providing jobs and requirements at one click. (Learn More: How ATS Systems Integrate with LinkedIn)
  • Provides an authentic resume extract facility which by parsing extracts accurate information about the candidate.

 Price: Contact the Website

Zoho recruit: It a Saas based online recruiting system software. Moreover it helps staffing agencies and recruiting departments to track job openings, resumes, candidates, etc. quickly and efficiently. It provides features such as:

  • Automatically captures and import resume information from email attachments, outlook inbox, etc.
  • It lets the recruiters to post job opening on popular sites such as CareerBuilder, Indeed, LinkedIn, etc.
  • Manages candidate activity effectively from one location inside Zoho recruit.
  • Provides facilities like event management and candidate source tracking.

Price:

  • Free edition- Rs. 0 for 1 recruiter
  • Standard edition: Rs. 1500/recruiter/month
  • Enterprise: 3000/ recruiter/month

RecruitPro 360: Highly customized, RecruitPro 360 enhances recruitment process, synchronizes workflow and increases productivity. Moreover it provides high level automaton process which makes the recruitment process burden free and less time consuming. Here are some of its notable features

  • Provides intuitive user interface and automated resume import facility
  • It has comprehensive internet search and match capabilities.
  • It has a sophisticated tracker which tracks the candidate in an unique and user friendly manner
  • Has easy to use data migration facility with zero data entry

 Price: Contact the Website

Talentpool: It helps in executing better joining ratio by quality and streamlined recruitment process. It empowers front line users with better profiles, getting real time visibility of resumes and track key metrics. Take a look at its features:

  • It helps managing multiple sourcing activities, including marketing campaigns to access more candidates.
  • Imports candidate resumes from job portals directly into its centralized database.
  • Works seamlessly with agencies to manage vendors thus reducing time spent by recruiters on candidate status update.
  • Provides effective and authentic duplicate resume detection.

Price: Contact the Website

employAstar: It’s a cloud-based applicant tracking system that gives a 360-degree view of client, candidates, requisition, etc. Its cloud-based solutions are focused shrinking efforts and time of the recruiters while the process is going on. Here are some of its most enthralling features:

  • Provides email alerts and approvals so that organization can send automated emails to their corresponding candidates.
  • Has quick and advanced resume searching technique.
  • Facilities effective vendor management system.
  • Provides easy and integrated platform to simplify the process of corporate internal hiring.

Price: Contact the Website

Adrenalin Recruitment Management: It is the most effective hiring platform which facilitates in tracking of individual skills and transforms recruitment into more simple and effective process. Moreover it effectively manages employee talent thus solves employee retention problems. Some of its noticeable features are:

  • Provides intuitive interface which requires minimal training which makes it easier for candidates and recruiters to operate.
  • Has an unique feature of marking out ideal candidates as per company requirements
  • Provides seamless integrations with job portals and consultants with a single click.
  • Has comprehensive requisition (official order) management and secure data access.

 Price: Contact the Website

TalentCube: TalentCube emphasizes on making the recruitment process simple, easier and cost-effective for organizations. Moreover with the facility of mobile apps, it completes a one-stop solutions regarding recruitment for its users. Take a look at its features:

  • Provides comprehensive sourcing of candidates which reduces the “Time to Hire” scenario by 30-40%.
  • With an extensive social media campaign feature, organizations can connect with their candidates and improve candidate experience.
  • Reduces cost of Hiring with integrations with job boards, social media, email campaign, etc.
  • Has a user centered design which provides complete analysis, user feedback, prototype structure, etc.

 Price: Contact the Website

iHIRING: It is a cloud based assessment platform with in-built applicant tracking system. Moreover with iHIRING candidate assessment can be done in all possible formats viz. code simulation, running text, video and audio. Here are some of its salient features:

  • Provides large database storage so as to maintain the records of past candidates for future referrals.
  • Has IP address blocking facility which prevents unsolicited or unwarranted candidates from accessing published assessment.
  • Provides intuitive dashboard which allows the recruiter to view the entire running process and control hiring process in real time
  • It is the best deal and a comprehensive solution for corporate or in-house HR teams

Price: Contact the Website

Talentnow: It is designed with a view to manage the entire recruitment cycle of job creation to candidate finalization with minimum human intervention. Moreover it is a boon for direct employers, staffing companies and permanent placement agencies. Some of its notable features are:

  • Automatically imports resumes from third party job portals, social networking websites, etc. with almost zero data entry
  • Reduces portal cost by building your own resume database
  • Implements different workflows for different jobs and increases workflow efficiency.
  • Provides team/user-level dashboards of activities to track performance, revenues, usage of resources, etc.

 Price: Contact the Website

For most staffing agencies and recruiting companies, analyzing optimum keywords for candidate search is been a tedious task. But with the increase in usage of comprehensive and authentic ATS systems not only candidate search but also the “Hire to join” time has come down to a great extent. Storing databases and automating the recruitment process has become easy and less time consuming. Moreover before buying any ATS Software you should check this amazing Applicant Tracking Software Buyer’s Guide by Greenhouse, Inc. If you are looking for an open source ATS Software you can find it here.

Posted on

A corporate wallet to simplify business payments and expense tracking: The Happay Story

B2C wallets like Paytm and Mobikwik are known well enough. The B2B wallet story, however, is still in its nascent stage. Happay is that wallet which helps companies manage their expenses through employees, using corporate wallets.

Varun Rathi and Anshul Rai were classmates at IIT Kharagpur. They worked for 2 years before they started up. After toying with different business ideas, they zeroed in on payments, and thereafter, quit their jobs.

Happay started as a platform for splitting payments or transfer money through its wallet. However, the team, even with over 2 lakh registered users, was unable to find a good revenue model. They pivoted to address B2B payment management hassles. They have tied up with Ratnakar Bank to issue corporate cards which double as expense management system for the company. The companies can issue these cards to all their employees, and, at the back end, track, or even cap the permissible amount for each card.

Here is an excerpt from Varun’s interview with iSPIRT:

Why did you Startup?

VR: “I come from a business family and so, I think I inherited the urge to start something of own business. It was different from a typical Marwari business, because I wanted to make a technology business that was scalable”.

Why did you choose to address payments?

VR: “The payments market in itself is globally very large and scalable. So even if you solve a small problem in payments, it can go big.

Last 5-10 years have seen a lot of sourcing through wallets. So we thought this was the problem we should solve. Our solution was quite a hit between students and young professionals. However, there was no strong revenue model. Also, we had to go to all vendors and get them to accept those payments through our instrument, which was proving difficult.

On the other hand, a lot of businesses would come to us looking for payments solution. There was no product that would address their issue. So we decided to pivot.”

You decided to pivot from B2C to B2B. What were your major challenges?

VR: “First biggest challenge was to unlearn whatever we had learned and focus exclusively on talking to customers which we didn’t do with the first product.

The first product seemed more intuitive to the team, as we ourselves were the customers. This time around the team talked to over 1000 customers to understand their problems.”

As for aligning the team, Varun shares, “Our team was very young, with no one with more than 2-3 years of experience. So they were open to learn new things. Besides, it took us 9-10 months, to come up with the new product. This gave enough time to the team to align themselves.”

Next challenge was in terms of requirements of the business. “With a B2B product, we realized that businesses needed handholding at every step. Where we scaled to 2 lakh registered users with just 5 members in the team, this time around, we ended up hiring for different teams, taking the number of employees to about 100.

We hired the first person that could give a demo to the customers. Then we needed someone for lead generation, as the product does not automatically reach the target audience. Even after a customer is acquired, we needed to hire for relationship management and customer support. The customers even after signing up would not take the next steps themselves.”

What are the challenges in coming up with an expense card? Why have other expense management companies not done it?

VR: “ Getting such a card and its integration in place, is a difficult process. It requires a license, partnership with the bank, a certification with VISA, and a strong technology team to support all of it. It takes about a year to complete just the processes.

We were in the business of payments, from the start. So our initial aim was to develop applications over the payments platform. We first solved the payments problem and then later on built expense management software over it. Other players made the software and started selling it. They never had the intention of going deeper into the payments problem.”

How is scaling a B2B business different from a B2C?

VR: “There are both pros and cons. B2B is slow and time taking but steady. There are some safe landings in between, so I cannot go down all of a sudden, as is the case with B2C. I can become an overnight success in a B2C product, with maybe some good PR but that can go away in a second, as it is very fragile and there is a lot of competition. In B2B, customers don’t sign up that fast, but they give you time. Once you have their trust, even if something is not perfect, they give you a month or 2 to make it right. That gives more stability to the business.”

What are the 3 things you wish you knew before you started?

VR: “Launch soon: One mistake we made was not launching the product soon. We, like most other companies, were trying to build a perfect product. But the sooner you take it to the customer; the steeper is the learning curve.

Talk to your customers: We assumed what our customers needed and built the product around it. Customers don’t know what they need till they see it. So let them see it.

Making the team will take time: Time required in hiring and nurturing team is very high. It takes almost 50% of our time. We didn’t account for it from the start and this has come across as a major learning.

What is your advice to other people starting up right off the college?

VR: “Understand the market first. If you start fresh out of college, you can take more risk. In terms of technology, you can stretch your limits, as you don’t have any responsibilities. But scaling brings problems. Hiring, building and managing the team and responding to the market needs more finesse. Understand the market so that you have at least some idea of how to respond.”

Corporate wallets address a very crucial bottleneck in managing expenses in an organisation. We wish Varun and his team at Happay, all the success.