Sound familiar?
What florists tell us before a project starts.
- On holiday week the phone, website and wire orders all become paper tickets.
- Delivery routes are planned by hand the night before and change by noon.
- Wedding quotes take an evening each and half never reply.
- We order flowers from the wholesaler by gut feel and either run out or toss stems.
- Customers ask where their delivery is and we have to call the driver.
What we build
Each one is a working piece you can open and check when it's done.
One order list
Web, phone and in-store orders brought into one list sorted by delivery date and time, with a printable ticket for the design table.
API integrations and data sync n8n, Make and Zapier automationDelivery routes
The day's deliveries grouped by area and time window, with a route for each driver and a text to the recipient when it is on the way.
Python scripts and utilities API integrations and data syncWedding and event quotes
A short inquiry form, a quote built from your packages, and a follow-up that goes out if the couple has not replied.
Google Sheets and Apps Script automation CRM setup and lead pipelinesWholesale order sheet
Orders for the next days turned into the stems and supplies to buy, so the wholesaler order is a check, not a guess.
Google Sheets and Apps Script automation Python scripts and utilitiesReminders for repeat occasions
Birthdays and anniversaries from past orders, with a gentle reminder to the customer a week before.
n8n, Make and Zapier automationPeak-day numbers
Orders, deliveries and revenue by day through a holiday week, on one page you can read at the counter.
Dashboards and reportingFlorists software we work with: Square, Shopify, WooCommerce, Lightspeed.
And the general tools around it: QuickBooks, Google Sheets, Google Calendar, Mailchimp, Twilio, Stripe, Zapier, Make.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Holiday week ticket board
Example: a shop that takes orders by phone, web and a wire service wants them in one sheet sorted by delivery slot, with a printable ticket for each arrangement.
Website orders, Google Sheets, PDF ticketsExample project
Driver route and arrival text
Example: a florist with three vans wants the day's deliveries grouped by area, and the recipient texted when the driver is about ten minutes away.
Order list, routing, TwilioExample project
Wedding quote follow-up
Example: a studio sends a quote after each consultation and wants a note to the couple after three days and again after a week if there is no reply.
Form, CRM, emailQuestions people ask first
Do we have to leave our wire service?
No. We work around it. Orders you receive and send through it can be brought into your own list by email or export, as far as the service allows.
Who owns what you build?
You do. It is built in your own accounts, and you get notes on how it works so your team can change it without us.
Will it hold up on Valentine's week?
We build and test for your busiest day, not an average one, and keep a paper fallback in the notes.
How do we start?
Tell us which tools you use and the one thing that wastes the most time each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com