<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Customer Modeling for Finance Folks</title>
	<atom:link href="http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/</link>
	<description>Moving from a Low Accountability to a High Accountability Business Model</description>
	<pubDate>Fri, 21 Nov 2008 11:05:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Tom Lutzenberger</title>
		<link>http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/#comment-54400</link>
		<dc:creator>Tom Lutzenberger</dc:creator>
		<pubDate>Sat, 11 Oct 2008 20:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/?p=219#comment-54400</guid>
		<description>Very informative capture of some critical questions in customer retention! Thank you! We've reviewed your blog and this post in particular on our own blog: http://retentionofcustomers.com/wordpress/?p=236</description>
		<content:encoded><![CDATA[<p>Very informative capture of some critical questions in customer retention! Thank you! We&#8217;ve reviewed your blog and this post in particular on our own blog: <a href="http://retentionofcustomers.com/wordpress/?p=236" rel="nofollow">http://retentionofcustomers.com/wordpress/?p=236</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marketing sussex</title>
		<link>http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/#comment-26023</link>
		<dc:creator>Marketing sussex</dc:creator>
		<pubDate>Tue, 03 Jun 2008 13:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/?p=219#comment-26023</guid>
		<description>Very interesting subject!</description>
		<content:encoded><![CDATA[<p>Very interesting subject!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Novo</title>
		<link>http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/#comment-25941</link>
		<dc:creator>Jim Novo</dc:creator>
		<pubDate>Mon, 02 Jun 2008 23:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/?p=219#comment-25941</guid>
		<description>Ned, thanks for the comments, agree completely.  

Example of #1 was in the advice to treat the annuals and the PAYG differently.  Clearly these are two different behaviors and scoring them together is just going to muck the joint up.

On #2, that's why I'm not a very big fan of "traditional RFM" - there's too much chance for people to screw it up *unless* they're using it for a one-off purpose - like mailing a catalog.  Much prefer the &lt;a href="http://blog.jimnovo.com/2007/04/25/engagement-customers/" rel="nofollow"&gt;LifeCycle Grids approach&lt;/a&gt;, which is similar to keeping track of monthly RFM scoring at the customer level but a lot easier to understand - I think, anyway!</description>
		<content:encoded><![CDATA[<p>Ned, thanks for the comments, agree completely.  </p>
<p>Example of #1 was in the advice to treat the annuals and the PAYG differently.  Clearly these are two different behaviors and scoring them together is just going to muck the joint up.</p>
<p>On #2, that&#8217;s why I&#8217;m not a very big fan of &#8220;traditional RFM&#8221; - there&#8217;s too much chance for people to screw it up *unless* they&#8217;re using it for a one-off purpose - like mailing a catalog.  Much prefer the <a href="http://blog.jimnovo.com/2007/04/25/engagement-customers/" rel="nofollow">LifeCycle Grids approach</a>, which is similar to keeping track of monthly RFM scoring at the customer level but a lot easier to understand - I think, anyway!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ned Kumar</title>
		<link>http://blog.jimnovo.com/2008/05/29/customer-modeling-finance/#comment-25780</link>
		<dc:creator>Ned Kumar</dc:creator>
		<pubDate>Sun, 01 Jun 2008 23:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/?p=219#comment-25780</guid>
		<description>Great summarization of key tenets of RFM/Latency. The only comment I have is on segmentation.


	1. I agree that there is no point in segmenting to the nth degree prior to scoring, especially to someone who is just starting on things like RFM. However, just based on my experience I will stress on some segmentation "if there are distinct customer groups in terms of behavior". As an example, it is possible that because of the nature of products or service a company offers, certain industries are more frequent users of the products/service. That does not [by default] make the customers in other industries any less valuable -- purely on the basis of RFM. Just bringing this up as I have see many folks creating an RFM model without adequate thought and coming to wrong conclusions on who are 'good' customers and who are 'risky/defecting' customers.


	2. The second point is on current value. Again, I agree with you that current value is a measure of customer value. However, just as before I want to caution users that one has to look at current value keeping (a) the customer profile in mind (e.g industry as mentioned above), and (b) the customer's past value. If one is doing a RFM scoring frequently then this is less of an issue. However, if someone creates a one-time RFM model they can wrongly classify a customer as 'low-value', when the truth is that the customer is a 'high-value' customer but on the declining life-cycle (giving their business to competition).</description>
		<content:encoded><![CDATA[<p>Great summarization of key tenets of RFM/Latency. The only comment I have is on segmentation.</p>
<p>	1. I agree that there is no point in segmenting to the nth degree prior to scoring, especially to someone who is just starting on things like RFM. However, just based on my experience I will stress on some segmentation &#8220;if there are distinct customer groups in terms of behavior&#8221;. As an example, it is possible that because of the nature of products or service a company offers, certain industries are more frequent users of the products/service. That does not [by default] make the customers in other industries any less valuable &#8212; purely on the basis of RFM. Just bringing this up as I have see many folks creating an RFM model without adequate thought and coming to wrong conclusions on who are &#8216;good&#8217; customers and who are &#8216;risky/defecting&#8217; customers.</p>
<p>	2. The second point is on current value. Again, I agree with you that current value is a measure of customer value. However, just as before I want to caution users that one has to look at current value keeping (a) the customer profile in mind (e.g industry as mentioned above), and (b) the customer&#8217;s past value. If one is doing a RFM scoring frequently then this is less of an issue. However, if someone creates a one-time RFM model they can wrongly classify a customer as &#8216;low-value&#8217;, when the truth is that the customer is a &#8216;high-value&#8217; customer but on the declining life-cycle (giving their business to competition).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
