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
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.
Inquiry
A new inquiry becomes a client record
Contact details, event date, venue and party size are kept together.
Proposal
A proposal is drafted from the record
Services and prices are laid out for the client.
Human approvalBooking
Contract and deposit
The client reviews the contract and pays the deposit through the client portal. Online signing is still being built.
Team
The job goes on the team board
A team member claims it, and the checklist travels with the card.
Follow-up
The assistant drafts the follow-ups
Each message waits for a person to approve it.
Human approvalEvent 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
- 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
2 Apr 2026 · Sam Example
Asked for a trial in August. Prefers a soft, natural look.
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 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.
Team
Job board
Job boardIn development
Deposit-to-job automationIn development
Board
Inquiry
No jobs in this example
Proposal
No jobs in this example
Booked
No jobs in this example
Prep
Ava Example - 17 Oct - Example Vineyard (this job)
Event day
No jobs in this example
Complete
No jobs in this example
Card · Prep · claimed by Sam Example
The card appeared on the board when the $330 deposit was paid on 11 Apr 2026, with the starter checklist on it.
Checklist · 2 of 5 done
- Confirm the deposit (done)
- Hold the trial session (done)
- Agree the running order with the venue (to do)
- Bring in the second artist for the party (to do)
- Ask the client for the balance (to do)
Owners and due dates
A paid deposit puts the card on the board; the checklist content it starts with is still being built. Giving each item an owner and a due date is planned, so this part of the example is marked as planned.
| Item | Owner | Due |
|---|---|---|
| Confirm the deposit | Sam Example | 11 Apr 2026 |
| Hold the trial session | Sam Example | 15 Aug 2026 |
| Agree the running order with the venue | Sam Example | 3 Oct 2026 |
| Bring in the second artist for the party | Noa Example | 3 Oct 2026 |
| Ask the client for the balance | Sam Example | 10 Oct 2026 |
TasksPlanned
Schedule
Event day
Online bookingIn development
Event-day schedulesIn development
Consultation, requested from the booking page
- What
- Trial session
- Requested
- 12 Apr 2026
- Held
- 15 Aug 2026 at 17:00
- Length
- 90 minutes with Sam Example
- State
- Completed
Running order · 17 Oct 2026 · Example Vineyard
One slot per service, laid out from the services on this example record so the morning ends before the party has to be ready.
| Time | Person | Service | Artist |
|---|---|---|---|
| 08:30–09:15 | Bea ExampleBridesmaid | Hair | Noa Example |
| 09:15–10:00 | Cleo ExampleBridesmaid | Hair | Noa Example |
| 09:30–10:45 | Ava ExampleBride | Hair | Sam Example |
| 10:00–10:45 | Dana ExampleBridesmaid | Hair | Noa Example |
| 10:45–11:45 | Ava ExampleBride | Makeup | Sam Example |
| 10:45–11:30 | Elena ExampleBridesmaid | Hair | Noa Example |
| 11:30–12:15 | Fran ExampleBridesmaid | Hair | Noa Example |
Ready by 12:30 · First look 13:00
Crew
- Sam ExampleLead artist2 slots
- Noa ExampleSecond artist5 slots
The artist on each row is a crew assignment. Assigning team members to a job by role, and seeing who is free, is planned, so the crew part of this example is marked as planned.
Crew assignmentPlanned
Client side
Client portal
Client portalIn development
Invoices and card paymentsIn development
Ava Example signs in with a link emailed to ava@example.com, and sees only this job.
Invoices
- DepositPaid by card 11 Apr 2026$330
- BalanceDue 10 Oct 2026$770
Documents
- Proposal - Bride and partyProposal · updated 11 Apr 2026Accepted
- Service agreementContract · updated 10 Apr 2026Shared for review
The agreement is shared here for the client to read. Signing it in the portal and keeping the signed copy on the record is planned.
Contracts and e-signaturePlanned
Forms
- Event-day detailsUpdated 2 Sept 2026Completed
Messages
Messaging the business from inside the portal, with the thread attached to this job, is planned. In this example the conversation happens over email and text instead.
Client portal chatPlanned
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.
Wedding hair and makeup
A wedding party is not one appointment.
One inquiry that lands months out, a trial, a party broken down person by person, and two different schedules for the morning of the day.
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.
Photography and videography
You sell a date once, then work for weeks.
A single day that can only be booked by one couple, and a job that runs on long after the cameras have gone back in the bag.
Wedding and event planners
You direct a team you do not employ.
One enquiry, a scope drawn on paper, then months as the single point between a couple and every supplier, on a timeline that keeps moving.
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.
Venues
The date is the thing you sell, and you hold only one of each.
An enquiry for a date, a show round, a deposit that turns a courtesy into a booking, then months of quiet before every detail arrives at once.
Planned, not written yet
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 developmentA 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 developmentClient records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.
Voice-memo updates
In developmentA 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 developmentSee 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 developmentClients can confirm or cancel a consultation by replying to a text, and the booking updates; automatic replies stay switched off.
Proposals
In developmentProposals 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 developmentCreate 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 developmentClients request a time from a team member's online booking page; calendar sync is still being built.
Client portal
In developmentClients 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 developmentWhen 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 developmentReplies 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 developmentAn 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 developmentFrom 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.
Contracts and e-signature
PlannedSend contracts for electronic signature and keep the signed copy with the client; electronic signing is still being built.
Calendar sync
PlannedKeep bookings and claimed jobs in step with the team's Google Calendar.
Invoice reminders and appointment confirmations
PlannedAgents prepare payment reminders and appointment confirmations for a person to release.
Human approval
Unified engagement record
PlannedOne record per wedding or job that every task, document and message links to.
Tasks
PlannedAssignable tasks with owners and due dates on each engagement, beyond the per-job checklists on the board.
Change requests
PlannedTrack scope and schedule changes with the approval and price adjustment they trigger.
Human approval
Crew assignment
PlannedAssign team members to an engagement by role and see their availability.
Services and price catalog
PlannedA maintained catalog of services and prices that proposals and invoices draw from.
Client portal chat
PlannedMessage clients inside the portal with the thread attached to their engagement.
Moving from your current CRM and task board
PlannedA 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
Public API, SDK, MCP server and CLI
PlannedPlanned programmatic access to clients, jobs, appointments, messages, documents and invoices; today only a read-only endpoint for email drafts exists, in testing.
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
PlannedA 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
01 Inventory
List every client, job, document and open payment
02 Normalize
Map records from both tools onto one client and job
03 Reconcile
Match the CRM and the board, job by job, and review the gaps
Human approval04 Re-check
Refresh the export from the old tools and compare again; nothing is written back to them
05 Switch
An owner approves, then the reviewed import is applied
Human approval06 Archive
Keep the old account read-only for reference