Find referral partners with a useful reason to work together
Define customer overlap, complementary value and a respectful handoff before pursuing referral relationships for your business.
Define the relationship you want to build#
A useful referral partner understands a customer problem your business can solve and is willing to explore a sensible way to connect people. Start with that relationship, rather than asking for access to someone else's client list.
Kite can help you identify relevant people and get qualified phone or video meetings booked. You decide the referral process, any commercial terms and how the relationship operates after the Introduction.
This guide is about finding partners for your own business. Joining the Kite program to refer or resell Kite is a separate relationship with its own agreed terms.
Map a useful customer moment#
Describe when a customer might benefit from being introduced to you. Then identify a complementary business that could encounter that moment in its normal work.
For a software implementation consultancy, the moment might be a customer choosing a new system but needing help planning the implementation. A possible partner could be a specialist adviser involved in that decision. Treat that direction as a hypothesis until the adviser confirms the work they do and why the relationship would be useful.
Fill in this relationship map:
| Part of the relationship | Your answer | Evidence to look for |
|---|---|---|
| Customer situation | The specific problem or transition we help with | The customer's own description, with appropriate permission to share |
| Partner's contribution | The work they do around that situation | Their stated services and a relevant conversation |
| Our contribution | The part we can deliver reliably | Accurate offer information and approved proof |
| A useful trigger | When an introduction would help the customer | A situation the partner actually recognises |
| A respectful handoff | What happens before details are shared and who follows up | Agreement on permission, minimum context and ownership |
The SBA's market-research guidance recommends learning about a specific market through both existing information and direct research. Here, use a partner conversation to test customer overlap; a company's category alone does not establish it.
Choose the partner model before choosing the audience#
Referral, joint delivery and reselling create different relationships. Write down which one you want to discuss so your audience and message have a truthful purpose.
| Direction | What you want to learn | What you should not imply |
|---|---|---|
| Referral relationship | Whether there is a useful customer situation and a respectful introduction process | An obligation to send leads or a guaranteed referral volume |
| Joint delivery | Whether complementary services could work together on a customer project | A shared delivery commitment before responsibilities are agreed |
| Reselling or representing your offer | Whether the business wants a commercial channel discussion | Approved resale rights, pricing or exclusivity |
For the consultancy direction, choose a referral conversation first. Your message can explain the customer situation, the help you provide and why you want to compare approaches. Do not promise reciprocal referrals you cannot deliver or invent a fee arrangement.
Find the person who owns the relationship#
Use your objective and business context to work out the relevant people with Kite. Possible roles include a business owner, practice lead or partnership lead, depending on the organisation. A person who works with clients may recognise the need but still need to involve someone else before agreeing a relationship.
Check three things separately:
- Complementary work: is there a credible connection between the partner's service and your customer's problem?
- Customer overlap: do they serve the people or organisations relevant to this objective?
- Relationship responsibility: can this person discuss the proposed relationship or bring the right colleague into it?
If you do not know the best category, ask Kite to help compare possible audiences. Keep the reason for each direction visible. Exclude unsuitable or competing propositions where relevant, existing relationships you do not want approached and people who must not be contacted.
Set partner-specific Introduction criteria#
For a referral exploration mission, the standard could require a complementary business, relevant customer overlap, an appropriate relationship contact, a reason to explore the relationship, willingness to talk and agreement to be connected.
Decide which facts matter to partner fit and include their evidence or unknown status in the handoff. Some firms may need a particular geography or customer type; others can discuss those details on the call. If you mark a condition required, unsupported evidence remains unknown for confirmation on the call. A required fact recorded as not met rules the person out.
Keep commission, exclusivity, a minimum lead volume and detailed operating terms for the subsequent business discussion. If one is a required condition, a recorded mismatch rules the person out and an unknown remains a question for the call. A potential partner does not have to want to buy your service to be relevant to this objective.
The criteria screen below helps you record this standard. Replace the financing conditions shown with your partner-fit and willingness requirements. A generic buyer checklist is not automatically the right standard for a partner relationship.
Qualify step separating required conditions from preferred context.
Prepare the mission in Kite#
Choose Create your own when you want to enter this brief directly. The mission builder follows the five stages below; recommendations are another starting route.
Use the first-mission guide to follow the current setup flow:
- In Describe, state the relationship objective and select the offer the potential partner needs to understand.
- In Decision-makers, review the partner categories, relevant roles, locations and exclusions against the relationship map.
- In Qualify, separate essential partner fit and willingness from later agreement questions.
- In Execution, review messages that invite the actual relationship discussion. Confirm sending identity and permissions without implying that a referral agreement already exists.
- In Review, check the saved direction, campaign, criteria, handoff and Reach allocation. Resolve readiness issues and choose when to start in Kite.
One unique person sourced into a mission consumes one Reach. A broad partnership audience is not unlimited sourcing, and changing the relationship direction does not restore previously used Reach. See Reach for the counting rules.
The walkthrough shows the criteria step and review context. Use your own relationship map when entering the conditions.
Define a qualified Introduction
Test the handoff evidence#
Read each response as evidence of a specific state, not a reason to count a partnership early.
| Response | What is supported | What remains to do |
|---|---|---|
| “Happy to connect here.” | Acceptance of a connection | Establish the relevant reason to talk and agreement to the proposed handoff |
| “We advise companies like those you described. I'd like to compare how we handle implementation needs; please introduce me to your team.” | Relevant customer overlap, expressed relationship interest and agreement to connect | Check the required fit and role evidence, then the actual handoff and next step |
| “Send us your client database and we can discuss it.” | A request for data | Do not share private records as a shortcut; clarify a suitable relationship process |
An interested relevant person can become an Introduction when nothing on record rules them out and the handoff occurs; unconfirmed required facts remain visible to confirm on the call. That does not establish a signed partner agreement, customer referral or revenue.
Design a small, clear first collaboration#
Use the first conversation to compare actual customer situations. Agree what makes a referral useful, how permission is obtained before sharing details, what minimum context accompanies it and who owns the follow-through.
Write a short operating note:
- A situation where an introduction would help the customer.
- The customer and partner permissions needed before sharing information.
- The information each side needs, and what should stay private.
- Who contacts whom and how to avoid duplicate approaches.
- How the parties will review what happened and handle a mismatch.
- Any commercial terms that still need separate agreement.
Choose a next step both parties can support, such as comparing a de-identified customer situation or planning a permitted introduction when one arises. Do not invent a live customer or promise a quota to demonstrate momentum.
Your business handles agreement, delivery and the resulting customer relationship. A partner's permission to talk with you is not permission to contact all their clients.
Recover from a weak relationship direction#
| What happens | What to examine | Useful response |
|---|---|---|
| Lots of polite networking but little relevant interest | The customer moment and reason to meet | Make the relationship purpose concrete; avoid counting connection acceptance as an Introduction |
| Relevant businesses serve a different customer group | The overlap assumption | Refine the audience or explore a different proposition; keep actual evidence visible |
| Everyone asks about fees or exclusivity | The offer and what your business has decided | Prepare the questions for your team; do not let Kite or an agent invent terms |
| A partner expects unapproved customer information | The proposed handoff process | Pause that disclosure and establish permission and boundaries before sharing |
| A required fact is missing | The criterion and its evidence | Keep it unknown and confirm it on the call; a recorded failure rules the person out |
For a setup or activity problem, use mission recovery. An observation about today's replies is not proof that a whole partner market is viable or unviable.
Work with your agent#
Give your agent the truthful offer and relationship map. Ask it to compare complementary categories, separate partner fit from buyer intent and identify unknowns. The copyable task below prepares a brief and tests its handoff decisions; it does not enrol a partner or contact customers.
A clear task to copy
Use the find-referral-partners University guide and my offer to prepare a referral-partner Introduction brief. Retrieve the current guide and cite its version and section URLs if University retrieval is available. Ask what customer situation we help, what a complementary partner contributes and which relationship model I want to discuss. Compare possible partner categories as hypotheses, not verified client access. Make a table of customer overlap, complementary service, relationship responsibility, required conditions, acceptable evidence, exclusions and unknowns. Do not require buying intent for this partner objective or infer willingness from a networking connection. Evaluate a connection-only response, a relevant interested adviser and a request for a private client database. Leave fees, exclusivity, reciprocal volume and disclosure arrangements for my business to decide. Keep finding partners for my business separate from the Kite referral/reseller program. Prepare guidance only: do not source people, import contacts, reveal paid data, change settings, create or start work, enrol partners, send messages, share client records, connect accounts or spend money. Any requested live account check needs current authenticated discovery, returned IDs and separate evidence; unknown facts remain unknown. Finish with the brief and questions I should review in Kite.
This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.
Build your brief#
Use the worksheet for one relationship model and one customer moment. In the objective field, describe the discussion you want to have with the potential partner. Saving it here stays in this browser and activates no work.
Your introduction brief
A practical worksheet you can take into Kite.
This worksheet stays in your browser. Review and start your mission in Kite.
Check your next step#
Review your mission when the customer situation, complementary role, essential conditions and truthful message are clear. At the Introduction, use handoff review and next-step preparation to carry the relationship forward.
Your readiness check
0 of 5 checked
Your experience should make the next step clearer.
About this guide and its sources
Sources used to write and check this guide.
- Kite V1 product explanationChecked 2026-10-10
- Getting started with KiteChecked 2026-10-16
- What counts as an IntroductionChecked 2026-10-16
- How Reach is countedChecked 2026-10-16
- Messaging and approvalChecked 2026-10-16
- Targeting, lists and exclusionsChecked 2026-10-10
- Introduction delivery and next stepsChecked 2026-10-16
- First-run platform source and capture methodChecked 2026-10-11
- Introduction objectivesChecked 2026-10-11
- Customer responsibilitiesChecked 2026-10-16
- Audience and service-planning researchChecked 2026-10-11
- Introduction counting owner decision, October 15Checked 2026-10-16
- Current qualification controls and native themed capture recordChecked 2026-10-17
- Current shared Introduction explanationChecked 2026-10-17