Warm intros that survive the handoff: a relations system
Access is cheap to get and easy to waste. Most warm introductions die in the gap between the person who made them and the person who was supposed to follow up. This post is about closing that gap with a system: how we track relationships, prep an introduction, and run the handoff so the goodwill someone spent on you does not evaporate in an unanswered thread.
What you'll learn
- Why a warm intro fails more often than a cold pitch
- The relationship ledger we keep, and the five fields that matter
- How we prep both sides of an introduction before it happens
- The 48-hour handoff rule and the automation behind it
- What a working relations system makes possible over a year
The old way: a contact list and a good memory
The classic approach to relationships is a CRM full of names and a founder who "knows everyone." It works until it doesn't, and it stops working at exactly the moment you scale, because memory does not scale and a name in a database is not a relationship.
The specific failure looks like this. Someone makes a generous introduction. It sits for nine days because the right person was busy. By the time anyone replies, the context is cold, the introducer feels ignored, and the door that took a year to open quietly closes. Nobody did anything wrong. The system just had no mechanism to catch the ball.
Access without a follow-through process is not an advantage. It is a list of people you have already let down.
The new way: a relationship ledger, not a contact list
We keep a relationship ledger in **Airtable**. It is not a contact dump. Every record is a person we have an actual line to, with five fields that do the work:
- **Last real touch** — the date of the last genuine interaction, not a newsletter blast.
- **What we owe** — the thing we promised or should send. Open loops, written down.
- **What they care about** — one honest sentence about their current focus, in their words.
- **Strength** — cold, warm, or trusted. We are honest here, because pretending a warm contact is trusted is how you burn it.
- **Intro-worthy for** — who in our network they should meet, if anyone.
That last field is the engine. A relationship ledger is most valuable not for who you can ask, but for who you can connect. The studios and operators who compound access are the ones who give introductions away faster than they request them.
We run a weekly query against this ledger: anyone with an open "what we owe" and a touch older than thirty days surfaces to the top. That list is the Monday ritual. Nothing fancy, just a saved view that refuses to let debts age out of sight.
Prepping an introduction so it actually lands
A bad introduction is "you two should talk." A good one removes all the friction before either party has to think. Before we ask anyone to make an intro for us, or make one ourselves, we prep both sides.
The double opt-in
We never blind-CC two people together. We ask each side privately first, with a one-line reason the other person is worth their time. If either hesitates, the intro does not happen. This single habit is the difference between an introducer who keeps helping you and one who learns to dodge your name.
The forwardable blurb
When we want an intro, we write the message the introducer can forward without editing. Three sentences: who we are, the specific reason this person matters, and the small clear ask. We are doing the introducer's homework so the favor costs them ten seconds, not ten minutes.
We draft these with Claude from the ledger fields, then cut them down by hand, because a blurb that sounds automated defeats the entire point. The tool assembles the facts. A person makes it sound like a person.
The 48-hour handoff rule
The rule is simple and it is the whole game: when an introduction lands in our inbox, the substantive reply goes out within 48 hours, no exceptions. Not "thanks, let me check my calendar." The actual next step, a proposed time or a real answer.
We enforce this with a label and a timer. Inbound intros get tagged on arrival, routed through our **Zoho** inbox rules, and anything tagged that crosses 36 hours pings us. The automation does not write the reply. It refuses to let the reply be forgotten. That distinction matters: the machine guards the clock, the human keeps the warmth.
When we started measuring this on ourselves, the embarrassing finding was how many warm intros we had personally let rot before the timer existed. The rule did not make us more charming. It made us reliable, which over time reads as the same thing to the people doing us favors.
A worked example: the intro we almost lost
The handoff rule exists because of a specific miss. An operator we respect introduced us to someone running a studio twice our size, the kind of door that does not open twice. The intro landed on a Friday. We were mid-render, heads down, and the thread sat.
By Wednesday the introducer sent a quiet follow-up, not annoyed, just checking. That follow-up is the sound of goodwill leaking. We replied that day, the conversation recovered, but the lesson stuck: the relationship had survived our competence and nearly died from our scheduling.
We built the timer that week. Now an inbound intro gets tagged on arrival, and the 36-hour ping is non-negotiable. The next intro from the same operator, months later, got a substantive reply in under three hours. They noticed. They said so. Reliability, it turns out, is a thing people remark on precisely because so few deliver it.
The receipt here is not a metric we can publish. It is the behavior change: we went from a team that occasionally let warm intros rot to one that structurally cannot, because the system will not let us forget. That is what a rule plus a timer buys you that willpower does not.
The strength field, and why honesty there pays
The strength field, cold or warm or trusted, is the one people fudge. It feels good to mark a contact as trusted after one nice call. It is also how relationships get burned, because you treat a warm contact like a trusted one, ask for too much too soon, and spend down goodwill you had not actually earned.
We grade strength conservatively and move records up only on evidence. A contact becomes warm when they have replied to us unprompted. They become trusted when they have done us a favor with no immediate return, or we have done one for them. Writing this down stops the wishful thinking that turns a polite acquaintance into an imagined ally, and it tells us exactly which asks are appropriate for which people.
The payoff is that every request we make is sized to the real relationship. We never ask a warm contact for a trusted-tier favor, so we never get the polite no that quietly downgrades us in their mind. The field keeps us honest about what we have actually built.
Closing the loop back to the introducer
The most-skipped step in all of relationship work is the thank-you that reports the outcome. Most people thank the introducer once, immediately, then disappear. We send a second note a week or two later that says what came of it, good or bad.
This costs nothing and it does two things. It tells the introducer their goodwill landed somewhere real, which makes the next intro more likely. And it gives them a story to tell about you, which is how reputation actually travels.
What this makes possible
Run a relationship ledger with a real handoff rule for a year and the math changes. Each kept commitment makes the next introduction easier to earn. Each reported outcome turns one introducer into a source of several. Access stops being a thing you spend and starts being a thing that grows, because you became the person other people are glad they vouched for.
None of this requires being well-connected to start. It requires being the one party in the chain that does not drop the ball. The system is just there to make sure you are that party every time, not on the days you happen to remember.
We keep our own ledger this way, and we built the handoff timer the same week we missed an intro we should have caught. If you want to see the rest of the studio's working machinery in public, the experiments at [temerarii.xyz](https://temerarii.xyz) and the other pieces in the [blog](/blog/) take it apart system by system.
Written by Dominique Davis, Founder, Temerarii Media.