How to approach a café cold, from the chef who used to bin those emails
A how-to on approaching a café or restaurant cold, written from the buying side: the moment the approach lands in a kitchen, why it's a buying decision about reliability, timing and channel, leading with the facts that let a chef say yes, a sample that makes no work, and a follow-up that isn't pestering. Grounded in the decade on the buying end and the microgreens side of selling to chefs. General throughout; no research or application notes attached, no figures used, no invented anecdotes. Links the one-page wholesale price list post.
The two seconds behind the pass
When a message came in from a producer I'd never heard of, it landed in the middle of something else. I was mid-prep, or checking a delivery, or setting up a section before service. I gave it about as long as it took to read the first line, and then it was either worth keeping or it was gone.
That is the window you are approaching into. Not a desk, not a quiet inbox someone reads with a coffee. A kitchen, where attention is rationed by the hour and the message from a stranger is competing with everything already on the list.
I spent about a decade on that side, receiving from producers. Later I was the one sending the messages, when I grew microgreens and sold them to restaurants and chefs. Selling to chefs was familiar ground, because I had been the chef on the other end of that order. Both jobs taught me the same thing: the approach that works is the one that reads well in two seconds to someone who is busy and slightly wary.
What the chef is actually deciding
Here is the part most guides get backwards. The chef reading your message is not looking for a new product. They already have suppliers, a menu that works, and an order routine they don't want to rebuild. What they are weighing, in those two seconds, is a risk: are you going to be one more thing that goes wrong on a Tuesday?
A supplier who doesn't turn up. A short delivery in the middle of prep. An invoice that arrives wrong, or three weeks late, or not at all. Every chef has been burned by that, and the burn is what your message is being measured against, whether you know it or not.
So the thing to signal first is not passion. Enthusiasm is cheap and every approach has it. What lands is evidence that you are organised, that you deliver when you say you will, and that you will be easy to deal with once the novelty has worn off. Reliability is what a busy kitchen is buying.
Timing and the channel
The fastest way to a no is to arrive or ring in the middle of service. A chef in the weeds cannot give you thirty seconds, and being the person who made service harder is not the first impression you want to leave.
Kitchens have a shape to the day. There is a lull, usually mid-morning after prep is under way and before the lunch push, or mid-afternoon between services. That is when a message gets read properly rather than swiped away. You rarely know a specific kitchen's rhythm from outside, so the safe move is a written approach they can pick up when the gap comes, not a call or a drop-in that demands attention on your schedule.
Written also does something a conversation can't. It lets them keep your details. A good message can be forwarded to the owner, or left open until the quiet bit of the afternoon. A phone call at the wrong moment is just gone.
Lead with what lets them say yes
Most cold approaches open with the story. How it started, the passion, the process, the founder's journey. All of that can come later. None of it answers the question the chef is holding, which is: can I actually use this, and what would it take?
Give them the facts that let them say yes without having to write back and ask. What it is. How it's packed and in what sizes. Which days you deliver and the area you cover. What it costs. When payment is due. That is the same short set of facts a good wholesale price list carries, and there is a real case for letting a one-page price list ride along with the first contact so there is nothing to chase.
When a chef has those in front of them, saying yes is one message. When they have to prise each fact out of you one question at a time, most won't bother, and the food never came into it. You have already shown them what ordering from you will feel like.
The sample that makes no work
A taste settles the one thing words can't. However well you describe it, the chef still has to try it to know whether it earns a place on their menu. A sample answers that faster than any pitch.
But a sample can also create a job, and that is where producers lose the goodwill they just earned. Something that turns up unannounced and has to be signed for during service. A tasting that needs the chef to stop and plate up. A box left at the door with no note saying what it is or who it's from. Now your sample is a small problem to solve, and you are the person who caused it.
Bring it the way you'd want a supplier to bring one to you. Arranged for a time that suits them, or dropped in the quiet part of the day, clearly labelled, ready to taste as it is, with your details and those same facts attached so a yes needs no follow-up call. The sample should ask nothing of the kitchen except the two minutes it takes to try it.
The follow-up that isn't a chase
Silence after a first approach usually means the message came at a bad moment, not that the answer is no. So a follow-up is fair. The question is what kind.
One clear, low-pressure check-in a week or so later does the job: a short note that repeats the useful facts, says you'd be glad to drop a sample if it's helpful, and leaves it there. That reads as a producer who is organised and relaxed about it.
The anxious version is the one to avoid. Three messages in five days, each one a bit more wounded than the last, gets you remembered, but for being hard work before you've even delivered anything. If the second nudge gets nothing, leave it a good while before the next. A kitchen's needs change with the seasons and the menu, and the producer who was easy to ignore in March is worth a reply in September.
The quiet signals
Everything in that first exchange is read as a preview of what you'll be like as a supplier. The chef can't see your fridge or your delivery van, so they judge the things they can see.
Did you tell them the price without being asked, or make them request it? Did you answer in one message, or over four, each arriving a day apart? Was the sample labelled, or a mystery box? Did you say which days you deliver, or leave it vague? None of these is about the food. All of them are about whether working with you will be smooth or a small ongoing negotiation.
Get them right and you read as the supplier who will be easy: orders in, delivery on time, invoice correct. Get them wrong and, however good the product, you read as admin the kitchen will come to regret. In a trade where a chef is choosing who to let near their menu, easy is most of the sale.
Before you send the next one
The exercise is simple. Take the approach you'd normally send and read it as the chef will: mid-prep, two seconds, deciding whether you're worth the risk. Cut the story to the back. Move the facts to the front. Pick a time that suits their day, not yours. Make the sample cost them nothing but a taste.
You are not trying to be memorable in that first message. You are trying to be the producer who is obviously going to be easy to buy from, so that when the kitchen does have a gap, yours is the name attached to no trouble at all.