They built the website first, then sold it 97 times

The problem with pitching websites

A web studio selling to local business has a positioning problem before it has a lead problem. "We build websites" is true of every competitor, and it asks the prospect to do the imagining — to picture what their own site might look like, what it would cost, whether it would be any good. Most of them decline the invitation.

This studio had been buying broad local lists: every business in a metro, no category filter, a few thousand rows at a time. Reply rates sat in the mid single digits and the calls that did happen opened with an explanation rather than a demonstration.

Narrowing until one demo could carry the pitch

The change was a constraint rather than a tactic. If every prospect on a list runs a comparable business, then a single piece of finished work is relevant to all of them — and the pitch stops being a description and becomes a thing you can look at.

So the pull was deliberately tight: one state, and every Asian-cuisine filter available. Georgia holds roughly 72,700 restaurants. The seven filters — Chinese, Thai, Sushi & Japanese, Korean, Vietnamese, Ramen & Noodle Bars and Indian — cover about 15.3% of them, a pool of roughly 11,100 venues. They took 1,000 of it.

At the single-state niche rate that came to $339, or 34 cents a record. Delivery was the same working day.

Building the demo before sending anything

Before a single email went out, the studio built one complete demo site for a fictional Atlanta restaurant. Not a template or a mockup — a working site: menu structure, an ordering flow, a reservation widget, and photography treated the way that kind of venue actually photographs.

That sequencing is the part most studios skip, and it is the part that did the work. Because every prospect ran a comparable business, the demo did not read as a portfolio piece from someone else’s project. It read as their own site, already finished, waiting for their name and their menu.

Email and phone against the same records

Both channels ran against the same 1,000 records inside the same week. Email went first, short, with a link to the demo and nothing else asked for. A phone call followed roughly two days later that referenced the demo rather than re-explaining it — the conversation started from "did you see it" instead of "let me tell you what we do".

Calling order came out of the file. The Google rating and review-count columns were used to sort: venues rated well but under-reviewed went first, on the reasoning that they were already good at the thing they do and were losing on visibility alone. That is a much easier opening than telling someone their restaurant needs help.

The phone number mattered more than usual here. Restaurant owners are famously hard to reach by email and easy to reach by phone, and the file carried a published line for effectively every record.

The numbers

Twenty-one addresses hard-bounced — a rate of 2.1%, comfortably inside the 95% validity guarantee, leaving 979 deliverable records.

Of the thousand records, 310 replied. Ninety-seven became clients. That is a 31% reply rate and 9.7% of the full list closed — or, put another way, just under a third of everyone who replied went on to sign.

The data cost $339. Against 97 clients won, that is $3.49 of list spend per client. Whatever the studio’s cost of delivery was, the acquisition side of it was not the expensive part.

Why the reply rate was that high

A 31% reply rate is far above what cold outreach normally returns, and it is worth being precise about the cause, because the wrong lesson here is expensive.

Almost none of it is the copy. The emails were short and unremarkable. What moved the number was that the list was narrow enough for one demo to be genuinely relevant to every name on it, that the demo existed before the outreach did, and that email and phone hit the same record within the same week rather than running as separate campaigns.

Widen the list and the same sequence degrades quickly, because the demo stops being about them. The constraint is the mechanism.

What they would change

Two things, by the studio’s own account. First, they did not use the website-status filter on this pull, which means a share of the 1,000 already had a site they were reasonably happy with. Filtering to venues with no resolving website would have cut the list and almost certainly raised the close rate.

Second, 1,000 records was more than the team could work properly in the window they gave it. A smaller batch worked harder would likely have produced a similar number of clients from fewer names.