My recommendation is to treat referrals as a relationship process, not a reminder to ask everyone for introductions. Define who you can help, make a useful introduction easy, assign responsibility for following up, and keep the relationship valuable after the original work is complete.
Technology can support that process. It should not decide the relationship strategy for you.
Start with the situation someone should recognize
“Send anyone who needs our services” asks a contact to do too much interpretation.
A clearer explanation names a situation. For Fidelis, that might be a business owner who sees potential in AI but does not know where to begin, or a team whose important work depends on disconnected tools and repeated manual steps.
That does not mean restricting the company to one service or industry. It gives the person making the introduction something recognizable to listen for.
For your own business, finish this sentence: “A useful time to introduce us is when someone says ___.” Use the language your customers actually use.
Give people a simple way to introduce you
Make the next step easy to understand. Who should receive the introduction? What context would help? What should the other person expect afterward?
A short introduction note could be enough. For example:
“I thought you two should connect because [relevant situation]. [Business] helps with [plain-language description]. I’ll leave you to see whether a conversation would be useful.”
This is an illustrative template, not a message to send automatically. The person introducing you should adapt it to a real relationship.
Avoid asking them to deliver a complete sales pitch. The first job is to establish a relevant connection.
Decide who follows up and what happens next
An introduction creates a responsibility. Someone needs to respond, understand the situation, and give the prospective customer an appropriate next step.
I would define where the introduction is recorded and who owns it before adding reminders. Otherwise the system can generate notifications without establishing accountability.
The process should also allow for “not now” or “not a fit.” Treating every introduction as an immediate sales opportunity can lead to the wrong follow-up.
A simple record could include the referring contact, the stated need, the responsible person, the last interaction, and the agreed next action. The appropriate tool depends on the business.
Maintain the relationship after the work
Staying in touch should have a purpose for the recipient. A relevant observation, helpful resource, or genuine check-in is different from repeatedly asking for more business.
I would decide what continued contact is useful before setting a cadence. The timing should reflect the relationship and the nature of the work, not a universal schedule copied from a marketing template.
Also decide what the referring person should hear back. Thanking them and closing the loop can be appropriate, while the prospective customer's private information should remain private.
The system should help people remember their commitments, not make personal relationships feel like a queue of automated messages.
Where AI and automation could help
Consider a hypothetical business that already has permission to keep suitable contact notes and a clear follow-up process.
AI could help prepare a first draft based on approved context. A person could check whether it is accurate and worth sending. Ordinary automation could remind the responsible team member when an agreed action is due.
Those are different jobs. A scheduled reminder does not need a generative model just to exist, and a draft should not invent a shared interest, relationship, or event.
I would start with the missing part of the process. If people do not know whom the business serves, clearer positioning may matter more than software. If the process is sound but inconsistently followed, a better system may help.
Review the quality of the process
Do not stop at how many messages were sent. Review whether introductions were relevant, whether the response was timely, whether the next action was clear, and whether the relationship remained useful.
Keep commercial outcomes separate from activity. More reminders are not the same thing as more valuable conversations, and more conversations are not automatically more business.
A useful review asks what needs changing: the explanation of fit, the introduction method, the handoff, or the follow-up itself.
Connect the strategy to the systems
Referral development is one example of how growth strategy and operational design belong together. A strong idea needs a way to happen consistently. Automation needs a worthwhile purpose.
That is how I approach growth strategy and custom systems at Fidelis. We learn about the business, identify the opportunity, and design how the supporting work should happen before deciding what to build.
Your next growth opportunity may involve a new channel. It may also involve better follow-through on relationships you already value.
Talk through your growth priorities
Related reading
How to Find the Business Bottlenecks Holding Back Growth
Business Process Improvement: Make Your Software Fit the Work