Skip to content
Lamiak

Andiamo SMB · Florists

The price is agreed long before the cost is known.

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

The path this business already walks.

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.

  1. Look

    A look, a date and a budget arrive as one message

    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.

    Human approval
  2. Recipe

    A piece is stems and labour before it is a price

    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.

  3. Estimate

    A quote is a promise about flowers nobody has cut yet

    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.

    Human approval
  4. Substitutions

    The season moves between the agreement and the week of the event

    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.

    Human approval
  5. Market week

    The buy goes in late and the cooler starts filling

    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.

  6. Install

    You are building in someone else's room on someone else's clock

    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.

  7. Strike

    The vessels come back or they come out of the margin

    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.

    Human approval

What the work leaves behind

Each step ends in a record, not a feeling.

  1. Look

    In development
    • A client record holding the event date, the venue and the budget the client named
    • An enquiry reply drafted from the incoming message, held for review
  2. Recipe

    Planned
    • A per-piece recipe of stems, hard goods and bench hours
    • A cost for the event built from the recipe rather than from memory
  3. Estimate

    In development
    • Proposal options in the portal, with the substitution wording attached
    • A deposit recorded against the client, with the balance due before the date
    • A job card raised from the paid deposit, with a starter checklist
  4. Substitutions

    Planned
    • The client's text-message history in one timeline on their record
    • A change request carrying the substituted variety and the price adjustment it triggers
  5. Market week

    Planned
    • A job card for the event with the prep checklist on it
    • An order and conditioning list held with the event rather than on the bench
  6. Install

    Planned
    • A load-in schedule of setup, placement and breakdown for the crew
    • A view of the day for the client, derived from the same description
    • Freelance hands assigned to the event by role
  7. Strike

    Planned
    • Proposed record changes from a spoken note after strike, pending review
    • A count of hard goods out against hard goods returned, on the event record
    • A prepared balance reminder waiting on a person

What this leans on

The parts of the workspace this workflow needs.

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

In development

Client records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.

Approval-gated email drafts

In development

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.

Human approval

Services and price catalog

Planned

A maintained catalog of services and prices that proposals and invoices draw from.

Unified engagement record

Planned

One record per wedding or job that every task, document and message links to.

Proposals

In development

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.

Human approval

Client portal

In development

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.

Invoices and card payments

In development

Create invoices and let clients pay them by card through Stripe checkout; connecting a payment account and emailing invoices are still being built.

Deposit-to-job automation

In development

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.

Change requests

Planned

Track scope and schedule changes with the approval and price adjustment they trigger.

Human approval

Text-message history

In development

See each client's text-message history in one timeline on their record; replying from the timeline is not built yet.

Job board

In development

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.

Tasks

Planned

Assignable tasks with owners and due dates on each engagement, beyond the per-job checklists on the board.

Event-day schedules

In development

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.

Crew assignment

Planned

Assign team members to an engagement by role and see their availability.

Voice-memo updates

In development

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.

Human approval

Follow-up drafts

In development

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.

Human approval

Invoice reminders and appointment confirmations

Planned

Agents prepare payment reminders and appointment confirmations for a person to release.

Human approval

Questions this work asks

The things you would ask before moving anything.

Can it quote from a recipe rather than from a flat line?
The breakdown of stems, hard goods and bench hours is what makes an event costable, and a maintained catalogue for proposals and invoices to draw from is designed rather than built. Today that breakdown still lives in your own spreadsheet.
What happens when a variety is off the market the week of the event?
Today you change the recipe and tell the client over text. A change request that carries the swap together with the price adjustment it triggers, and waits for approval, is designed and not built.
Are stem costs or piece prices fixed by the software?
No. What a piece costs comes from your own recipe and what you paid that week, and the workspace holds no price list of its own. That is also why no prices appear on this page.
Does the crew get the load-in details, or only me?
A job card on the board carries the event and its checklist, and a load-in schedule of setup, placement and breakdown can be derived from one description of the day. Saving those schedules for a business is switched off by default and delivering them is not built, so today the crew still gets them from you.
Where does the rental stock sit?
On the event record, as a count of what went out against what came back. Chasing what did not return is still yours to do: the workspace holds the count, not the collection.
Can a client see the proposal and pay the deposit in one place?
Proposals, contracts to read, invoices and payment history sit in a portal the client reaches with an emailed link. Connecting a payment account, emailing invoices and online signing are still being built.
Does anything go to a client while I am up a ladder?
The drafted enquiry replies and follow-ups in development are held until a person approves the exact wording, and sending approved messages is still being built, so today those drafts stop at the review step.

What it runs on today

The tools this work is already spread across.

  1. A spreadsheet of stems

    The recipe for every piece, rebuilt for each enquiry and costed against what the last buy happened to cost.

  2. A wholesaler order form

    The buy, placed close to the date against availability you learn about the same morning.

  3. A phone full of reference pictures

    What the client sent, the shot of the finished bench, and the substitution agreed in a text thread nobody else can read.

  4. A cooler and a whiteboard

    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.

  5. A rental list on paper

    Vessels, stands and mechanics counted out of the studio and, if somebody remembers, counted back in.

Tell us how this runs for you today.