Separation between businesses
In developmentEach business's records are tagged to its organization, and database access rules limit staff to their own organization's data; known gaps in this separation are still being closed.
Andiamo pilot program
Build Andiamo around your business.
We are opening Andiamo to a small group of service businesses. You bring the real workflow. We build the system around it, with a person approving every message a client sees. You get a system shaped by your work, and we learn what it takes to run it well.
Who it is for
Owner-run service businesses that live in their inbox.
The pilot fits a business where inquiries arrive by email, the owner writes most of the replies, and a job moves from a first message to a proposal, a deposit and a day of work with a team. Wedding hair and makeup, beauty and wellness, photography and video, planners, florists and venues are where we start.
It fits if
- An owner or manager can review drafts and tell us why one was wrong.
- You can describe how a job moves from inquiry to delivery today, including where it gets stuck.
- You are willing to work with software that is still being built, with its status shown.
It does not fit if
- You need a finished product with a support contract right now.
- The work involves health records, payment card data or government identifiers.
The workflow we pilot
Inquiry to approved reply, first.
We start with one slice and make it dependable before widening it. A new inquiry arrives by email. Andiamo opens the client record and drafts a reply from your own details and tone. You read the exact message, edit it or approve it, and the approved words are the words that send. From there the pilot widens along the same job: proposal, deposit, the team job board, and the follow-ups that usually slip.
Approval-gated email draftsHuman approvalIn development
Client recordsIn development
ProposalsHuman approvalIn development
Deposit-to-job automationIn development
Follow-up draftsHuman approvalIn development
These labels are the same ones used across the site. In development means partly built and exercised in testing, with parts still missing.
How the pilot runs
Four steps, each with a person in the loop.
Apply
Tell us about the workflow through the form. We read every request and reply by email.
Map
If there is a fit, we map the workflow with the people who do it: what happens today, who does it, and where it gets stuck.
Agree
You get a written proposal that separates what exists today from what we would build, and a pilot agreement that covers scope, data and how either side can stop.
Run and review
We switch on one slice at a time. Every client-facing message is a draft until you approve it. We review the drafts, your edits and the results with you, and the system changes from what we learn.
Data boundaries
Ordinary business records only.
The pilot works with client contact details, job details, messages and documents of the kind a service business already keeps. Your records are tagged to your organization and access rules are set per organization. We are still closing known gaps in that separation and will not call it complete until they are closed.
- No health records, payment card numbers or government identifiers.
- Card payments are designed to run through your own connected payment account, not through us.
- Before the pilot starts, we list in writing which outside services receive your data and why.
- Your data is not used to train models unless you agree to that in writing.
- You can leave, and ask for your data to be returned and deleted.
What success means
You would keep it if we left.
We agree the measures with you before the pilot starts, and we measure them in your business, not in a demo. We publish no figures from a pilot without your written consent and a measured source.
- Inquiries get a reply you were happy to send, sooner than they do today.
- You edit fewer drafts over time, and the edits you make change what comes next.
- A job does not fall between the inbox, the proposal and the board.
- You can see who approved what, and you trust the record.
What happens after
A decision, in writing, both ways.
At the end of the pilot we review the results together. If it worked, you continue on terms set out in the pilot agreement, and what you taught the system stays with your business. If it did not, you leave with your data, and we tell you plainly what we could not make work.
Bring the workflow. We will build around it.
Tell us what happens today, who does it, and where it gets stuck. Please describe the kind of data involved, not the data itself.