Codify your company
What you decide no longer sits in a signed document in a drawer: Yulen turns it into code and checks it before every action, so you can delegate without repeating yourself.
The problem
Agreements, permissions and policies tend to live in documents nobody looks at day to day. With AI acting in every service, the risk grows: a tool can do in seconds what nobody would have approved, and you find out afterwards.
AI can't follow a rule that sits in a signed document in a drawer.
How Yulen solves it
Yulen turns your decisions into rules that apply to Yulen's capabilities and to the tools you connect, and before anything happens it checks it against your rules and your red lines. That way you can delegate without reviewing every step. It goes ahead, is stopped, or is checked with the right person.
- 1
You write the rules
Who decides what, how much can be spent and what is never done.
You decide - 2
Yulen checks each action
When it's planned and again before it runs.
- 3
It's recorded
Why it went ahead, was stopped or was checked with someone.
Anatomy of a rule
Approved by leadership.
Up to the first tier, it goes ahead without asking. Above that, the area lead approves. Above the second tier, leadership approves.
Pay suppliers that aren't approved.
From v1 to v3, with the date and reason for each change.
For example: each company sets its own tiers and limits.
Rules, culture and strategy
Who approves an expense and up to what amount.
The tone and standard of customer service.
Market priority and the quarter's goals.
Illustrative examples.
What you gain
You decide once; it's checked on every action
A check on every action
Red lines are checked before every action, whoever asks for it.
Fewer routine approvals
Only what falls outside the framework gets checked with someone.
Every rule has a history and an owner
Rules applied on every action
“Customer discounts never go above the maximum set by leadership.”
“We only pay suppliers that are already approved.”
“Nothing goes to production without a person reviewing it.”
“Customer data doesn't leave the company without explicit permission.”
Illustrative examples.
How it works
A decision, from start to finish
- 1
Propose
Go-to-market proposes raising the ads budget.
- 2
Agree
Leadership reviews it and adjusts the amount.
You decide - 3
Approve
It's approved according to who decides what, and expenses.md v4 is created.
You decide - 4
Apply
Campaigns use the new limit; anything above it gets checked.
- 5
Record
Every action links to v4.
Leadership decides
What the rules don't allow doesn't go ahead.
AI proposes. A person approves.
AI can propose changes to the rules; only people approve them, according to who decides what in your company.
What you can turn into rules
Authority
Who decides what, by role: powers, limits and delegations.
Thresholds
Amounts and volumes above which another approval is needed.
Red lines
What the company never does, whoever asks for it.
Separation of duties
Whoever proposes a payment isn't the one who approves it.
Escalation
When a decision goes up to leadership, the board or the partners.
Versions
Each change shows its differences and impact, and takes effect once approved.
How each action is assessed
- 1
It's planned
The action is proposed with its context and its cost.
- 2
It's checked
Yulen checks it against authority, thresholds and red lines.
- 3
It's decided
It goes ahead, is stopped, or is checked with the right person.
- 4
It's checked again
Just before it runs, in case something has changed.
- 5
It's recorded
What was done, with which permission and who approved it.
An example of escalation
Sales lead
Can increase campaign spend up to a threshold.
CEO
Approves above that threshold.
Competent body
Decides whether the expense affects the minimum cash reserve.
For example: each company configures its own thresholds.
You decide, Yulen takes care of it
You decide
- The rules, the thresholds and the red lines.
- Who approves each type of decision.
- When a rule changes, with the majority set by the agreement.
takes care of
- Applying the rules to Yulen's capabilities and to the tools you connect.
- Asking for the right approval and waiting.
- Flagging if a rule change affects work in progress.
Safeguards for delegating
Agents work for one person. 
works for the whole company.
Request early access. We will get in touch to learn about your project and how Yulen can help.