PL EN

automation agents · operational apps

Operations lab

Automation agents and apps for companies that want measurable change. Every step within agreed bounds, every result with evidence.

Book a call kontakt@onosato.xyz
contract / rescheduleexample
task
reschedule a booking
access
calendar: read; booking system: propose a change
does not
refunds or payments
evidence
step log, before and after
decision
front desk approves or rejects
status
awaiting decision

01 — pillars

Two kinds of work, one way of acceptance

A / agents

Automation agents

An agent performs one defined task in a process. It knows what it can access, what it does not do and when it hands the case over to a person. Every result leaves a trace that can be checked.

  • checking documentation before it is filed with an authority
  • registering correspondence and attachments
  • reports generated from a single database

B / apps

Operational apps

Bookings, ticket and service sales, team dashboards. We build them around a specific client process, so that data from daily work can be measured and compared.

  • bookings of stays, places and dates
  • ticket and service sales
  • dashboards for the team and the owner

02 — how the lab works

Contract, work, review, evidence. A person makes the decision.

Before an agent starts, we write a contract: scope, access and acceptance criteria. A second agent checks the result against the contract. The result reaches a person together with the evidence.

run / one taskwindow

contract

scope, access, acceptance criteria

coder

performs the task

auditor

checks against the contract

loop: fix and review again until the auditor accepts the result

evidence

log, tests, before and after

human decision

approves or rejects

document flowwindow

source

unchanged

agent work

preparation and checks

for review

version v01 and decision card

approved

who, when, for what

archive

reason and successor

  • r1The source is never overwritten.
  • r2A correction is a new version; the reviewed one stays unchanged.
  • r3File checksums show what changed between sessions.
  1. 01

    Understanding the process

    We talk to the people who run the process every day and write it down step by step.

  2. 02

    Measurement

    We agree what we measure before the change and how we will read the result after it.

  3. 03

    Limited pilot

    The agent or app runs on a slice of the process, within the bounds written in the contract.

  4. 04

    Assessing effects and risks

    We compare measurements, review the evidence and name the risks before a decision is made.

  5. 05

    Rollout and maintenance

    After the client decides, we widen the scope and look after operation in the following months.

03 — acceptance

Three axes of acceptance

We assess the pilot result together with the client, separately on each axis. The criteria are written into the contract before the start.

axis 1

Operating bounds

Did the agent do only what was agreed: scope, permissions and the points where the case goes to a person.

axis 2

Business effect

Is the change visible in the measure agreed before the pilot, for example handling time, number of corrections or team workload.

axis 3

Algorithmic quality

Are the results correct, repeatable and verifiable on a sample prepared together with the client.

04 — work

What we are working on

  • Four-star hotel

    Digital sales for the whole hotel: its own sales platform, a new website and measurement. Code and architecture on our side.

    status in development

    • sales platform event tickets, bookings, sale of services and packages, marketing consents in development
    • new hotel website six languages, CMS with department roles, integration with the room booking system, keeping search rankings in development
    • measurement and consent sales analytics, cookie consent, withdrawal of marketing consent planned

  • Architecture studio

    An agent supports the design team in the documentation flow. It prepares and checks documents; the architects approve them.

    status pilot

    • document review flow source → agent work → review → approved → archive pilot
    • audit before filing documentation and the authority’s requests checked separately, with legal sources pilot
    • product register one database from which the team’s schedules are generated planned
    • correspondence and attachments recording correspondence and attachments with a document card planned

  • Amarra

    Marina berth bookings.

    status showcase project

  • Sailing Architects

    Berth bookings on sailing cruises with payment in instalments.

    status pilot

  • domy-modulowe.eu

    Website for modular house models with a panel for managing the offer.

    status pilot

05 — principles

Principles

A person approves

The agent prepares the result and the evidence. A decision that changes something in the company is made by a designated person on the client’s side. The agent does not approve documents that require professional qualifications.

Independent of the model provider

The contract and the process are not tied to one language model. The provider can be changed without rebuilding the deployment.

Client data kept separate

Each client’s data runs in a separate environment and does not mix with other clients’ data.

06 — contact

Let’s talk about one process

Briefly describe the process you want to change. We will reply with a proposed time for a call.

kontakt@onosato.xyz Book a call