An alliance of 65 restaurants. A web department of one.

The ask arrived in a conversation

The alliance came to us with a problem stated the way clients actually state problems: not as a spec, but as a goal. The site as it stood spoke to restaurants about joining. What the team really wanted was the reverse. They wanted the site to give value back to the members they already had, and they wanted the public using it to find local restaurants worth supporting.

That's the whole brief. No wireframes, no feature list. A direction.

Translating that goal into a website is what an SEO firm is actually for. If diners are meant to find member restaurants, then every member needs a page of its own, built the way people search: by neighborhood, by cuisine, by name. The structure of the site is the strategy. We didn't need the client to know that; we needed to hear what they wanted and already know the rest.

That conversation happened on a Monday, June 23. The working demo was in the client's hands Thursday, June 26. Full approval came July 3, and the new site was live in production the afternoon of July 4.

Why this was even possible

The alliance keeps Distill Works on a monthly retainer, and the hinge of this story was set well before the redesign: their site had already been moved off a rented site builder and onto our own infrastructure.

On a rented builder, a 65-member directory is a maintenance nightmare you edit by hand until it goes stale. On our infrastructure, the site is generated: every member page, every neighborhood guide, every cuisine guide is built from one set of records, and a change ships the entire site in minutes. A complete change in direction becomes a three-day build instead of a three-month project, because the plumbing already existed and the people who built it answer the phone.

What happened next

Google noticed almost immediately.

• Search impressions grew tenfold in the first week. The site went from 87 impressions a day to 883 and was still climbing at the edge of the data.
• The site's average search position went from 42 to 10. Page four to page one, site-wide, in a week.
• Dozens of member restaurants now rank on page one when someone searches their name, on pages that did not exist eight days ago. And that's the point of the whole redesign: the alliance's site is now working for its members, not just describing them. A second layer of neighborhood and cuisine guides is still indexing behind the first wave.

Clicks more than doubled in the same week. The positions are new and will take weeks to settle into their full click share; the early numbers are the direction, not the ceiling. But a site that spent months invisible on non-brand searches now sits on page one for the names of the restaurants it exists to promote.

What the retainer looks like the rest of the month

The rebuild is the dramatic part. The value is the ordinary part: an alliance with a small team and a 65-restaurant surface has, in effect, a web department on call.

The retainer belongs to the alliance; what the members get is everything it powers.

• Members keep their own listings current. Each one gets a single emailed link. No password, no training. The form arrives prefilled with what's already on file, and every change is reviewed by the team before it goes live.
• The right message reaches the right people. The team's dashboard sends to members, to vendor partners, to applicants, or to everyone, and the lists stay in sync with the membership records on their own.
• Changes happen the same day they're asked for. When a vendor relationship went on pause, the listing came down that day, fully reversible if negotiations turn. When two neighborhoods needed to be filed together, the guides were reorganized, the old addresses forwarded, and the change was live before the follow-up email. When application notifications weren't landing where the team could find them, the routing was traced and fixed the same week.

None of those items generated an invoice. That's what the retainer is.

The result

• Three days from a conversation about direction to a working demo. Eleven days to live.
• Ten times the search visibility in week one, with the site's average position moving from page four to page one.
• 65 member restaurants, each with a page that ranks for its name, maintained through a system their owners can use from a phone.

The part that matters if you're responsible for more than one storefront

The redesign isn't really the story. The story is what it means when the organization's website is infrastructure someone owns, and the someone is on retainer. This summer, the ask was a new direction, delivered in days. Before that it was a membership pipeline. Next month it will be something nobody has thought of yet, and it will not require a proposal, a scoping call, or a new vendor.

A rented website can describe your organization. Owned infrastructure can carry it: every member, every partner, every message, every change, at the speed the ask arrives.

That's what the retainer is. If you're responsible for a lot of moving pieces on a website that can only hold brochure pages, that's a conversation worth having.