Questions worth asking first.

Both, and they are separate. The service is working with your team to study a workflow, compare fixes and run a measured pilot. The software is the workspace we use to keep that work structured: evidence, maps, baselines, approvals and reports. You can start a conversation about the service without signing up for anything.

No. We start from the tools you already use. Where something is missing, the first options considered are usually a process change or a small piece of software around your current systems, not a replacement.

No. AI is one option among several. Many workflow problems are better solved by a clearer process, a checklist or ordinary software. Every comparison includes those alternatives — and doing nothing.

An Operational X-Ray focuses on one workflow. We talk with the people who do the work, observe real cases, map the process, record a baseline and compare improvement options. It ends with a map, an evidence-backed list of bottlenecks and one scoped pilot proposal.

A pilot is one small change on a defined scope for a defined period. Before it starts it has a measure, acceptance criteria, stop conditions, a rollback plan and an approver who did not propose it. Afterwards we compare the result with the baseline.

We record only what your organisation has authorised, and consent is tracked per company and per purpose — observation, storage, AI processing and publication are separate. Restricted records are hidden from read-only users and from reports shared outside the team. See the Security page for details and current limitations.

Yes, and for sensitive pilots it is required: the approver must be someone other than the person who proposed the change. Approvals, stops and other decisions are recorded with a note and cannot be edited afterwards.

Against the same measure recorded before the change, with the period, sample size and source stated. A result is only called observed when both sides were measured on a usable sample. A before-and-after difference is reported with its confounders, never as proof of cause on its own.

It is designed for service businesses where a few people carry most of the operational load. Starting with one workflow keeps the effort proportionate.

An automation agency usually starts from a technology and looks for places to apply it. We start from a workflow, measure it, and treat AI as one option to be compared against simpler ones — with the right answer sometimes being no AI at all.

Ampassador is founded and developed by Theodoros Ampas, who works with founders and operations leaders as an embedded AI partner. The founder leads the method and development of the software.

Tell us about one workflow you would like to understand better. We will reply to arrange a conversation. There is no obligation and no automated sales sequence.