How Many Flowers Does a Wedding Take? You Don't Have to Know.

A bride asked us recently — a little apologetically — how many flowers she was supposed to tell us to order. It's one of the best questions we've been asked all year, because the answer surprises almost everyone: none. That's the part we do.

She had a spreadsheet started. Columns for roses, eucalyptus, "filler." She assumed that booking a florist worked like ordering catering — that at some point she'd have to commit to quantities, and if she guessed wrong, her centerpieces would arrive thin or her budget would vanish into stems nobody needed.

It's a completely reasonable assumption. It's also not how any of this works, and we'd rather explain it once, properly, than have every couple quietly carry the same worry.

The counting was done years ago

When a design comes together — your palette, your venue, the shape of the day — the quantities fall out of recipes we've been refining for the better part of a decade, across more than a thousand weddings. A garden-style bridal bouquet is not "some roses and whatever looks nice." It's a formula: so many focal blooms, so many secondary flowers to carry the palette, so much texture, so much greenery to give it structure and movement. The same is true of a boutonniere, a bud vase, an arch.

Those recipes exist because we've built each of these pieces hundreds of times and kept score. We know how many stems a bouquet takes to look generous without getting heavy in the hand, because we know what happened at the weddings where we used five fewer and the ones where we used ten more. That knowledge is most of what you're hiring.

What a recipe actually protects

The formulas aren't just for our benefit. They're doing three jobs for you.

Your budget goes into flowers, not guesswork. Because the recipes are exact, we order exactly. There's no padding "to be safe" that you quietly pay for, and no gap that gets discovered the morning of. When you change something — one more table, a bigger arch — the count updates the way a good recipe scales, and the quote moves with it honestly.

The day looks like one design. The recipe keeps proportions consistent from your bouquet down to the last bud vase — the same balance of focal, secondary, texture and green, repeated at every scale. That repetition is why some weddings photograph as a whole and others read as a collection of separate arrangements.

The season can change without the design changing. If a flower comes in poorly the week of your wedding — and some week, somewhere, one always does — the recipe tells us exactly what the substitute has to do: same scale, same tone, same role. You may never know it happened. That's the point.

About a third of it, you'll never consciously see

One more thing the spreadsheet couldn't have known: a surprising share of the stems in any arrangement are structural. Greenery that builds the shape, texture flowers that catch light between the focal blooms, the pieces that make a bouquet move when you walk. Nobody points at them in photographs, but take them out and everything goes flat. When people say garden-style looks "effortless," these are the stems doing the effort.

So what do we actually need from you?

Not quantities. The inputs to the recipe are things only you know:

• The feeling — romantic and loose, clean and sculptural, wild, quiet
• The palette — even roughly; even "her dress is this colour and I hate orange" is a palette
• The venue and the guest count — they set the scale of everything
• What matters most to you — the bouquet in every photo? the ceremony moment? the tables your guests sit at all night? The recipe puts the weight where you care.

You bring those four things. We'll bring the math.