B2b Trust Engineering

---
name: b2b-trust-engineering
description: "Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak."
category: engineering-core
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/LVTD-LLC/skills/skills/b2b-trust-engineering/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/LVTD-LLC/skills/skills/b2b-trust-engineering/SKILL.md
---


# B2B Trust Engineering

Use this skill when qualified buyers engage but do not take action. The goal is
to make the buying decision feel safe by reducing risk, increasing relevant
proof, and making next steps obvious.

## Source Traceability

Primary source: Unf*ck Your Sales by Jakob Greenfeld, especially the "Trust",
"Diagnostics", "The Confidence Fallacy", "The Persuasion Fallacy", "The Best
Option Fallacy", "The 7-11-4 Law", and "Engineering Trust" sections.

## Diagnostic Signals

Trust is likely the constraint when:

- Qualified buyers book calls, request proposals, or start trials but do not
  close.
- Prospects say the offer sounds good and then vanish.
- The buyer appears to need the outcome but still chooses an incumbent or no
  decision.
- The pitch relies on confidence, vision, or ROI claims without enough proof.
- The sales call tries to persuade instead of confirming what the buyer already
  believes.

## Trust Check

Review the last 50 qualified opportunities where possible:

- How many closed?
- How many ghosted after meaningful engagement?
- How many stalled after a proposal or trial?
- What proof did buyers see before the call?
- What risks, ambiguities, or next-step friction remained?

If qualified close rate is weak or ghosting is high after engagement, treat
trust as the likely constraint.

## Workflow

### 1. Lead With Relevant Proof

Use proof that matches the buyer's world:

- Case studies tied to the same pain.
- Testimonials with specifics.
- Screenshots, dashboards, or before/after evidence.
- Logos or references that reduce perceived risk.
- Third-party mentions, referrals, podcasts, or credible appearances.

### 2. Remove Hidden Risk

Audit friction:

- Can the buyer understand the offer quickly?
- Is pricing or scope ambiguous?
- Are next steps explicit?
- Is implementation risk addressed?
- Is the downside named and handled?

Anything ambiguous increases risk.

### 3. Build Layered Familiarity

Create trust across multiple surfaces before the call:

- One-to-one outreach.
- Case studies or proof drops.
- Helpful content.
- Video or Loom walkthroughs.
- Social posts or founder presence.
- Third-party channels where buyers can see independent signals.

Use 7 hours, 11 touchpoints, and 4 platforms as an exposure target, not as a
rigid law.

### 4. Design The Call To Confirm

Assume serious buyers arrive with a partial preference already formed.

On the call:

- Reflect the buyer's problem clearly.
- Map proof to their exact situation.
- Avoid over-explaining or adding complexity.
- Make the next step low-risk and obvious.
- Confirm decision criteria and approval path.

## Output Format

```markdown
# B2B Trust Plan

## Opportunity Pattern
- Qualified leads reviewed:
- Close rate:
- Ghost/stall pattern:
- Main risk signal:

## Proof Stack
| Buyer Fear | Proof Needed | Existing Asset | Gap |
|------------|--------------|----------------|-----|

## Risk Removal
- Offer clarity:
- Pricing/scope:
- Implementation:
- Next step:
- Approval path:

## Call Design
- Problem mirror:
- Proof to show:
- Risk to address:
- Next action:
```

## Quality Bar

- Do not try to close with confidence when proof is missing.
- Do not treat buyer hesitation as a persuasion problem before checking risk.
- Do not overload buyers with detail when simpler proof would reduce risk.
- Do not ignore approval path, career risk, or incumbent safety.
- Make "yes" feel safer before making the upside sound bigger.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/b2b-trust-engineering/SKILL.md`