Showing posts with label predictive lead scoring. Show all posts
Showing posts with label predictive lead scoring. Show all posts

0 LeadSpace Offers A No-Memory Approach to B2B Lead Scoring

My discussion last week of Infer, Mintigo, and Lattice Engines raised the question of what other B2B data vendors might be considered Customer Data Platforms. It’s easy to exclude companies that provide basic B2B lists (D&B, Data.com, Netprospex, ZoomInfo, etc.) since they’re clearly in a different business. But there’s another set of vendors that look very much like Mintigo, Infer, and Lattice Engines building detailed profiles by extracting data from Web sites, social networks, and other sources. This group includes InsideView, OneSource, SalesLoft and LeadSpace. So far as I know, none of them maintains a permanent copy of a client’s own customer file, which is the essence of being a Customer Data Platform. But if you’re a marketer needing to identify and score B2B prospects, you’d still want to give them a look.

I bring this up because a colleague suggested reconsider classifying LeadSpace as a CDP, which prompted me to learn more about them. Here’s what I found.

- LeadSpace, like the other vendors, scans Web sites, blogs, Twitter feeds, LinkedIn profiles, job hunting sites, and other sources to build a picture of a company’s business, managers, technologies, and similar attributes. Of course, every vendor argues it does this better than anyone else.  I  suspect there are indeed significant differences.  But I haven’t done any testing or seen anyone else’s test results – so all I can say is that wise buyers will test for themselves before making a choice.

- LeadSpace does build lead scores, something its Web site doesn’t reflect. This is one of the major points of differentiation among vendors in this space, so it’s worth understanding exactly what kind of scores each company provides. In LeadSpace’s case, the company builds “ideal buyer profiles” that measure how similar a lead is to a sample of existing customers provided by a client. Most clients have multiple profiles for different products or customer segments. Other companies in this group build different types of scores: say, for response to a specific campaign, or becoming a sales accepted lead, or having a high lifetime value. Some also estimate the incremental financial value of taking an action. It’s easy for buyers to gloss over these differences, but that would be a big mistake: they largely what kinds f applications a system can support. So be sure to explore them in detail (or read our explanations once we release the CDP Report itself.)

- LeadSpace doesn’t maintain its own permanent master database of all companies on the Internet. Rather, it conducts a fresh scan as each client requests research into its target audience.  This is another big difference from its competitors, who do run continuous scans and keep the results. LeadSpace argues that its approach avoids outdated information, saves the cost of storing and updating a persistent database, and lets the system collect precisely the right attributes for each situation – which can’t be known in advance. The company also points out that even a new scan will capture some history: the public Twitter feed goes back one year, as do job site listings. I have doubts about these arguments – I think older data can show important trends, am sure there’s plenty of outdated information on current Web pages, and suspect there’s the important attributes are pretty similar from one project to another.  Perhaps LeadSpace is really making the subtler argument that the incremental value of older information doesn’t justify the incremental cost of scanning and storing it, which is perfectly possible.  The company does store some old information, such as common job titles, to help analyze and classify inputs.

- LeadSpace doesn’t load a copy of its clients’ customer names, either. That’s essential for a CDP, which by definition has the potential of evolving into a primary marketing database. But it's not essential for LeadSpace's primary business of lead scoring, where even can be built on just a sample of a few hundred records. The arguments for and against the permanent master database also apply here, so I won’t repeat them. In addition, LeadSpace says its clients care more finding prospects with the right attributes, such as industry, company size, and technology fit, than trends in their behaviors or new job titles. Again, I’m not sure I agree, but should point out that LeadSpace mentioned combining their own scores with behavior data captured in marketing automation: so LeadSpace itself is at least implicitly acknowledging that behaviors are important.. LeadSpace's approach also means it can’t monitor a set of names and issue alerts when they do something interesting.  This is definitely something salespeople like to do. LeadSpace is closing that particular gap by developing a service, soon to enter beta testing, that will do a monthly scan of a client’s customer records.  It will feed the results back to the client's CRM or marketing automation, which themselves will highlight any changes.

