Skip to content
Lamiak

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.

Andiamo pilot

At a glance

You bring
The real workflow, and one person who can say why a draft was wrong.
We build
One slice first, inquiry to approved reply, with a person approving every message a client sees.
You keep
The system your work shaped, your data, and what you taught it, whichever way the pilot ends.

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.

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

  1. Inquiry

    In development

    A client writes in

    The message lands in one inbox instead of someone's phone.

  2. Record

    In development

    The client record opens

    Contact details, stage, tags and the event details beside them.

  3. Draft

    In development

    A reply is drafted from your own details and tone

    One draft per inquiry.

  4. Approval

    In development

    You read the exact message, edit it or approve it

    The approved words are the words that send.

    Human approval

Then, along the same job

ProposalsHuman approvalIn development
Deposit-to-job automationIn development
Follow-up draftsHuman approvalIn development

How the pilot runs

Four steps, each with a person in the loop.

The pilot is agreed in writing before anything is switched on, and it widens one slice at a time.

  1. Apply

    Tell us about the workflow through the form

    We read every request and reply by email.

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

  3. Agree

    A written proposal and a pilot agreement

    The proposal separates what exists today from what we would build. The agreement covers scope, data and how either side can stop.

    Human approval
  4. Run and review

    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.

Separation between businesses

In development

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

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

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.