ERP leads in B2B sales: turning change interest into a focused discovery call

An ERP discovery call is useful for your sales team when it clarifies the business problem you should address and the people who need to support the next step. A request for a quote provides a starting point. It does not replace checking whether your offer fits or jointly defining a project. Preparing a broad product presentation immediately can consume considerable consulting time without advancing the company’s actual decision. A focused conversation instead provides material for a relevant demonstration, a deliberate postponement or a reasoned decision not to proceed.

This article is for ERP vendors, implementation partners and consultancies handling business enquiries from Germany. It develops a completed discovery guide using a fictional trading company. Names, processes and answers are invented examples. The questions are recommendations for your sales team, not promises about fields delivered with a lead. The example moves from initial interest in changing systems to a concrete agreement for the next conversation. You can use its logic without pushing the customer into a predefined project or an immediate purchase. The purpose is to make the next decision better informed.

Separate known enquiry details from your open questions

The webRichtung ERP industry page describes enquiries containing process area, current system setup and planning stage, together with business location and contact details in Germany. These details help you choose a relevant opening. A company with an existing ERP needs a different introduction from a business trying to connect separate tools. Planning stage also gives direction. Initial research does not yet establish a fixed selection process, and implementation planning does not mean that your business already has an order. The information frames the conversation without deciding its outcome.

The target page also makes clear that user numbers, specific products and integrations are explored in conversation; it does not collect a completed requirements document. Do not fill the gaps with assumptions. “Trade” does not imply a particular warehouse structure, “existing ERP” does not identify an interface, and a named contact is not necessarily the final decision maker. Before responding, write down what was actually stated and what you still need to learn. This separation prevents a presentation whose central conditions exist only in your own planning notes.

In the example, the known starting point is a trading company with an existing ERP, preparing vendor selection. Mia is the contact at the fictional Havel Handel in Germany. Sales initially leaves open why change is being considered, which processes are affected and how selection will happen. The call objective is to identify a relevant business workflow and an appropriate clarification step. It is not yet to replace the entire system. This turns the enquiry into a focused consulting opportunity with a manageable preparation scope, instead of an invitation to demonstrate everything.

Explore ERP enquiries and their starting information, and register your business for relevant conversations in Germany.

Understand the trigger behind the wish to change

A useful opening is: “You are preparing to select an ERP provider. What has happened in daily work that made you look at this now?” In the fictional conversation, Mia replies: “Sales has to ask the warehouse before promising deliveries. We want to prepare a second warehouse location and understand how to get a reliable view in future.” The consultant now knows an operational trigger. They do not yet know whether the existing ERP is unsuitable, whether processes are missing or whether existing functions need to be used differently.

The next question makes the difficulty specific: “Could you describe a recent order where that extra check was necessary?” Mia explains that an item appeared to be in stock, but part of the quantity was already intended for another order. Sales had to phone the warehouse to establish what could be promised. This answer identifies an observable problem: availability relevant to a delivery commitment is unclear within the workflow. It provides neither a verified error rate nor a financial loss. Those figures remain unknown if the company cannot establish them from its own information.

The consultant then asks: “What should sales be able to see independently after an improvement?” Mia wants to see the quantity available for the specific order and when a partial quantity might be delivered. The consultant reflects back: “We will first examine a traceable delivery commitment for one customer order, including quantities already allocated elsewhere.” Mia confirms that scope. The potential second location remains a reason for planning, while its implementation date and required functions are still unclear. A future expansion therefore does not accidentally become a current mandatory requirement.

Clarify participation and decisions without assuming roles

Ask about the work involved in deciding: “Who needs to judge whether this process fits operationally, and who decides on the wider project?” That is more useful than asking only whether Mia is the decision maker. In this example, Mia coordinates business requirements. Aron is responsible for the warehouse, Jonas assesses IT matters, and managing director Selin decides on the investment. These roles are stated during the conversation. Your team should not infer them from job titles or company size. Responsibility here comes from a confirmed answer that can guide the next discussion.

The consultant continues: “What question does each person need answered before selecting a provider?” Mia identifies reserved quantities and partial deliveries for Aron. Jonas needs to establish which current systems and data would be affected. Selin needs a reasoned assessment of benefit, effort and implementation risks. A later meeting now has an operational purpose. Not everyone necessarily needs to attend every conversation. What matters is that the current question reaches the appropriate person and that their conclusion contributes to the wider decision, instead of being lost in a general demonstration.

Budget and timing can also be explored respectfully: “Is there an approved budget already, or will that be developed once the scope is clearer?” Mia says that no budget has been approved. The company first wants to understand the affected workflow and then define the selection scope. Sales records exactly that position. It invents neither an investment amount nor a closing month. The enquiry remains worth working on, but the conversation does not yet justify preparing an extensive individual proposal. The next investment of consulting time should match what has actually been established.

Develop a use case instead of a general product show

The business problem leads to a preparation question: “Which simple order could we walk through together so that you can judge the requirements?” Mia suggests an order for ten units of one item. Six should be supplied from available quantity; the delivery path for the other four needs clarification. These numbers belong to the fictional illustration, rather than a real company’s stock. The consultant agrees to use the example to examine operational expectations. The aim is not to present a complete company configuration before those expectations are understood.

The prepared case starts when the customer order arrives. Sales should be able to see what quantity can actually be promised for that order. The possible first delivery of six units is then examined. The remaining four stay visibly open and must not disappear behind an order screen that looks complete. Finally, it should be clear who will establish the next delivery status and what the customer can be told. Ten ordered units thus remain six in the first delivery and four outstanding. No new delivery deadline is invented to make the example appear finished.

