✗ The Problem
Three working chefs with a real business and no way for anyone to book them. No site, no booking path, and a logo that existed only as a drawing on paper. They needed something that looked like the food they actually put out, and they needed it to be theirs, not rented from a builder.
✓ What I Built
- Full custom site: services, crew profiles, how it works, and a booking flow that routes straight to their inbox
- Their hand-drawn whisk logo digitized into clean vector art, then used as the wordmark, the favicon, and the punctuation in "WHY COOK?"
- A members-only section for their private dinner club
- Copy written and rewritten across several rounds with the chefs until the voice was theirs
- DNS and SSL set up on the domain they already owned, so the site lives at their address and they keep control of it
✗ The Problem
Most mobile operators cannot tell you what they actually made at an event. Revenue is easy to see. Food cost, labor, the event fee, and the drive are not. So they book the same unprofitable festival a second time because it felt busy. Permits are the same story: thirteen of them across different jurisdictions, all renewing on dates nobody is tracking.
✓ What I Built
- Event tracking with real profit per event, not just revenue
- Permit vault with renewal dates and alerts before they lapse
- Expense logging and POS report import for Square and Toast
- Profit analytics that rank your events best to worst
- Operator community built into the app
- Free tier plus paid plans, with live Stripe billing and automated email digests
✗ The Problem
A restaurant with thirty one years of cooking behind it and a website that made it look closed. The menu was hard to read on a phone, the contact info was buried, there was no catering section despite catering being a real part of the business, and nothing on the page told Google what the place was.
✓ What I Built
- Tabbed menu that stays readable on a phone
- Click-to-call for orders, with a separate line for catering
- Catering section with the 100+ dish range they actually offer
- Their real Facebook and Yelp reviews pulled onto the page
- Embedded map and clear hours
- Proper heading structure and metadata for search
✗ The Problem
A truck site has one job that a restaurant site does not: answer where are you today. Most truck websites bury that, or skip the menu entirely and push everyone to Instagram. That works until someone is deciding between you and the truck down the street at eleven in the morning.
✓ What I Built
- Menu with real pricing across tacos, quesadillas, bowls, nachos, sides, and dessert
- Daily location handoff to their Instagram, where they already post it
- Catering section for private parties, corporate, and weddings
- Their existing 4.8 star review presence surfaced on the page
- Home base address and contact for the people who want it
✗ The Problem
Barbecue sells on the food looking good and the menu being findable. Most operators in this category end up on a drag and drop template that loads slowly, buries the menu two clicks deep, and looks identical to every other site from the same builder.
✓ What I Built
- Menu and ordering path above the fold, not behind a nav drawer
- Custom layout instead of a template, so it does not look like the truck next to it
- Click-to-call ordering on every screen size
- Heading structure and metadata built for local search