Zoho AI lead generation for UK small businesses: the system we built, end to end

Most UK small businesses that run on Zoho are losing prospects the same way: not because the leads are bad, but because nobody has the time to chase them. The owner is on a job site, the office manager is buried in admin, the sales rep doesn't exist. The leads sit in the inbox, get stale, and quietly die. The honest answer is that most UK small businesses do not need more leads. They need the leads they already have worked harder. Zoho AI lead generation is the system that does that — without hiring anyone.

What Zoho AI lead generation actually does

Three things, every Monday, Wednesday and Friday at 7am UK time. The system runs itself. You read the digest. Finds the right people on LinkedIn. You give us a target persona (job titles, industries, regions, exclusions) and the system searches LinkedIn via Bright Data every digest run. People who match the persona and whose recent activity suggests they're a real fit get added to your list. The search is targeted, not spammy — the right people, not a thousand random connections. Ranks them against your fit criteria. Each new prospect is scored against the criteria you set on day one. Top-of-list is highest fit. Low-fit gets dropped before they ever reach your inbox. You only see the leads worth your time. The score is logged on the prospect in Zoho so your team can see why each one was prioritised. Writes the LinkedIn message in your voice. The system drafts a short, specific LinkedIn message for each scored prospect in your brand voice (we scrape your existing public content to learn it on day one). Drafts wait in a queue for you to read, edit, send. The message reads like you, not like a bot.

How it works inside your existing Zoho

The architecture sits behind your existing Zoho CRM. Nothing changes on your side. The team logs into the same Zoho they always have. The AI writes into the workflows you already use. Zoho CRM is the system of record. Every prospect, every lead, every status change lives here. We never write to anything you haven't approved. The AI sits behind the scenes, your team logs into the same Zoho they always have. Bright Data is the LinkedIn search engine. Residential proxies, no monthly cap. Replaced Apify in 2026. Roughly three pence per weekly Cornwall run. Pay-as-you-go. The data is the data; the AI is the AI. OpenRouter is the LLM gateway. One key, many models. Cheap models for routine scoring and drafting. Frontier models for high-stakes replies. The router picks automatically based on the task. Supabase is the read-cache for the admin dashboard. Real-time. Zoho is the source of truth. Supabase is the speed layer. The admin dashboard reads from Supabase for instant filtering and search; the source data lives in Zoho. Next.js 15 is the admin dashboard. Runs on Railway. See the digest, review drafts, edit brand voice, change filters. Your team logs in, no training needed. Hermes Agent is the orchestrator. Plans, delegates, runs the right model for the right task. Open source. Cost guardrails built in. Falls back to cheaper models automatically when monthly budget hits 80%. The full architecture is documented in the Zoho Lead Engine product page and the original build case study.

How long it takes to set up

Fourteen days from kickoff to first digest. We have written about the setup process in detail on the approach page. The short version: Days 1-2 — Discovery. A 30-minute Zoom. We learn your persona, region, what "warm" means to you, what a good lead looks like in your pipeline, and what a bad lead looks like. You share your Zoho login (read-only first, write access when you're ready). You walk us through an existing prospect you liked. Days 3-7 — Setup. We configure your tenant's filter criteria, brand voice profile, and Zoho schema mapping. Zoho becomes the system of record for every prospect; our admin dashboard reads from a real-time cache so you can review and edit drafts without going into Zoho. Setup runs in 7 to 10 days. Days 8-14 — First digest. The first Monday, Wednesday or Friday after setup completes, the system runs end-to-end: search, score, draft, queue. You log in to your admin dashboard, read the AI's picks, edit the drafts you want to personalise, send the ones you're happy with. The rest sit in the queue for review.

What it costs

The CRM cost is unchanged — you keep paying Zoho. The AI layer costs roughly fifteen to twenty-five pounds a month per tenant in API spend, plus a small Next.js admin dashboard hosted on Railway Hobby at five pounds a month. Total: under thirty pounds a month for the AI layer, on top of whatever Zoho already charges you. We don't publish a price for the build itself because the cost depends on the complexity of the persona and the integrations. Most builds run in the low four figures. Talk to us about a 30-min scoping call to get a real number for your business.

Who this is right for

Zoho AI lead generation is right for a UK small business that: Already runs on Zoho (or another CRM that we can wire into the same architecture). Sells a service that takes time to research and qualify (B2B, professional services, recruitment, etc). Has a clear target persona and a region. Has the discipline to read the weekly digest and send the drafts. Doesn't need to be in 50 LinkedIn conversations at once. It is not right for a business that wants volume over quality, or that hasn't yet defined what a good lead looks like. The system amplifies what the team already does. It does not invent a sales motion from nothing.

What this means for you

If you run a UK small business on Zoho and the above describes what you need, the system is right for you. The AI layer costs under thirty pounds a month on top of Zoho. The setup takes two weeks. The hard part is having the discipline to read the weekly digest and send the drafts. If you cannot do it yourself, that's fine. We build these systems for a living — see the Zoho Lead Engine product page for the full architecture, or the work page for what's already shipping. The forty-quid plumbing firm post is a working example of the right-sized stack. You can read about how I build these systems in the Approach section, or see real builds in my Work.