Ed Weeks Jr. argues that handshakes and warm introductions aren't enough. You need written agreements on ownership, responsibilities, compensation, and what happens if things stall. Without them, you risk losing access, reputation, and control.
Welcome to Weeks Weekly. I'm Ed Weeks Jr. This week, a handshake is not economics. A handshake is not economics. Owners get burned when an introduction goes out before the commercial structure is written down. In plain English, a warm introduction can still leave a cold commercial question behind. The people may be aligned, the intent may be good, the language may sound completely reasonable. But a social agreement is not the same thing as commercial infrastructure. The introduction may feel small, but the owner is asking it to carry real commercial weight. The moment an owner routes a relationship, the owner has spent access, context, and reputation. The first question is simple: Who owns the relationship after the intro? If the answer is unclear, the introduction creates motion without creating ownership. The second question is what each party is responsible for. Who makes the introduction? Who follows up? Who supplies context? Who keeps the process moving? Written roles keep the relationship from depending on whoever happens to remember the conversation best. The third question is how everyone is compensated if something real happens. Because once money appears, memory gets creative. The point is not to predict the outcome. The point is to define the terms before timing changes. The fourth question is what happens if progress stops. Without that answer, the owner can be parked in a process with no written path, back to a decision. An unclear route can cost the owner time, credibility, and the ability to explain the opportunity cleanly. The first failure mode is money showing up after the fact. Then everyone remembers the original conversation a little differently. The second failure mode is nothing showing up, even though reputation was already spent. A stalled process is not neutral when nobody has agreed who is responsible for bringing it back. The owner made the connection, opened the door, and now has no clean way to explain what happened next. The third failure mode is the process stalling. The owner is parked, waiting for someone else to decide whether the process is still alive. So the first operating standard is this: write the economics before the introductions. Not a complicated agreement, just enough written clarity to prevent the commercial meaning from changing later. The floor does not need to be elaborate. It needs to be clear enough to start without guessing. The second operating standard is to agree the floor before shared work or shared lists. The floor is the minimum commercial understanding that makes collaboration safe enough to begin. Before lists move, before time is committed, before introductions multiply, everyone should know what the shared work means. A return path keeps a helpful handoff from becoming a permanent loss of visibility. The 3rd operating standard is to protect the return path before a soft handoff. A soft handoff can be useful, but it cannot mean the owner disappears into someone else's process. The return path answers who comes back, what comes back, and when the owner can make a decision. That is the difference between being helpful and building a process that can actually carry commercial weight. The commercial standard is simple: the route should still support a decision when the first path does not. A useful test is to read the plan backward from the moment something goes wrong. If the process stalls, can the owner identify the next decision, the responsible party, and the path back? This is not a case against introductions. It is a case against making introductions carry terms they were never given. Put the paper before the routing. From the owner's perspective, written clarity is not bureaucracy. It is protection for the relationship and the decision. Before the next introduction, write the 4 answers down. Write the economics before the introductions. Agree the floor before shared work. Protect the return path. Before you route the relationship, ask whether the owner can still see the next decision. Owners do not need more introductions. They need introductions that can still produce a decision if the first path fails. The discriminating question is this: If this stalls, who still owns getting me to a decision and what did we agree happens next? Owners do not need more introductions. They need introductions that can still produce a decision if the first path fails. I'm Ed Weeks Jr. More at edweeksjr.com.
