goua.laBook a free call

For companies

Notion is rolled out. Adoption isn't.

Everyone has their own way of doing things, onboarding gets reinvented every time, and if the person holding the system leaves, the structure leaves with them. I build the adoption that's missing with you, not another tool.

Virgile Gouala
Virgile GoualaNotion Ambassador · Certified Notion consultant · Solution Partner

10 years in tech before Notion (developer, then engineering manager), including leading an 80-person migration from Jira to Linear at Welcome to the Jungle and papernest. Company training is eligible for OPCO funding.

The problem

The symptom isn't Notion. It's adoption.

You rolled out Notion. Maybe with good intentions, maybe by copying what another team did. And yet:

This isn't a tool problem. It's an adoption problem, and reconfiguring pages won't solve it.

Acme · Team workspace4 problemsAdopted
HomeWikiClientsProjects
No results1 result · Time off and leave
OnboardingOutdated
Onboarding (copy)Duplicate
Onboarding v2 MarcDuplicate
Onboarding FINALDuplicate
OnboardingUp to date
Time off and leaveHR
Team guideReference
Client tracker.xlsx3 wk. ago
Clients · shared databaseSynced
System ownerMarc D. · left the company
System ownerLéa M. · trained champion

Who I am, what I bring

Not another Notion consultant. Someone who's already driven a tool migration across a whole team.

Before Notion, I was a developer, then an engineering manager. I led the migration from Jira to Linear for an 80-person team: I know what it costs to change a team's habits, and I know resistance doesn't go away by being ignored.

Structural clarity. A system designed for your actual organization, not a generic template copy-pasted in.

Training matched to the right audience. A deeply trained internal champion (Champion Training), or the whole team trained on the basics (Team Training), depending on what you need.

Handling resistance. One-on-one conversations with the people who aren't adopting the tool, to understand why before imposing anything.

Presence over time. Ongoing support over several months when adoption needs to stick long-term, not a one-off visit that gets forgotten.

You come out with a system your team understands and uses, not a dependency on me for every change.

How it works

Three steps.

1

We look at your current system.

20 minutes to understand where it's stuck: structure, adoption, or both.

2

We build with your teams, not for them.

Every decision is explained as it's made.

3

We train the right people.

An internal champion, the whole team, or both, depending on your organization. Company training is eligible for OPCO funding.

Pricing

Two ways to work together.

The format gets decided on the call, based on what's actually stuck.

See all pricing

Training OPCO-eligible

Champion Training for one internal point person, Team Training for the whole team. Always built from your actual system.

from €1,800depends on format

Ongoing support

Three months of continuous presence to overcome resistance, adjust to real usage, and make the tool stick past launch.

€1,500-2,000per month, 3 mo. min.
Célia Barah

"Between structuring advice and practical tips, I really learned to get the full value out of the tool, a real time-saver day to day."

What you're probably wondering

That's the most common situation. Most rollouts fail because they were done without the people who'd actually have to use it afterward. We start from there.

Virgile Gouala

Shall we look at where it's stuck?

Twenty minutes to find out if the problem is structure, adoption, or both.

You are
You areCompanyFreelancer