← All resources
Case studyJun 15, 2026·6 min read

How Lacy Bird stopped losing weddings to Excel

A real floral studio went from notebooks and three messengers to a single inbox and stem-accurate proposals in one week.

How Lacy Bird stopped losing weddings to Excel

The shape of the problem

On a busy Friday the studio juggled three messengers, two notebooks and an Excel sheet for weddings. Quotes for the same bouquet came out with different prices depending on who answered. Two weddings were lost that month not because of the price — because the reply came two days too late.

What we changed

All chats now arrive in one inbox tied to the customer card. Wedding proposals are built from recipes — the system counts every stem and shows the margin live. The proposal goes out as a branded link in WhatsApp; the bride opens it on the phone within minutes.

What it changed in numbers

Time from inquiry to proposal dropped from ~36 hours to under 40 minutes. Wedding margin became visible during the call, not after the event. Repeat orders rose because the date reminders started landing on time.

What was hard

The hardest part wasn't the system — it was deciding to let go of the parallel notebooks. We migrated three months of orders from Excel in one afternoon; the team mostly retrained itself by Wednesday.

Read next

Guide

Wedding proposals in minutes: recipe → cost → photo

Why average wholesale prices kill wedding margin, and how to assemble a real, branded proposal that lands on the phone in 40 minutes.

Guide

WhatsApp Web or Business API: what to pick as a florist

Why a self-hosted WhatsApp Web bridge is the right starting point, and the two moments when you should switch to the official Business API.

See it on your own shop

Set up with your data and a 60-day free trial — try it with your real flower shop, not with examples.

1acc06b· 02.07 13:44