Do I need to know Notion before hiring a consultant?

No. And I'd go further: trying to learn it first is usually what makes the whole thing take longer.

I get asked this more than almost anything else. Someone tells me they want their business organised properly, we have a good conversation, and then a week later the message comes: "I think I need some time to learn how Notion works first, before I invest in this."

I understand the instinct completely. It feels irresponsible to pay someone to build you something you don't understand. Nobody wants to be handed a tool they can't drive.

But it's backwards, and here's why.

The first step isn't the tool. It's your business.

When I start with someone, we don't open Notion. We talk about how their week actually goes.

Where does the time go. What gets dropped. Which part of the business only works because you remember to do it. Who does what, and what happens when that person is on holiday. Where the money is tracked, and whether you trust the number.

None of that requires knowing what a relation or a rollup is. It requires knowing your own business, which you already do better than anyone.

That conversation is the actual work. What comes after it — the databases, the automations, the dashboards — is just the shape the answers take. If you skip straight to the tool, you end up building something that looks organised without being organised, and that's the version people give up on three weeks later.

What happens if you try to learn it first

You open Notion. It's a blank page. It can do anything, which means it tells you nothing about what you should do.

So you look for a template. The template was designed for someone else's business, so you bend yours to fit it. Then you find another template for the bit that didn't fit. Then a YouTube video that does it a third way.

Two months later you've spent real hours and you have a workspace that's prettier than before and still doesn't hold your business. And now you're more discouraged than when you started, because you've concluded you're "bad at Notion."

You weren't bad at Notion. You were asked to design a system before anyone had worked out what the system needed to do.

What you actually need to bring to a Notion consultant

Genuinely, this is the whole list:

• How your business really runs — not the tidy version, the real one
• Where it hurts — the bits you dread, the bits that break, the bits you redo
• Who's involved — you, a VA, a small team, freelancers
• What you've already got — even if what you've got is eleven tools and a folder called Final_v3
• An honest answer about how you feel about tools — some people enjoy tinkering, some want to touch it as little as possible

That last one matters more than people expect. If you tell me you get overwhelmed easily, I build you something simpler with fewer moving parts. If I don't know that, I might build something more powerful than you want to live in.

But I'll have to run it afterwards

True. And you will learn it — just in the right order, and on a system that already matches how you think.

Learning Notion in the abstract means learning every feature, most of which you'll never use. Learning your own system means learning the five things you actually do: where to add a client, where to check what's due, how to send the invoice, where the process for that thing lives.

That's a much smaller thing to learn, and it sticks, because it's attached to work you already care about.

It's also why a good Notion consultant doesn't hand over a workspace and disappear. There's a walkthrough, instructions written for your setup, and support afterwards. The whole point is that it keeps working when I'm gone. You can see what a finished one looks like in this case study.

When you should wait

I'd rather say this plainly than have you find out after paying me.

Wait if you don't know what your business does yet. If the offer is still moving, the systems will be rebuilt in three months anyway. Get the business steady first.

Wait if nothing hurts. If you're solo, you've got four clients, and your setup genuinely works — you don't have a systems problem. Spend the money somewhere else.

Don't wait, but be honest, if what you really want is someone to run your operations for you. That's a different job. I build the thing and hand it over; I'm not going to sit in your Monday meetings making decisions. If that's what you need, you want an operations manager, not a Notion consultant.

What working with a Notion consultant actually starts with

The smallest version is a one-hour Notion consultation. You bring whatever's messiest, we go through it live together, and you leave knowing what to do next — whether you do it yourself or not. Mine is €150 + IVA, and it's deliberately small, because "I'm not sure what I need yet" is a completely normal place to start.

The bigger version is a proper discovery and audit — €750 + IVA — where we map how your business runs and decide what to build and in what order. You'd keep that document whether or not you ever build it with me.

Neither one asks you to know Notion. They ask you to know your business.

So the real question isn't whether you know the tool well enough yet. It's this: which part of your business is currently held together by you remembering to do it?