How to price a wedding floral proposal

Price a wedding floral proposal from a recipe for every design. Total the current cost of stems, foliage, hardgoods, and mechanics, account for normal purchasing loss, add the labor required to process, design, pack, deliver, install, strike, and recover rentals, then apply your studio’s overhead and profit method. The finished proposal should be traceable to what the team will actually buy and build.

A floral recipe is the itemized build specification for one arrangement. It names the ingredients, quantities, mechanics, and hardgoods needed to produce that design.

A build list is the production total created by multiplying each accepted recipe by the number of arrangements. It should agree with the proposal before anyone orders flowers.

Hardgoods are the nonfloral materials consumed or supplied with the design, such as vessels, foam, wire, tape, pins, candles, and structural mechanics. Reusable vessels and structures need a separate rental and return policy because the studio still owns them after the wedding.

Start with recipes, not a round number

Give every proposal line a real design behind it. A bridal bouquet, low centerpiece, bud vase grouping, ceremony meadow, and bar arrangement each need their own recipe. Name the intended scale and style clearly enough that the recipe, written proposal, and reference image describe the same result.

Build the recipe from ingredients you can realistically source for the event date. If the design brief allows seasonal substitutions, cost the role each flower plays rather than promising an exact variety that may not be available. The couple buys a defined look and scale. Your team buys actual stems and hardgoods to produce it.

This is why a priced recipe library matters. It lets a florist reuse a proven design while adjusting the stem mix, vessel, color direction, or scale for a specific wedding. The wedding florist software page shows how Everbook connects that library to proposals and build lists.

Build a complete cost basis

Stems and foliage

Use current acquisition cost for the quantity you must purchase, not an old remembered price. Include supporting foliage and filler as deliberately as focal flowers. If product must be bought by a bunch or case, the proposal has to absorb the purchasable unit even when the recipe uses less.

Hardgoods and mechanics

Add every consumed material to the recipe. Small mechanics disappear easily during estimating, then appear across every centerpiece during production. For reusable inventory, distinguish the charge for use from the labor and risk involved in delivery, pickup, cleaning, and loss.

Purchasing loss and substitutions

Perishable product rarely arrives in perfectly usable recipe quantities. Account for the way your studio buys, conditions, and grades product. Keep that allowance grounded in purchasing history and recipe risk. A delicate specialty stem and a durable foliage do not need the same treatment.

Price the labor the design creates

Design time is only one part of floral labor. The price also has to carry receiving, processing, hydration, recipe staging, mechanics preparation, packing, loading, travel, installation, room resets, strike, unloading, cleaning, and rental recovery when those tasks apply.

Estimate labor from the production method, not only from the flower value. A cluster of bud vases may use modest product but require repeated cleaning, filling, placement, and collection. A ceremony structure may concentrate the work into mechanics, ladder time, transport, and a narrow installation window. Those are different cost shapes even if their stem totals look similar.

• Record bench labor by recipe, including mechanics preparation and packing.
• Record event labor separately for delivery, installation, room moves, strike, and rental recovery.
• Include production management when someone must receive product, assign builds, check recipes, and solve shortages.
• Revisit labor when the venue, access window, room flip, or arrangement count changes.

Keep design, logistics, and rentals visible

A clear wedding floral proposal separates what the couple is buying from how it reaches the room. Design lines should state the arrangement, quantity, scale, and important inclusions. Logistics should state delivery, installation, transfers, strike, and pickup. Rental lines should identify what must come back and the condition expected on return.

Bundling everything into each arrangement can make the proposal shorter, but it hides the reason a venue change affects the total. Separating logistics makes revisions easier to explain. The tradeoff is that the proposal needs disciplined language so it still reads as one coherent event, not a pile of fees.

Protect the price with assumptions and change rules

State the facts that make the price valid: event date, venue, arrangement counts, table plan, installation access, strike timing, floral direction, substitution boundaries, rental return terms, and how long the proposal remains open. These are operating inputs, not fine print. A change to one of them can change product, labor, or both.

Set a clear revision process before acceptance. After booking, treat count or scope changes as updates to the accepted proposal and event record. Do not let a new centerpiece count live only in an email. Reprice the affected recipe, labor, and logistics, then issue a revised total the couple can approve.

Check markup, gross margin, and overhead

Markup and gross margin are different measures. Markup describes what you add to cost to reach a selling price. Gross margin compares the gross profit with that selling price. Mixing the two can produce a proposal that looks profitable during estimating but does not meet the studio’s target.

Your method also has to support overhead that no single recipe captures, including workspace, software, insurance, utilities, equipment, sales time, and general administration. Choose a consistent way to recover those costs. Then test both each major design and the whole event, because a strong centerpiece line cannot rescue underpriced delivery or strike.

Use a repeatable pricing sequence

1. Confirm the event scope, venue access, counts, design direction, installation window, strike plan, and rental needs.
2. Create or adapt one recipe for every design, with stems, foliage, mechanics, and hardgoods.
3. Refresh ingredient costs and account for the units in which product can actually be purchased.
4. Estimate bench labor and event labor from the work each design and location create.
5. Add delivery, installation, transfers, strike, pickup, and rental handling as applicable.
6. Apply the studio’s overhead and profit method, then check the result at the line and event level.
7. Write the proposal scope and assumptions so a later change can be priced without reconstructing the estimate.

Example: a reception design with repurposed flowers

Suppose the plan includes guest table centerpieces, a couple’s table design, bar flowers, and ceremony pieces that move into the reception. Build separate recipes for each original design. Then add the labor, carts, packing materials, access time, and placement instructions required for the room move.

Repurposing can reduce the need for a second set of flowers, but it does not make the move free. Someone must remove, transport, reset, and check the pieces while guests and other vendors are working nearby. If the timeline cannot support that move, the honest proposal is a different design or additional labor.

Make the accepted proposal usable in production

Acceptance should turn the sales document into a production source. Aggregate the accepted recipes into a stem and hardgood order, organize builds by event and work area, and carry install and strike commitments into the timeline. The detailed recipe, proposal, and build list workflow explains that handoff.

Everbook keeps the priced recipe, proposal, build list, invoice, and Floral section on one connected event record. A changed count can update what the team builds as well as what the couple approved. That approach is useful for studios that want sales and production to share the same record; the platform overview explains the broader workflow.

Review the proposal before sending

• Every design line has a quantity, scale, recipe, and clear scope.
• Stem and hardgood costs reflect current purchasing conditions.
• Bench labor, event labor, delivery, installation, strike, and rentals are included where needed.
• Venue access, room moves, substitutions, and rental returns are stated as assumptions.
• The event meets the studio’s overhead and profit requirements as a whole.
• The accepted proposal can produce a build list without someone estimating the designs again.