Cake Consultation Questions: What to Ask Before You Quote

A message arrives at 11pm. "Hi! How much for a unicorn cake?"

There is no honest answer to that message. A unicorn cake is anywhere from 90 dollars to 600 depending on servings, on whether the horn is fondant or wafer paper, on whether it is being collected or driven across the city on a Saturday in July, and on whether it is needed next month or the day after tomorrow.

So you ask a question. They answer. You ask another. Two days and forty messages later you finally have enough to quote, they say the number is more than they expected, and the whole thread evaporates.

The problem is not the customer. The problem is that you were asking the questions one at a time, in the wrong order, in a channel built for chatting rather than ordering. Here is the full list of what you actually need to know, grouped by why it matters.

The Five That Decide the Price

If you learn nothing else, learn these. Until you have all five you cannot quote at all, and every other question in this article is a refinement.

1. What date is the cake needed, and what time? This governs whether you can take the order before anything else does. It also flags rush work. A cake wanted in nine days at the end of an already full week is a different price to the same cake in six weeks.
2. How many people does it need to feed? Not what size, how many people. Guest count is the input and cake size is your output. If you are unsure how those convert, our cake serving size chart does the arithmetic.
3. Is it being collected or delivered, and to where? A postcode changes the price. A third-floor apartment with no lift changes it more, and a wedding venue that needs on-site stacking is a different service entirely.
4. What does it need to look like? Photos, colors, theme, any lettering. This is the one customers volunteer first and it is the only one of the five that is genuinely negotiable.
5. What budget did they have in mind? Yes, really. Section below.

Ask About Budget Early, Not Last

Most bakers save budget for the end because asking feels rude. It is the single most expensive habit in the trade. You spend an hour scoping a cake for someone who was picturing half your minimum, and you both leave the conversation annoyed.

Budget asked at the end sounds like a challenge. Budget asked early sounds like service, because it is. It lets you steer the design toward something they can afford instead of quoting a cake they will never buy.

Phrase it as a design constraint rather than a means test.

• "So I can design something that actually fits, do you have a rough figure in mind for the cake?"
• "Cakes this size usually run between X and Y depending on the detail. Which end of that were you thinking?"

That second version does most of the work. You have anchored a real range before they had a chance to invent an unrealistic one, and their answer tells you whether to sketch sugar flowers or a clean buttercream finish with a fresh flower crown.

Design Questions Worth Asking

• Do you have inspiration photos? Ask for two or three, not one. A single photo is a request to copy someone else's work. Three photos tell you what the customer actually likes across all of them.
• What are the exact colors? "Blush" means six different things. Ask for a photo of the invitation, the bridesmaid dress or the party decorations instead of a color name.
• Buttercream or fondant? A finish preference changes both the look and your labour hours.
• Is there a message or name on the cake, and how is it spelled? Get the spelling in writing. Always.
• What flavor, and what filling? Offer your list rather than an open question. Open questions produce requests you cannot deliver.
• Are there any elements that absolutely must be there? This surfaces the non-negotiable detail the customer has not mentioned yet, which is usually the one they will judge the whole cake on.

The Questions That Protect You

These are boring and they are the ones that save orders.

• Any allergies or dietary requirements at the event? Ask on every single order, even when it is obviously a birthday cake for four people. Then state in writing what your kitchen handles, and note that a home kitchen producing nut and gluten items cannot guarantee a nut-free or gluten-free cake.
• Will the cake be outdoors, or in a heated room? This is the question that saves buttercream cakes in August. It can change your entire recipe.
• How long will the cake sit out before it is served? Four hours on a display table under spotlights is a structural decision, not a detail.
• Who is the point of contact on the day, and what is their number? Not the bride. The bride is not answering her phone.
• Does the venue have a table ready, and does it need a stand? Ask who is providing the stand and who is returning it.
• When do you need to stop changing things? Set a design lock date and say it out loud during the consultation. Two weeks out for a wedding, one week for everything else.

Stop Doing This Live

Read that list again and notice how few of those questions need you present. Almost none of them are a conversation. They are data collection, and every one of them costs you a message, a notification and a context switch when it happens in a DM.

The consultation is worth your time for exactly two things: the design conversation, and closing the sale. Everything else, the date, the guest count, the postcode, the allergies, the spelling of the name, belongs on a form the customer fills in before you speak.

That reordering also fixes the qualification problem. When budget and guest count arrive before you have invested an hour, you find out in ninety seconds whether this is an order or a browse.

Letting the Answers Arrive First

This is precisely the shape CakeVision is built around. You send customers to your own design page, they answer your questions there, and the AI renders a mockup of their cake from those answers on the spot. Nothing is generated until the required questions are filled in, so an incomplete enquiry is not a thing that can reach you.

A new bakery is provisioned with a question set matched to what it makes rather than a generic form. A wedding bakery gets the wedding date, guest count, number of tiers and style. A birthday bakery gets who is celebrating and what age, plus the theme and the message for the top. A cupcake bakery is asked for a quantity instead of servings. Every one of those questions, including the ones we ship by default, is yours to rewrite, reorder or delete from the questions page in your dashboard, so the allergy question and the venue question and the lock date can all live there too.

The customer refines the mockup until it is the cake they want, submits it, and the order arrives in your inbox as a picture with every answer attached. You open one email instead of scrolling forty messages, and the first thing you say to that customer is a price.

FAQ

Should I charge for a cake consultation?

Charge for anything with a tasting attached, and credit the fee against the order if they book. A fifteen-minute call to discuss a birthday cake should stay free, because the friction of a payment link will cost you more orders than the fee recovers. The paid consultation belongs to weddings, where you are giving away an hour plus baked samples, and where a booking fee filters out couples who are collecting free cake across five bakeries.

What should I do when a customer will not give me a budget?

Give them the range instead and let them react to it. Say that a cake for their guest count typically runs from X to Y depending on detail, then watch which way they move. Customers who are uncomfortable naming a figure will almost always tell you honestly whether your range works, and that is the same information.

How far in advance should I take custom cake orders?

Most custom bakers book two to four weeks out for a standard celebration cake and three to six months for wedding cakes in peak season. What matters more than the window is that you have one and you state it publicly, because an unstated lead time invites the next-day request you will feel obliged to say yes to.