Skip to content
← All guides
NOTION23 Jul 202621 min read2 hours to do

How to set up Notion with Claude: the founder command centre

TL;DR

Most founders run Notion as a graveyard and Claude as a chatbot. Connected properly, they become a command centre: one board holding everything on your plate, a morning brief that reads it before you're out of bed, a capture routine that files your stray thoughts, and a live dashboard of the whole company you can click. This guide is the full install: five steps, seven prompts, word for word, including the 20-minute interview prompt that builds the entire thing for you.

This is the system I install for founders as part of my agency work, written out in full. Not the idea of it. The actual build: the board schema, the connection steps, the seven prompts, the safety rules, in the order I run them with clients. You could hand this page to Claude and have the whole thing working this afternoon.

It assumes nothing technical. If you can use Notion and you have a paid Claude plan, you can build this.

One scope note before we start. This guide is about your personal command centre: your board, your brief, your day. Getting Claude set up properly for the whole company (workspace, team projects, organisation instructions) is its own job, and I've written that one up too: how to set up Claude for your business. Do either first, they meet in the middle.

What you're actually building

Five pieces, stacked in order:

  1. One board that holds the whole company. A single Notion database, call it Company HQ, where every open task lives with a status, a department, an owner, a priority and a due date. Not seventeen scattered pages. One board.
  2. A live connection between Claude and that board. Claude reads it and, with your confirmation, writes to it.
  3. A morning brief. Every morning Claude reads your board, your calendar and your inbox, and hands you the single most important thing today, the shape of the day, and your open tasks by department, in under 350 words, readable on your phone before you're out of bed.
  4. A capture routine. You finish a call, rattle off "capture these: send Marta the revised quote by Friday, someone needs to book the venue, and remind me to renew my passport", and each item lands on the right board, structured, with nothing lost and nothing duplicated.
  5. A live dashboard. A one-screen, clickable command centre built from your real board: what's hot today, everything by department, colour-coded, each task linking back to its Notion page. You say "refresh" and it re-reads the company.

Here's the day that falls out of it. You wake up and read the brief on your phone. You walk into your 10am having said "prep me for the 10am" five minutes before. You end each call with thirty seconds of capture instead of a mental note you'll lose. And any time the day gets loud, you open the dashboard and see the whole company on one screen instead of scrolling four apps to reconstruct it.

The magic is not the AI. It's that for the first time, everything on your plate is in one structured place a very fast assistant can read.

Why Notion and Claude, specifically

Claude on its own is brilliant and forgetful. Every chat starts blank, so every answer is generic. Notion on its own is structured and dead. It only knows what you type into it, and nobody has time to be their own secretary.

Connect them and each one fixes the other. Notion becomes the memory: a database with real fields that survives between conversations. Claude becomes the hands: it reads the board in seconds, ranks what matters, files new items into the right fields, and turns the whole thing into briefs and dashboards on demand. The board keeps Claude honest. Claude keeps the board alive.

That's the whole trick, and it's why this outlasts every productivity app you've abandoned: the system maintains itself, because maintaining it is a sentence ("capture these") instead of twenty minutes of admin.

Step 1: connect Claude to Notion

Two minutes, no code.

  1. Open Claude (desktop app or claude.ai) on a paid plan.
  2. Go to Settings, then Connectors.
  3. Find Notion in the connector list and click Connect.
  4. A Notion window opens asking what Claude may access. Sign in and grant access to the workspace you'll build in.
  5. Back in Claude, open a new chat and ask: "What can you see in my Notion?" It should name real pages.

Two rules that save pain later. First, only grant access to what you'd be happy a sharp new employee could see. You can widen access any time. Second, if you're on a Claude Team plan, this is a per-person connection: each user connects their own Notion account, and Claude only ever sees what that person can see. Nobody inherits your access.

Step 2: the board schema (steal this exactly)

The heart of the system is one Kanban-style Notion database. I use the same schema with every founder, because it's the minimum structure that supports briefs, capture and dashboards without turning into a part-time job:

  • Status: To do, In progress, Done. That's it. Resist the urge to add six statuses, you will not maintain them.
  • Department: a select field with the 5 to 8 areas your business actually runs on. Sales, Marketing, Operations, Finance, Hiring, whatever they truly are in your company. These become the lanes of your dashboard and the sections of your brief.
  • Owner: a person field. Defaults to you. The day you hand a department to someone, the board is already built for it.
  • Priority: High, Medium, Low, or empty. Empty is allowed. A fake priority is worse than none.
  • Due date: a date, or empty. Same rule. Never invent a deadline just to fill the field.
  • Notes: one line of context per task, where it came from and why it exists, so that when you read it cold in two weeks it still makes sense.

Alongside the database, one page per department for anything that isn't a task (notes, links, standing context), and one separate private page as your personal capture target, because your passport renewal does not belong on the company board where your ops lead can see it.

Three design rules that make this work with an AI attached, and this is where most DIY setups quietly fail:

  1. The empty field rule. Claude is told to never invent a status, department, owner, priority or date. If it isn't stated, it stays blank for you to decide. A board full of guessed metadata is worse than a notebook.
  2. The live options rule. Claude reads your actual status and department options from the board at runtime, every time. Rename a department and nothing breaks, because nothing was hardcoded.
  3. The one write-target rule. Work goes to Company HQ. Personal goes to the personal page. Claude never writes anywhere else, no matter how convenient it would be in the moment.

You can build all of the above by hand in ten minutes, and if you love Notion, go ahead. But you don't have to, because the rest of this guide is the prompts that build and run it for you. That's what's behind the gate below: the 20-minute interview prompt that constructs the board and files everything currently in your head onto it, the four daily prompts, the live dashboard build, and the 15-minute version.

Free with your email

That's the free preview. The rest unlocks right here.

Drop your email and this page unlocks instantly, along with every other gated guide on the site. Still in the locked half:

  • The command centre build prompt: a guided 20-minute interview where Claude builds your whole HQ board, then files everything currently in your head onto it
  • The four daily prompts: morning brief, action capture, call prep, weekly priorities
  • The live dashboard prompt: a clickable one-screen view of the whole company, built from your real board
  • The 15-minute simple version, one paste, for when you want the payoff without the full build
  • Three starter prompts and the one safety rule that keeps all of this boring and reliable

Unlocked before on another device? Enter the same email, it works again. You also get each new guide by email before it becomes a video. No spam, unsubscribe any time.

This guide started as a video. Follow along for the rest: