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
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.
Andiamo pilot
At a glance
Who it is for
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.
The workflow we pilot
We start with one slice and make it dependable before widening it along the same job: proposal, deposit, the team job board, and the follow-ups that usually slip. Each step carries the status of the registry entry it rests on, and the step where a person decides is marked.
The labels are the registry's, the same on every page; the complete list is on the Trust page.
Inquiry
In developmentThe message lands in one inbox instead of someone's phone.
Record
In developmentContact details, stage, tags and the event details beside them.
Draft
In developmentOne draft per inquiry.
Approval
In developmentThe approved words are the words that send.
Then, along the same job
How the pilot runs
The pilot is agreed in writing before anything is switched on, and it widens one slice at a time.
Apply
We read every request and reply by email.
Map
What happens today, who does it, and where it gets stuck.
Agree
The proposal separates what exists today from what we would build. The agreement covers scope, data and how either side can stop.
Run and review
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
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.
Each 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.
What success means
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.
What happens after
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.
Tell us what happens today, who does it, and where it gets stuck. Please describe the kind of data involved, not the data itself.