What's written down stays.

Knowledge transfer

Turn individual expertise into shared wealth.

Preserve and share your company's essential knowledge: the kind that goes on leave, retires, or moves to a competitor. Whoever knows writes it down with me, and the whole team benefits.

3 to 5 minutes · No credit card needed

The problem

Your company depends on a few people.

You only notice at the worst moment. Spot who's irreplaceable →

The departure

A resignation, a retirement, and fifteen years of method walk out the door.

The absence

Three weeks of holiday, and everyone calls the only person who knows, on the beach.

The new arrival

The new hire learns by watching, for months, what could have fitted on three pages.

What you're looking for

Essential knowledge, written down, up to date, and easy to find.

  • What's missing, spotted: the essentials of a well-structured company
  • Every method written by the person who practises it
  • Documents that are checked, dated and reviewed on time
  • A team that finds the answer on its own, or with its AI
  • New arrivals up and running faster

How it works

From someone's head to a document, in five steps.

01
Spot

I tell you what's missing.

My catalogue holds 28 essentials: sales process, delivering a service, invoicing, recruitment, one-to-one meetings… At the top of your Library, I show you the ones your company hasn't written yet.

02
Write

Whoever knows writes it with me.

I ask them the right questions, one at a time, then I draft it, in their voice. They start from a template, a blank page or their own document.

03
Approve

Leadership makes it the rule.

A document can become an Essential: it sets the rule for the whole team, and for me in everything I write.

04
Keep up to date

The document says how long it holds true.

It's marked “Checked” for 90, 30 or 7 days. When that runs out, it comes up in the Review. Its author updates it when their practice changes.

05
Find

Everyone finds it, and so does their AI.

In the team's space, through search, or by asking their own Claude or ChatGPT, which cites the source.

An example

“I'm off for three weeks.”

Before her holiday, Camille's client onboarding method fits on three pages, written with me. The team follows it without calling her.

app.marcel-os.com · Library
Help me write down my client onboarding method before my holiday.
Consulted Marcel: “Client onboarding” templateOffersMy voice
Let's go. First question: between signing and the first meeting, what do you send the client, and within how many days? Then we'll look at who does what at kick-off, and the three pitfalls you avoid every time.

The proof

See for yourself.

What's missing, at the top of the list

In the demo, Klaris Digital's Library recommends the essentials it hasn't written yet.

Who wrote it, and when

Every document shows its author, its date, and how long it's checked for.

Nothing gets lost

A version is saved before every working session, and nothing is ever deleted.

Your questions

Do we need to document everything?

No. We start with what creates the most dependency: what only one person knows how to do, and what the company needs every week. I show it to you at the top of your Library.

How long does it take to write down a method?

It depends on the method, but you never start from a blank page: I ask the questions, I draft, the person corrects. A typical method often fits in one session.

What if the method changes?

Its author updates it, and the whole team works from the new version. Previous versions are never deleted.

Who can write?

Leadership writes and updates processes, rituals and documents. Team members suggest their own, and leadership approves them; it also chooses what becomes an Essential.