What practice is actually in the public record?
The services page states that the founders build and operate Scenaryo (web and mobile) and Tiding, and that they use bounded coding agents, automated checks, and localisation workflows to ship and maintain them. Company facts, including who the founders are, live on /about.
A bounded agent gets one task, a limit on what it may change, and a check a person can review. The team keeps product intent, access, and release decisions. That is the operating description we are willing to publish. Counts of agents, tokens, or hours saved on this workflow are not in the public source we used, so they are absent here.
Why is this linked from logistics?
Logistics teams ask how a small group keeps agents inside a workflow. The practice above is ours, from product engineering, and the logistics page links here so the question has a primary source. It is not evidence from a logistics client.
When a mid-market team wants the same kind of boundary drawn around one of their workflows, the priced start is the AI Audit at €3,000 for one week, or the Agentic Automation Review at €1,000 for three days if the workflow is already chosen. Building one agreed agent is an AI Pilot from €20,000.
Questions about this draft
Is this a client case study?
It is an own-ops draft about Leapfrog AI’s products, Scenaryo and Tiding. It is not a client engagement and it includes no client metrics.
What can a buyer commission from this practice?
The AI Audit is €3,000 for one week and produces a roadmap. The Agentic Automation Review is €1,000 for three days on one workflow. An AI Pilot starts at €20,000 and builds one agreed use case over six weeks.