Start with the purpose of the partnership
A referral partnership connects people who serve similar customers but solve different problems. For example, a web designer might hear from clients who need product photography, while a photographer might meet businesses preparing for a website redesign. A shared lead-qualification process helps both partners decide when an introduction would be useful. It should protect the prospect’s time as well as the partners’ time.
Before making a checklist, discuss why each of you wants to refer work. Ask what kinds of projects you can serve well, what falls outside your scope, and how much capacity you typically have for new inquiries. Be candid about constraints such as service area, project size, or scheduling requirements. The aim is not to make every inquiry pass through a rigid system. It is to avoid introductions that sound promising but are unlikely to help anyone.
Agree on what makes a lead worth introducing
Write a short description of a suitable prospect for each partner. Include the problem the prospect is trying to solve, the type of customer you usually work with, and the signs that they are ready for a conversation. A designer’s suitable referral to a photographer, for instance, might be a business that needs images for a planned website and has identified someone who can discuss the project. A vague comment that the business “should get better photos” is a reason to ask more questions, not necessarily to make an introduction.
Keep the shared questions few enough to use in an ordinary conversation. You might ask what the prospect needs, when they hope to begin, whether they have a budget range in mind, and who will decide how to proceed. A prospect does not need a perfect answer to every question. Record unknowns as unknowns rather than filling in gaps with guesses.
Also agree on reasons to pause. If the requested service is outside the partner’s scope, the timeline appears unworkable, or the prospect has not expressed interest in speaking with anyone, hold off. A lead can be a poor fit without being a poor customer. A respectful process leaves room to suggest another route or simply continue the original conversation.
Make permission part of the handoff
Qualification should not become an excuse to collect and circulate unnecessary details. Before sharing a prospect’s contact information or project notes, ask whether they want an introduction and explain who the partner is. If they agree, confirm the best way to connect them. A brief email that introduces both people and states the relevant need is often easier to act on than a long private briefing.
Decide together what belongs in a referral note. Useful basics might include the prospect’s name, organization, stated need, approximate timing, and any question they want the partner to answer. Share only details the prospect has agreed you may pass along. Avoid forwarding a full conversation or making claims about budget, urgency, or buying intent that the prospect has not confirmed.
Assign one person to make the introduction and one person to respond. For example, the referring partner sends the agreed note, and the receiving partner replies with a proposed next step. If the receiving partner cannot take on the inquiry, they should say so promptly rather than leaving the prospect waiting. Neither partner should imply that an introduction guarantees a quote, availability, or a working relationship.
Use a lightweight shared record
A simple record can prevent duplicate introductions and missed follow-ups. It may be a shared spreadsheet or another tool both partners already use, provided it is appropriate for the information being stored. Include only fields you need: date of introduction, referring partner, receiving partner, broad service need, next action, and status. Agree on who updates each field and who can access the record.
Choose a few plain-language statuses, such as “permission requested,” “introduced,” “conversation scheduled,” “not a fit,” and “work agreed.” These describe where the handoff stands without treating every introduction as a sale. Decide how long you need to keep notes and remove details that no longer serve the partnership. If you use separate systems, you can still review a brief summary together rather than sharing access to entire customer lists.
Review the process, not just the results
After several introductions, set aside time to compare what happened with what you expected. Were prospects clear about why they were being connected? Did the receiving partner have enough information to start a useful conversation? Were any questions awkward to ask too early? Look for patterns in fit and handoff quality, not just how many introductions became projects. Some useful referrals will not lead to work, and that does not automatically mean the qualification was poor.
Use those observations to revise one part of the process at a time. You might clarify a service boundary, remove a question that rarely helps, or change the introduction note so the next step is clearer. Keep each other informed when availability or offerings change. A shared qualification process works best as a small, maintained agreement: specific enough to guide decisions, but flexible enough to treat each prospect as a person rather than an entry in a pipeline.
