Let me introduce you (after I ask)
On a Friday call, two founders told me about the app they’re considering building. Along the way they mentioned they needed a lawyer, specifically someone with experience drafting contracts for content creators.
I told them I thought I knew someone and that I’d check whether it was a fit. That was their opt-in. They’d asked me, and now I was going to ask the other side.
The someone was Gabe Levine. I’ve worked with Gabe since 2011. In our first contract negotiation he caught a clause that never should have been there, and he’s been my lawyer ever since. Before I put him in front of anyone, though, I wrote to him with the shape of the request:
“I have a request from a potential client. They are looking for someone with experience drafting contracts for content creators. They are very early in the process … If it’s a fit, great! If it’s not a fit. No sweat. If you know of other folks who would be a better fit, let me know.”
Gabe didn’t say yes right away. He asked a question first: “To be clear, this is for a lawyer to work with the product/app company to draft contracts between them and content creators?” I wrote back, “That’s correct!” and once that was settled, I made the introduction.
I love that question. Gabe got to find out exactly what he’d be signing up for while it was still just the two of us talking. If the answer had changed his mind, he could have told me so, and the founders would never have been left waiting on a reply that wasn’t coming.
The introduction itself opened like this: “As I mentioned on our call on Friday I always try to do double opt-in introductions to avoid burdening either side with contact that can’t work.” Then I told them who Gabe is to me: “Meet, Gabe Levine of Matchstick Legal. He’s based in Northern California and there is nobody I trust more in the realm of contracts than him.” And then I got out of the way: “I mentioned in my words what you’re looking to build and what I understand your needs to be but it would probably be best for you all to discuss on a quick call.”
Almost every introduction I make works this way. Before I connect two people, each of them knows what’s being asked and gets a real chance to say whether it fits. The founders heard that I thought I knew someone and would check first. Gabe heard “If it’s not a fit. No sweat.” I didn’t promise the founders a lawyer, and I didn’t promise Gabe a client. Neither one’s time matters more than the other’s, so they both get the same ask.
The same day I sent that introduction, I saw it from the other side. An agency emailed me looking for Rails help with Solidus experience. Someone I know had passed my name along without checking with me first, which is fine; we know each other well. Before I replied, I talked with Jared Norman of Super Good Software about his availability. The next day I wrote back that we could help, and honestly it “would help us to close out the year.” Then I introduced Jared and his team instead: “They are Solidus experts and good at what they do.” Jared wrote back that evening and moved me to BCC.
There’s a little bit of judgement involved in knowing when a quick intro is welcome, especially when I know both sides well or know more about their circumstances, and some people have told me I can always make a certain kind of intro. From time to time, one side says no, and when that happens I usually leave the request open so I can ask someone else, or I tell the person who asked that it isn’t a fit this time, without passing along the why.
In my experience, the person asking for an intro is often assumed to be a yes, and all the care goes to the busier side. I’d rather both sides get the same care, and that matters most for whoever has the least pull. I last interviewed for a job in 2007, and “each new opportunity in my career has come through my network.” I know not everyone has a network like that, and when you’re the one asking, let me check first can sound like a door closing. I hope it reads the other way. Asking first is how I make sure that when the person on the other end says yes, it’s because they want to help, and that nobody ends up stuck in a thread they didn’t ask for.
Connections like that are a big part of what XO Ruby is for. As I wrote about San Francisco, “I’d inevitably end up introducing two locals who lived in the same city but had never crossed paths until a visiting friend gave them both a reason to show up somewhere.” Double opt-in is how I try to do that one email at a time.
So if there’s someone you’d like to meet, tell me what you’re looking for. I’ll ask them the same way I asked Gabe. And if you’re ever the one getting that email from me, you can tell me it’s not a fit, no sweat.
If you’re looking for a team to help you discover the right thing to build and help you build it, get in touch.
Published on November 10, 2026
