93 Brew
A café website the owner can update without a developer
A customer website for a café: prices and items are changed in one place and update across the site, each drink has its own page, and the site is set up to be found in local search. We hold a stake in the café.
Owned venture
We hold a stake in this business. This is our own operation, not a client project.
- Recorded outcome
- Production site live with menu, visit, and FAQ content
- Status
- In production
- Practice
- Build · Growth
- Sources
- 2 figures
Delivered build, live check of every route, 29 August 2026
Owned venture
Specialty coffee
running system, engineering record
The problem.
A new owner-operated café, one we hold a stake in, needed a customer-facing website ready for its opening in March 2026, local discovery from the first week, paid-social measurement, and a menu that stays accurate as prices change without a developer on call for every update.
What was built.
- Multi-page customer website: menu, product detail, about, space, visit, contact, and FAQ content
- A central menu data model, so pricing and item changes flow through the whole site from one place: 25 drinks across five categories (Classic, Matcha, Signature Iced, Flavours, Slow Bar), each with its own page carrying a tasting profile, ingredients, and milk options
- Local search is covered: page metadata, a sitemap, a 14-question FAQ, and a Business Profile
- Structured content set up for ongoing updates
- A WordPress twin of the site with a custom menu plugin, so the owner can change items and prices without a code deploy: local build delivered with owner and deploy guides on 28 June 2026, GA4 installed 1 July 2026
- Launch collateral ahead of opening: coming-soon posters (16 February 2026), then grand-opening flyers and menu reels (17–20 March 2026)
Timeline.
Coming-soon posters out ahead of the opening
Content prototype built, the Sanity content model connected to the production project, and the first production deploys
Google Ads advertiser verification completed for the café
Production site live, alongside the café's opening
Meta Pixel and Conversions API installed for paid-social measurement
Menu pricing revised from the point-of-sale export through the central menu model; the 41st production deploy of the Next.js build
WordPress twin of the site delivered with owner and deploy guides; GA4 on it from 1 July
Live check: HTTP 200 on every route across 28 screenshots
What this case claims, and what it does not.
On the record
- The site is live and in production use
- A price change is made once, in the menu record, and every page that shows it updates
- Local search is covered: page metadata, a sitemap, a 14-question FAQ, and a Business Profile
Withheld, and why
Figures that exist internally and are not on this page, with the reason.
- Traffic, footfall, or revenue impact
- No analytics are attached to the site, so there is no sourced outcome to publish. A Business Profile view count exists, and a view count is not an outcome.
- The café operations system as production software
- It exists as an internal prototype with a 20-table schema and is listed on this site as an internal product. It is not running the café.
- This as client work
- We hold a stake in the café. It is on the page because it is the most complete shipped build we can show, and it is not counted as an engagement anywhere on this site.
The public site.
Elsewhere on the site
Read next
Where to next
Have a problem in this shape?
Send a short description. The form opens with this case already named, so you only add the part that is yours. We will tell you whether it is worth building at all.