Notion Systems Claude Architects From Scratch
20 Claude prompts for database schemas, formulas, workspace architecture, workflow design, and the structured thinking Notion power users need.
In short: This page contains 20 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.
Architecture
5 promptsWorkspace Architect
1/20✨ What it does
Claude designs a Notion workspace for the role you [describe], with 5-7 hubs, database versus page choices, relations, what to keep out, and daily and weekly rituals. Set [solo / team size] and [areas to manage], then build one hub this week, not all seven.
<task>Design my Notion workspace</task> <role>[describe]</role> <needs>[areas to manage]</needs> <team>[solo / team size]</team> <output> 1. Page hierarchy (5-7 hubs max) 2. Database vs page per area 3. Relation structure 4. What NOT to put in Notion 5. Daily + weekly usage ritual </output>
Pro tip: Most Notion workspaces die from too many databases. Start with 3-5 (Tasks, Projects, Notes) and expand only when real pain forces it. Over-architecting kills adoption.
Database Schema
2/20✨ What it does
Claude designs a database schema for [tracking need] from the entities you [list], with property types, relations, rollups, views, and what not to track. Create the properties first, then add only the views you will open daily.
<task>Design database schema for [tracking need]</task> <entities>[list]</entities> <output> 1. Properties with types 2. Relation + rollup to avoid redundancy 3. Views per use case 4. Filters and sorts 5. What NOT to track </output>
Pro tip: 5-8 properties per database is the sweet spot. More and you've probably needed a second database with a relation, not more columns.
Second Brain / PKM
3/20✨ What it does
Claude builds a second brain in Notion from the capture habits you [describe], organized for [writing / teaching / decisions], with a notes schema, quick capture, weekly review, and retrieval. Capture one note today, then run the weekly review once before you add more databases.
<task>Build second brain in Notion</task> <capture_habits>[describe]</capture_habits> <output_needs>[writing / teaching / decisions]</output_needs> <output> 1. Notes database schema 2. PARA or similar organization 3. Quick capture workflow 4. Weekly review ritual 5. Retrieval surfacing </output>
Pro tip: Design retrieval first, capture second. "How will I find this in 6 months?" matters more than "how do I capture fast?" Notes without retrieval are cemeteries.
Project Management Template
4/20✨ What it does
Claude builds a Notion PM template for the project type you [describe] and a team of [number], with Projects and Tasks databases, role views, automations, and archive rules. Duplicate the template, then archive a finished project so your pattern sticks.
<task>Build PM template in Notion</task> <project_type>[describe]</project_type> <team_size>[number]</team_size> <output> 1. Projects DB with properties 2. Tasks DB related 3. Role-specific views 4. Automation opportunities 5. Archive strategy </output>
Pro tip: Notion's relation property is what makes it real PM. Flat task lists without relations are prettier sticky notes. Relations unlock the system.
CRM Lightweight
5/20✨ What it does
Claude builds a lightweight Notion CRM for the business you [describe], with contacts, stages, interactions, kanban, a next-step calendar, and when to leave for a real CRM. Add five live contacts, then move one card across your kanban this week.
<task>Build lightweight CRM in Notion</task> <business>[describe]</business> <output> 1. Contacts DB + stages 2. Interactions DB related 3. Kanban by stage 4. Calendar view for next steps 5. When to graduate to real CRM </output>
Pro tip: Notion CRMs work up to ~100 active contacts. Past that, real CRMs win. Don't force Notion to be Salesforce — use it for the 80% solopreneur case.
Formulas & Automation
5 promptsFormula Builder (2.0)
6/20✨ What it does
Claude writes a Notion 2.0 formula for [need] using if, let, and switch, with an explanation, empty and divide-by-zero handling, and display format. List [list with types], then paste the formula and test an empty row on your database.
<task>Write Notion formula for [need]</task> <properties>[list with types]</properties> <output> 1. Formula in 2.0 syntax (if/let/switch) 2. Each part explained 3. Edge cases (empty, divide-by-zero) 4. Display formatting </output>
Pro tip: Notion Formula 2.0 is a massive upgrade — let/if/switch cleanly. If you're still using nested prop() 1.0 formulas, upgrade. Cleaner, faster, easier to debug.
Rollup Master
7/20✨ What it does
Claude configures a rollup for [scenario], including when a formula is better, filtered rollups, speed on large databases, and dashboard display. Build the rollup on a small view first, then add it to your dashboard if it stays fast.
<task>Configure rollup for [scenario]</task> <output> 1. Rollup setup 2. When rollup vs formula-that-does-it 3. Filtered rollup (e.g., active tasks only) 4. Performance on big DBs 5. Dashboard display </output>
Pro tip: Rollups are Notion's most underused feature. "How many open tasks per project?" updates automatically. Most "I need a spreadsheet" moments actually need rollups.
Status Automation
8/20✨ What it does
Claude automates status changes from the process and rules you [describe], using formulas, buttons, Notion Automations if you pay, or Make/Zapier for the hard cases. Turn on one rule, then click the button on a test task before you trust it.
<task>Automate status changes</task> <current_process>[describe]</current_process> <rules>[describe]</rules> <output> 1. Formula-based automation where possible 2. Button automations 3. Notion Automations if paid 4. External tools (Make/Zapier) for complex </output>
Pro tip: Automation only pays when process is truly repetitive. Changing status once a day = don't automate. 20 times a day = absolutely. Count first.
Dashboard with Rollups
9/20✨ What it does
Claude builds a cross-database dashboard from the databases you [list] and the KPIs you [describe], with rollups, filters, hierarchy, and a refresh cadence. Open it each morning for a week, then remove any KPI you never look at.
<task>Build cross-database dashboard</task> <databases>[list]</databases> <kpis>[describe]</kpis> <output> 1. KPI formulas/rollups 2. Single-page layout 3. Filter controls 4. Visual hierarchy 5. Refresh cadence </output>
Pro tip: Dashboards with 20+ linked databases load slowly. Show only 5-7 KPIs that matter. Everything else belongs one click away.
Template Gallery for Teams
10/20✨ What it does
Claude builds a team template gallery from the templates you [list], with a categorized hub, usage notes, governance, featured rotation, and onboarding. Publish the hub, then rotate one featured template this month for your team.
<task>Build team template gallery</task> <team_templates>[list]</team_templates> <output> 1. Categorized hub page 2. Usage instructions per template 3. Governance 4. Featured rotation 5. Onboarding guide </output>
Pro tip: Template galleries die without shepherds. Assign one owner, review quarterly, retire unused. Without ownership: 50 templates nobody uses.
Workflows
5 promptsDaily Dashboard
11/20✨ What it does
Claude designs a daily dashboard from the priorities you [describe], with Today, This Week, Waiting, Capture, morning intentions, capture buttons, and an end-of-day review. Open it tomorrow morning, then close the day with your review, not another tool.
<task>Design daily dashboard</task> <priorities>[describe]</priorities> <output> 1. Page layout (Today, This Week, Waiting, Capture) 2. Linked views filtered to today 3. Morning intentions 4. Quick capture buttons 5. End-of-day review </output>
Pro tip: Daily page is the front door. If finding what you need takes >10 seconds, system isn't working. Test: can I start my day in under 5 min?
Weekly Review Template
12/20✨ What it does
Claude builds a weekly review template for [work / health / etc.] with questions, stats pulled from other databases, patterns, next-week top three, and a wins section. Duplicate it each Friday, then write the three priorities before you close the laptop.
<task>Build weekly review template</task> <areas>[work / health / etc.]</areas> <output> 1. Review questions per area 2. Auto-populated stats from other DBs 3. Pattern notes 4. Next week top 3 priorities 5. Wins celebration </output>
Pro tip: Weekly reviews are where productivity systems earn their keep. 20 minutes every Friday beats any app or template. Without review, capture creates clutter.
Meeting Notes Template
13/20✨ What it does
Claude builds a meeting notes template for the meeting types you [describe], with agenda, notes, decisions, tasks linked out, reminders, and a scratchpad variant. Use it in the next meeting, then tick the action items in your Tasks database.
<task>Build meeting notes template</task> <meeting_types>[describe]</meeting_types> <output> 1. Meetings DB 2. Template with agenda/notes/decisions/action items 3. Action items linked to Tasks DB 4. Follow-up reminders 5. Scratchpad variant </output>
Pro tip: Meeting notes die when action items don't escape the notes page. Always link to your Tasks DB — otherwise decisions decompose into noise.
Content Calendar
14/20✨ What it does
Claude builds a Notion content calendar for the types you [describe], with calendar, kanban, and timeline views, an idea-to-scheduled pipeline, performance fields, and a Tasks link. Park three ideas in the backlog, then schedule one on your calendar this week.
<task>Build content calendar in Notion</task> <content_types>[describe]</content_types> <output> 1. Content DB with properties 2. Calendar/Kanban/Timeline views 3. Idea backlog → scheduled pipeline 4. Post-publish performance tracking 5. Linked to Tasks DB </output>
Pro tip: Content calendars work when connected to work needed. Without linked tasks, deadlines slip. With them, deadlines stay real.
Goals / OKRs Tracker
15/20✨ What it does
Claude sets up goals or OKRs on an [annual / quarterly] horizon with parent goals, child key results, weekly percent check-ins, a season dashboard, and a retro. Fill this week's percent, then run the retro at the end of your cycle.
<task>Set up goals / OKRs in Notion</task> <horizon>[annual / quarterly]</horizon> <output> 1. Goals DB with parent-child structure 2. Key results as children 3. Weekly check-in updating progress % 4. Dashboard per season 5. Retrospective template </output>
Pro tip: OKRs fail when reviewed quarterly. Notion makes weekly check-ins trivial — 10 min per week is the entire secret to OKRs actually working.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. The library keeps growing.
Advanced
5 promptsNotion AI Workflow Design
16/20✨ What it does
Claude designs Notion AI usage for the pain points you [describe], with commands to try, what to keep manual, AI blocks in templates, when to use Claude or ChatGPT instead, and guardrails. Use one command on a real page, then leave the sloppy drafts off your published pages.
<task>Design Notion AI usage</task> <pain_points>[describe]</pain_points> <output> 1. Specific Notion AI commands per pain 2. What stays manual (AI slop worse than human) 3. AI blocks in templates 4. Notion AI vs Claude vs ChatGPT for different tasks 5. Guardrails </output>
Pro tip: Notion AI is best for context-aware work (summarizing, rewriting). For strategic/creative work, Claude and ChatGPT still win. Pick tools by strength.
Public Notion Site
17/20✨ What it does
Claude plans publishing a Notion page as a public site for the purpose you [describe], comparing native Sites versus Super, Potion, or Feather, plus SEO, domain, limits, and when to leave Notion. Pick the host that fits, then add your domain only after the page looks right.
<task>Publish Notion page as public site</task> <purpose>[describe]</purpose> <output> 1. Native Notion Sites vs third-party (Super/Potion/Feather) 2. SEO considerations 3. Custom domain 4. Design limitations 5. When to migrate off Notion </output>
Pro tip: Notion Sites (official) is now good for simple sites. For heavy customization or high-traffic, migrate to a real CMS — Notion's SEO ceiling is real.
Notion + Calendar Sync
18/20✨ What it does
Claude plans syncing Notion with [Google / Outlook / Apple], covering native options, the Notion Calendar app, Zapier or Make, and which system stays the source of truth. Turn on one direction first, then check a week's events before you two-way sync.
<task>Sync Notion with calendar</task> <calendar>[Google / Outlook / Apple]</calendar> <output> 1. Native integration options 2. Notion Calendar app setup 3. Zapier/Make for complex sync 4. Source-of-truth management </output>
Pro tip: Notion Calendar (standalone app) blends tasks + events. Best Notion feature you're not using. Schedule tasks directly alongside meetings.
Migration Plan (To/From)
19/20✨ What it does
Claude plans a migration [from / to] Notion with export format, import steps, what survives, phases, and a rollback, based on the source and volume you [describe]. Export a sample first, then migrate one section before the rest of your workspace.
<task>Migrate [from / to] Notion</task> <source>[describe]</source> <volume>[describe]</volume> <output> 1. Export format 2. Import approach 3. What preserves vs loses 4. Phased migration plan 5. Rollback plan </output>
Pro tip: Never migrate everything at once. Pick one use case, migrate, use 2 weeks, then migrate next. Big-bang migrations fail because you don't know what to keep.
Habit Tracker Template
20/20✨ What it does
Claude builds a habit tracker from the habits you [list] at [daily / weekly], with checkbox schema, current and longest streaks, a consistency review, progress bars, and a home widget. Check today off, then review consistency at the end of your week.
<task>Build habit tracker</task> <habits>[list]</habits> <frequency>[daily / weekly]</frequency> <output> 1. DB schema with checkboxes 2. Streak formulas (current + longest) 3. Weekly review showing consistency 4. Progress bars 5. Home page widget </output>
Pro tip: Habit trackers fail when daily logging takes >60 seconds. Make it one click. If you can't log during a toothbrush session, the system dies within 3 weeks.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
7-day free trial. Cancel anytime.
Related guides