Showing posts with label enterprise software. Show all posts
Showing posts with label enterprise software. Show all posts

Tuesday, February 17, 2015

NGData Gives Enterprise Marketers a Customer Data Platform of Their Own

If you read my recent post on Customer Data Platforms Revisited very, very closely, you might have noticed it listed a category of data vendors who “store unified profiles and expose to other systems”, which is pretty much the core definition of a Customer Data Platform. You would also have noticed that category had only two members, Aginity and NGData. I reviewed Agnity back in November 2013 and when I spoke with them more recently, found they were still doing pretty much the same thing and growing nicely. But, until today, I’ve never discussed NGData.


I wish I could come up with a really cool reason for that, but it’s only because NGData just recently came to my attention. The company itself has been serving clients in late 2012. As my classification suggests, they are in the business of assembling client data from multiple systems, using it to build detailed customer profiles, and making the results available to execution systems like campaign management, call centers, Web sites, and mobile apps.

The technology involved is Hadoop as the primary data store and HBase to expose the profiles to external systems. Data is unified mostly with customer IDs supplied by the source systems, although NGData can also build cross reference tables to associate related IDs and do some probabilistic matching to link related devices. The profiles include both raw data and calculated metrics such as trends, exceptions, signals, affinities, predictions of fraud risk, churn likelihood, and next product to buy.  The predictions can be based on conventional predictive methods like regression or on integrated machine learning. Often the company is able to use regression models that the client has built already for other data sources. The base version of the company’s system, called Lily Enterprise, has about 700 such metrics, and clients can add their own. (There’s also an open source version of Lily, which has only the data management components of Lily Enterprise.)  External systems access profiles via SQL queries against HBase, API calls, or file transfers.

This may all sound pretty straightforward and should be familiar to readers of this blog. But out there is the real world, most companies are still struggling with the challenges of assembling customer data and making it accessible.  Those firms will find this is pretty novel stuff. NGData stresses its ability to easily add new data sources and to retain huge amounts of detail, something it inherits from Hadoop. Complex metrics like exceptions and trends are also relatively unusual.  They make it much easier for execution systems to act intelligently, since the hard work of surfacing opportunities and selecting responses is largely done in advance.  Predefining those metrics as part of the base system speeds initial deployment.   One proof point: NGData says clients can typically start running programs based on its system in four to five months, and sometimes as quickly as three months. Conventional data warehouse projects usually take more than one year and many are never delivered.*

NGData stresses that marketers get better results when they can look at all the data associated with each individual, rather than treating people as members of broad segments. Again, no reader of this blog will disagree.  But I did still like their example of using behaviors to identify people who are likely to call customer support with a particular problem, and then preempting those calls with personalized messages about how to solve the problem. Everybody wins: the customer appreciates the proactive service, and company fields fewer phone calls. The underlying point, which NGData stresses often, is that they're going beyond insight to producing an actionable result.

NGData also highlights the value of responding to customer behaviors in real time or near real time.  It can do this because it immediately updates its metrics in Hbase whenever it receives new information. Still is more old news, but conventional solutions often update their scores and recommendations nightly or even less often. To be fair, NGData can only update in real time if the source systems are providing immediate updates – which often isn't the case.  The vendor does have its own Web tags to capture real time information about Web visits, which lets it use in-session behavior to drive product and page recommendations.

The one thing you may not expect about Lily is that it’s old-style on-premise software, not software-as-a-service. That’s mostly because current clients are big companies in financial services, telecommunications, and media, industries that have been reluctant to let precious company data outside their walls (although plenty of hackers still manage to get it, he added snarkily). It’s also not clear how much SaaS would benefit NGData, since each client’s data store would remain separate in any case and the software needs to be installed on relatively few desktops. For what it's worth, Aginity is also on-premise and also serves primarily enterprise clients. 

I suspect it's no coincidence that the two "pure" Customer Data Platform vendors both focus on enterprises.  Smaller firms need to justify a CDP by combining it with a specific application, but big companies can afford a separate CDP project that they'll later tie to separate execution systems.  Perhaps this will change as CDPs get cheaper, the model is better understood, and integration with execution systems becomes easier.

NGData has about 25 current paying clients in Europe and the U.S. Pricing is based on volume of data and/or number of customers. Total cost for software and services starts around $150,000 to $200,000 and can go much higher. As I said, this is enterprise software.

________________________________________________________________________________
*This is one of those things that “everybody knows” but few cab document. Here’s one paper that says data warehouses “usually” take 12 to 36 months, cost $1 to $1.5 million, and have a 70% failure rate. It’s not clear where the author got his data but it all sounds about right.








Friday, September 02, 2011

Dreamforce 2011: Salesforce.com Will Leave Marketing Automation Alone. But Revenue Performance Management Might Be Another Story.

I spent most of this week at Salesforce.com’s Dreamforce conference. With 45,000 registrants, the company says that Dreamforce is now the largest technology industry gathering. I don’t know whether that’s true (as someone pointed out, the Consumer Electronics Show is much bigger, for starters). But I did notice about two years ago that pretty much everyone in the B2B marketing automation space was more or less assuming I’d attend. Peer pressure worked, and there I was.

If the big question on the mind of the marketing automation industry has been whether Salesforce would launch its own product, the show provided what I consider to be a definitive answer: No (at least for now; never say never). In both public announcements and private conversations, Salesforce leaders made clear their focus is on much bigger game: becoming a strategic enterprise technology supplier on par with IBM or HP. They plan to do this by becoming the platform for the “social enterprise”, which they see as the next major generation of computing.

