Skip to content
Lamiak

Andiamo SMB · Beauty and wellness

Appointment-led work, with the history attached.

A chair, a room or a table booked again and again by the same people, where the value is in what the record remembers between visits.

How the work runs

The path this business already walks.

Written for Salons, barbershops, nail studios, beauty studios, spas and wellness practices that run on booked appointments rather than one-off projects.

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. Menu

    The services and the hours decide what can be booked

    Appointment work starts from two lists: the services offered, each with its own length, and the hours each team member works. A booking page reads both, so a client picks a service and a time rather than opening a conversation. Holding those lists as a maintained catalogue that proposals and invoices also draw from is planned, and so is describing a quiet Tuesday or a holiday once instead of declining requests one at a time.

  2. Request

    The client picks a service and a time, not a conversation

    A client choosing from a booking page is choosing a service with a known length against a person with known hours, which is why this work can be booked without anyone replying. The request arrives against the team member who offers it and lands on the client's record rather than in a separate diary. Keeping those bookings in step with the team's calendar is planned.

  3. Confirm

    Whether someone turns up is settled over text

    In this trade the deciding conversation is a text message, not an email. A client can confirm or cancel by replying to one, and the booking updates from the reply. The whole thread sits in one timeline on their record, so the next person to open it sees what was already agreed. Automatic replies stay switched off, and replying from the timeline is not built yet.

  4. In the chair

    What was done is worth more than that it happened

    A repeat client's record is the formula, the pressure, the shade, the thing they said they hated last time. That is the part usually kept in a notes app or on paper, and the part that walks out of the door when a team member leaves. A spoken update after the appointment becomes proposed changes to the record that wait for a person to apply or reject them; the review screen for those is not built yet.

    Human approval
  5. Payment

    The payment belongs to the visit, not to a separate terminal

    Raising the invoice against the appointment keeps the money and the record of what was done in one place, and the client can pay it by card or see their payment history and any published forms by signing in with an emailed link. Connecting a payment account and emailing invoices are still being built.

  6. Rebook

    The next visit is the whole business model

    A colour every six weeks, a massage every month, a fill every three: the revenue is in the return, and the gap between visits is the thing to notice. Preparing appointment confirmations and payment reminders for a person to release, and queueing follow-up drafts for approval, is where this is heading. The drafts exist in development; releasing them is planned.

    Human approval

What the work leaves behind

Each step ends in a record, not a feeling.

  1. Menu

    Planned
    • A service, with its length, attached to every request the page takes
    • The hours a team member is bookable for, as the page offers them
  2. Request

    Planned
    • An appointment against the team member who offers the service
    • The appointment's status, from booked through to completed, cancelled or no-show
  3. Confirm

    In development
    • The client's text-message history in one timeline on their record
    • An appointment status updated from the client's own reply
  4. In the chair

    In development
    • Visit notes on the client record, with lifecycle stage and tags
    • Proposed record changes from a spoken update, pending review
  5. Payment

    In development
    • An invoice raised against the client, payable by card
    • A payment history the client can see in the portal
  6. Rebook

    Planned
    • Follow-up drafts queued for a person to approve or reject
    • Prepared confirmations and reminders 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.

Online booking

In development

Clients request a time from a team member's online booking page; calendar sync is still being built.

Services and price catalog

Planned

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

Calendar sync

Planned

Keep bookings and claimed jobs in step with the team's Google Calendar.

Text replies to appointments

In development

Clients can confirm or cancel a consultation by replying to a text, and the booking updates; automatic replies stay switched off.

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.

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

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.

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.

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.

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 two team members offer the same service on different hours?
Yes. Each team member has their own booking page and their own weekly hours, and the bookable times come from those rather than from a shop-wide setting.
Does a client have to install anything to confirm?
No. A client can confirm or cancel by replying to a text message, and the booking updates from that reply. Automatic replies stay switched off.
Where does a regular's history live?
On the client record: lifecycle stage, tags, visit notes and the text-message history in one timeline. Replying from inside that timeline is still being built.
Can I keep my own lengths and prices?
Each service carries its own length, and the values the workspace starts with are defaults to replace rather than a price list. That is why no lengths or prices appear on this page.
What happens to the gap a cancellation leaves?
An appointment carries a status through booked, confirmed, completed, cancelled and no-show, so the history stays honest about what happened. Filling the gap on its own is not something the workspace does.
Do I have to run the books somewhere else?
Invoices and card payments sit in the workspace against the client. Connecting a payment account and emailing invoices are still being built, so today that part is not finished.

What it runs on today

The tools this work is already spread across.

  1. A booking page

    Clients request times out of the hours you publish, with each service's length already known.

  2. A phone with the client's number in it

    The text thread that actually decides whether someone turns up, held outside any record of the visit.

  3. A card reader at the desk

    The payment, taken apart from the note of what was done.

  4. A notes app or a paper card

    The formula, the shade, the pressure, the thing they asked for last time, kept by one team member.

  5. A reminder you set yourself

    The nudge for the visit that is due, which arrives only if someone remembered to set it.

Tell us how this runs for you today.