For the demonstration, the consultant asks Aron for a simplified description of the workflow that the company has approved for use in the meeting. Jonas should identify which current data sources matter. Real customer data or a full export is not automatically needed for this initial operational clarification. The provider checks internally what its own solution can actually demonstrate and which points require further investigation. This guide claims no ERP functionality for webRichtung. webRichtung provides access to the enquiry; your company evaluates and presents its own software and implementation offer.

Make the boundary between fit and open investigation visible

A useful question about the demonstration is: “How would you recognise that this workflow answers your question?” Mia needs the first delivery commitment to follow from an understandable situation. Aron wants to find the outstanding quantity. Jonas needs clarity about which data source was merely represented for demonstration and which connection remains to be checked. These criteria let your team limit preparation deliberately. A successful demonstration then means that a defined case has been understood. It does not establish suitability for every process in the company or resolve the whole implementation plan.

Suppose your team can show the standard case but has not assessed the connection to the existing system. Make that visible in the summary: “Business workflow prepared; technical connection open, to be reviewed next by Jonas and our responsible specialist.” This is more useful for a decision than a blanket claim that integration is possible. It connects uncertainty with responsible people. Unknown effort must not disappear inside a binding implementation promise simply because the interface looks convincing in a meeting. A clear open question is something the next step can resolve.

If the central requirement lies outside your offer, that is also a useful result. Explain which necessary workflow does not fit your confirmed scope. If only an additional question remains, agree a limited investigation. If the need is still unclear, continue defining it together. These different situations call for different next steps. Your sales team gains a reasoned work decision and spends consulting time where specific uncertainty can actually be reduced. Progress is measured by what has become clearer, rather than by keeping every enquiry moving towards a proposal regardless of fit.

End with an agreement someone can use

In the example, the consultant proposes: “We will prepare the order with ten units, a first delivery of six and four remaining open. Mia and Aron will review the operational workflow, while Jonas checks the relevant data sources. Could we discuss this together next Tuesday at ten?” Mia confirms the appointment and participants in the fictional conversation. Only that confirmation turns a suggestion into an agreement. If she still needed to ask the others, the meeting would be recorded as proposed. A preferred next step remains distinct from a confirmed one.

The completed conversation note reads: “Havel Handel is considering an ERP change because sales must ask the warehouse before committing delivery. First, we will examine a customer order with a partial delivery and an outstanding quantity. Mia coordinates, Aron reviews warehouse operations, and Jonas clarifies data sources. Selin will decide on investment later. Budget and implementation date remain open. Next agreed step: use case meeting Tuesday at ten; provider prepares the presentation, customer team the simplified workflow description.” A colleague can take over without mistaking general interest for a fully defined project.

The follow-up also records what is deliberately outside the next meeting. In this example, the full second warehouse is not yet being planned, and no complete migration is promised. Participants first examine the delivery commitment described. Send a summary using the communication route agreed with the contact and allow misunderstandings to be corrected. Its value lies in shared understanding. Perfect internal notes help little if the prospect expects something entirely different from the next appointment. Check that the agreed preparation really supports the same question on both sides.

Plan acquisition across several decision steps

An ERP project may still require operational review, internal agreement and a budget decision after a good first call. Plan these steps from the actual case instead of assuming a standard duration. Havel Handel has agreed the next operational discussion, while the investment decision remains open. Sales should track those facts separately. An appointment in a calendar is not an incoming order. Equally, an open budget is not automatically a final rejection while a concrete clarification step is jointly wanted. The recorded state should show both the progress and its limits.

Capacity planning includes existing preparation and follow-up commitments alongside new discovery calls. A consultancy that accepts every new enquiry but fails to prepare promised use cases loses the benefit of good opening conversations. Before planning further lead orders, review the time genuinely available for responses, specialist preparation and later meetings. Do not substitute an invented closing rate for this work plan. Economic evaluation can later combine actual acquisition costs, internal effort and real project outcomes. This guide promises neither prices nor a particular number of sales, and a busy calendar alone does not establish commercial success.

Follow-up also needs a reason. If Mia must first clarify data sources internally, agree a response connected to that result. If the initiative has no next step, mark it as unresolved or postponed instead of keeping it indefinitely as an imminent sale. If the company returns later, use the recorded position but check whether it is still current. The consulting process can then resume coherently without treating an old statement as present approval or unchanged buying interest. Useful continuity depends on updating the facts, not simply preserving the history.

Align enquiry purchasing with your consulting capacity

The current ERP offer page allows regional targeting within Germany or nationwide coverage in Germany. Standard enquiries go to at most three providers; with exclusive delivery, only one provider receives the particular enquiry. Exclusivity describes that delivery and does not oblige the prospect to buy. The selectable monthly ceiling is not a guaranteed volume either. Use these settings to align your purchasing while your team remains responsible for the specific advice and further project development. The service area stays Germany, regardless of the language in which your team works.

The existing business registration route starts on the industry page. You can review the offer and access there; the current price is shown before placing a binding order. Prepare your first conversation internally beforehand: known starting point, a question about the trigger for change and a way to narrow down the relevant process. A new enquiry then has a responsible recipient and a concrete consulting objective. The next useful benefit arises when your team turns interest into a jointly understood use case and a reliable agreement on what happens next.

Review ERP enquiries from Germany and register your business to align lead purchasing with your consulting capacity.