The enquiry arrives
From your website's intake form — built for floral enquiries, so it already asks about the date, the venue and the budget — or pasted straight from an email or WhatsApp. Either way it lands on your pipeline with nothing retyped.
Chalmsy for florists
Florist proposal software,
fluent in flowers.
Stems, buckets, wholesale runs, hard goods, the 4am market alarm — floral work has its own arithmetic, and most business software has never heard of it. Chalmsy grew up inside a working floral & events studio, so it arrived already knowing what a flower recipe is, what a markup rule does, and why a wedding proposal has to be beautiful.
Flower recipe software, built in
It knows what a recipe is.
Not a metaphor — an actual floral recipe. "24 × David Austin roses, 30 × ranunculus, eucalyptus, vessel, labour" is something Chalmsy reads, stores and prices, stem by stem.
- Per-stem recipes — every arrangement broken into flowers, quantities and units, saved and reusable. A bridal arch you've built once is a recipe you drop into the next proposal.
- Wholesale cost lists — keep your growers and wholesalers on file with the prices you actually buy at, ready to pull into a quote.
- Your own markup rules — 5× on fresh, 3× on hard goods, or whatever your studio works to. Set it once and every proposal costs itself from your real numbers, not a template's guess.
- A price guide that remembers — rates, materials and labour in one place, so nobody prices a peony from memory at eleven at night.
- Palette & assembly notes travel with the recipe, so the brief your freelancers see matches the quote the client signed.
Your wholesale ordering itself stays however you run it today — Chalmsy prices the work and keeps the record; it doesn't place market orders for you.
Bridal arch — garden style
Blush, ivory & sage · serves ceremony + repurpose
| Stem | Qty | Cost |
|---|---|---|
| David Austin rose — Patience | 24 | $96.00 |
| Ranunculus — Hanoi | 30 | $52.50 |
| Delphinium — pale blue | 18 | $41.40 |
| Eucalyptus — cinerea | 12 | $21.60 |
| Mechanics, foam-free base & hire | — | $84.00 |
Cost → quoted at your markup
$295.50 → $1,180
Illustrative data
Enquiry to final invoice
The whole commission, in the studio's language.
The proposal writes itself first
Chalmsy drafts the full proposal from the enquiry — in your voice, because it learned from proposals you've already sent, and at your prices, because your recipes and markups sit behind it. You shape it; it never ships without you.
Worked through, then signed
The couple and the planner each get their own private link. They comment on the line they mean, suggest what's missing, and sign off properly — a code to their own inbox, the agreed version locked with their name on it.
The booking holds every detail
Venue, run of day, freelancers, the mood board in Drive, the email thread — one card carries the whole wedding, and the calendar knows about it without being told twice.
Deposits & balances follow
The invoice builds itself from the proposal the client accepted — deposit now, balance before the day, sent from your own email address. And when a sent proposal goes quiet, a polite chase is prepared on schedule, with you on the send button.
The books keep themselves
Photograph the market receipt in the van and it files itself. By month end the P&L already knows whether wedding season actually made money — per entity, if you trade through more than one.
Some of these follow the plan: intake forms join at Studio, bookkeeping at Practice — the pricing grid has every line.
Why it's fluent
Built inside a working studio — not adapted for one.
Chalmsy exists because a working floral & events studio needed software that simply wasn't for sale: software that understood quoted, visual, seasonal work — and represented the studio's own brand, not the software company's. The first workspace Chalmsy ever ran belongs to that studio, and it has run every proposal, invoice and client record since spring 2026.
Florists ask
Fair questions, straight answers.
Do I need a Google account?
Yes — Chalmsy runs on one. It's how your proposals and invoices go out from your own address rather than a no-reply robot, how your enquiry threads sit beside the booking they belong to, and why there's no Chalmsy password for anyone to steal. A Gmail or Google Workspace address is all it takes. If your business email lives on Microsoft or elsewhere, Chalmsy isn't for you yet — we'd rather say so now than after you've moved.
Will the proposals actually look like my studio's?
Yes — that's the point. Your logo, your colours, your typefaces and your voice dress every proposal, every invoice and the workspace itself. Clients see your studio, never Chalmsy. See how the brand system works.
I keep my recipes and prices in a spreadsheet. Do I have to rebuild everything?
No. Start with one commission: paste the enquiry, let Chalmsy draft the proposal, and add recipes as you go — each one you save prices the next job faster. Your client list imports from a CSV whenever you're ready.
Does it replace my wholesaler or ordering tools?
No — and it doesn't pretend to. Chalmsy holds your recipes, your suppliers and the prices you buy at, and uses them to cost and win the work. How you place the market order stays yours. If you use a dedicated ordering tool, Chalmsy sits happily alongside it.
What does the AI do with a florist, specifically?
It reads the enquiry and drafts the proposal in your voice, priced from your recipes and markup rules. It reads receipts you photograph. It writes up the client call you record on the drive home. And nothing it drafts reaches a client until you've read it and pressed send.
Is this wedding florist software or flower shop software?
Wedding and event floristry — proposals, recipes, invoices, the books. It is not retail point-of-sale: if you run a counter, keep your POS and let Chalmsy run the commission side, where the money is quoted before it's earned.
Stay calmsy
Bring one wedding across.
Start free, paste one enquiry, and see whether the next proposal takes ten minutes instead of an evening after the market run.