Influence & Trust
The ethical use of persuasion science, and the trust math that makes technical advice actually land.
Cialdini's principles, used honestly
Robert Cialdini's seven principles of influence are widely taught in sales — and widely abused. Used with integrity, in a role whose entire value proposition is trustworthiness, they're simply good practice:
| Principle | Legitimate pre‑sales use |
|---|---|
| Reciprocity | Give real value first — a sharp diagnostic, a useful benchmark, an honest "you don't need this module" — before asking for anything |
| Commitment & consistency | Get small, specific agreements at each stage ("if we can show X, is that a blocker removed?") so the final decision is consistent with steps already taken |
| Social proof | Relevant reference customers — same industry, same scale, same problem — not just logos |
| Liking | Genuine rapport and specificity about their world beats generic charm; people buy from those who clearly understand them |
| Authority | Earned through demonstrated expertise in the discovery call itself, not claimed via job title |
| Scarcity | Use only when true (a real capacity or pricing constraint) — fabricated urgency is the fastest way to burn trust with a technical buyer |
| Unity | Frame the vendor and customer as one team solving a shared problem ("here's how we'd tackle this together"), not a seller and a target |
The trust equation
David Maister's trust formula gives a practical model for what "trusted advisor" actually means:
The equation's most useful insight for pre‑sales: self‑orientation divides, it doesn't subtract. A visible whiff of "I need this deal to close this quarter" doesn't just dent trust a little — it collapses it disproportionately, because it's in the denominator. Reliability is the cheapest of the three numerator terms to build (just follow up when you said you would) and the one most pre‑sales people under‑invest in.
Adapting to behavioural style
You will present the same solution differently to a CFO, a security architect, and a Head of Operations — not by changing the facts, but by changing what you lead with. A simple, durable model (DISC-style) for reading a stakeholder fast in the first ten minutes:
- Dominant / results‑driven: lead with the bottom line and the decision, not the journey to get there. Bring options, not open questions.
- Influential / relationship‑driven: lead with story, people impact, and vision before detail. Give them room to talk.
- Steady / process‑driven: lead with how the transition will be managed, not just the end state. Change itself is the risk they're evaluating.
- Conscientious / detail‑driven: lead with rigour — data, architecture diagrams, edge cases addressed proactively. Vague enthusiasm reads as a red flag to this stakeholder, not a green one.