| name | trust-loop-cultivation |
| description | When operating in relationship-driven business cultures (Japan, partnership-heavy markets, high-context industries), run the trust loop — pre-emptive contribution → first-week heavy output → increased contact frequency → contact becomes a fan → shared meal → referral. The goal is a state where existing clients bring the next clients. Cannot skip steps; loop integrity matters. |
| composition_level | molecule |
| extraction-lens | capability |
| source_attribution | Moriki (Hivemind Library) |
| license | pending-consent |
| status | candidate |
Trust Loop Cultivation
When to use
- Building a client / partner pipeline in relationship-driven cultures
- Long-term BD strategy where each engagement should generate the next
- Service businesses where referrals are the primary acquisition channel
- High-context industries (Japan, Asia, partnership-heavy crypto) where digital-only acquisition stalls
When NOT to use
- Transactional one-off work without continuity
- Pure self-serve product distribution (Web2 PLG)
- Cold outbound at scale (different mechanic; trust loops require seeded relationships)
- Markets where direct sales / paid acquisition is more efficient
Composition note
This is a molecule — a multi-step loop that orchestrates atomic skills:
Cannot skip steps. The loop integrity is what produces compounding referral pipelines.
Core thesis
The only way to grow revenue sustainably is to continuously grow the trust loop.
People only move based on referrals from those they trust.
The goal: a state where customers bring the next customers.
The loop (6 steps)
Step 1: Pre-emptive contribution
Before the relationship is formal, contribute value. Send a relevant article, make an introduction, share a useful framework. Demonstrates competence and generosity before any "ask."
The pre-emptive contribution must be:
- Specific to them (not generic content blast)
- Useful enough to be worth thanking you for
- Without strings — no immediate ask attached
Step 2: First-week heavy output
When the engagement formalizes, run first-week-trust-deposit. This is the atomic move that establishes the deposit balance for the rest of the loop.
Step 3: Increased contact frequency
After week 1, maintain rhythm — short check-ins, proactive updates, surfacing relevant signal. The cadence matters more than the content; you want the relationship to feel active, not transactional.
Cadence calibration:
- Active engagement: 2-3 touchpoints per week
- Quieter phase: 1 touchpoint per week
- Below 1/week: relationship goes cold; trust deposits decay
Step 4: Contact becomes a fan
The output of steps 1-3 is not the deal. It's the contact moving from "vendor I work with" to "person I'm genuinely glad to know." This is an emergent state — you can't force it. But you can recognize it.
Signals the contact has become a fan:
- They reference you in conversations with others (without being asked)
- They surface opportunities for you proactively
- They protect you from internal friction
- They invite you to non-transactional spaces (events, internal channels, personal recommendations)
If you don't see these signals after months, the loop has stalled at step 3 — usually because the contact frequency was too transactional.
Step 5: Shared meal (in person)
When the relationship is fan-strong but digital-only, run in-person-escalation-trigger. This is where the relationship becomes durable.
Step 6: Referral
After IRL has cemented the relationship, ask for the referral — but not transactionally. The right question is something like:
"Who else do you know who might benefit from this kind of work?"
If the loop has been run correctly, the contact volunteers the referral before you ask. If you have to ask twice, the loop hasn't completed yet — return to step 3 and increase contact-quality, not frequency.
Output format
When advising on trust-loop strategy:
RELATIONSHIP STAGE: pre-engagement | first-week | active | fan-state | IRL-established | referral-flowing
CURRENT LOOP POSITION: [step 1-6]
NEXT MOVE:
- Specific action: [aligned to current step]
- Atomic skill to invoke: [first-week-trust-deposit / in-person-escalation-trigger / N/A]
- Expected outcome: [what changes after this move]
LOOP HEALTH CHECK:
- Step 1 (pre-emptive contribution): completed | skipped | n/a
- Step 2 (first-week deposit): completed | skipped | n/a
- Step 3 (contact frequency): healthy | declining | calcified
- Step 4 (fan state): emerging | stalled | confirmed
- Step 5 (in-person): completed | pending | n/a
- Step 6 (referral): flowing | manual ask required | not yet
Anchor evidence
Rootstock Japan engagement (Moriki) — full loop:
- Pre-emptive contribution before engagement
- First-week heavy output (large volume of reports)
- Sustained contact frequency
- Contact (CGO) became a fan
- ETHCC in-person meal
- Referral to new client + long-term scope expansion
The full loop produced both: (a) the original engagement scaling, and (b) the next engagement via referral. That's the compounding state.
Failure modes
- Skipping step 1. Going straight to engagement without pre-emptive contribution; relationship starts in transactional mode.
- Skipping step 2. Sustainable pace in week 1 erodes the deposit balance; later steps require more effort to compensate.
- Step 3 calcifying into transaction. Contact frequency that's all "status updates" stops feeling like a relationship; loop stalls.
- Trying to force step 4. Fan state is emergent. You can't optimize directly for it; you can only run steps 1-3 well.
- Skipping step 5. Treating IRL as optional; loop completes weakly without it, especially in high-context cultures.
- Asking for referral too early. Step 6 fails when steps 4-5 weren't established. The contact hasn't moved to advocacy mode yet.
Cultural calibration
The loop is most explicit in Japanese / East Asian business culture but applies broadly:
- Japan: loop is near-mandatory; skipping steps is often fatal to deals
- Crypto / Web3 partnership work: loop is highly relevant due to conference circuit + small-world dynamics
- B2B SaaS in regulated industries: modified loop; in-person is replaced by formal review meetings
- Pure consumer products: loop doesn't apply; PLG mechanics dominate
Related skills
first-week-trust-deposit — atomic component (step 2)in-person-escalation-trigger — atomic component (step 5)costly-signal-credibility-check — each step in the loop is a costly signal of commitmentcommunity-diagnostics — adjacent: how to scale the loop pattern from 1:1 to 1:many in community