More precisely, they are almost mechanically mimicking Facebook, which they see as the new center of online life. Their equivalent is Salesforce Chatter, the social network for company workers they see as connecting all company systems. Part of the strategy is to build enterprise applications on Salesforce platforms, and part of it is to access other enterprise applications from within Chatter. The still broader goal is to add customers and suppliers to each firm’s Chatter network, and to incorporate non-human objects such as orders and equipment. For better or worse, this is already happening today: the company demonstrated networks where an automobile can warn you that its tire pressure is low or a network switch can report on its status.

As someone who gets pretty darned annoyed when my printer tells me it wants an expensive new cartridge, I have mixed feelings about letting so many new and completely self-centered voices clamor for my attention. In fact, I’d say most people's biggest computer-related problem today is social media overload: people need better ways to structure and filter their social messages, not ways to get more of them. The Chatter group that Salesforce set up for Dreamforce itself struck me as a perfect example: it was filled with largely irrelevant noise that made it nearly impossible to see the useful information. If Salesforce hadn’t also sent nicely structured emails with schedules and contact information, I wouldn’t have known what to do when I got there.

Of course, any true believer would dismiss me as part of a pre-digital generation, and therefore both obsolete and irrelevant as a human being. Maybe so. I do recall that some (traditional, structured) research has shown that human brains physically adjust when they must process unstructured inputs. But even if people get better at filtering noise, that filtering still takes energy from other, more directly productive purposes. So unless the value of the nuggets captured by that filtering exceeds the effort consumed by the filtering, the result is a net loss.

Oh dear, I do sound pretty crotchety, don’t I? Blame lack of sleep from social networking of the old-fashioned, face-to-face kind. Cranky or not, I came away from Dreamforce very impressed how clearly Salesforce has defined their vision and aligned their actions to execute it. Although I heard some grumbling that there was nothing really new in the show’s announcements, I took that as evidence that Salesforce had previously decided what it wants to do and is now doing it. The specific announcements were all tied directly to the “social enterprise” strategy: things like adding Java support to the Heroku platform (making it easier to deploy applications on the Salesforce infrastructure) and adding presence and external parties to Chatter (making it easier to replace other collaboration systems).

That said, there’s a difference between a clear strategy and a successful strategy. I’d say that Salesforce has a pretty good chance of evolving Chatter into a ubiquitous enterprise social network. But whether that translates to becoming the core platform for all enterprise systems is another question. After all, there are other ubiquitous enterprise systems – for example, the telephone and email – that didn’t end up controlling everything else. But maybe I’m missing the point; perhaps all Salesforce wants or needs from this is continued revenue growth from processing on its platforms. “Social enterprise” offers a nice theme to make this possible by attracting application developers. Although Salesforce CEO Mark Benioff clearly has a more messianic vision than that, fulfilling the grander vision isn’t really necessary from a business standpoint.

All of which brings us back to B2B marketing automation. As a $2.1 billion company, Salesforce is looking where its next $2 billion in revenue will come from. Marketing automation is clearly too small to make a serious contribution to that goal. Existing B2B marketing automation systems already support Salesforce, so it has no particular strategic reason to replace them with its own applications.

On the other hand, Salesforce would probably like marketing automation to run on its own platforms, rather than simply synchronizing with Salesforce data and campaigns. So I wouldn’t be surprised to see Salesforce encourage third party developers to build marketing automation systems using Salesforce's Force.com and Heroku platforms and Database.com database, or to see them encourage existing vendors to migrate to the Salesforce.com infrastructure. This is pretty much the notion of “Salesforce add-ons” that I wrote about on August 16 (see "Can CRM Add-Ons Replace Marketing Automation?")

I also still expect that Salesforce will continue to enhance its core Sales application with features that make it better at specific marketing automation functions like complex campaign flows and Web tracking. Between native apps and organic product growth, today’s B2B marketing automation vendors definitely face some serious threats from Salesforce even if it doesn’t target them directly. It’s like sleeping with an elephant: it could roll over and crush you without even noticing.

Speaking of which, one thing you don’t do when sleeping next to an elephant is to poke it awake. There’s an element of that in Revenue Performance Management, which stakes a claim to a much larger territory than marketing automation by itself. I discussed RPM with both Eloqua and Marketo during Dreamforce. Both share a vision of combining marketing automation data with sales data, and ideally with data from other sources. This expanded database is really the core of RPM because it’s what gives the end-to-end view of the revenue cycle.

I agree with the goal, but Salesforce also has its eye on storing all that data. The bigger the pool of data the marketing automation vendors assemble, the more appealing it looks to Salesforce. And if you combine the data with a claim to managing strategic decisions about marketing and sales programs, you’re definitely poaching on their turf. At the moment, it’s a bit of a blind spot because analytics and business intelligence have not been Salesforce strengths. But that could well change – in fact, it must change if Salesforce is to provide a comprehensive alternative to existing enterprise platforms. When it does, they won’t just accidentally crush RPM vendors by rolling over: they’ll take aim with their giant feet and stomp them directly.

Or maybe I'm being naive. Perhaps RPM is a way for marketing automation vendors to attract Salesforce's attention as a potential strategic acquisition. In that case, poking the elephant is exactly the right approach.