Demographic data : things like age, gender, position, experience Phone Number Database level, how does he or she contribute to a decision and of course contact information. Firmographic data : data about the company. How much Phone Number Database revenue or budget do they have? How many people work there? What industry are they in? Where are they active? And so forth. Technographic data : What tools are currently being used? 2. Standardize Phone Number Database the data policy Now that you know which data you want to collect, it is important to ensure that data quality is guaranteed.
Many companies have not made a Phone Number Database clear policy about this, which makes proliferation unavoidable. In order to take all interests into account, multiple stakeholders must be involved in the development and implementation of this policy. It is essential that (especially) sales and marketing clearly define what a 'lead' is. Such agreements Phone Number Database must be laid down with internal SLAs in order to create clarity and to optimize cooperation between all parties involved. More details about this including underlying Phone Number Database principles (including the demand waterfall of Sirius Decisions ) I have described in this article on LinkedIn .
Either way, make sure everyone Phone Number Database speaks the same language! Responsibility for the implementation of the policy In addition to clear agreements, a few people from different disciplines (for example sales, marketing and legal ) must also be given (and feel) responsibility for the implementation of the policy. Careful Phone Number Database consideration should also be given to who will have rights to modify data and how this will be monitored. If you look at the organization of data, marketing data (in general) must be housed in a Marketing Automation Platform (MAP) and sales data in a CRM.