Start with what already runs in your company: the agents.
The first offer is to organize and govern the agents and AI uses that already exist. Decisions come later, once the base is in place. Each stage ends with your decision.
How we start
The first step is the Organization & Agents hub: giving an owner, a limit and proof to what already runs. Decisions come later, once the base is ready.
Map
We survey the agents and AI uses the company already has, on any platform, and who answers for each one.
Organization & Agents
Organize
People and agents go on the same map. Each agent gets an owner, a team and a limit accepted by name.
Organization & Agents
Govern the operation
What carries risk goes to another person. Every act leaves a receipt, and every piece of work has a cost ceiling.
Organization & Agents
Connect to decisions
With the base in place, the agents’ work starts serving business decisions, with an owner and a tracked effect.
Decisions
Each stage ends with your decision: continue, correct, expand or stop.
Ways to engage
A sequence with an exit criterion at each stage. Nobody has to buy everything, and nothing moves forward without the previous stage’s evidence.
Stage: AI governance
Organization & Agents
Organize and govern what already runs
Where most companies start
We survey the agents and AI uses the company already has, on any platform, and organize them in the hub. Each agent gets an owner, a team and a limit accepted by name. What carries risk goes to another person, every act leaves a receipt and every piece of work has a cost ceiling.
What stays with the company
An inventory of agents with owners, a map of people and agents, accepted limits, risk-based review rules, cost per piece of work and a weekly summary for each owner. The module already includes the EDAVEN Builder Agent, to create new plug-in agents with your team.
Stage: Decisions
VÉRTICE Executive
Structure the first case
A critical decision is read end to end: data, owners, baseline and the map of governance dimensions the case requires. It ends with candidate recipes and the proposal for the next step.
What stays with the company
Decision reading, baseline, case governance map, candidate recipes and CoE Seed within scope.
Stage: Decisions
Decision Sprint
Apply a capability
One to three recipes run in shadow mode: the recommendation appears next to the human decision, against the baseline, with an initial mandate and declared controls. Cookbooks guide the application when relevant.
What stays with the company
A case in shadow mode, recorded divergences, evidence and a continuation decision.
Stage: Operation
MDC · Managed Decision Cell
Operate and co-manage
Qualified recipes operate under mandate, authority limits and supervision: every action leaves a receipt and the effect is tracked against the baseline. Autonomy rises only with proof.
What stays with the company
Supervised operations, receipts and tracked effect within the agreed package.
Stage: Teams
Arcogi Academy
Enable and transfer
Applied training so the team and partners understand, operate and evolve the practice: roles, authority limits, review and evidence.
What stays with the company
Skills, materials and applicable routines.
Six entry points
Every company arrives with a different question. These are the most common ones, and what each delivers.
Decision map
The company says: “I don’t know where to start with AI.”
Inventory and the priority decision.
Differentiating decision
The company says: “I already know which decision I want to solve.”
Decision in operation and effect measured.
Govern the AI you already have
The company says: “We have Cortex, Copilot, AI in the ERP, and no one controls it.”
Third-party AI under control.
Agent factory
The company says: “I want my team to build agents, with governance.”
Agents with an owner and a mandate.
Data ready
The company says: “Nobody trusts the numbers.”
Data products with a contract.
Agents in your ecosystem
The company says: “My people want to use agents, in a controlled way.”
Adapters and connectors with Snowflake, Databricks, AWS, GCP, Microsoft and others, per project.
A door is not a product: each one combines Organization & Agents, Data Ready and Decision Intelligence as the case requires. Scope and status are confirmed in the proposal.
Every agent is born governed.
AI and agent governance is not a separate project, nor a policy document. It is part of each agent’s architecture, engineering and operation from day one, and every rule is applied to every act while the agent works.
Gartner expects more than 40% of agent projects to be canceled by 2027 because of cost, unclear value and gaps in risk management. Gartner, Hype Cycle for Artificial Intelligence, 2026
In the architecture
Policies and risk
- An inventory of agents, models and third-party AI
- Risk classified per case, with the control it requires
- Purpose, owner, team and a limit accepted by name
- Only data with defined origin, purpose and retention
- Only models approved for that type of data
In the engineering
Security and quality
- Its own identity and mandate for each agent
- Actions outside the mandate denied before they run
- Adversarial and bias tests, and tests for the known risks of agent applications
- Vendor agents qualified on entry and again when they change
- A person reviews and signs each version before use
In the operation
Oversight and audit
- Another person reviews what carries risk; dual approval for high risk
- A stop condition and who authorizes resuming
- Monitoring of drift, exceptions and consumption, with a cost ceiling
- Incidents handled with an evidence package
- A receipt and provenance for every act; autonomy that rises and falls with the track record
And the learning stays with the company: human-curated memory, in your environment, outside the vendor’s model.
Controls are linked to the frameworks auditors and customers ask for: the EU AI Act, GDPR, ISO/IEC 42001, the NIST AI RMF and OWASP for LLMs and agents. This is a reference mapping, not legal advice or certification. See governance in detail
Capability and support within a defined scope.
The proposal defines applications, assets, integrations, specialist involvement, support and acceptance criteria. Fixed packages may include specialist hours. Continuation follows the business need.
Case assets, configurations and evidence specified in the contract remain with the client. Licenses, support and updates have separate terms; the proprietary body of knowledge is not transferred in full.
Read the full playbookWhich agents already work in your company?
In half an hour, Matias helps map what already runs and tells you where to start.