From buying motive to sales action
10 minChoose the sales action from the buyer’s , not from your product’s feature list.
In plain words
Before you decide what to say in a sales conversation, ask why this buyer would act at all. Most buyers have one main reason: they want to feel safe (trust), they want the total cost to be clear (price), they want to see a result (benefit), or they want to keep working with people they know (relationship). Each reason calls for a different action from you, and a different kind of proof.
Why it matters
The whole day starts from the buyer's reason. A offered to a buyer who is worried about risk gives away and leaves the worry exactly where it was; later, the you choose for DigitalIT Solutions has to answer a reason too.
How to read the picture below
The four boxes on the left are the buying motives, and the boxes on the right are the strategy each one calls for. Click a motive: the panel underneath lists the proof that buyer looks for, and adds a note on how it looks in a German company.
Motive → strategy
Trust → Reduce the buyer’s risk
The proof this buyer looks for
- (Referenzkunden) in the same sector and size
- A paid phase () before the full contract
- Compliance proof: an certificate, a attestation for cloud services, a Art. 28 data-processing agreement (, AVV)
German B2B IT context. In a (mid-sized company) buying committee the and the data protection officer can each stop the deal, so the proof has to be on the table before they ask.
What this showsEvery motive keeps the same shape — a claim the buyer has to be able to check — but what counts as proof changes completely from row to row: trust needs an outside party to vouch (a reference, a pilot, a certificate); price needs the whole contract life made visible, not the headline number; benefit needs the buyer's own KPI, not the vendor's case study; relationship needs a named, stable person. A pitch built to prove one motive rarely helps with another.
- What it is. A starts from why this buyer would act, the buying , and derives the sales action and the proof from it. A feature-led pitch starts from what the product does and hopes the motive matches.
- Why it matters in long-cycle IT . The buyer carries the risk of a wrong choice personally: Bauer (1960) called this . Where risk aversion is the motive, the strategy is to build trust: references, a phase and compliance proof, exactly the things a security-minded committee can check.
- Trust is built, not asserted. Morgan & Hunt (1994) found that trust and commitment together carry a business relationship forward. Anderson, Narus & van Rossum (2006) add the value side: a states the points of difference the buyer will actually get.
How to decide when this comes up in the task
- Name the motive first (trust, price, benefit or relationship), then choose the action and the proof. If you cannot say which motive an action serves, it is a feature pitch.
- Match the action to the motive: trust → references, a and compliance proof; price → the total cost made visible; benefit → a in the buyer’s own figures; relationship → named, stable contacts and a review rhythm.
- An action aimed at a different motive spends effort without touching the reason. A discount answers the price motive only; offered against a trust or relationship motive it gives margin away and leaves the reason in place.
- A motive is inferred from evidence, and one observation is not evidence of a motive. State what you saw before you name what it means.