yulen.aiv1.0AGENT

Yulen · For partner teams

The partners agree. What the agreement does not allow does not run.

Yulen turns the agreement into rules for the AI and for each tool: permissions, budgets, hard limits, and who approves what. Every decision stays in the record.

What gets in the way

01

The agreement never reaches the AI

What was signed is in a PDF. The AI and the tools do not know it.

02

Each partner uses AI their own way

With different accounts, permissions, and criteria, nobody controls what the AI does in the company's name.

03

Contracted services with no limits

Tools and suppliers spend and act without the agreed budget or approvals.

04

No trace of what was done

When something goes wrong, it is not clear what the AI did, with which permission, or who approved it.

What changes

01

The AI works inside what was agreed

Majorities, permissions, and hard limits from the agreement apply to each AI task. What is inside the agreement goes ahead. What is not waits for the right approval.

02

The AI does not carry out what the agreement forbids

The rules apply to everyone. A request outside the agreement is blocked or waits for approval, and the context stays with the company.

03

Each tool, within the agreed limits

Bank, customers, ads, or development: each service acts within the agreed limits, and Yulen coordinates it. The specific integrations are not published.

04

Everything the AI does is recorded

Each action, with which permission and who approved it, is written and visible to the partners according to the agreement.

05

Each service applies the agreement

Yulen speaks to each tool's AI in the company's name. Each one applies what was agreed. The specific integrations are not published.

Interface examples. Not a customer's data.

A day with Yulen

Before · With Yulen

Before

  • Each partner uses AI with their own account and judgment
  • A contracted service spends more than was agreed
  • Nobody knows what the AI did or who authorised it
  • You have to meet to review what has already happened

With Yulen

  • The company's AI works with the agreement's rules
  • Each service operates inside its budget and its permissions
  • Everything is recorded: what, with which permission, and who approved
  • The meeting is left for deciding what matters

What you can turn on

Capabilities and rules, from day one.

Yulen Core

Agreement, goals, budget, norms, and hard limits in one place.

Governance and rules

Agreement, majorities, permissions, and hard limits applied to the AI and to each service.

Finance and operations

Budgets and payments with the approvals the agreement requires.

Product and engineering

Code and product created with AI. The agreement says who owns them.

Suggested plan

What gets turned on.

You start with the core and turn on only the capabilities you need. You pay for the capability and its volume, never per agent or per token. Prices are not published.

Join the waitlist
For partner teams
  • Yulen Core
  • Governance and rules
  • Finance and operations

Questions

What people usually ask.

Does it replace the signed shareholders' agreement?

No. The agreement remains the legal document. Yulen turns it into rules for the AI and for the contracted services.

Can a partner use the company's AI outside the agreement?

No. The company's AI and tools work with the same rules. What the agreement does not allow is blocked or waits for approval.

What about tools that are already contracted?

They connect to Yulen and operate with the agreed permissions and budgets. The specific integrations are not published.

Can you see what the AI has done?

Yes. The record keeps what was done, with which permission, and who approved it.

What if a partner leaves?

Their permissions are adjusted according to the agreement. The context stays with the company.

How it works

Three steps. A person approves anything outside the plan.

  1. 1Write the rules

    Agreement, permissions, budget, and what is never done. Each rule is a file with a path and a version.

  2. 2Agents work inside them

    An action inside the rules goes ahead. Anything outside is asked of the person who has permission. You choose the AI. There is no published automatic recommendation.

  3. 3Every decision is recorded

    The record says what was done, with which permission, and who approved it. If you change provider, the context leaves in an open format.