← All workBrand launch site · Waitlist & intake
Shaka Bros
A Chicago wellness start-up got a clean launch site for its hand-pressed ginger, apple and lemon shots — with live intake, client-owned operations, and a build that fails when the design export drifts.
The engagement
Shaka Bros is a Chicago health-and-wellness company started by three friends who train hard. They press ginger, apple and lemon by hand, bottle it in glass, and deliver weekly to the Friday sunrise lake plunge at Frosty Fridays, gym floors, and start lines. Euphemios turned the approved eight-screen Claude Design export into a launch site on shakabros.co, covering the daily 2 oz shot, 750 mL and 1.75 L bottles, partner intake, athlete and model applications, the Road to Hyrox training story, and Shaka Collective apparel while leaving planned media and product placeholders clear for the client to update.
01
The challenge
The export carried the brand's launch energy, but it was still a design artifact: hash routing, one runtime shell, placeholder media, and forms that looked complete without a client-owned backend. The business also needed room to keep moving after launch, because beetroot capsules, raw honey, the first Shaka Collective drop, the hero film, and the weekly Hyrox log are all intended to evolve as the founders re-export the design.
02
The approach
We built a deterministic Python pipeline around the bundled export. It unpacks the bundle, applies 74 exact-string patches with required occurrence counts, writes one HTML shell per route, replaces the hash router with clean history-backed URLs, and lets the brand loader play once per session so QR-code deep links such as /waitlist open instantly. All four forms post once to a client-owned Google Apps Script and Google Sheets backend, route to the contact@, partners@, and collective@ aliases named in the design, and return short branded confirmations. The apex domain runs through Cloudflare DNS and Vercel, with www and the Euphemios staging alias redirected to shakabros.co while Google Workspace mail records stay untouched.
9clean launch routes
5live intake forms
74verified template patches
03
Scope of work
- Eight clean routes from the approved Claude Design export: Home, Products, Partners, Shaka Athletes, Find us, Road to Hyrox, Waitlist, and Shaka Collective
- The approved launch copy carried over faithfully: daily 2 oz shots, 750 mL and 1.75 L bottles, in-development beetroot capsules and raw honey, and the first Shaka Collective apparel drop
- Waitlist, partner inquiry, Shaka Collective model and athlete application, and first-drop email intake flows backed by the client's Google Workspace
- Road to Hyrox route for two co-founders racing Hyrox Chicago on February 14, 2027, with the weekly training log left ready for client updates
- Apex-domain deployment on shakabros.co with clean URL shells, canonical metadata, Open Graph tags, and once-per-session loader behavior
- Brand asset production from the shaka mark: favicon set, 1200x630 Open Graph card, email logo, and self-hosted Lexend
04
What we delivered
- Static production launch site with eight route shells and History API navigation
- Python clone pipeline that applies 34 verified exact-string patches and fails on unexpected export drift
- Five live forms posting once to Google Apps Script and separate Google Sheet tabs, with honeypot protection and branded email confirmations, including a dedicated Shaka Athlete application at /apply
- Cloudflare DNS to Vercel apex deployment, with www and Euphemios staging aliases redirected to shakabros.co
- Favicon set, 1200x630 Open Graph card, email logo, and self-hosted Lexend with zero third-party runtime requests
- Playwright render gate across desktop and mobile routes, including console, request, navigation, overflow, and local form checks
- 01
Shaka Bros launched on its own apex domain with a site that explains the weekly delivery ritual and sends visitors directly to waitlist or product paths.
- 02
Four intake flows now land in client-owned Google Sheets and the named aliases, so waitlist, partner, Collective, and first-drop interest can be handled from the client's workspace.
- 03
The client can keep iterating from Claude Design re-exports; 34 counted patches make drift fail visibly instead of silently dropping launch behavior.
- 04
The launch is plain about placeholders: the hero film, some photo slots, and the weekly Hyrox training log remain intentionally provisional by client instruction.
- 05
Runtime stays self-contained: Lexend is self-hosted and the shipped page makes zero third-party requests.
Built with
- Static web
- Claude Design export pipeline
- Python build
- Google Apps Script
- Google Sheets
- Playwright render verification
- Cloudflare DNS
- Vercel