Skip to content
Lamiak

Andiamo SMB

One operating workspace for your service business.

Clients, bookings, proposals, contracts, payments and the team's job board in one place, with an assistant that drafts and a person who decides.

One job, start to finish

From inquiry to event day, in one place.

This is the path the workspace is designed around. Steps marked for approval wait for a person; what exists today is listed under Status.

  1. Inquiry

    A new inquiry becomes a client record

    Contact details, event date, venue and party size are kept together.

  2. Proposal

    A proposal is drafted from the record

    Services and prices are laid out for the client.

    Human approval
  3. Booking

    Contract and deposit

    The client reviews the contract and pays the deposit through the client portal. Online signing is still being built.

  4. Team

    The job goes on the team board

    A team member claims it, and the checklist travels with the card.

  5. Follow-up

    The assistant drafts the follow-ups

    Each message waits for a person to approve it.

    Human approval
  6. Event day

    Everyone works from the same record

    Schedule, checklist and client details in one place, once the unified record is built.

Example

One wedding, four views.

A walkthrough of one invented job. Each view shows the status of what it depicts, and the parts that are only planned are labelled where they appear.

Synthetic dataSynthetic example data. Names, dates and amounts are invented for illustration.

Example workspace

Job EX-0001

Ava Example - 17 Oct - Example Vineyard

An inquiry in April, a proposal the client picked from, a deposit that put the job on the team board, and the morning of the event itself.

Record

Client record

Client recordsIn development
ProposalsHuman approvalIn development

Client and event

Client
Ava Example
Email
ava@example.com
Phone
+1 555 0142
Stage
Prep
Event date
17 Oct 2026
Venue
Example Vineyard
Party size
6
Ready by
12:30, first look 13:00
  • Wedding
  • Party of six
  • Trial done

How it started

A form on the business's own site, received 2 Apr 2026:

Hi! Getting married in October and would love a trial in August if you have space.

Notes

  1. 2 Apr 2026 · Sam Example

    Asked for a trial in August. Prefers a soft, natural look.

  2. 15 Aug 2026 · Sam Example

    Trial done. Agreed on the softer style, and a second artist for the party.

Proposal · sent 5 Apr 2026 · Accepted

Bride and party

Chosen by the client

Hair and makeup for the bride, hair for five bridesmaids, and one trial session.

  • Bridal hair and makeup$475
  • Bridesmaid hair x 5$475
  • Trial session$150

Total$1,100

Deposit 30% · $330

Bride only

Hair and makeup for the bride, and one trial session.

  • Bridal hair and makeup$475
  • Trial session$150

Total$625

The client accepted 11 Apr 2026 and paid the 30% deposit of $330 by card, leaving $770 due 10 Oct 2026. Amounts in this example are invented, not a rate card.

Every view above reads from this one example. Holding a single record per job that each task, document and message links to is planned.

Unified engagement recordPlanned

Industries

The same workspace, read against one trade at a time.

A booking is not the same shape in every business. These write-ups follow one trade from the first message to the work being done, and name what exists today at each step.

Status

What exists today, and what is next.

Andiamo SMB is not yet offered to customers. Parts in development are partly built and exercised in testing; planned parts are designed but not built.

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.

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.

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

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.

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.

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

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.

Online booking

In development

Clients request a time from a team member's online booking page; calendar sync is 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.

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.

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

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

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.

Planned

Contracts and e-signaturePlanned
Calendar syncPlanned
Invoice reminders and appointment confirmationsHuman approvalPlanned
Unified engagement recordPlanned
TasksPlanned
Change requestsHuman approvalPlanned
Crew assignmentPlanned
Services and price catalogPlanned
Client portal chatPlanned
Moving from your current CRM and task boardHuman approvalPlanned
Public API, SDK, MCP server and CLIPlanned

The complete list, with what each planned part is meant to do, is on the Trust page.

Moving over

A planned, staged switch.

Many service businesses keep clients in one tool and jobs on a separate task board. Andiamo holds both. Moving is planned in stages, and a person reviews a reconciliation report before anything is switched.

Moving from your current CRM and task board

Planned

A read-only export, a reconciliation report, then an import an owner approves, with nothing written back to the old tools; the import tooling is still being built.

Human approval
  1. 01 Inventory

    List every client, job, document and open payment

  2. 02 Normalize

    Map records from both tools onto one client and job

  3. 03 Reconcile

    Match the CRM and the board, job by job, and review the gaps

    Human approval
  4. 04 Re-check

    Refresh the export from the old tools and compare again; nothing is written back to them

  5. 05 Switch

    An owner approves, then the reviewed import is applied

    Human approval
  6. 06 Archive

    Keep the old account read-only for reference

Tell us how your bookings run today.