- LeadSpace provides both prospect lists (i.e., new names) as well as data enhancement (i.e., information on names provided by the client). Most of its competitors also do both, but some do only enhancement. Again like its competitors, LeadSpace provides an interface for sales people to view the details associated with an existing customer. This is where its on demand approach comes in handy, since the interface can present information in categories tailored to each client’s needs. The system also lets sales people rate each lead with a thumbs up or thumbs down, providing feedback to fine tune the scoring model. I haven’t seen that particular feature in competitive systems but it’s not something I’ve specifically researched.

LeadSpace was founded in 2007 as a prospecting tool that let salespeople enter a company name and receive a list of individuals and their associated information and social conversations. The evolutionary path from there to the current system , launched in 2012, is fairly obvious. The company currently has more than 50 clients, mostly large B2B technology vendors. Pricing is based on the number of records either enhanced or provided in prospect lists, and starts around $25,000 per year.

0 KXEN Packages Automated Predictive Models within Salesforce Apps

As I mentioned in my Marketing Automation Beer Goggles post, KXEN introduced a free lead scoring app  for Salesforce.com users at Dreamforce. KXEN has since given me a closer look at the lead scoring product, underlying technology, and future plans.

First for details on Predictive Lead Scoring itself. As originally reported, it’s free and requires no configuration to set up. The trade-off for this simplicity is users have no control over which variables are included or what the models predict. The variables will include all standard and custom fields on the lead object, which isn’t too bad except that there might be useful data on related objects such as activity details.  At best, marketers could summarize such data and add the summary to the lead object, but that requires human intervention. Predictions are limited to conversions from lead to contact.  This isn’t always what you want, but it does stay within the lead object’s contents.

Some of these limits might be relaxed in future versions of the app.  However, KXEN is wary of making deployment more difficult or letting users make poor decisions such as removing variables they should keep. The system does provide reports showing the contributions made to the scoring formula by different variables and by values within those variables. Recognizing that this is already more than many users will care to review, KXEN plans to add simpler reports over time.

Although the lead scoring app attracted more interest than KXEN expected, it was really developed to illustrate the power of KXEN’s new “Cloud Prediction” model-building engine.  This uses the same automated modeling methods as KXEN’s established on-premise product. What’s new is a REST API that lets external applications send inputs over the Internet, wait while the engine builds a new model, and then receive the completed model formula. Scoring happens within the external application itself – Salesforce.com in this case – allowing the system to update scores as Salesforce data changes without running on KXEN’s own servers. Similarly, the app relies only on data stored within Salesforce.com’s own database, so KXEN doesn’t have to keep a copy.

The limits of the lead scoring app are a design choice: the cloud prediction API allows as much end-user control as KXEN’s on-premise system. But KXEN isn’t planning to expose the full API any time soon.  Instead, it's pursuing the app-based model as a way to expand use of its technology beyond its current base of relatively skilled users.

The next Salesforce.com app KXEN will release – pretty much any day – will tackle prediction of the “next best activity” for a given customer. This is substantially more complicated than the lead scoring app, since it creates a separate predictive model for each activity and then chooses the activity with the highest probability of response in each situation.  This one won’t be free: list price is $50 per user per month.

The next best activity app also requires more user effort to set up, since users must define the activities to model and specify eligibility rules for each activity. The system recommends activities randomly at first, to build some experience with different situations.  After the initial models are built it will still make occasional random selections to keep the models current.  Unlike lead scoring, the next best activity app reads from several Salesforce.com data objects in addition to the lead object.  Eventually, users will get control over which data elements to include.

The next best action app also relies on data stored within Salesforce.com. It won’t store a full history of offers made and rejected, because this would take more data than Salesforce.com can economically hold. That means the system won’t know when agents decide not to make the recommended offer. This can be a problem because the models based on a user-selected subset of cases.  It's a common issue with recommendation systems.

Whether these and similar issues cause serious problems for KXEN's cloud modeling apps remains to be seen.  Some amount of skilled human intervention may be essential to apply modeling effectively.  But it's worth exploring what's really needed: the ever-growing volumes of data and decisions make low-cost, automated predictions increasingly important for marketing success.