By Brett Kaufman. 8 years using relationships to build sales pipelines, from political fundraising to a 7 figure business to running matchmaking for two communities. Over 1,000 introductions facilitated.

To make introductions at scale, stop treating each one as a separate favor and run them through one weekly system: capture the promise, ask both sides, send, check back at 30 days, log what came back. Batch the work into one block a week, and say no early to the intros you should not make.

Here is the week that breaks most connectors. Monday you promise two intros on calls. Wednesday a mastermind dinner adds four more. Thursday a lender says yes to an ask you sent last week, but the buyer on the other side has gone quiet. Friday someone texts “did you ever hear from Dana?” and you cannot remember if you sent it. At five intros a month, memory works. At 25, it does not, and the ones that slip are the ones people remember.

I have facilitated over 1,000 introductions, and I run matchmaking for two communities. At that volume an intro stops being a favor and becomes a process with stages. If you do not run the stages, they run you.

Why volume breaks intros

One intro is not one action. It is at least four touches spread over five or six weeks: the ask to the first side, the ask to the second, the intro itself, and a check back about a month later. Often a bump in between.

Illustrative math. Say you make 30 intros a month. That is roughly 120 touches in flight at any moment, each with its own date, each waiting on someone else. Nobody holds 120 open loops in their head, and nobody should try. Trying harder is not the fix. Giving every intro a stage and looking at all of them once a week is.

The five stages of every intro

Every intro moves through the same five stages. Your job each week is to move each one forward by one.

1. Captured. You said “I’ll connect you.” Write it down before you leave the room: both names, the one line why, the date you said it. If it is not captured, it does not exist.
2. Asked. You sent the ask to the side with more to lose, then to the other side. The ask itself is covered in the double opt in intro template, so I will not repeat it here.
3. Sent. Both said yes, and the intro is out with one person named to move next.
4. Checked. About 30 days after the intro, one line to each side: “Did you two end up talking?”
5. Logged. What came back goes in the ledger, even if the answer is “nothing yet.” What to record and why is in how to track introductions and referrals.

The point of naming the stages is that an intro can be stuck in only one place. When someone asks “did you ever hear from Dana?” you know in five seconds whether it is waiting on Dana’s yes, waiting on his reply, or done.

The weekly intro block

Here is how I would run it. Pick one slot a week, same day, same time. Thirty to forty five minutes covers a heavy month. Work the queue in this order:

1. Clear the captures. Go through everything you promised since the last block. For each one, decide: ask, decline, or hold with a date. Nothing leaves this step undecided.

2. Send the asks. All of them, back to back. Batching asks is faster and they get better, because you are in the same headspace for every one.

3. Send the intros that have two yeses. These are the most fragile items in the queue. A yes that sits a week goes cold, and the person who said yes starts to wonder why they bothered.

4. Bump the silent asks once. Anything with no answer after a week gets one short nudge. After that, it is a no, and you tell the asking side.

5. Do the 30 day check backs. Everything introduced about a month ago gets its one line.

6. Log what came back. Calls, deals, fees, referrals back to you, and nothing. The nothings matter. They tell you which pairings to stop making.

Order matters. Captures and yeses go first because they decay fastest. Check backs go last because they can wait a day without costing anything.

Batch the work, not the promise

Batching does not mean making people wait in silence. Two rules keep the block from looking like slowness.

Tell people when. At the dinner, say “I’ll send the ask Monday.” Now a Monday ask is you keeping your word, not you being late.

Pull deadlines forward. If the reason has a date on it, it skips the queue. A searcher with an LOI who needs a lender this week gets the ask today. A founder who might raise next year can wait for Monday.

Batching also shows you patterns one off intros never will. When you send 15 asks in one sitting, you notice you are asking the same SBA lender for the third time this month. That is your signal to find a second lender before you wear out the first.

When to say no

At scale, the most important intro skill is not making some of them. Every intro you send spends a little of your credibility with the side that has more to lose. Decline early, at capture, before anyone is waiting.

What I tell people: say no when

• You cannot write the why in one line. “You two should know each other” is not a reason. If you cannot say what each side gets, neither can they.
• You do not know one side well enough to vouch. Met them once, at a crowded event, for four minutes? Get to know them first or pass.
• The receiving side has said yes to you a lot lately. Even great contacts have a limit. Spread the asks or wait.
• The asking side has a pattern of no follow through. If your last two intros for them died because they never booked the call, the third one will too.
• The fit is a stretch you are making to be helpful. A near miss intro wastes two people’s time and teaches both of them to take your next ask less seriously.

How to say it:

I don’t know her well enough to put my name on it. Send me two lines on the deal and I’ll think about who else fits.

Fast and honest, with something you can do instead. A clean no today costs far less than a promise you carry for six weeks and never keep. It is also how the super connector’s operating system stays credible at volume: fewer intros, better ones, all of them finished.

Where the weekly block breaks

The block works on paper. In practice, three things kill it.

The captures never get written down, because the promise happened at a dinner and you were not going to pull out a laptop. The block gets skipped the week you travel, which is the same week you made the most promises. And the queue lives in a spreadsheet that tells you nothing until you open it, so the yes from Thursday sits until the following Monday.

Each of those is the same problem. The queue has to come to you, not wait for you.

The system that runs the queue for you

That is why I built FRONT OF MIND. It runs the intro queue inside your 10 minutes for today. After dinner, say a name and a sentence out loud, “promised the HVAC buyer an intro to the SBA lender,” and it is filed under the event. No laptop.

Intros to make this week show up with dated proof on both sides, so you can see the reason is current before you spend your credibility on it. Asks, bumps and check backs come as drafted text style messages, 40 words max, in your voice. Nothing sends without your tap, and it learns from your edits. When you need a second lender, ask Liala “who do I know that is an SBA lender” and get the right people with why.

Your contacts are encrypted. No one on our team looks at them. Export and delete anytime.

Start free with your first 25 contacts and 1 intro, and see which promise comes up first.

See how it works