Client records
In developmentClient records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.
Andiamo SMB · Florists
A look quoted from pictures, stems priced by whatever the market has that week, and an install window borrowed from someone else's venue.
How the work runs
Written for Event and wedding florists and floral designers who quote from a look, buy from a market, and build and install against a date that does not move.
Steps marked for approval wait for a person. Andiamo SMB is not yet offered to customers; the parts each step leans on, and how far along they are, are listed further down.
Look
An enquiry for event work carries pictures of something somebody else made, a venue, a date that will not shift, and a figure the client already has in mind. Those details decide whether the job is worth taking, and they belong on the client record from the first message rather than split between a mailbox and a saved folder. The reply is drafted from the incoming message and held until a person has read the exact wording; sending approved replies is still being built.
Recipe
Nothing can be quoted until the work is broken down the way it is actually bought and built: stem counts per piece, the hard goods it stands in, and the bench hours it takes to make. That breakdown is the only thing that makes an event costable, and today it usually lives in a spreadsheet rebuilt from scratch for every enquiry. Holding recipes as a maintained catalogue that proposals and invoices draw from is designed and not built, and so is one record per event that every document and message hangs off.
Estimate
What protects the margin is being explicit in the document itself: what is being priced, how substitutions will be handled, and what happens when the market moves under the design. Proposal options a client reviews and chooses from in the portal are in development, and sending one waits for a person to approve the exact document, though delivery is still being built. Once the deposit clears, the event can become a card the whole studio works from.
Substitutions
A crop fails, a colour comes in the wrong shade, the variety that carried the whole palette is not on the market that week. Each swap changes the recipe and often the cost, and the client has to be told in a way that does not reopen the design. Today that conversation happens over text and stays on the phone that had it. Text-message history in one timeline on the client record is in development; recording a substitution with the price adjustment it triggers, held for approval, is designed and not built.
Market week
Buying happens close to the date because the material will not wait. The wholesaler order, the market run, the conditioning that starts the moment boxes land, and the order pieces are built in are one dependent chain, and a step missed on the earliest morning shows up in what goes on the van. A board of job cards with a checklist on each is in development; assignable tasks with owners and due dates across the whole event are designed and not built.
Install
The window is whatever the venue leaves between the previous booking and the guests arriving, and it is shared with the caterer, the lighting crew and the band. What the crew needs is the load-in door, the hours either side of the window, what goes where, and who is carrying it. From one description of the day, a logistics view of setup, placement and breakdown can be derived alongside a view written for the client. That generator is exercised in testing, saving the schedules for a business is switched off by default, and delivering them is not built. Assigning freelance hands to the event by role is designed and not built.
Strike
Stands, vases, candelabra, mirror plates and mechanics go out with the flowers and are the studio's own stock. Somebody has to collect them, count them against what left, and chase what did not come home, usually the morning after a long day. A spoken note on the drive back becomes proposed changes to the record that wait for a person to apply or reject them, and the review screen for those is not built yet. Follow-up drafts prepared for a person to approve are in development, and preparing the balance reminder for a person to release is designed and not built.
What the work leaves behind
What this leans on
Each card carries its own status. Parts in development are partly built and exercised in testing; planned parts are designed and not built yet. The full list for Andiamo SMB is on the product page.
Client records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.
Replies to new client inquiries are drafted from incoming email and held until a person reviews and approves the exact message; sending approved replies is still being built.
A maintained catalog of services and prices that proposals and invoices draw from.
One record per wedding or job that every task, document and message links to.
Proposals with options that clients can review and choose from in the portal; sending a proposal waits for a person's approval, and delivery is still being built.
Clients sign in with an emailed link to see their invoices and payment history, view their contracts and proposals, and fill in forms their provider publishes; online signing is still being built.
Create invoices and let clients pay them by card through Stripe checkout; connecting a payment account and emailing invoices are still being built.
When turned on for a business, a paid deposit creates the job card on the team board with a starter checklist; the checklist content and team notifications are still being built.
Track scope and schedule changes with the approval and price adjustment they trigger.
See each client's text-message history in one timeline on their record; replying from the timeline is not built yet.
A drag-and-drop board of jobs with stages and a checklist on each card; letting team members claim open jobs is built but switched off by default.
Assignable tasks with owners and due dates on each engagement, beyond the per-job checklists on the board.
From one description of an event day, two schedules are derived: a logistics view of setup, per-person service slots and breakdown for the crew, and an experience view for the person being served. The generator is exercised in tests; saving the schedules for a business is switched off by default, and delivering them is not built yet.
Assign team members to an engagement by role and see their availability.
A spoken update is turned into proposed changes to the client record, which wait for a person to apply or reject them; the review screen is not built yet.
An agent prepares client follow-up drafts and queues them for a person to approve or reject; sending approved follow-ups is not built yet.
Agents prepare payment reminders and appointment confirmations for a person to release.
Questions this work asks
What it runs on today
The recipe for every piece, rebuilt for each enquiry and costed against what the last buy happened to cost.
The buy, placed close to the date against availability you learn about the same morning.
What the client sent, the shot of the finished bench, and the substitution agreed in a text thread nobody else can read.
What is conditioning, what is built and what still has to be on the van, written where only the people in the room can see it.
Vessels, stands and mechanics counted out of the studio and, if somebody remembers, counted back in.