Don't Fall into the Trap of Losing Corporate Records
For the past three years, your company as been working feverously to finish a new technology that will benefit all walks of life. It has been a difficult three years as the financials of the company are all heading into the red, and the investors are anxiously demanding a return on their initial investment. The stress levels and demands on each employee have been extreme. As CEO, you've been walking a tightrope between investor's demands and your own expectations of your employees. Realizing the highly competitive market your find yourself in, internal control and security have been a high priority. The company would fall if the design plans of your new technology were to reach the competitors hands. Confident that you have done everything possible to ensure control over internal documents, you sit back and relax for a minute knowing that your company is about to make a huge contribution to society, as the engineers are reporting positive results from the final testing phase.
It is at this moment that your CTO walks in to the room with a pale face, looking as if he had witnessed death himself. He tells you that one of the engineers has e-mailed pieces of the technology to a foreign competitor. This has been going on for the past 8 months, he says. The CTO continues to say that the extent of the damage is not fully known, but that he expects the worse. As CEO, you ask yourself, what else could have been done, what else could we have implemented to catch these actions?
To answer this question, a record management software package created by NextPage would have protected the documents describing the company's new technology. This software tracks risky documents from start to finish. Throughout the document lifecycle, any changes made to the document are tracked and noted in a central location. The documents are monitored on desktops, through e-mail, key drives or on a server. A date/time stamp is created for each user when they access the document. It is very easy to see which employee was the last to access the document and to view what changes were made by that employee.
This risk management tool also monitors internal financials and assists greatly in Sarbanes Oxley compliance requirements. Each change made from a member of the financial team is securely noted. This aids in the turn around time for account/auditing firms to validate a corporation's earnings statements.
NextPage's software also aids in the development of products. Through the ability to access a document centrally, and make and save changes to one location, all users will have an interactive approach to documenting revisions. As improvements or setbacks take place, developers and project managers can easily view a central document and see a real-time image of how a product is progressing. Many errors though work duplication or lack of communication are avoided through Next Page's software.
So when it comes to your own business, eliminate the risk of losing corporate secrets and improve the document management within your company. These days one can never be too careful!
Ryan Knapp is an Internet Marketing Consultant for 10x Marketing. For more information about record management, contact NextPage.
Why CRM Projects Fail
1 Overview
This articles looks at some of the “human”, i.e. people-related factors that can cause a CRM project to fail. We then look at why, for those businesses already utilising Microsoft® Outlook® for their day-to-day e-mail, diary and contact management, implementing an Outlook-based CRM system gives you the best chance of overcoming these issues and ensuring a successful CRM implementation.
2 The Problem
CRM has received a lot of negative publicity over the years because of the failure rate of CRM implementation projects.
A recent Butler Group report found that 70 percent of CRM implementations fail. A Gartner study found that approximately 55 percent of all CRM projects failed to meet software customers' expectations. In a Bain & Company survey of 451 senior executives, CRM ranked in the bottom three categories among 25 popular tools evaluated for customer satisfaction.
While there are a multitude of reasons cited for failure of these projects, our experience in implementing over 200 CRM projects directly is that user acceptance is the one of the most critical factors.
In his article on “Why CRM Projects Fail”, Rajiv Chaudhry quotes:
You can design the best process in the world, and back it with the latest and greatest technology, but if your people don't buy into the project, it won't work. There are three people-related issues that have surfaced in many of the CRM programs, that are worth noting:
• The Fear-of-Change Syndrome. You already have a sales process in place. It may be based on printed reports, paper clips, and post-it notes, but it does work to some extent and people are familiar with it. Reengineering requires change, which most people instinctively resist. This fear of change needs to be dealt with early on, or the very people the system is designed to help will be the ones to see that it fails.
• The It's Easy Enough Syndrome. For your CRM system to be successful, every single person must use it. For the sake of speed, a temptation may be to let IS or a few computer-literate users design the system interface. What you will end up with is a system that they think is easy enough for them to use, but isn't easy enough for everyone. One CIO's observation sums up the whole issue about usability: Too easy never is.
• The Big Brother Syndrome. Be aware that horror stories of the hidden reasons that companies implement CRM programs may already be circulating through your sales force. They may have heard how these systems are designed to track their every move, just waiting for them to make a mistake so that management can pounce on them. This initial distrust is a very serious issue that must be dealt with swiftly.
Leaving any of these concerns unresolved will only result in bigger problems when you get ready for implementation. They need to be dealt with head-on so that everyone is on board and supportive of what the company is trying to accomplish.
Another one that I would add to the list above is:
• The “WIIFM” Concept: More completely known as “What’s In It For Me”. It’s no good introducing a system that only benefits the company. This is closely allied to the Big Brother Syndrome above. That is, you cannot expect a system to sustain itself if it does not produce any direct benefits to the users themselves.
3 Answering these Challenges with a CRM System based on Microsoft Outlook
The Fear of/Resistance to Change Syndrome dictates that the less the users have to change the way they work, the more likely they will adopt any new system that is based around what they are already used to. So if your users are already sending mail, managing their own contacts in their own Personal Contacts folder, and scheduling appointments with the Outlook Calendar, they don’t want to change this. We saw this frequently in the past where the first thing users asked us after introducing a new non-Outlook-based CRM system usually was “Why should I learn a different calendar? – I already know Outlook and I’m comfortable with it”. And trying to introduce a system that “sychronised” or “integrated” with Outlook also caused endless problems with calendars that got “out of sync”, etc. So this did little to reduce user frustration.
The Resistance to Change factor has another side that’s reflected in a popular saying namely “Up to the age of 18 you make your habits; thereafter they make you”. The reality of these words of wisdom is summarized as follows: If a new system is introduced such that not only is training required to learn the system but one also has to form a new set of habits associated with the procedures necessary to run the system, then it will take the average worker 3 to 6 months to develop these new habits to the point where they are ingrained into their daily work routines. And invariably if the user does not see sufficient benefit in the system soon enough (i.e. before these new habits are fully developed), then they continue to do what they were doing before the new system was introduced and as such the new system falls into disuse. One common excuse we used to get during post-implementation audits from users who were found not to have been entering activities into the new CRM system was “Oh, I keep forgetting to open the system”, or “it takes too long to open the system when I need it”.
The It's Easy Enough Syndrome: If everyone is already using Outlook, and has been trained on Outlook, or at least has become familiar with its functionality then it will be easy enough for them to learn a few new things associated with “relating” items together to transform Outlook into a Customer “Relationship” Management system. Microsoft has made enormous investments in studying the usability of Outlook and soliciting user feedback. So why reinvent the wheel when the users already know (and usually love) this interface.
The Big Brother Syndrome: Installing a new Sales Automation system with Activity Analyses and Productivity Comparison Reports already conjures up the wrong impression amongst the sales people. However just adding to Outlook’s functionality to provide a customer-centric “related” view of the existing disjointed elements in Outlook (appointments, tasks, journals, contacts and documents) makes all the sense in the world to users, and does not introduce any negative connotations.
The “WIIFM” Concept: Here Outlook definitely comes to the rescue. Users already appreciate the benefits of Outlook as a “Personal Information Manager”, especially as Microsoft touts Outlook as being one. The emphasis on Personal implies the primary benefit is to the user and not necessarily the company. So Microsoft in that sense has solved the issue of “What’s in it for me?”
Having looked at the fact that Outlook certainly addresses some of the “human” factors associated with a CRM implementation, we still need to look at how well Outlook meets the challenge in terms of functionality. We can do this by looking first at the basics of a Contact Management system, which still today is the core of any CRM system.
4 The Basics of any Contact Management System
Any contact management application needs at least the following basic functionality:
a) A mechanism to store and profile Contact information.
b) A means to plan and organize appointments with those contacts, not only for yourself but other team members managing those same contacts.
c) A means to schedule tasks and to-do’s for those contacts.
d) A mechanism to record any kind of interaction with a contact, namely meetings, phone calls, e-mail, documents, etc.
e) Some way of storing documents sent to and received from a contact.
f) A way to send and track e-mail communication.
5 Outlook’s inherent Contact Management Functionality
With reference to the requirements list above, Outlook at least satisfies the following requirements:
a) A mechanism to store and profile Contact information: The “Contacts” folder in Outlook already allows a comprehensive profile of any personal or business contact to be maintained.
b) A means to plan and organise appointments for those contacts: Outlook’s calendaring facilities provide these very effectively and when coupled with Exchange Server incorporate a huge number of collaborative features that are extremely difficult for any other stand-alone CRM system to emulate or reproduce.
c) A means to schedule tasks and to-do’s for those contacts: Outlook’s task management facility is excellent for this.
d) A mechanism to record any kind of interaction with a contact: The “Journal” facility of Outlook contains the standard fields necessary to record phone calls, meeting, etc. with clients, and can even time such activities.
e) A way to send and track e-mail communication: The Inbox and Sent Items stores inward and outward e-mails.
However, while Outlook does have the basic foundation for solid contact management functionality, there are certain limitations of Outlook that one needs to be aware of.
6 Limitations of Outlook
As a contact management application however, Outlook has the following limitations:
a) Private Mailbox (Contacts, Appointments, etc.): Without setting up and customising Public Folders, most users will just utilise their Private Mailbox Contacts folder for managing their contacts, thus limiting the sharing of that information and potentially creating massive duplication of the same data within the organisation.
b) Contact-centric: By virtue of their being only a Contacts folder (and no Companies folder), Outlook tends to be Contact-centric rather than Account-centric, which can be limiting for those users managing corporate accounts.
c) Discrete, independent folders: Most users tend to use their Outlook folders as discrete elements, i.e. because it is fairly cumbersome for users to link one item to another, (e.g. a contact to an appointment) they seldom do this. Thus it is difficult for users in the organisation to get an overall picture of all the activity occurring within the organisation against any particular company or contact. The universal objective of any CRM system however, is to provide a “single-view of all customer-related information to everyone in the organisation”.
7 Overcoming Outlook’s Limitations
Several Outlook-based CRM systems such as MX-Contact (www.mxcontact.com) are Outlook Add-Ins that overcome these limitations by extending the functionality of Outlook to transform it into a powerful CRM system without changing the way users send mail, schedule appointments, etc. Such systems utilise all of Outlook’s existing functionality but add the functionality found in CRM systems to co-ordinate the activities and items in Outlook into “one central view of all customer related information”. This is the so-called holy grail of CRM.
8 Other Advantages of an Outlook-based CRM System
There are several other distinct advantages to deploying Outlook as the basis for contact/customer management. We summarise them here:
Ease of Use:
a) Outlook is always the first application to be opened: Whenever knowledge workers arrive at their place of work each day, Outlook tends to be the first application that is opened, given that one needs to check what e-mail has been received since last clocking out of the office. He or she therefore opens by default the application needed for Contact Management. One of the greatest obstacles to overcome in the implementation of any CRM system is to get the users into the habit of opening the new system. With Outlook this is not an issue.
b) Outlook is always kept open: The nature of customer interaction is that it is very often re-active, sporadic and impromptu. Therefore it is imperative that the application used to log these interactions is always “at one’s fingertips” so to speak. Given that users keep Outlook open all day so as to respond timeously to e-mail ensures that this is the case.
c) Familiar Interface: If users are already utilising Outlook for at least e-mail and calendaring then they are already familiar with the interface and how to add new items, edit existing items, etc. Thus there is usually very little requirement for extensive training when an Outlook system is deployed. This dramatically shortens the average implementation time.
d) Increasing Percentage of E-Mail Interaction: An ever-increasing number of users are discovering the advantages of e-mail communication over other forms of contact (phone, fax, letter, etc.). So as e-mail becomes more widely used for customer interaction, it makes sense to deploy your e-mail client as the primary vehicle for managing customer communications, rather then utilising a totally different application.
e) One calendaring system universal across company & supply chain: Given that the vast majority of corporate users are utilising Outlook, it is easy for instance to send meeting requests to suppliers or customers, who can then use many of the same collaboration features that are available to internal users/co-workers. Many CRM systems have their own calendaring system and given that not all users will (or can) necessarily adopt this system means that one has to immediately contend with the problem of keeping these dissimilar calendars synchronized so that all users can effectively co-ordinate their diaries.
f) One e-mail store: Many of the conventional database-based CRM systems on the market have difficulty linking to e-mails given that an e-mail is not the same type of object as say a document. For this reason most systems not running inside Outlook tend to copy the contents of an e-mail into their database tables, thereby effectively duplicating the data and also disconnecting it from its original item, thus losing its formatting and also making handling of “Replies” and “Forwards” to the item difficult.
g) One document management system: Some CRM systems also copy documents into their database so as to enable replication of these documents to remote users. The disadvantage of this approach is that a document can only be edited from within the CRM system and not also from its original source on the Windows File System or Exchange Public Folder in the way that most users would already be familiar with.
h) Easy synchronization with most PDA’s: Given that all PDA’s synchronize with Outlook as a standard, this means that you have automatic access to your Contact Management data if it is kept in Outlook rather than being in another application.
Reduced Cost of Ownership:
i) No additional Infrastructure Needed: If a company already has the infrastructure in place necessary to run Outlook on client machines and Exchange Server, then no additional client or server hardware is needed to run an Outlook-based system.
j) Cost of upgrade to new versions of Outlook shared: Very often a client has to justify the costs of upgrading Office as well as the costs of purchasing the CRM application. With an Outlook-based solution this upgrade cost is shared given that the company receives a whole host of additional benefits and functionality from upgrading Office/Outlook as well as receiving a new CRM system.
k) Reduced Training Time (Cost): Given that users will already be familiar with the basics of Outlook, the time needed to train users, and hence the cost of that training, is significantly reduced.
l) Wider Support Base: Given that there are a large number of internal users and external consultants that know Outlook and VBA/VBScript (used to extend its functionality) it is easier and therefore less costly to enhance the functionality and support your user base.
m) Wider application of same training: If a company invests in training its staff in the functionality of Outlook, so as to more effectively use a CRM system based on Outlook, then this knowledge of Outlook will be utilised in everything a user does in Outlook, even those activities not linked to customer management but more internal collaboration etc. However, when one invests in training around a separate proprietary system then this training can only be applied to the use of that system and nothing else.
n) Reduced Installation Time: Given that an Outlook-based system installs itself inside Outlook, it is a simple matter for IT personnel to install the system. In many instances this can be done by the user him or herself.
9 Summary
Microsoft’s earlier promotion of Outlook as a “Personal Information Manager” created the impression amongst users that Outlook was only intended to manage one’s personal contacts and was not suited as the basis for a corporate-wide Customer Management System. Hopefully this article has rectified some of these misconceptions and shown that, given that so much of one’s day-to-day customer interaction is initiated from within Outlook, Outlook coupled with Exchange or SQL Server is the perfect environment for one’s all important Customer database. For an example of an Outlook-based CRM system, please have a look at MX-Contact (http://www.mxcontact.com). A free version is available for download from http://www.free-contact-manager.com.
10 PDF Version
A PDF version of this article may be downloaded from:
http://www.outlookwise.com/OutlookWise/Why_CRM_Projects_Fail/01_Why_CRM_Projects_Fail.htm
11 About the author
This article was written by Brian Drury, founder of ExchangeWise (http://www.exchangewise.com), and the architect of MX-Contact (http://www.mxcontact.com), a CRM, Contact Management and Sales Automation System for Microsoft Outlook. Brian has over 20 years experience in the IT industry and has focused on Contact Management, CRM and Collaboration systems for the last 14 years. During this time Brian and his staff have been involved in over 200 direct CRM project implementations covering 7 different products. He is also the editor of OutlookWise(http://www.outlookwise.com), a free newsletter aimed at keeping Outlook users up to date with news, views and articles of interest on Microsoft Outlook and Exchange Server.
This articles looks at some of the “human”, i.e. people-related factors that can cause a CRM project to fail. We then look at why, for those businesses already utilising Microsoft® Outlook® for their day-to-day e-mail, diary and contact management, implementing an Outlook-based CRM system gives you the best chance of overcoming these issues and ensuring a successful CRM implementation.
2 The Problem
CRM has received a lot of negative publicity over the years because of the failure rate of CRM implementation projects.
A recent Butler Group report found that 70 percent of CRM implementations fail. A Gartner study found that approximately 55 percent of all CRM projects failed to meet software customers' expectations. In a Bain & Company survey of 451 senior executives, CRM ranked in the bottom three categories among 25 popular tools evaluated for customer satisfaction.
While there are a multitude of reasons cited for failure of these projects, our experience in implementing over 200 CRM projects directly is that user acceptance is the one of the most critical factors.
In his article on “Why CRM Projects Fail”, Rajiv Chaudhry quotes:
You can design the best process in the world, and back it with the latest and greatest technology, but if your people don't buy into the project, it won't work. There are three people-related issues that have surfaced in many of the CRM programs, that are worth noting:
• The Fear-of-Change Syndrome. You already have a sales process in place. It may be based on printed reports, paper clips, and post-it notes, but it does work to some extent and people are familiar with it. Reengineering requires change, which most people instinctively resist. This fear of change needs to be dealt with early on, or the very people the system is designed to help will be the ones to see that it fails.
• The It's Easy Enough Syndrome. For your CRM system to be successful, every single person must use it. For the sake of speed, a temptation may be to let IS or a few computer-literate users design the system interface. What you will end up with is a system that they think is easy enough for them to use, but isn't easy enough for everyone. One CIO's observation sums up the whole issue about usability: Too easy never is.
• The Big Brother Syndrome. Be aware that horror stories of the hidden reasons that companies implement CRM programs may already be circulating through your sales force. They may have heard how these systems are designed to track their every move, just waiting for them to make a mistake so that management can pounce on them. This initial distrust is a very serious issue that must be dealt with swiftly.
Leaving any of these concerns unresolved will only result in bigger problems when you get ready for implementation. They need to be dealt with head-on so that everyone is on board and supportive of what the company is trying to accomplish.
Another one that I would add to the list above is:
• The “WIIFM” Concept: More completely known as “What’s In It For Me”. It’s no good introducing a system that only benefits the company. This is closely allied to the Big Brother Syndrome above. That is, you cannot expect a system to sustain itself if it does not produce any direct benefits to the users themselves.
3 Answering these Challenges with a CRM System based on Microsoft Outlook
The Fear of/Resistance to Change Syndrome dictates that the less the users have to change the way they work, the more likely they will adopt any new system that is based around what they are already used to. So if your users are already sending mail, managing their own contacts in their own Personal Contacts folder, and scheduling appointments with the Outlook Calendar, they don’t want to change this. We saw this frequently in the past where the first thing users asked us after introducing a new non-Outlook-based CRM system usually was “Why should I learn a different calendar? – I already know Outlook and I’m comfortable with it”. And trying to introduce a system that “sychronised” or “integrated” with Outlook also caused endless problems with calendars that got “out of sync”, etc. So this did little to reduce user frustration.
The Resistance to Change factor has another side that’s reflected in a popular saying namely “Up to the age of 18 you make your habits; thereafter they make you”. The reality of these words of wisdom is summarized as follows: If a new system is introduced such that not only is training required to learn the system but one also has to form a new set of habits associated with the procedures necessary to run the system, then it will take the average worker 3 to 6 months to develop these new habits to the point where they are ingrained into their daily work routines. And invariably if the user does not see sufficient benefit in the system soon enough (i.e. before these new habits are fully developed), then they continue to do what they were doing before the new system was introduced and as such the new system falls into disuse. One common excuse we used to get during post-implementation audits from users who were found not to have been entering activities into the new CRM system was “Oh, I keep forgetting to open the system”, or “it takes too long to open the system when I need it”.
The It's Easy Enough Syndrome: If everyone is already using Outlook, and has been trained on Outlook, or at least has become familiar with its functionality then it will be easy enough for them to learn a few new things associated with “relating” items together to transform Outlook into a Customer “Relationship” Management system. Microsoft has made enormous investments in studying the usability of Outlook and soliciting user feedback. So why reinvent the wheel when the users already know (and usually love) this interface.
The Big Brother Syndrome: Installing a new Sales Automation system with Activity Analyses and Productivity Comparison Reports already conjures up the wrong impression amongst the sales people. However just adding to Outlook’s functionality to provide a customer-centric “related” view of the existing disjointed elements in Outlook (appointments, tasks, journals, contacts and documents) makes all the sense in the world to users, and does not introduce any negative connotations.
The “WIIFM” Concept: Here Outlook definitely comes to the rescue. Users already appreciate the benefits of Outlook as a “Personal Information Manager”, especially as Microsoft touts Outlook as being one. The emphasis on Personal implies the primary benefit is to the user and not necessarily the company. So Microsoft in that sense has solved the issue of “What’s in it for me?”
Having looked at the fact that Outlook certainly addresses some of the “human” factors associated with a CRM implementation, we still need to look at how well Outlook meets the challenge in terms of functionality. We can do this by looking first at the basics of a Contact Management system, which still today is the core of any CRM system.
4 The Basics of any Contact Management System
Any contact management application needs at least the following basic functionality:
a) A mechanism to store and profile Contact information.
b) A means to plan and organize appointments with those contacts, not only for yourself but other team members managing those same contacts.
c) A means to schedule tasks and to-do’s for those contacts.
d) A mechanism to record any kind of interaction with a contact, namely meetings, phone calls, e-mail, documents, etc.
e) Some way of storing documents sent to and received from a contact.
f) A way to send and track e-mail communication.
5 Outlook’s inherent Contact Management Functionality
With reference to the requirements list above, Outlook at least satisfies the following requirements:
a) A mechanism to store and profile Contact information: The “Contacts” folder in Outlook already allows a comprehensive profile of any personal or business contact to be maintained.
b) A means to plan and organise appointments for those contacts: Outlook’s calendaring facilities provide these very effectively and when coupled with Exchange Server incorporate a huge number of collaborative features that are extremely difficult for any other stand-alone CRM system to emulate or reproduce.
c) A means to schedule tasks and to-do’s for those contacts: Outlook’s task management facility is excellent for this.
d) A mechanism to record any kind of interaction with a contact: The “Journal” facility of Outlook contains the standard fields necessary to record phone calls, meeting, etc. with clients, and can even time such activities.
e) A way to send and track e-mail communication: The Inbox and Sent Items stores inward and outward e-mails.
However, while Outlook does have the basic foundation for solid contact management functionality, there are certain limitations of Outlook that one needs to be aware of.
6 Limitations of Outlook
As a contact management application however, Outlook has the following limitations:
a) Private Mailbox (Contacts, Appointments, etc.): Without setting up and customising Public Folders, most users will just utilise their Private Mailbox Contacts folder for managing their contacts, thus limiting the sharing of that information and potentially creating massive duplication of the same data within the organisation.
b) Contact-centric: By virtue of their being only a Contacts folder (and no Companies folder), Outlook tends to be Contact-centric rather than Account-centric, which can be limiting for those users managing corporate accounts.
c) Discrete, independent folders: Most users tend to use their Outlook folders as discrete elements, i.e. because it is fairly cumbersome for users to link one item to another, (e.g. a contact to an appointment) they seldom do this. Thus it is difficult for users in the organisation to get an overall picture of all the activity occurring within the organisation against any particular company or contact. The universal objective of any CRM system however, is to provide a “single-view of all customer-related information to everyone in the organisation”.
7 Overcoming Outlook’s Limitations
Several Outlook-based CRM systems such as MX-Contact (www.mxcontact.com) are Outlook Add-Ins that overcome these limitations by extending the functionality of Outlook to transform it into a powerful CRM system without changing the way users send mail, schedule appointments, etc. Such systems utilise all of Outlook’s existing functionality but add the functionality found in CRM systems to co-ordinate the activities and items in Outlook into “one central view of all customer related information”. This is the so-called holy grail of CRM.
8 Other Advantages of an Outlook-based CRM System
There are several other distinct advantages to deploying Outlook as the basis for contact/customer management. We summarise them here:
Ease of Use:
a) Outlook is always the first application to be opened: Whenever knowledge workers arrive at their place of work each day, Outlook tends to be the first application that is opened, given that one needs to check what e-mail has been received since last clocking out of the office. He or she therefore opens by default the application needed for Contact Management. One of the greatest obstacles to overcome in the implementation of any CRM system is to get the users into the habit of opening the new system. With Outlook this is not an issue.
b) Outlook is always kept open: The nature of customer interaction is that it is very often re-active, sporadic and impromptu. Therefore it is imperative that the application used to log these interactions is always “at one’s fingertips” so to speak. Given that users keep Outlook open all day so as to respond timeously to e-mail ensures that this is the case.
c) Familiar Interface: If users are already utilising Outlook for at least e-mail and calendaring then they are already familiar with the interface and how to add new items, edit existing items, etc. Thus there is usually very little requirement for extensive training when an Outlook system is deployed. This dramatically shortens the average implementation time.
d) Increasing Percentage of E-Mail Interaction: An ever-increasing number of users are discovering the advantages of e-mail communication over other forms of contact (phone, fax, letter, etc.). So as e-mail becomes more widely used for customer interaction, it makes sense to deploy your e-mail client as the primary vehicle for managing customer communications, rather then utilising a totally different application.
e) One calendaring system universal across company & supply chain: Given that the vast majority of corporate users are utilising Outlook, it is easy for instance to send meeting requests to suppliers or customers, who can then use many of the same collaboration features that are available to internal users/co-workers. Many CRM systems have their own calendaring system and given that not all users will (or can) necessarily adopt this system means that one has to immediately contend with the problem of keeping these dissimilar calendars synchronized so that all users can effectively co-ordinate their diaries.
f) One e-mail store: Many of the conventional database-based CRM systems on the market have difficulty linking to e-mails given that an e-mail is not the same type of object as say a document. For this reason most systems not running inside Outlook tend to copy the contents of an e-mail into their database tables, thereby effectively duplicating the data and also disconnecting it from its original item, thus losing its formatting and also making handling of “Replies” and “Forwards” to the item difficult.
g) One document management system: Some CRM systems also copy documents into their database so as to enable replication of these documents to remote users. The disadvantage of this approach is that a document can only be edited from within the CRM system and not also from its original source on the Windows File System or Exchange Public Folder in the way that most users would already be familiar with.
h) Easy synchronization with most PDA’s: Given that all PDA’s synchronize with Outlook as a standard, this means that you have automatic access to your Contact Management data if it is kept in Outlook rather than being in another application.
Reduced Cost of Ownership:
i) No additional Infrastructure Needed: If a company already has the infrastructure in place necessary to run Outlook on client machines and Exchange Server, then no additional client or server hardware is needed to run an Outlook-based system.
j) Cost of upgrade to new versions of Outlook shared: Very often a client has to justify the costs of upgrading Office as well as the costs of purchasing the CRM application. With an Outlook-based solution this upgrade cost is shared given that the company receives a whole host of additional benefits and functionality from upgrading Office/Outlook as well as receiving a new CRM system.
k) Reduced Training Time (Cost): Given that users will already be familiar with the basics of Outlook, the time needed to train users, and hence the cost of that training, is significantly reduced.
l) Wider Support Base: Given that there are a large number of internal users and external consultants that know Outlook and VBA/VBScript (used to extend its functionality) it is easier and therefore less costly to enhance the functionality and support your user base.
m) Wider application of same training: If a company invests in training its staff in the functionality of Outlook, so as to more effectively use a CRM system based on Outlook, then this knowledge of Outlook will be utilised in everything a user does in Outlook, even those activities not linked to customer management but more internal collaboration etc. However, when one invests in training around a separate proprietary system then this training can only be applied to the use of that system and nothing else.
n) Reduced Installation Time: Given that an Outlook-based system installs itself inside Outlook, it is a simple matter for IT personnel to install the system. In many instances this can be done by the user him or herself.
9 Summary
Microsoft’s earlier promotion of Outlook as a “Personal Information Manager” created the impression amongst users that Outlook was only intended to manage one’s personal contacts and was not suited as the basis for a corporate-wide Customer Management System. Hopefully this article has rectified some of these misconceptions and shown that, given that so much of one’s day-to-day customer interaction is initiated from within Outlook, Outlook coupled with Exchange or SQL Server is the perfect environment for one’s all important Customer database. For an example of an Outlook-based CRM system, please have a look at MX-Contact (http://www.mxcontact.com). A free version is available for download from http://www.free-contact-manager.com.
10 PDF Version
A PDF version of this article may be downloaded from:
http://www.outlookwise.com/OutlookWise/Why_CRM_Projects_Fail/01_Why_CRM_Projects_Fail.htm
11 About the author
This article was written by Brian Drury, founder of ExchangeWise (http://www.exchangewise.com), and the architect of MX-Contact (http://www.mxcontact.com), a CRM, Contact Management and Sales Automation System for Microsoft Outlook. Brian has over 20 years experience in the IT industry and has focused on Contact Management, CRM and Collaboration systems for the last 14 years. During this time Brian and his staff have been involved in over 200 direct CRM project implementations covering 7 different products. He is also the editor of OutlookWise(http://www.outlookwise.com), a free newsletter aimed at keeping Outlook users up to date with news, views and articles of interest on Microsoft Outlook and Exchange Server.
How to Manage a Project
Project management is the application of knowledge, skills, tools and techniques to project activities to meet project requirements. Project management is a specialized management technique to plan and control projects. A project is generally deemed successful if it meets pre-determined targets set by the client, performs the job it was intended to do, or solves an identified problem within the pre-determined time, costs and quality constraints.
To successfully manage a project there are various tasks that must be performed. A few of such tasks includes:
1.Appointing a Project Manager
The project manager must be someone who has a proven track record in managing; can command respect from a mix of seniorities and can get action from teams. They should be able to:
* plan and communicate all aspects of the project
* motivate with integrity, sensitivity and imagination
* gain productivity and trust from shared decision-making
* lead both by example and by taking a back seat when appropriate
* monitor costs, efficiency and quality without excessive bureaucracy
* get things done right first time without being a slave-driver
* get the right people for the right task at the right time
* use both technical and general management skills to control the project
* see clear-sightedly through tangled issues.
2.Define the objectives
Fundamental to the management of any successful project are both understanding and agreement of:
* what is required to be achieved
* what is to be the outcome and/or delivered as a result
* dates and budgets for project completion by both project sponsor and project manager.
Lack of clear objectives will doom the project from the beginning.
3. Establish the Terms of Reference
The Terms of Reference specify the objectives, scope, time-frames and initial scale of resource required. They should also clarify any risks, constraints or assumptions already identified. It is important to make any early allowances for cost escalation, plans veering off course, and build in a level of contingency, or safety margin.
4. Planning/ Construct the Work Breakdown Structure Document (WBSD)/
Having established what the project should achieve, next consider how to achieve it.
The WBSD forms the basis of much subsequent work in planning, setting budgets, exercising control and assigning responsibilities. The key is to break the project down into identifiable phases, then into controllable units for action. Dividing a piece of work into more approachable, discrete units facilitates the functions of estimating, planning and controlling. As soon as possible allocate time- scales to each unit of work, taking care to allow for both sequential units - those that need to be accomplished before the next can be tackled, and overlapping units - those that can run in tandem.
5. Plan costs
A key area in which the most frequent error is to under-estimate costs. Typical cost elements include:
* staff time and wages - usually the most substantial cost item of all
* overheads - employer on-costs
* materials and supplies - the raw materials
* equipment
* administration
6. Plan for quality
Planning for quality requires both attention to detail and ensuring that the project output or outcome does what it is supposed to, or is "fit for its purpose". Quality measures (systematic inspections against established standards) should be built into the process from the beginning, not later when things have started to go awry.
7. Plan time-scales
In order to calculate the shortest time necessary to complete the project you need to know:
* the earliest time a stage or unit can start
* the duration of each stage
* the latest time by which a stage must be completed.
* Gantt charts, PERT diagrams and Critical Path Analysis may be used for effective planning of time-scales.
8. Plan Scope, Integration, Human Resources, Communication, Procurement and Risk
9. Monitor & Report Progress
The monitoring of in-progress costs, time-scales and quality is a major factor for consideration throughout the duration of the project. In addition to progress reports, feedback sessions and Management By Walking About, there are various control tools which help check that implementation is going according to plan.
10. Execution, Execution
Deliver the output. Obtain the client's acceptance of the project result". The penultimate stage before project completion is ensuring that the outcome of the project is accepted by the customer or sponsor.
11. Evaluate the project and Lessons learnt
By building in a final stage of evaluation it is possible to gain a measure of the project's success and see what lessons can be learned. Once again, the three key areas for review are quality, time and costs. Others include:
* staff skills gained or identified
* mistakes not to be repeated and what would be tackled differently.
* tools and techniques that were valuable
* processes that were flawed
--
By Samuel Lartey, Project Manager.
To successfully manage a project there are various tasks that must be performed. A few of such tasks includes:
1.Appointing a Project Manager
The project manager must be someone who has a proven track record in managing; can command respect from a mix of seniorities and can get action from teams. They should be able to:
* plan and communicate all aspects of the project
* motivate with integrity, sensitivity and imagination
* gain productivity and trust from shared decision-making
* lead both by example and by taking a back seat when appropriate
* monitor costs, efficiency and quality without excessive bureaucracy
* get things done right first time without being a slave-driver
* get the right people for the right task at the right time
* use both technical and general management skills to control the project
* see clear-sightedly through tangled issues.
2.Define the objectives
Fundamental to the management of any successful project are both understanding and agreement of:
* what is required to be achieved
* what is to be the outcome and/or delivered as a result
* dates and budgets for project completion by both project sponsor and project manager.
Lack of clear objectives will doom the project from the beginning.
3. Establish the Terms of Reference
The Terms of Reference specify the objectives, scope, time-frames and initial scale of resource required. They should also clarify any risks, constraints or assumptions already identified. It is important to make any early allowances for cost escalation, plans veering off course, and build in a level of contingency, or safety margin.
4. Planning/ Construct the Work Breakdown Structure Document (WBSD)/
Having established what the project should achieve, next consider how to achieve it.
The WBSD forms the basis of much subsequent work in planning, setting budgets, exercising control and assigning responsibilities. The key is to break the project down into identifiable phases, then into controllable units for action. Dividing a piece of work into more approachable, discrete units facilitates the functions of estimating, planning and controlling. As soon as possible allocate time- scales to each unit of work, taking care to allow for both sequential units - those that need to be accomplished before the next can be tackled, and overlapping units - those that can run in tandem.
5. Plan costs
A key area in which the most frequent error is to under-estimate costs. Typical cost elements include:
* staff time and wages - usually the most substantial cost item of all
* overheads - employer on-costs
* materials and supplies - the raw materials
* equipment
* administration
6. Plan for quality
Planning for quality requires both attention to detail and ensuring that the project output or outcome does what it is supposed to, or is "fit for its purpose". Quality measures (systematic inspections against established standards) should be built into the process from the beginning, not later when things have started to go awry.
7. Plan time-scales
In order to calculate the shortest time necessary to complete the project you need to know:
* the earliest time a stage or unit can start
* the duration of each stage
* the latest time by which a stage must be completed.
* Gantt charts, PERT diagrams and Critical Path Analysis may be used for effective planning of time-scales.
8. Plan Scope, Integration, Human Resources, Communication, Procurement and Risk
9. Monitor & Report Progress
The monitoring of in-progress costs, time-scales and quality is a major factor for consideration throughout the duration of the project. In addition to progress reports, feedback sessions and Management By Walking About, there are various control tools which help check that implementation is going according to plan.
10. Execution, Execution
Deliver the output. Obtain the client's acceptance of the project result". The penultimate stage before project completion is ensuring that the outcome of the project is accepted by the customer or sponsor.
11. Evaluate the project and Lessons learnt
By building in a final stage of evaluation it is possible to gain a measure of the project's success and see what lessons can be learned. Once again, the three key areas for review are quality, time and costs. Others include:
* staff skills gained or identified
* mistakes not to be repeated and what would be tackled differently.
* tools and techniques that were valuable
* processes that were flawed
--
By Samuel Lartey, Project Manager.
Middleware Message and Identity Management
CIO Enterprise Identity Project Approaches
The Enterprise Identity Management project is all about automating business processes and synchronizing identity-related information across the enterprise.
Why do we need Identity Management?
Identity management is necessary to support a strong and flexibly security framework. Most system and data vulnerabilities come from improperly managed rights and entitlements. Many companies do not have the necessary identity-related security implementations to adequately control access to services, devices, applications, and data. Properly securing an enterprise today means implementing automated processes and procedures for granting and revoking access to company resources. Intelligent identity management implementation will provide staff with the means to control, enforce, and monitor access to company resources. Additional benefits include access to monitoring and providing a proof of compliance to Sarbanes-Oxley auditors.
Identity Related Access
Control of employee, supplier, and partner access can be far from perfect. Terminated contractors and employees may have access to company resources long after they have officially left the company. Access credentials that employees and contractors need in order to perform their normal tasks are frequently so numerous that they write down their access codes and store them in or near their workspace. Securing the enterprise means providing a process or framework to synchronize employee, supplier, and partner identities across all systems. An intelligent identity management system provides the means to achieve a high degree of security and a secure trust level while allowing employees, suppliers, and business partners to access company resources.
Best Approach to Identity Management
The best approach for an intelligent identity management framework is an open system approach, which uses standardized, readily available commercial components. The open system approach creates an environment that is adaptable and enables the company to respond quickly to rapidly changing business environments. The approach also provides a framework in which individual components can be replaced, maintained, or upgraded on demand with minimal or no impact to the overall system. Additional benefits are achieved by reducing reliance on any one vendor or technology, and this provides a buffer against technological change and vendor consolidation. This approach allows the framework and methodology to reduce the risk associated with implementing or changing components.
Implementation Methodologies
Considering the required cost and complexity of integrating identity repositories in the enterprise, an open flexible system that reuses readily available components is an ideal solution to a very complex problem. Identity-related processes require communication between technologically diverse identity repositories, applications, and processes. Each application and identity repository is designed for a specific purpose and not necessarily designed to integrate with other solutions. However, achieving the desired goal of integrating these technologically diverse repositories with ongoing business processes is a difficult and complex issue. The ideal solution is to integrate the applications, identity repository, and business process by using a common, robust, and scalable transport to exchange information. Enabling applications, a legacy system, and a business process to exchange information in a common and reliable manner is a necessity to meet long-term business needs. This technology must provide for guaranteed data delivery, regardless of network changes or outages, and it must also provide a level of abstraction from diverse identity repositories and processes.
Service Oriented Architectures (SOA)
With the increasing acceptance and reliance on SOA (Service-Oriented Architectures), Web Services, Middleware Messaging, and Database solutions, these items are being adopted in many enterprises and are becoming a common component of numerous business enterprises.
Web Services?
The loosely coupled nature of Web Services provides a flexible, component-based, open, extensible, and reusable solution. Web services also enable platform and application-independent communication methods of exchanging information over HTTP. However, if there are unexpected network connectivity issues, does the client have a mechanism to guarantee that any and all data will be delivered to the Web service? No matter how good your network is, there will always be a chance that critical data can be lost owing to a variety of reasons. Web services by themselves cannot provide the necessary guaranteed data delivery service that is required for today's demanding business environments. On their own, Web Services have no standardized mechanism to provide a guaranteed data delivery service when network outages occur unless the application is specifically designed and developed with a guaranteed data delivery mechanism.
Why Not Database Replication?
Data exchange can also be achieved by using database replication. The client can insert data into a local operational database and it can eventually be replicated to the central subscriber. In this case, application communication requires a local database on every server a replication mechanism that has either been developed or bought will provide the delivery mechanism. This may not be the best solution, as it requires extra effort to configure, maintain, and monitor. These extras are already provided by middleware messaging products.
Middleware Messaging Transport Service
The middleware messaging transport service provides a layer of abstraction between the application, identity repositories, and business process. It also provides the necessary guaranteed data delivery service that is so crucial in today's enterprise environments. The middleware messaging provides the ideal environment to enable open, extensible, and flexible identity management solutions. It also provides the necessary abstracted environment for exchanging information between identity repositories, processes, and applications, as well as providing an effective integration for outside vendors and suppliers. The most open extensible and scalable method to exchange information is middleware oriented messaging.
Middleware vendors
Several of the more popular middleware vendors are listed below.
IBM's WebSphereMQ http://www-306.ibm.com/software/integration/wmq/
Tibco Rendezvous http://www.tibco.com/software/enterprise_backbone/rendezvous.jsp
SonicMQ http://www.sonicsoftware.com/index.ssp
Microsoft MSMQ http://www.microsoft.com/windowsserver2003/technologies/msmq/default.mspx
Conclusion
The middleware messaging transport service provides the necessary support infrastructure that enables integration teams to focus on business logic rather than on the development of custom solutions or components. The abstracted environment also provides the ideal environment to build effective, open, and extensible identity management solutions.For more information on how to use middleware messaging to support your identity management initiatives, please visit http://www.eaisimsolutions.com
The Enterprise Identity Management project is all about automating business processes and synchronizing identity-related information across the enterprise.
Why do we need Identity Management?
Identity management is necessary to support a strong and flexibly security framework. Most system and data vulnerabilities come from improperly managed rights and entitlements. Many companies do not have the necessary identity-related security implementations to adequately control access to services, devices, applications, and data. Properly securing an enterprise today means implementing automated processes and procedures for granting and revoking access to company resources. Intelligent identity management implementation will provide staff with the means to control, enforce, and monitor access to company resources. Additional benefits include access to monitoring and providing a proof of compliance to Sarbanes-Oxley auditors.
Identity Related Access
Control of employee, supplier, and partner access can be far from perfect. Terminated contractors and employees may have access to company resources long after they have officially left the company. Access credentials that employees and contractors need in order to perform their normal tasks are frequently so numerous that they write down their access codes and store them in or near their workspace. Securing the enterprise means providing a process or framework to synchronize employee, supplier, and partner identities across all systems. An intelligent identity management system provides the means to achieve a high degree of security and a secure trust level while allowing employees, suppliers, and business partners to access company resources.
Best Approach to Identity Management
The best approach for an intelligent identity management framework is an open system approach, which uses standardized, readily available commercial components. The open system approach creates an environment that is adaptable and enables the company to respond quickly to rapidly changing business environments. The approach also provides a framework in which individual components can be replaced, maintained, or upgraded on demand with minimal or no impact to the overall system. Additional benefits are achieved by reducing reliance on any one vendor or technology, and this provides a buffer against technological change and vendor consolidation. This approach allows the framework and methodology to reduce the risk associated with implementing or changing components.
Implementation Methodologies
Considering the required cost and complexity of integrating identity repositories in the enterprise, an open flexible system that reuses readily available components is an ideal solution to a very complex problem. Identity-related processes require communication between technologically diverse identity repositories, applications, and processes. Each application and identity repository is designed for a specific purpose and not necessarily designed to integrate with other solutions. However, achieving the desired goal of integrating these technologically diverse repositories with ongoing business processes is a difficult and complex issue. The ideal solution is to integrate the applications, identity repository, and business process by using a common, robust, and scalable transport to exchange information. Enabling applications, a legacy system, and a business process to exchange information in a common and reliable manner is a necessity to meet long-term business needs. This technology must provide for guaranteed data delivery, regardless of network changes or outages, and it must also provide a level of abstraction from diverse identity repositories and processes.
Service Oriented Architectures (SOA)
With the increasing acceptance and reliance on SOA (Service-Oriented Architectures), Web Services, Middleware Messaging, and Database solutions, these items are being adopted in many enterprises and are becoming a common component of numerous business enterprises.
Web Services?
The loosely coupled nature of Web Services provides a flexible, component-based, open, extensible, and reusable solution. Web services also enable platform and application-independent communication methods of exchanging information over HTTP. However, if there are unexpected network connectivity issues, does the client have a mechanism to guarantee that any and all data will be delivered to the Web service? No matter how good your network is, there will always be a chance that critical data can be lost owing to a variety of reasons. Web services by themselves cannot provide the necessary guaranteed data delivery service that is required for today's demanding business environments. On their own, Web Services have no standardized mechanism to provide a guaranteed data delivery service when network outages occur unless the application is specifically designed and developed with a guaranteed data delivery mechanism.
Why Not Database Replication?
Data exchange can also be achieved by using database replication. The client can insert data into a local operational database and it can eventually be replicated to the central subscriber. In this case, application communication requires a local database on every server a replication mechanism that has either been developed or bought will provide the delivery mechanism. This may not be the best solution, as it requires extra effort to configure, maintain, and monitor. These extras are already provided by middleware messaging products.
Middleware Messaging Transport Service
The middleware messaging transport service provides a layer of abstraction between the application, identity repositories, and business process. It also provides the necessary guaranteed data delivery service that is so crucial in today's enterprise environments. The middleware messaging provides the ideal environment to enable open, extensible, and flexible identity management solutions. It also provides the necessary abstracted environment for exchanging information between identity repositories, processes, and applications, as well as providing an effective integration for outside vendors and suppliers. The most open extensible and scalable method to exchange information is middleware oriented messaging.
Middleware vendors
Several of the more popular middleware vendors are listed below.
IBM's WebSphereMQ http://www-306.ibm.com/software/integration/wmq/
Tibco Rendezvous http://www.tibco.com/software/enterprise_backbone/rendezvous.jsp
SonicMQ http://www.sonicsoftware.com/index.ssp
Microsoft MSMQ http://www.microsoft.com/windowsserver2003/technologies/msmq/default.mspx
Conclusion
The middleware messaging transport service provides the necessary support infrastructure that enables integration teams to focus on business logic rather than on the development of custom solutions or components. The abstracted environment also provides the ideal environment to build effective, open, and extensible identity management solutions.For more information on how to use middleware messaging to support your identity management initiatives, please visit http://www.eaisimsolutions.com
Why Every Company Needs A Fax Server
Every day more and more businesses of all sizes and types are developing or refining their strategy to transmit, store and retrieve their business documents electronically. And while the majority of all electronic document transmission is primarily conducted via email, or downloaded from the internet, smart organizations realize a critical part of this strategy also involves the handling of their inbound and outbound fax traffic.
Every company needs a fax server for the following reasons:
- Competitive necessity. The faster business documents transmitted by fax, either sent or received, reach the proper destination the higher probability of increased organizational efficiency.
- Increase employee productivity. Fax Servers allow users to send/receive faxes from their computers without leaving their desks. These faxes can be sent either from thin, thick or internet based fax client (Microsoft Internet Explorer) or email application such as MS Outlook/Exchange, Lotus Notes, Novell Groupwise. The most common operating systems used are Microsoft Windows XP and Microsoft Windows 2000.
- Minimize consumable costs such as paper, toner. The typical fax transaction first requires the document to be printed to a printer and delivered to a fax machine via sneaker net. Documents that are transmitted via fax server start electronically as word processing documents and end electronically as digital images at the recipients’ destination.
- Documents transmitted via fax server are recognized as legal documents in a court of law. Once a document has been transmitted by fax, information about the fax transmission is recorded during the process, including date/time of transaction, duration and total # of pages.
- Improve Customer Relationships and Find New Opportunities. Fax documents are always read or at least perused. If the information on the fax properly addressed to a particular recipient or addresses an immediate business need, there is a good probability of some sort of response. Many fax savvy organizations use fax for newsletters, press releases, billing, product announcements and expedited contract delivery.
Try the following: Go into your existing customer database and choose an existing client. Send a fax concerning a new product release or update directly to his or her attention. In addition, within the fax, provide multiple methods of return correspondence i.e. email, website, telephone and a deadline for response. Chances are you will receive some level of response faster than email!
- Email Alternative. While sending emails is extremely reliable and common practice, it has its draw backs when dealing with loan applications, purchase orders and signed contracts. Business conducted with these types of documents typically occurs via fax machine or fax server.
Fax Servers compliment all business units in one form or another. They convert documents from their native format into Black and White Tiff G3 or DCX format. These tiff documents are then sent over the PSTN (Public Switched Telephone Network) or IP (Internet Protocol). Fax Servers can integrate into any application, Email system, ERP, CRM or operating system in the world. They can interrogate raw text from any AS400 or Host based output system and convert it into a legible formatted document (either PDF or Tiff). Some Fax Servers can also send email, act as middleware, fax enable websites, operate as a back office application or be used in an ASP service bureau model.
Summary
Fax Server technology has been around since the late 1980’s. Even though all fax servers are not created equal, there are fax servers available for every platform i.e. Microsoft Windows, Unix, Linux. The most reliable fax servers primarily support intelligent fax cards such as Brooktrout, Eicon, Pika Technologies or Natural Microsystems. Depending on your organizations needs, infrastructure and budget, there is a fax server solution out there for you. If you are entire organization is sending or receiving more than 20 pages of fax per day, ROI cost justification can be 3 months or less.
Document Imaging - Chris Norwood has been in this industry for over 13 years and is currently the Business Development Manager for One Touch Global Technologies. One Touch Global Technologies is a Platinum Solution Provider, Specialized Software Developer and Systems Integrator for several of the leading fax server and document management technologies on the market. Chris may be reached directly at cnorwood@otgt.com.
Subscribe to:
Posts
(
Atom
)
Popular Posts
-
Perfumes and fragrances have been used by many cultures over centuries with one goal in mind: to incorporate fascinating scents that smell r...
-
There is no doubting the fact that women have an ongoing love affair with luxury handbags. Purse blogs or e-magazines and comments on purse ... -
When it comes to designer handbags, many people think one expensive bag as just like any other expensive bag. This article gives advice on h...
-
Just about everyone who is in touch with the pricey world of high end fashion knows that any purse created by a well-know fashion guru is go...
-
How much is too much to spend on a designer hand bag? An Hermes' Birkin just sold at auction for more than $80,000. Is that too much to ...
-
If you hate to shop then you most likely run out of steam after finding the clothes - accessories seem way too overwhelming to consider. The...
-
Fashion is a concept that changes as often as the seasons and to most women, keeping up with the latest trends is a must! Knowing what'...
-
Shopping online can be scary, especially for clothing and dresses for women, as items usually look completely different once they're put...
-
Wholesale prices are the greatest thing that can happen to those who have a passion for designer handbags . You will find a large variety of... -
When wanting a replica bag, much research has to be done. There are about 90% crappy bag sites versus about 10% that have great quality repl...