Prepare ERP demos: assess one workflow together
Give your ERP demo a clear assessment task. Agree the workflow, participants and outcome so the presentation leads to a useful project step.
A useful ERP discovery conversation has identified a relevant workflow. The demo now needs to show whether your offer fits it. For ERP vendors and implementation partners serving Germany, a clear assessment task is valuable: participants should be better able to answer one concrete question afterwards. That gives preparation and subsequent project discussions a purpose.
Turn the conversation topic into a demo brief
Before sending the invitation, write one sentence your contact can confirm: “We will examine how an internal request becomes an approved purchase order.” Add where the case starts and what outcome should be visible at the end. Use a simplified example workflow that both sides understand.
Ask who can assess the workflow from daily experience and who decides the next project step. A large audience is not automatically better. Each participant should know which question they are there to answer. Check internally which parts your own solution can actually demonstrate.
Agree three assessment questions beforehand
Give the presentation a short, shared basis for discussion:
- Understanding: Can the responsible people explain the demonstrated workflow in relation to their work?
- Outstanding difference: Where does the example differ from the real business process?
- Next assessment: Which difference needs investigation before a further proposal?
The demo then avoids becoming a contest to show the most features. Present the agreed case coherently and pause briefly at relevant handovers. Ask for feedback on each step before moving to the next.
Capture new requests without losing the meeting
Example: During a purchase approval demonstration, the purchasing manager asks about an additional report. Your consultant records the question and checks whether it is essential to today’s assessment. If not, it remains a separate point for afterwards. First, the group finishes examining the agreed purchasing workflow.
For a function you have not prepared, explain what you can already show and what your team must investigate. An improvised integration promise does not help the buying decision. Data transfer, interfaces and implementation require professional assessment of the actual environment; the demo does not replace that work.
End with a shared understanding of the outcome
Summarise three states: demonstrated and understood, requiring professional assessment, and outside today’s scope. Ask participants for corrections. Assign a responsible person and concrete response to a decisive outstanding question instead of immediately arranging another broad presentation.
Reserve that specialist time when planning new enquiries. webRichtung provides ERP conversation opportunities from Germany; your team delivers the demo and project analysis. Register your company and prepare the lead order in webRichtung Customer. You see the current price before placing a binding order.
Frequently asked questions
How much should the first demo cover?
Enough to answer the agreed workflow question. Define the start and end of the case and collect other topics separately instead of expanding the whole project during the presentation.
What if an important department is missing?
Record which assessment remains outstanding as a result. Arrange the relevant response or a focused follow-up; agreement from those present does not replace the missing perspective.
Does a successful demo confirm integration?
No. Separate the demonstrated workflow from open questions about data, interfaces and implementation. Assign those to a separate professional assessment.