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

How Lacy Bird stopped losing weddings to Excel

A real floral studio was up and running in a day and fully moved over from notebooks and three messengers within a week — to a single inbox and accurate estimates.

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

WhatsApp chats now arrive in one inbox tied to the customer card. Wedding estimates are built from master-catalog recipes, and markup gives the client price straight away. The client gets a live presentation by link, marks the blocks and signs the proposal from the phone.

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 birthday calendar started prompting on time.

What was hard

The hardest part wasn't the system — it was deciding to let go of the parallel notebooks. We were up and running in a day, moving three months of orders from Excel; by the end of the week the old sheets were gone and the team had retrained itself.

Read next

Guide

Wedding proposals in minutes: recipe → estimate → presentation

Why average wholesale prices eat wedding margin, and how to assemble a live proposal by link that the client approves from 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. Free plan — free with no time limit; Pro and Max — 14 days free to try.