Notion Consulting
Your company knows a lot. Almost none of it is written down.
We build the Notion workspace that turns what your team knows into something the business owns.
What Notion actually is
Notion is a connected workspace — documents, databases, and wikis in one place. The important word is connected. A page can be a document and a database entry at the same time, so a client, a project, and the SOP for serving them can all link to each other instead of sitting in separate systems.
That’s what makes it the right tool for a knowledge base. Most documentation dies because it’s a folder of files nobody can find. In Notion, information is structured, searchable, and linked to the work it relates to.
It’s also where Notion goes wrong. Give a team a blank Notion and six months later you have four hundred orphaned pages and no idea which onboarding doc is current. Structure and permissions are what separate a knowledge base from a mess.
Who this is for
Notion consulting is a fit if you recognise most of these:
- The same questions get asked and answered over and over in Slack
- When someone leaves, their knowledge leaves with them
- Onboarding a new hire means someone senior loses a week
- Your SOPs are Google Docs nobody has opened since they were written
- You have Notion already and it's turned into a page graveyard
Not a fit if: You want a project tracker above all else. Notion can do it, but Asana does it better — use each tool for what it's good at.
What we build
Company knowledge base
One searchable home for how your business runs — policies, processes, tools, and the answers to the questions your team keeps asking.
SOP and playbook library
Procedures written in a consistent format, owned by a named person, with review dates so they don't quietly go stale.
Employee onboarding hub
A structured first 30/60/90 days a new hire can work through mostly on their own, instead of shadowing whoever is least busy.
Connected databases
Clients, projects, suppliers, and staff as linked databases — so opening a client shows their projects, their contacts, and the process for serving them.
Permissions and access design
Teamspaces and sharing rules so finance sees finance, contractors see only their project, and the whole company sees what it should.
Meeting and decision records
Meeting notes and decisions captured in a database, linked to the projects they affect, so you can find out why something was decided a year later.
How we work
-
01
Audit what you already have
Where does knowledge live now — Notion, Drive, email, someone's head? We find it before we design anything.
-
02
Design the information architecture
Teamspaces, database schemas, and how pages relate to each other. This is the step that decides whether the workspace survives its first year.
-
03
Build and migrate
We build the structure, move real content in, and set up templates so new pages come out consistent instead of freeform.
-
04
Set permissions
Access designed deliberately — who can see, comment, and edit — rather than everything shared with everyone by default.
-
05
Train and hand over
Your team learns how to add to it, not just read it. A knowledge base only one person maintains is a liability.
Certified Notion Expert
Thomas is a Certified Notion Expert. Notion runs his own businesses — knowledge base, client work, and operations — so this is a system he uses daily, not one he only teaches.
Common questions
We already have Notion and it's chaos. Start over?
Rarely. We usually restructure around what's there — archive the dead pages, pull the good content into proper databases, and put an architecture around it. Starting over throws away real knowledge.
Is Notion secure enough for company information?
For most small businesses, yes. Notion supports SSO, granular permissions, and audit logs on business plans. If you handle regulated data with specific residency requirements, tell us early — that changes the recommendation.
What about Confluence or SharePoint?
Both are fine at what they do. Notion wins for small businesses on speed of setup and how well documents and databases connect. SharePoint makes more sense if you're already deep in the Microsoft stack.
Who keeps it up to date after you leave?
Your team — that's the point. We assign page ownership and set review cycles as part of the build, so maintenance is somebody's named job instead of nobody's.
Can Notion replace our project management tool?
It can, and for some businesses that's the right simplification. But if you run complex work with dependencies and heavy reporting, a dedicated tool is better. We'll be straight with you about which case you're in.
Stop losing what your business knows
A short call to look at where your knowledge lives today and what it would take to put it in one place.
Book a call