Back
Founder · Product · Live

Booking the caterer is easy. Everything after is where it breaks.

MyCaterer is a B2B marketplace connecting event planners with vetted caterers, built to close the communication gap that traditional directories ignore.

RoleSolo founder · design & build
StackLovable · Supabase · Claude Code · Anthropic API
StageLive · early vendor discovery
WhereSwitzerland
MyCaterer marketplace home, showing curated event caterers across Switzerland with structured first-contact briefs
TL;DR

MyCaterer is a B2B catering marketplace I built solo as a non-technical founder, directing AI to write the code. 40 personalized cold emails to event planners → 5 replies (12.5%) → 1 discovery call surfaced the real gap: not finding a caterer, but everything that happens after. The marketplace is live and in active vendor discovery across Switzerland.

The problem I found

I didn't assume the problem. I went looking for it. I scraped Google Maps for event caterers and planners across Switzerland, then ran personalized cold-email outreach to find out where the real friction lived. The same frustration kept surfacing: the hard part isn't finding a caterer, it's everything that happens after first contact. Chasing availability, waiting on proposals, and the struggle to communicate the atmosphere they actually want for their event.

40
event planners contacted via personalized cold email, sourced through my Google Maps scraper.
12.5%
response rate (5 replies). Every reply pointed at the same gap.
1
discovery call booked — where the insight became impossible to ignore.

Chasing availability and waiting for detailed proposals can slow things down. It's also frustrating when the caterer isn't flexible, proactive, or doesn't anticipate practical details.

Event planner · outreach response

The most challenging part is communicating clearly what is important to us, and conveying the overall impression or atmosphere we'd like to create for the event.

Event planner · outreach response

Real responses from planner outreach. Used to identify the gap, anonymized.

How it works

MyCaterer starts with a curated set of event caterers. But it's not a directory. A directory hands you a phone number and walks away. MyCaterer is built around the part that actually breaks: the communication between caterer and planner, from first contact through to the end of the event.

1

Curated, vetted caterers

Not an open listing, a selected set of event caterers, so planners start from quality, not noise.

2

Structured first contact

Planners convey what matters (atmosphere, practical details, the impression they want) in a form caterers can actually act on.

3

Communication through the whole event

The marketplace holds the thread from booking to delivery, so nothing falls into the gap that planners kept describing.

A directory solves discovery. The real pain is communication. So that's what MyCaterer is built around.

How I built it

I built MyCaterer end to end as a non-technical solo founder, directing AI to build rather than writing the code myself, a prompt-to-production workflow. That included the product itself plus a Google Maps scraper that feeds personalized vendor outreach, which is how I reached the planners and caterers whose feedback shaped the problem above.

Lovable Supabase Claude Code Anthropic API Google Maps scraper Automated outreach

Where it is now

Early, and deliberately so

MyCaterer is live, and I'm in active discovery, talking with vendors and caterers to figure out the right communication model to build into the marketplace. Rather than guess at the workflow, I'm designing it from how caterers and planners actually want to work together. The product follows the evidence.

Honest caveats

Next: close the first real catering bookings through the marketplace, validate the structured-brief workflow with planners and caterers, and let the early evidence shape what gets built next.