Rabu, 31 Oktober 2012

Small Business CRM Tips: Top 5 Reasons Why You Need a Customer Relationship Management Tool

If you're an entrepreneur, you most likely have a solution or two in place to manage data about your clients, partners and prospects. At first, you may perhaps be fine with simply compiling business cards of your customers in a card holder on saving their contact information on your mobile phone. However, you'll soon realize that you need a more systematic means of storing/accessing data. That's the time you should consider getting a small business CRM tool. Here are top five reasons why you need one:

1. To find, attract and get new customers - A customer relationship management tool can facilitate in coming up with highly-targeted, relevant campaigns using the most preferred communication channels to obtain new customers. A CRM system will also help you monitor, evaluate and determine which marketing campaigns or promotions are working and not. With loads of information you can gather, you'll also be able to understand how to best use your marketing budget.

2. To cultivate and maintain current customers - Many entrepreneurs are already aware that it costs more to acquire a new customer than maintain a current customer. Using a small business CRM, you'll have all the required tools/features to help you cultivate and keep existing customers. Example: Ability to know and understand what your audience needs or wants, and how to accomplish them.

3. To attract past customers - Losing a customer to your competition is tough for any entrepreneur. But with the right CRM system, you can find out the reason/s they left and then concentrate on fulfilling their needs. As a result, you can then easily determine the ideal marketing avenues to lure previous customers back to your business.

4. To lessen customer service cost - Using a small business CRM, entrepreneurs can offer online customer support and technical assistance to better serve their customer base. This will then transform to improved customer satisfaction and reduced costs related to servicing customers.

5. To improve overall productivity - In the long run, companies that utilize a CRM tool will prove to be much more productive and proficient in deploying their products/services than those that do not. CRMs offer better customer relationships, which is synonymous to greater yield and ROI.

Bizness CRM is "selling to small businesses made easy." Bizness CRM is simple to use, free to try, and the only CRM built for companies targeting small businesses.

Sabtu, 13 Oktober 2012

Simple Interrow Computation: Keep It Simple!

The interrow computation is quite common, such as the aggregate, comparison with same period of any previous year, and link relative ratio in business statistics and analytics. Both R language and esProc provide a pretty good interrow computation ability with slight difference to each other. In the case below, the utilization of some basic inter-row computations is demonstrated to expound the differences between the two methods:

Since Christmas is coming, and the sales department of a company wants to make statistics on the outstanding sales persons after the Christmas big promotion, for example, the salesman who achieves half of the total sales amount of the company. The data are mainly from the order of table database: salesOrder. The main fields include the ID of order: ordered, Name of sales person: name, Sales amount: sales, and date of order: salesDate.

The straightforward solution is shown as below:

1. Group by sales person to calculate the sales amount of each sales person.

2. Sort by sales amount in reverse order on the basis of the data from the previous step.

3. According to the previous step, calculate the aggregate value of each record, and calculate the standard of comparison: the half of total sales of this company.

4. Of the aggregate values calculated in the previous step, select out the list of sales persons whose sales achievement meeting the below conditions: lower or equal to the standard of comparison; or although higher than the standard of comparison, the sales achievement of previous sales person is lower than the standard of comparison.

The detailed solution of R is shown as below:

01 library(RODBC)

02 odbcDataSources()

03 conn<-odbcConnect("sqlsvr")

04 originalData<-sqlQuery(conn,'select * from salesOrder')

05 odbcClose(conn)

06 nameSum<-gNameMonth<-aggregate(originalData$sales,list(originalData$name),sum)

07 names(nameSum)<-c('name','salesSum')

08 orderData<-nameSum[rev(order(nameSum$salesSum)),]

09 halfSum<-sum(orderData$salesSum)/2

10 orderData$addup<-cumsum(orderData$salesSum)

11 subset(orderData,addup<=halfSum | (addup>halfSum & c( 0, addup[- length (addup)]) Please find the detailed solution of esProc ( download ) below:))


$select * from salesOrder


=A2.sort@0(salesSum:-1) =A2.sum(salesSum)/2


=A4.select(addup<=B3 || (addup>=B3 && addup[-1]<b3)) Then, let us study on the differences between aggregate values:

The R uses cumsum to calculate the aggregate value in the line 10.

esProc uses cumulate in A4 to calculate the aggregate value.

Both writing styles are very convenient for users. However, the operation principle of esProc is aimed to each record: firstly, calculate the cumulate, then, get the aggregate value corresponding to this record according to the # row number. By comparison, R enjoys a higher efficiency than esProc on this respect since the calculation will be executed only once.

Dividing one statement of esProc into two statements can solve the efficiency issue, that is, firstly, calculate the list of aggregate value separately, and then insert it to the original dataset. However, such writing style is not as concise as the R that only requires one line of code.

Then, let us check the qualified sales person and the differences:

R completes the computation at the Line 11, mainly by moving the line, and using c( 0, addup[- length (addup)]) to construct a column for the new data. Compared with the column addup, the new column just moves down one column, and the last entry of data is removed and filled with 0 of the first entry. Then, you can compare whether the aggregate value is lower than the standard of comparison, or although it is higher than the standard of comparison, its previous record is lower than the standard.

R does not provide the ability to access the data at the relative position. Therefore, the method of "move the data in the relative position to the current position" is adopted. Though the result is still the same, the style of writing is not intuitive enough, and it requires the analyst a relatively higher ability in logic thinking.

The writing style of esProc is select(addup<=B3 || (addup>B3 && addup[-1]

Unlike the fixed algorithm of aggregate value, the algorithm of this step is relatively much freer. You may find that the style of expression regarding the relative position of esProc is very agile with great advantages.

Compared with the fixed algorithms, this step of algorithm is much freer.

As we can see from the above case, the computations of relative position and interrow computations can solve many problems which are apparently complex. esProc is more flexible in expressing the relative positions. Therefore, esProc users can feel more relax when calculating the complex problems.

Regarding the R language, appending to the whole column/row and the fixed algorithm are relative more concise and very impressive.

For industries like marketing and sales, healthcare and pharmaceutical, educational, financial and telecommunication, statisticsl computing tools like R or esProc are usually helpful to ease working strength and improve efficiency.