Amybuilds

Your process becomes an application.
Without writing software.

Once a process is mapped and reviewed, it runs as an application for your team. Everyone sees their cases there, Amy does the routine and brings decisions to the right person. Reading quotes, checking budgets, creating PDFs, sending emails, calling your systems through their interfaces: all within the rules you set, with every step in the history.

  • No code, no deployment
  • Decisions stay with people
  • Every step in the history
Your team’s home in Amy: Amy welcomes Maya and offers apps, procedures, messages and colleagues.

How a case runs.

A purchase with everyone involved: Lena uploads the quote, Amy checks it against the budget in the ERP, Jonas approves because the amount is over €2,500, and Amy sends the order as a PDF to the supplier.

A purchase request, from quote to order

Illustrated example. Press play and follow the case step by step.

Your team

Lena

Operations

  • Uploads the supplier quote
  • Hears the order is placed

Jonas

Head of operations

  • Approves the order at 14:02

Amy

Runs the purchase procedure

Your ruleOrders over €2,500 need the head of operations.

  1. Reads the quote: 14 items, €4,800
  2. The budget covers it
  3. Over €2,500, so Jonas decides
  4. Approved, so the order goes out
  5. Done. Every step is in the case history.

Your systems

Your ERP

Over its own API

  • Budget left: €12,300
  • Order PO-089 placed

Purchase order

PDF

  • PO-089.pdf created

Email

To the supplier

  • Sent to Acme with the PDF

What your team asks Amy for is a skill.

A skill is a process or a result from your model that Amy carries out for your team. It comes from what you described about your work.

A process.

Several steps, several roles. The purchase above is a skill: Amy runs the process, the approval stays with Jonas.

A result.

One person asks, Amy delivers: a quote text, an analysis, a report as a PDF. Every time by the rules you set for it.

For the roles you choose.

You try a skill, switch it on and decide which roles can ask for it. Until then nobody on the team sees it.

What Amy takes on in a case.

Your model decides which of these a step uses.

Read in data.

Lists and quotes from Excel, CSV or Word. Amy carries the details into the case.

Check and present.

Amy checks details against your rules. Where approval is needed, she brings the decision to the right person.

Create documents.

Purchase orders, confirmations and reports as designed PDFs.

Send emails.

To verified recipients, with the content from the case.

Call your systems.

Your systems through configured REST APIs or MCP tools.

Show the overview.

Tables, boards, timelines and charts, fitted to the task and to the person’s permissions.

Describe. Rehearse. Release.

You maintain the model, not the code. Amy provides the runtime and the interface.

Describe.

Map the process with Amy, assign people to roles, set up connections to your systems.

Rehearse.

Play every role and make every decision in the sandbox, without touching live operations.

Release.

The process appears for the people assigned to it. Running cases keep the rules they started with.

You set the boundaries.

Amy checks every action against your model before it changes anything. Data changes the model doesn’t provide for are rejected.

Which AI works.

You decide which AI models are allowed, local ones included. Every call and its estimated cost is visible.

Who may do what.

Each person sees only the cases of their role. Amy checks permissions at every step.

Where a person decides.

When your rule requires approval, Amy prepares the decision and waits. She never makes it herself.

What happened.

Every step is in the history: who, what, when. Running cases keep the rules they started with.

Try it, no sign-up.

Expense Approval as a live sample: switch between employee, manager and finance, and take a claim all the way to reimbursement.

Which routine will you hand off first?

Start with a recurring process your team knows well. Amy maps it with you and brings it into your team’s everyday work.

Tell Amy how your team works