Cold call scripts from website facts (not compliments)

Open with one verified website problem and a short permission question. Compliments sound like every other vendor call.

For Web freelancers · Micro-agencies · No-code / automation consultants

“I was looking at businesses in your area and love what you do” is the kind of line owners hear all day. It burns trust before you have said anything useful.

A stronger first call names a checkable fact about their digital front door, explains in one calm sentence why it might cost them customers, asks a short permission question, and then stops talking. This is for manual calling. ApexPull can draft scripts from audit facts; you still review what you say or send. Automatic dialers stay out of scope.

If you cannot state a verified fact, audit first. Dialing without evidence trains the wrong habit.

Opening lines by fact type

Use only what you have checked. Swap the bracketed bits for the real business.

No own website: “Hi [Name], this is [You]. I help [niche] in [city] with their online booking path. I noticed [Business] is active locally but doesn’t have its own website; it looks like you rely mostly on [Maps / Instagram]. A lot of new customers compare options online before they call. Would it help if I showed you what a simple site would need to cover for [niche]?”

Social profile only: “…I can see a strong [Facebook/Instagram] presence, but no site you control. That works for updates; it is shaky for [bookings / quotes / menus] when the feed buries the post. Have you tried a simple site, or is social a deliberate choice?”

No HTTPS: “…I opened [domain] this morning and the browser flags it as not secure. Some customers leave before they see your services. I can walk through what fixing that involves in plain language if that would be useful.”

Broken mobile layout: “…on a phone, [domain] doesn’t lay out cleanly; [form / menu / text] is hard to use. Most walk-ins probably checked you on a phone first. Want a short note on what is breaking?”

No booking or contact path: “…I couldn’t find online booking or a working contact form on [domain]. For [niche], after-hours demand often goes to whoever answers fastest. Is booking online something you’ve wanted, or do you prefer phone-only?”

Site down or error: “…I tried [domain] today and got [timeout / 5xx / parking page]. It may be temporary, but if customers hit the same thing you are leaking calls. Open to a sixty-second recheck together?”

Permission after the fact

Once the fact is on the table, stop selling features. Ask something low-commitment: whether this is a bad time for a two-minute check, whether they decide on the website, or whether a one-page summary would help. If they say no, thank them and log the outcome. Lists improve when “not interested” is recorded instead of deleted out of embarrassment.

Avoid subjective insults (“your site looks outdated”), fake scarcity, invented studies, illegally scraped personal names, and multi-minute monologues. Small towns especially remember the scarcity trick.

Leave-behinds and compliance

If they want something written, send a short factual note: a screenshot, two concrete observations, one suggested next step. A white-label one-pager usually beats a twelve-page PDF.

After signup you can open Search, run an audit on a place, and use the outreach panel to draft a script or report link. Edit before anything goes out.

Cold calling rules differ by country and number type. Honor do-not-call lists, calling hours, and local advertising law. This is a messaging framework, not legal advice.

Related: website audit checklist for local prospects, when a Facebook page isn’t a website, and a micro-agency prospecting system.