My job here is to turn Notion's documentation and the published evidence around it into a clear call: which setup to build, which feature to use, where Notion falls short of what its marketing promises, and when another app is the better choice.
What I cover
Most of my guides deal with work you do for other people: client and project databases, what a client can see when you share a page, formulas that drive status and dates, and automations that pass work along. I also write template guides for personal planning, such as a habit tracker or a meal planner, and comparisons with the apps people weigh against Notion, from Airtable and ClickUp to Obsidian and Evernote.
Calls I make again and again
A few recommendations run through the whole library. Each one is argued in full in the guide it links to.
- One database per kind of record. I'd keep every task in one Tasks database even with a dozen clients, because a template change then applies everywhere and a cross-client "due this week" list is a filter, not a merge job. The database organization guide explains the rule.
- Add a property only when it changes a decision. In project management in Notion, I'd start from Notion's own Projects & tasks template and add one piece at a time, since every property is one more field someone has to keep filling in.
- Give clients the narrowest access that works. For a client reviewing a proposal, I recommend a guest invitation with Can comment, and I'd keep a returning client as a guest while their work stays on a defined set of pages. Guest vs member covers when that changes.
- Settle the rule before you automate it. "Weekly" can mean two different recurrence rules, so I'd pin down the rule first and then pick the smallest setup that keeps it, as the recurring tasks guide shows.
- Let AI draft and let a person decide. I'd start a small team on Basic Autofill for notes and briefs, and keep fact checks and the final edit with a person. The Basic vs Custom Agent Autofill comparison shows where each kind fits.
- Notion isn't always the answer. For a consultant whose research and drafts stay on one laptop, I'd start in Obsidian, and for a studio that keeps adding clients to a per-seat tool, Basecamp's flat price wins. My guide to Notion alternatives sorts out when to switch.
How I work
Every guide starts from a question people are searching for and a read of the pages Google ranks for it, so I know what's already answered and what's missing. Product behavior comes from Notion's help center, API reference and pricing, with the plan or role it depends on stated beside the claim. Where readers need a number, such as user ratings for competing templates, I pool published results and report the median, the range and the number of sources. Where the number is a measurement of public web pages, such as how fast a Notion-built site loads on a phone, I take it myself and publish the tool, settings and run count. The editorial method covers each step.
Examples use fictional clients, projects and records, so no real client data appears in a guide.
What I won't do
A few lines hold in every guide, whatever the topic.
- Quote productivity statistics from a vendor or a template seller. Those numbers are marketing, not measurement, so they stay out, along with case-study figures nobody outside the company can check.
- Hide the plan a feature needs. If something works only on Business or Enterprise, or only for a workspace owner, the guide says so next to the claim.
- Move a recommendation for a discount code or a sponsorship. A template seller can't buy a better spot in a guide, and no company sees a draft before it goes live.
- Invent reader reactions. When a guide reports what users ran into, it comes from a public thread or forum post, and I leave usernames out.
Editorial responsibility
I write the guides and reviews on this site under the name Kevin Turner, and I'm responsible for the wording, sources, recommendations and corrections on every page published under it. When a fact turns out to be wrong, I fix the page and any related guide that repeats it, following the editorial policy. NotionSolutions isn't affiliated with Notion, and no company pays for a recommendation here.
Publication profile
- Role: Writer and publisher
- Focus: Notion databases, client workflows, formulas, automations and templates
- Audience: Freelancers, consultants and small teams
- Market: United States
- Start here: the learning paths in the library
- Archive: every guide I've published, newest first