in-person-escalation-trigger

name	in-person-escalation-trigger
description	When a relationship is digital-only and reaching a ceiling (high stakes, slow trust accumulation, plateauing engagement), travel for one in-person meal. One hour of breaking bread beats unlimited email and Slack — and the ROI justifies the travel cost. Triggers when the next step would otherwise be "more digital touchpoints."
composition_level	atom
extraction-lens	principle
source_attribution	Moriki (Hivemind Library)
license	pending-consent
status	candidate

In-Person Escalation Trigger

When to use

• High-stakes relationship where digital touchpoints are hitting a ceiling
• Partnership negotiation that's been stuck on async exchanges for >2 weeks
• Client / partner you've engaged with for months but never met
• Pre-launch alignment with a critical stakeholder
• Whenever the default move is "another email" or "another video call"

When NOT to use

• Low-stakes relationships where digital is sufficient
• The other party is genuinely remote-only and resistant to IRL
• One-off transactional work without relationship continuity
• Cost of travel exceeds plausible relationship value

Core principle

Almost no one speaks badly of someone they've shared a meal with. No matter how much you build a relationship via email or Slack, it cannot match one hour of eating a real meal together. It is worth traveling for.

The skill's value is overcoming the default bias toward digital efficiency when the relationship has reached the limit of what digital can produce.

How to apply

Recognize the trigger

The relationship needs IRL escalation when:

• Digital touchpoints are increasing in number but not in trust
• The other party's responses are getting shorter, not longer
• Decision velocity is slowing despite alignment on substance
• You can't tell what the other party is actually thinking

Don't optimize the meal

The mistake is treating the meal as another business meeting. The value isn't the agenda — it's the unstructured hour where defenses come down.

Specific moves:

• Pick a place that's theirs (their home turf, their preferred restaurant) when possible
• Don't bring slides or agenda
• Talk about non-work topics for at least the first 20 minutes
• Be willing to listen more than talk

The travel ROI logic

The travel cost is almost always low compared to the relationship value being unlocked. Founder-level relationships, partner deals, and key client engagements are decided in person — not because of any single conversation, but because IRL signals commitment that digital cannot.

Anchor evidence

ETHCC × Rootstock CGO Ben (Moriki):

• Digital relationship was solid but plateauing
• One in-person meal during ETHCC
• Outcome: developed into long-term large deal + new client referral
• ROI: travel investment was a small fraction of the multi-year engagement value unlocked

Output format

When advising:

RELATIONSHIP STAGE: [digital-only / mixed / IRL-established]
DIGITAL CEILING SIGNALS:
- [specific evidence of digital plateau]

ESCALATION RECOMMENDATION:
- Should escalate to IRL: yes / no / wait
- If yes: target meeting type [coffee / meal / event / conference co-attendance]
- Travel cost estimate: [$X]
- Relationship value at stake: [$Y or strategic]
- ROI thesis: [why X << Y]

EXECUTION:
- Place selection (their turf if possible): [...]
- Non-work conversation budget: [first 20 min minimum]
- Topics to AVOID: [pitch, agenda, asks in first half]

Failure modes

• Treating the meal as a meeting. Bringing slides, agenda, asks. Defeats the purpose.
• Skipping it because "we're remote." Some of the highest-ROI engagements come from breaking the remote-only default.
• Going too soon. First-week-trust-deposit hasn't been completed yet; in-person without prior signal feels presumptuous.
• Going too late. The relationship has already calcified into pure transaction; IRL can't unlock what's already closed.
• Picking the wrong venue. A sterile hotel restaurant doesn't unlock the same conversation as the other person's preferred place.

Cross-cultural note

This skill carries especially high weight in:

• Japan — relationship-driven business culture; meals are foundational
• China and broader East Asia — guanxi dynamics
• LATAM — high-context relationship cultures
• IRL conferences (ETHCC, ETHDenver, Token2049) — temporary high-density opportunity

In these contexts, the skill is closer to a baseline expectation than an optimization. Skip it at your own risk.

Related skills

• first-week-trust-deposit — comes BEFORE this; the in-person meal works because the digital deposit is established
• trust-loop-cultivation — the molecule that orchestrates first-week + in-person + referral together
• costly-signal-credibility-check — travel + IRL is itself a costly signal