For teams of 30 to 300 who already use AI, each on their own
Your teams use AI alone. Mycel connects it.
Agents prepare the replies, offers and reports. Your people approve them before anything goes out.
- 24 of 35
people at one investment firm said AI that reads their mail and calendar is what they want most.
- 8
people at the same firm had built their own AI skills. Each one lived in a single personal account.
- 4 of 8
leaders we interviewed at another company said missing rules stop them from using AI.
From our surveys and interviews with client teams in 2026. Names withheld.
From one person to the company
Nobody installs a company brain on day one. A team AI pushed onto people ends like the company wiki. Mycel grows from what people already use.
Every person gets an AI that knows their job
Role, tone, documents and tools, set up in one session. Built in one room with the team, on the same shared knowledge.
Teams share what works
The team agrees what good looks like. Then the best routines become shared skills, each with an owner and a review.
The company runs on it
Agents work in the background on company data. Everything that would go out lands in one approval queue.
What we set up, at every level
The same five building blocks for each person, each team and the company. One set of rules on top.
| Block | Each person | Each team | The company |
|---|---|---|---|
| Context | Your role and your voice | Team brief and glossary | Company model and policies |
| Content | A folder of their real documents | A shared knowledge base, every entry linked to its source | Company data, read through one gateway |
| Connections | Mail and calendar, read-only first | Team tools with team permissions | Personal login, every change logged |
| Capabilities | Two routines, written down | Skills the team agreed on, an owner each | Background agents in draft mode |
| Cadence | A weekly slot to improve | A digest of what worked | Reviews after two and six weeks |
| Rules | Nothing leaves without you | Guidelines on two pages | Four rule levels per team, enforced |
Pick a team, follow its threads
Each team keeps its own setup. Mycel shares between teams only where your rules allow it.
AI prepares. People decide.
Every agent works under four rules. You set them per team. Every draft shows what it is based on.
- Alone
- Read, sort, summarise, draft
- Do and tell
- Small, reversible steps, logged
- Ask first
- Anything that leaves or changes data
- Never
- Paying, signing, deleting
- Ask first HR agent
Reply to an applicant
Draft ready, in your tone, with two interview slots. Based on the job ad and the calendar.
- Ask first Operations agent
Swap two shifts next week
Both people agreed in the team chat. Based on the chat thread and the shift plan.
- Ask first Finance agent
Book this week’s supplier invoices
Matched to orders, one needs a look. Based on the orders and the bank feed.
Example queue. Nothing here is sent.
One day at Fernlicht
Fernlicht is made up: 84 people, trade fairs, Berlin. You run it. Agents handle the routine, three things need you. Takes about a minute.
AloneAgents start before you do.
Fernlicht and everyone in it are invented. Nothing here is sent.
How we plant it
Agency work that leaves software behind. The durations are typical; your teams set the pace.
Understand
2 to 3 weeksSponsor, survey, interviews. IT and compliance from day one.
Focus
1 to 2 weeksMap the core work. Decide what to build, buy or leave.
Enable
6 to 8 weeksHands-on sessions, one room per team, on shared knowledge. Everyone leaves with a setup that works.
Build and hand over
6 to 10 weeksThe team agrees the criteria, then we build shared skills, the gateway and agents. Two owners on your side run it, then we step back.
We run Supercharged on Mycel ourselves. The Fernlicht demo is invented, the setup behind it is ours.
Start with one team
A 30‑minute call: where your teams stand, and what Mycel connects first.
- With
- Benjamen Mateev
- Book
- a 30-minute call