Customized database marketing for Indian e-commerce

Most of the players in the Indian e-commerce market are losing money.

My friend, Sanjay Dattatri has blogged about the challenges facing Indian e-commerce (click here). As he points out, Indian consumers are price-sensitive, dis-loyal and ill-behaved. I tend to agree with him.

As Sanjay points in another blog post, pricing sanity needs to prevail (click here). I agree with him on this one as well.

I do think that e-commerce vendors in India need to adopt a more customized approach to marketing and pricing. After all, aren't online marketers supposed to know all about their customers' buying behavior, browsing, email response (and customer care calls).

Why give the discount to all your customers when the reality is that some customers value your brand and superior delivery performance (and couldn't care less about the few rupees extra for that). The vendor can give a golden treatment to these price-insensitive customers by giving differential free shipping terms, and loyalty points. Some players like indiaplaza and healthkart do have a loyalty program.

On the other hand, one cannot lose out on selling to the price-sensitive customers, who will switch on a better deal available somewhere else.

The only way out is customized database marketing.

In my opinion, e-commerce vendors need to stick to the following rules of customized database marketing:

1) Target your discounts at customers who are likely to shift their purchases from your competition to your website, when given a discount. Examples of these customers include:

• Customers who bought a regular purchase like clothes, or diapers, or books, or groceries or nutritional products many months back and have not purchased since. I was delighted to see that healthkart sent me a  customized coupon code for whey protein 6 months after my first purchase. They avoided giving the discount to everyone as they know they have targeted a potential buyer. The key is to send out a customized coupon code which works only with the specific customer's login.

• Customers who have browsed a particular product or a category for a long time and not bought that product/ category. This can be done only when the customer is browsing with his cookie activated, and the e-commerce vendor is smart about tracking browsing behavior. A classic example would be a books-buyer browsing a mobile phone product page, getting a customized offer. My recommended approach would be to price the product at slightly higher than competition for the masses, and to give a discount coupon to customers who browsed and did not buy. (Quick programming note to vendors: Please don't send discount coupons for lingerie to men who are just browsing. But for that you've got to read the next point.)

2) Get to know more about the customer (even though you may know nothing to begin with). I get shocked when online retailers say that they deliberately have no information about their customer other than their user ID, name and shipping address. As a trusted seller you should try to get more information about the customer. Incentivize customers to update their profile online (such as gender, date of birth, marital status, interests, etc). The Payback program (called imint earlier) did that when they transitioned. When you know that you are dealing with a single guy who has never bought women wear before, you can stop sending him lingerie ads and coupons. Also some interesting things you can do with demographic data:

• Promote Gudi Padva to Maharastrians, and Onam to the Keralites and Eid to Muslims (irrespective of where they live)! -- if you can classify names by mother tongue and religion
• Promote kids items to families with kids

3) Send personalized recommendations/ suggestions, by putting yourself in the customer's shoes. Most e-commerce vendors are using formulaic recommendation engines which give recommendations based on the customer's last purchase. Ideally the recommendation engine should be based on the basket of goods purchased by the customer in the last 6 months.

Also, the recommendation logic needs to be altered for capital goods purchases (mobiles, electronics) vs. regular purchases (books). A mobile phone buyer does not need recommendations on what other similar mobile phones to buy! However a book buyer may appreciate recommendations on which other similar books to buy. For the mobile phone buyer, a list of accessories which go with his/her phone may be useful, but a formulaic recommendation engine may not capture that.

More later...let me know what you think!

Is Windows 8 doomed?

Mr Hampton of Bronte Capital published a blog article called "Changing my mind on Microsoft" .

He opines that Windows 8 will be a failure because it does not adapt to the usage behavior of different usage situations (tablet, desktop, phone):

Windows 8 was to serve a dual purpose. It was to be above all a pad operating system - one that doubled as a desktop operating system. You were going to be presented with bunch of tiles - the functional equivalent of Apple's app icons. If you used it as a pad it would have the limited functionality of a pad.

However you could take the pad, put it on a docking stand and use it with a keyboard and mouse as a desktop computer. This solves a lot of problems.

(a) it offers a distinct improvement over existing pads which are not very good for content creation. I cannot see myself editing a video on a pad or writing a blog post this long. But hey - I could with a plug-in-keyboard and mouse,

(b) it offers enterprises a chance to take their existing enterprise software and make it mobile. For example if a customer relationship system runs on Windows you could - without much further development - make it run on a Windows pad. This means there would be no incentive to redevelop it using (say) Python to run on iOS.

(c) it gets a large number of people used to the Windows system. There is a lot of human capital developed in using computer systems - trying to change - even Windows to Mac or vice-versa costs a lot of time as you work out how to say copy a file to an external hard drive or from a camera.

(d) it leads you to a world where the pad has some computing power - but if you need more grunt you connect it to a docking station in turn connected to a fast internet connection and you put the power in a cloud and rent the power out by usage. A world of semi-smart terminals - a pad if not docked, a super-computer if docked.

But the combined desktop interface has a big problem. Because desktops and pads and phones do different things they have different interfaces. A windows, icons, mouse and pull down menu interface has a venerable history because it works.

He also feels that Microsoft is losing its hold over developers:

The Microsoft virtuous circle is now dead. Two related things killed it: the rise of platform agnostic developer tools and the rise of alternative operating systems (Linux for servers, iOS and the "Big Cat" series for Apple, Android).

To my way of thinking the platform-agnostic developer tools came first - though this is a chicken-and-egg problem. The first really important platform-agnostic tool was Java. Programs written in Java run on Linux computers precisely the same way as they run on Apple computers or Microsoft computers. If you developed something on Java you could run it anywhere and you thus undermined the Microsoft virtuous circle.

Developing things for Java became widespread when people downloaded programs (applets really) from the internet. The person writing the applet had no idea what the customer computer set-up was and so had to write in a platform-agnostic fashion. Interactive Brokers for instance writes its software to run on Java - and they do this because it is a complex piece of software that has to run on many different flavours of client computer.

Over time Python developed as an even more important platform agnostic developer tool.

Nowadays nobody under thirty writes anything on Microsoft developer tools unless they are demented or brain-dead. Firstly the kids out of the colleges know the platform agnostic stuff well. Secondly when half the computers leaving factories either run iOS or Android (that is are smart-phones) nobody sensible will write in a way that does not allow easy porting to these platforms.

Microsoft's developer tools business and the customer lock it created has had a bullet through the brain. The body is lying on the floor - and most the users who have never developed anything and did not know that there even was a developers tool business have not noticed the blood-soaked victim.

I agree that Windows 8 may find a limited number of takers in the 'always-at-home' consumer market. However I feel that office goers will find good use for a product that docks to their office desktop (and can run enterprise applications), can be used as a portable for corporate presentations and can be carried on the subway ride back home to consume media. 

On the developer front, I feel that there is still a fair number of .Net programmers out there, and it is too early to call the doomsday on Microsoft.

What do you think?