Fixing what happened after someone searched, instead of buying more people to search

The situation

Copper & Oak ran three restaurants under two names — a flagship, a second location four miles away, and a small bar concept that shared a kitchen with the flagship. Twenty-two years old, well reviewed, and busy on Fridays.

Marketing was whatever the general manager had time for, which in practice meant posting a photo when a dish looked good. The owner’s read was that they needed more visibility. They had been quoted a monthly retainer to fix it.

What they actually had was a demand capture problem. People were already looking for them.

What we found

We pulled the profiles before proposing anything. Two of the three had hours that were wrong — one had shown closed on Sundays for at least eight months, through a full summer.

Three specific failures:

1. The menu was a PDF. Search engines could not read it, phones rendered it at 40% zoom, and the kitchen had changed six items since the file was generated.
2. Reservations ran through three systems. The flagship used one platform, the second location another, and the bar took walk-ins and phone calls into a paper book. No one system knew what the others held.
3. The profile for the bar concept was a duplicate. It had been created twice years apart, and the copy with the good reviews was not the copy that surfaced.

None of this was a visibility problem. Every one of these people had already found Copper & Oak and then hit something broken.

What we did

Claimed and corrected all three profiles, merged the duplicate, and set hours to update from one source instead of three memories. The Sunday error alone had been quietly costing them a service a week.

Rebuilt the menu as real pages rather than a PDF — readable by search, legible on a phone, editable by the GM in a browser without calling anyone. Consolidated reservations onto one system, which meant moving the bar off paper and training two people who did not want to be trained.

Then the part the owner had not asked for: we scoped the social work down to one post a week tied to the actual menu cycle, because that was the volume the GM could sustain without it becoming the first thing dropped in a busy month.

The part worth stealing

We turned down the retainer we had been asked to quote. The work that mattered was three weeks of fixing plumbing, not an ongoing content program, and saying so cost us the larger engagement.

A restaurant that posts twice a week to an audience that cannot find its hours is buying reach it has no way to convert. Fix the capture first, and you often discover the visibility was never the constraint.

They asked us to make them more visible. We showed them a profile that said “closed” on the busiest brunch day in the county and asked whether visibility was really the problem.