① DMP and DMU
In B2B business, the DMP and the DMU are key concepts that describe the purchasing decision process and the people involved in it. DMP stands for Decision Making Process, the procedure an organization follows when buying a product or service. It can have several stages, but generally includes problem recognition, information search, evaluation of alternatives, purchase decision, and post-purchase evaluation. In B2B settings, the DMP is complex and time-consuming, involving many stakeholders along with technical and economic factors to weigh. DMU stands for Decision Making Unit, meaning every individual or group that takes part in a B2B purchasing decision, and it largely overlaps with the buying center. The DMU is made up of people who play different roles in influencing the purchase, often including the Initiator, User, Buyer, Influencer, Decider, and Gatekeeper. Each DMU member has different perspectives and criteria for the decision, and their interests may conflict. Meeting their needs and expectations is the key to successful B2B marketing and sales strategy.
Let’s explore the DMP (Decision Making Process) and DMU (Decision Making Unit) from the perspective of a company that sells IT software solutions for data management and analytics to businesses.
• Identifying the Problem
This is the stage where the client recognizes that a problem or opportunity requires a decision. It is mainly about identifying the key challenges the client faces, such as difficulty integrating data, limited access to information, and data quality management.
• Gathering Information
This stage gathers the data and information you need to understand the problem or opportunity more clearly. Start by reviewing the client's current data management and analytics environment: the existing technology stack, data sources, processing workflows, and analysis tools.
• Analyzing the situation
In this stage, you evaluate the collected information to identify possible courses of action and their potential outcomes. Analyze the client's current situation based on the information gathered. This clarifies the customer's needs and requirements and identifies technical or operational constraints.
• Developing options
In this stage, the vendor generates possible solutions to the situation. Develop a range of solution options that can resolve the customer's problem or pain point. These may include features such as data integration, analytics, visualization, and reporting, and you can consider various deployment options, including cloud-based and on-premises solutions.
• Evaluating Alternatives
In this stage, you weigh the pros and cons of each option, including feasibility, risks, benefits, and alignment with goals and values. Apply a range of criteria to evaluate the options you developed, such as cost-efficiency, ease of implementation, user-friendliness, scalability, and security. Also confirm that each option fits the client's long-term business goals.
• Choosing the Best Alternative
In this stage, you select the most suitable option based on the evaluation. This usually happens in close consultation with the client: the vendor's sales representative proposes 3-5 alternatives and collects the client's feedback. Based on that feedback, the client makes the final decision.
• Implementing the Decision
Draft an implementation plan for the selected solution, with concrete step-by-step actions, including owners and deadlines. This process may include project management, user training, and technical support.
• Reviewing and learning from the outcome
In this stage, you evaluate the results of implementation, learn from the experience, and inform future decisions. Monitor the solution's performance and assess how well the goals were met. Use what you learn to drive continuous improvement and to draw insights that both clients and vendors can apply to similar cases in the future.
Let's work out the client's DMU (Decision Making Unit) from the standpoint of a company that provides IT software solutions for enterprise data management and analytics.
• Initiator
These are the people who recognize a problem in their own company and begin looking for a solution. They are often employees who first notice a technical issue or business challenge. In this case, the marketing team was struggling with customer data management and started looking for a solution to improve it. At the request of the marketing director, an assistant manager in the IT department begins searching for a suitable solution.
• User
These are the people who will use the IT software solution directly. Their feedback and requirements strongly influence which solution is chosen. The sales team and the customer service team are the main user groups who will use CRM software directly. They require the software to be easy to use and to provide the features they need.
• Buyer
These are the people who negotiate the purchase terms and sign the contract. A representative from the purchasing department may play this role, or the IT department may decide. Either way, they will negotiate price, delivery schedule, support, and maintenance terms with the software vendor.
• Influencer
These are the people who influence the purchase decision, and technical experts or consultants often play this role. They evaluate product specifications or service details and make recommendations. Technical experts in the IT department assess the software’s technical fit and integration potential.
• Decider
These are the people who make the final purchase decision. They are usually senior executives or the head of the relevant department. At a small company, the CEO may decide. The client's CEO, CFO, or CTO will make the final call, weighing cost-effectiveness and ROI.
• Gatekeeper
These are the people who control the flow of information. For example, an administrative assistant may decide what information reaches the decision maker. A CEO’s executive assistant, for instance, decides what information goes to the CEO and which meetings need to be set up. From the standpoint of users who will work directly with the IT software solution, if they believe automation puts their jobs at risk, they can become gatekeepers who actively obstruct this DMP (Decision Making Process).
A company that provides IT software solutions should tailor its information and messages to the needs and interests of each DMU member: technical details for the IT department, cost-efficiency data for executives. It should also develop and deliver a clear value proposition showing how the solution addresses each stakeholder's concerns from different angles, such as user-friendliness, technical stability, and cost savings. References showing how companies of similar size or industry have used the solution successfully build trust with decision makers and speed up the purchase decision. Sales and marketing teams should build individual relationships with each DMU member, listen directly to their needs, concerns, and pain points, and then work out solutions. Where possible, they should demonstrate real-world use cases of the software or offer hands-on trials, so users and influencers experience its value firsthand. This makes better results more likely.
To be continued