Building an AI Client-Finding System That Prioritizes Relevance Over Volume
Hey frens! How I’m approaching AI-assisted research, outreach preparation, and follow-up as a hands-on CMO and entrepreneur.
Finding potential clients is not just a search problem. It is a judgment problem.
You can collect company names, identify decision-makers, and prepare messages—and still have no convincing reason for someone to speak with you.
That is why the AI-assisted client-finding system I’m designing starts with relevance, not volume.
The objective is not to automate as much outreach as possible. It is to identify where my work could genuinely be useful, investigate the opportunity, and prepare a better conversation.
Define the opportunity before choosing the tools
Before building a workflow, I want a clear brief:
What result can I help a client achieve?
Which businesses can I serve well?
What changes might make my service more relevant?
What evidence would justify a closer look?
What would make an opportunity unsuitable?
For example, imagine you help property agencies improve enquiry handling and follow-up.
An agency announcing a new office could be worth researching. But expansion does not prove that its existing processes are broken.
The announcement is a fact. A possible need for your service is a hypothesis.
A useful system should keep those two things separate.
Make research the first deliverable
Instead of asking AI for “100 qualified leads,” I would ask for a small set of evidence-backed opportunity notes.
Each note should explain:
What happened and when.
Where the information came from.
Why it might relate to the offer.
What remains unknown.
Whether the next step should be further research, a conversation, or no action.
That final option matters.
If every company receives a positive recommendation, the workflow is not helping me prioritize. It is simply generating justifications for outreach.
Prepare a conversation, not a diagnosis
Research should improve the questions we ask.
It should not encourage claims such as:
“Your agency is losing leads, and I can fix it.”
Unless we have evidence, that is an assumption.
For a hypothetical agency that has genuinely announced an expansion, a more useful opening could be:
“I saw your announcement about the new office. Is enquiry handling managed centrally as you expand, or does each office handle it separately?”
That question creates space to understand the business before proposing a solution.
Any approach would still need an appropriate contact channel and human review.
Build a controlled workflow
The structure I want to implement is straightforward:
textPermitted information sources → Research and evidence checks → Opportunity notes → Human review → Approved next actions → Reply and outcome tracking
My proposed stack includes Claude for research synthesis and drafting, n8n for orchestration, and a CRM as the operational record. These are implementation options—not a claim that the complete system is already running.
The shared record matters as much as the AI component. It needs to show who owns the relationship, what has been discussed, whether further contact is appropriate, and what should happen next.
Measure commercial usefulness
I would judge the pilot by research accuracy, the quality of recommendations, useful conversations, qualified opportunities, and review time.
Messages sent would be a secondary metric.
The first version should be small enough to inspect closely. Before expanding it, I want to understand where the research fails, which drafts need rewriting, and what actually leads to meaningful conversations.
That is the direction I’m taking: using AI to support disciplined business development, while keeping responsibility for the relationship with a human.
For the full framework, practical prompts, and implementation considerations, read the complete article in my newsletter, The New Entrepreneurship:
Designed a modern and intuitive AI-powered mental wellness website focused on emotional well-being and personalized digital experiences.
The platform features an AI therapist, mood tracking, meditation, sleep improvement, wellness plans, and data-driven insights. A calming blue color palette, immersive visuals, clean layouts, and thoughtful UI elements create a seamless and engaging user experience.
Before you add AI to your product, find the screen where your users already copy and paste.
That's usually where the real AI feature lives. Not a chatbot in the corner, but a step people already do by hand: summarising a ticket, drafting a reply, tagging an upload, pulling fields out of a PDF.
Here's the order I follow when a founder asks me to add AI to an existing SaaS:
1. Pick one workflow, not "AI everywhere." Watch where users leave your app to paste something into ChatGPT and come back. That round trip is your feature.
2. Keep the model behind your own API. One service owns prompts, retries, logging and cost limits, so you can switch providers without touching the frontend.
3. Make it tenant-aware from day one. Each customer's data, prompts and usage stay scoped to their account, or the first enterprise security review will stop you.
4. Ship a draft, not a decision. Let the AI suggest and the user approve. You earn trust and get real feedback before you automate anything.
5. Measure accepted output, not tokens. If users rewrite most of what it produces, the prompt or the context is wrong, and that's your real roadmap.
Most AI features that flop didn't fail because of the model. They were bolted onto the wrong step.
What's the one task your users still copy into ChatGPT?