New — Introducing Yaju Software Factory — Try the tool for free
Explore nowPlatform
Functionalities
Use Cases
Deployment
By Industry
Explorations
Initiatives
Product
We put new capability in front of a small number of teams before it ships. This is what that involves on both sides, including the parts that are inconvenient for the people taking part.
Yaju Team · 28 May 2026
Shipping agent capability without watching real teams use it produces features that are correct and unhelpful. We have done that, and the early access programme is the correction.
Access to capability before general availability, and direct contact with the people building it rather than a support queue.
More usefully, influence. Almost everything that changed in Oran 3.6 came from watching teams hit something we had not anticipated. Per-agent attribution being used as an inventory tool rather than a cost tool. Budgets set deliberately tight and used as a signal rather than a guard rail. Those changed the product.
That you use it on real work rather than a sandbox. A pilot built to try the feature tells us the feature works under conditions we chose, which we already knew.
That you tell us when it is wrong. The useful reports are the awkward ones: this is slower than our old process, this produced something we had to unpick, we turned it off after a week.
That you accept the rough edges. Early access means the documentation lags, the behaviour changes between builds, and something occasionally does not work.
We do not use participation as a pricing lever, and we do not require a case study. A team that tries something, decides it is not for them and says so has given us the most valuable thing available.
We also do not put early capability outside the governance layer. Ownership, attribution, policy enforcement, audit and evals apply exactly as they do in general availability. Capability that arrives ungoverned is not early access, it is a liability we shipped ahead of schedule.
Teams already operating agents with some rigour: owners assigned, spend attributed, some evaluation in place. Not because we are precious about it, but because a team without those cannot distinguish a problem with the new capability from a problem with their setup, and neither can we.
The Agent Orchestration System pages cover what is generally available today. To ask about participating, write to contact@capconsultor.eu.
