30 Claude Prompts That Build Notion Templates
Describe the system you need and Claude returns a precise build spec — databases, property types, views, relations, and formulas — ready to recreate in Notion. Prompts for CRMs, project trackers, wikis, habit trackers, content calendars, and OKRs. Not "give me some text".
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly — no signup needed. Hand-curated and tested by the AI Academy team.
CRM & Sales Pipelines
5 promptsSales Pipeline CRM
1/30You are a Notion systems architect who designs revenue-tracking CRMs for small teams. <context> I need a complete, self-contained Notion build spec for a sales-pipeline CRM. The output must be precise enough that I can recreate every database, property, view, and formula in Notion without guessing anything. </context> <inputs> - Business type: [WHAT I SELL] - Pipeline stages: [E.G. LEAD, QUALIFIED, PROPOSAL, WON, LOST] - Team size using it: [SOLO / SMALL TEAM] - Average deal size and cycle: [AMOUNT AND WEEKS] - Key fields I care about: [SOURCE, OWNER, NEXT STEP, ETC.] </inputs> <task> Specify a Deals database and a linked Contacts database. For each database give a properties table with columns: Property name, Notion type (Title, Select, Status, Number, Date, Person, Relation, Rollup, Formula, etc.), and purpose. Include a Relation from Deals to Contacts, a Rollup pulling the contact company, a Formula for weighted deal value (probability by stage), and a Formula flagging stale deals with no activity in 14 days. Then define these views with their filters, sorts, and grouping: a Board grouped by stage, a Table of open deals sorted by close date, and a filtered "Needs follow-up" view. </task> <constraints> - Use only real Notion property types and valid Notion formula syntax (prop(), if(), dateBetween(), now()). - Every property must have a stated type; no vague "custom field". - No filler rows — only fields a real pipeline uses. </constraints> <format> Return the spec as markdown tables (one per database) plus a views list, then a numbered build order and one note on how to extend it with a Kanban automation button. </format>
Produces a full sales-pipeline CRM build spec with deal/contact databases, weighted-value and stale-deal formulas, and pipeline views, ready to use.
Pro tip: Give Claude your real stage-by-stage win probabilities so the weighted-value formula forecasts revenue you can trust.
Contacts & Companies Database
2/30You are a Notion data-modeling expert who builds relational contact systems. <context> I want a self-contained Notion build spec for a two-database people-and-companies system that other databases (deals, projects) can relate to. It must be recreatable field-by-field with no ambiguity. </context> <inputs> - Who I track: [CLIENTS / LEADS / PARTNERS] - Contact details I need: [EMAIL, PHONE, ROLE, LINKEDIN, ETC.] - Company details I need: [INDUSTRY, SIZE, WEBSITE, TIER] - How I segment people: [E.G. VIP, COLD, ACTIVE] </inputs> <task> Define a Contacts database and a Companies database. For each, give a properties table (Property, Notion type, purpose) covering identity, contact fields (Email/Phone/URL types), a Select or Status for segment, and a Person owner. Add a Relation linking each Contact to one Company, a Rollup on Companies counting related contacts, and a Formula on Contacts building a clean display label like "Name — Role @ Company". Then define a Table view grouped by segment, a Gallery view of companies, and a filtered "My contacts" view for the current user. </task> <constraints> - Use correct property types: Email, Phone, URL, Person, Relation, Rollup, Formula. - Formula must be valid Notion syntax and handle empty fields gracefully. - No duplicate free-text fields where a Select or Relation is correct. </constraints> <format> Return two markdown property tables plus a views list, then a short note on which other databases should relate in. </format>
Generates a relational contacts-and-companies Notion spec with correct field types, a display-label formula, and segment views, ready to use.
Pro tip: Ask Claude to make Company the single source of truth so tier and industry roll down to every contact automatically.
Deal Forecast & Commission Tracker
3/30You are a Notion revenue-operations analyst who builds forecasting dashboards. <context> I need a self-contained Notion build spec for a deal forecast and commission tracker that turns won deals into projected revenue and rep payouts. It must be precise enough to rebuild without guessing formulas. </context> <inputs> - Sales reps and commission rate: [NAMES AND PERCENTAGES] - Deal stages and probabilities: [STAGE: %] - Forecast period: [MONTH / QUARTER] - What counts as booked revenue: [SIGNED / PAID] </inputs> <task> Specify a Deals database with properties (Property, Notion type, purpose) for amount, stage, probability, rep (Person), and close date. Add these Formulas in valid Notion syntax: weighted forecast (amount times probability), commission owed (amount times rep rate, only when Status is Won), a quarter label derived from the close date, and a days-to-close countdown. Add a Rollup-driven summary via a linked Reps database that sums each rep's commission. Then define a Table view grouped by rep with a commission sum, a Board grouped by forecast quarter, and a Calendar view by close date. </task> <constraints> - All formulas must be valid Notion formula syntax (prop, if, dateBetween, formatDate). - Commission must only apply to Won deals; handle other statuses as 0. - State every property type explicitly. </constraints> <format> Return markdown property tables, each formula in its own labeled code block, a views list, then a note on connecting a Reps rollup summary. </format>
Delivers a Notion forecast-and-commission spec with weighted-pipeline, commission, and countdown formulas plus rep rollups, ready to use.
Pro tip: Feed Claude your exact commission tiers so it writes a nested if() ladder instead of a flat single rate.
Customer Onboarding CRM
4/30You are a Notion customer-success architect who designs onboarding trackers. <context> I want a self-contained Notion build spec for a customer onboarding CRM that moves each new customer through a repeatable onboarding checklist and flags stalls. It must be fully recreatable. </context> <inputs> - Product: [WHAT CUSTOMERS ONBOARD ONTO] - Onboarding steps: [E.G. KICKOFF, SETUP, TRAINING, GO-LIVE] - Target onboarding length: [DAYS] - Owner roles: [CSM, ONBOARDING SPECIALIST] </inputs> <task> Specify a Customers database with properties (Property, Notion type, purpose): name, Status through the onboarding stages, start date, target go-live date, CSM (Person), and health Select. Add a Formula computing days since start, a Formula for on-track vs at-risk based on stage versus elapsed days, and a Formula for percent-complete from a checklist. Include a related Onboarding Tasks database with a Relation back to Customers and a Rollup showing completed-of-total tasks. Then define a Board grouped by onboarding stage, a filtered "At risk" view, and a Timeline view by start-to-go-live. </task> <constraints> - Use Status and Select types correctly and valid Notion formula syntax. - The at-risk logic must compare elapsed time against the target length. - Include a database template for a new customer with the standard tasks prefilled. </constraints> <format> Return markdown property tables, formulas in code blocks, a views list, and the new-customer template contents, then a build order. </format>
Builds a customer-onboarding CRM spec with stage tracking, at-risk and percent-complete formulas, and a prefilled new-customer template, ready to use.
Pro tip: Tell Claude your true target onboarding length so the at-risk formula fires before customers actually churn.
Investor / Fundraising CRM
5/30You are a Notion fundraising-operations specialist who builds investor pipelines for founders. <context> I am raising a round and need a self-contained Notion build spec for an investor CRM that tracks every conversation from intro to committed. It must be recreatable field-by-field. </context> <inputs> - Round and target: [E.G. SEED, $1.5M] - Investor stages: [E.G. TO CONTACT, INTRO'D, MEETING, DILIGENCE, COMMITTED, PASSED] - Fields I track: [FUND, CHECK SIZE, WARM INTRO SOURCE, NEXT STEP] - Close target date: [DATE] </inputs> <task> Specify an Investors database with properties (Property, Notion type, purpose): name, fund, Status through the stages, potential check size (Number), warm-intro source, next step, next-touch Date, and owner. Add a Formula summing committed dollars vs target as percent, a Formula flagging investors overdue for a follow-up (next-touch in the past), and a Formula estimating weighted commitment by stage probability. Add a related Interactions log database with a Relation to Investors and a Rollup of last contact date. Then define a Board grouped by stage, a "Follow up now" filtered view, and a Table sorted by check size. </task> <constraints> - Valid Notion formula syntax only; handle empty amounts as 0. - Percent-to-target must reference the round target. - State every property type; no free-text where a Status fits. </constraints> <format> Return markdown property tables, formulas in code blocks, a views list, then a note on a weekly-raise summary view. </format>
Generates an investor-fundraising CRM spec with stage pipeline, percent-to-target, overdue-follow-up, and weighted-commitment formulas, ready to use.
Pro tip: Give Claude your commit probability per stage so the weighted-commitment number reflects a realistic close, not the full pipeline.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Project & Task Management
5 promptsTeam Task Board (Kanban)
6/30You are a Notion workflow designer who builds team task systems. <context> I need a self-contained Notion build spec for a team task board that a small team can run their week from. It must be recreatable with exact property types, views, and formulas. </context> <inputs> - Team and function: [E.G. 5-PERSON MARKETING TEAM] - Task statuses: [E.G. BACKLOG, TODO, IN PROGRESS, REVIEW, DONE] - Priority scheme: [P1-P3 OR HIGH/MED/LOW] - Fields I need: [ASSIGNEE, DUE DATE, PROJECT, EFFORT] </inputs> <task> Specify a Tasks database with a properties table (Property, Notion type, purpose): title, Status, assignee (Person), due Date, priority Select, effort Number, and a project Relation. Add a Formula for an urgency score combining priority and days-to-due, a Formula labeling overdue tasks, and a Formula for a friendly due-in string. Then define views with filters, sorts, and grouping: a Board grouped by Status, a "My tasks this week" filtered by current user and due date, a Calendar by due date, and a Table grouped by assignee. Include a task database template with default subtask checklist. </task> <constraints> - Use Status and Person types correctly; valid Notion formula syntax. - The urgency formula must combine priority and due-date proximity. - No columns the team would never fill in. </constraints> <format> Return the properties table, formulas in code blocks, a views list, the task template contents, then a numbered build order. </format>
Delivers a team Kanban task-board spec with urgency and overdue formulas, personal and calendar views, and a task template, ready to use.
Pro tip: Ask Claude to weight the urgency formula so P1 always outranks a soon-due P3 in the sort.
Agile Sprint Board
7/30You are a Notion agile-delivery consultant who builds sprint systems for product teams. <context> I need a self-contained Notion build spec for an agile sprint board with sprints, stories, and points. It must be precise enough to rebuild without inventing property types. </context> <inputs> - Sprint length: [E.G. 2 WEEKS] - Story workflow: [E.G. BACKLOG, TODO, DOING, REVIEW, DONE] - Estimation unit: [STORY POINTS / HOURS] - Roles: [PO, DEV, QA] </inputs> <task> Specify a Sprints database and a Stories database. Stories properties (Property, Notion type, purpose): title, Status, points Number, assignee (Person), a Relation to a Sprint, and a Select for type (feature/bug/chore). Add Formulas: completed-points ratio per story, a boolean for carry-over (not done when sprint ends), and a cycle-time in days from start to done. On Sprints, add Rollups summing planned points and completed points, plus a Formula for velocity. Then define a Board grouped by Status filtered to the active sprint, a Table grouped by assignee with a points sum, and a sprint-review Gallery. </task> <constraints> - Valid Notion formula and Rollup configuration; state which Rollup aggregates which relation. - Carry-over logic must compare done status against sprint end date. - Only real agile fields; no filler. </constraints> <format> Return two property tables, formulas and rollups in code blocks, a views list, then a note on running a burndown-style summary. </format>
Produces an agile sprint-board spec with sprint/story databases, velocity and cycle-time formulas, point rollups, and sprint views, ready to use.
Pro tip: Tell Claude your definition of done so the carry-over and completed-points formulas count exactly what your team counts.
Client Project Tracker
8/30You are a Notion operations lead who builds agency project-delivery systems. <context> I run client projects and need a self-contained Notion build spec linking clients, projects, and tasks with budget tracking. It must be fully recreatable. </context> <inputs> - Service I deliver: [E.G. DESIGN, DEV, CONSULTING] - Project phases: [E.G. DISCOVERY, BUILD, LAUNCH] - Billing model: [FIXED FEE / HOURLY] - Fields I track: [BUDGET, HOURS, OWNER, DEADLINE] </inputs> <task> Specify three related databases: Clients, Projects, and Tasks. Give each a properties table (Property, Notion type, purpose). Projects relate to a Client; Tasks relate to a Project and to an owner (Person). Add a Rollup on Projects summing logged hours and completed tasks, a Formula for budget-used percentage, a Formula flagging over-budget projects, and a Formula for days until deadline. Then define a Board grouped by phase, a Table of active projects sorted by deadline, a per-client Gallery, and a "Tasks due this week" filtered view. </task> <constraints> - Correct Relation and Rollup wiring across all three databases, stated explicitly. - Valid Notion formula syntax; handle zero-budget projects without dividing by zero. - No orphan properties duplicated across databases. </constraints> <format> Return three property tables, the relation map, formulas in code blocks, a views list, then a build order. </format>
Generates a three-database client-project tracker spec with client-project-task relations, budget-used and over-budget formulas, and views, ready to use.
Pro tip: Have Claude add a rollup that surfaces each client's total lifetime billings straight on the Clients database.
Product Roadmap
9/30You are a Notion product-operations designer who builds roadmaps for product teams. <context> I need a self-contained Notion build spec for a product roadmap that links initiatives, features, and quarters, with a prioritization score. It must be recreatable field-by-field. </context> <inputs> - Product area: [WHAT WE BUILD] - Time horizon: [E.G. NOW / NEXT / LATER OR QUARTERS] - Prioritization inputs: [REACH, IMPACT, CONFIDENCE, EFFORT] - Statuses: [IDEA, PLANNED, BUILDING, SHIPPED] </inputs> <task> Specify a Features database with properties (Property, Notion type, purpose): title, Status, a Select or Relation for the target quarter/horizon, owner (Person), and Number fields for reach, impact, confidence, and effort. Add a Formula computing a RICE score, a Formula bucketing the score into High/Medium/Low, and a Formula for a shipped-this-quarter flag. Add a related Initiatives database with a Relation to Features and a Rollup counting shipped features. Then define a Board grouped by horizon, a Table sorted by RICE score descending, and a Timeline by target quarter. </task> <constraints> - RICE formula must be valid Notion syntax and guard against effort of 0. - State every property type; horizon should be one consistent field. - No vague priority text where the computed score belongs. </constraints> <format> Return the property tables, the RICE and bucket formulas in code blocks, a views list, then a note on a stakeholder-facing read-only view. </format>
Builds a product-roadmap spec with feature/initiative databases, a RICE prioritization formula, horizon views, and shipped rollups, ready to use.
Pro tip: Ask Claude to expose the RICE score as a Bar formula so priority is visually obvious in the table without opening each card.
Meeting Notes & Action Items
10/30You are a Notion knowledge-systems designer who builds meeting-management hubs. <context> I need a self-contained Notion build spec for a meetings hub where notes automatically surface open action items across the team. It must be fully recreatable. </context> <inputs> - Meeting types: [E.G. STANDUP, 1:1, CLIENT, ALL-HANDS] - Who attends: [TEAM OR ROLES] - What I track per meeting: [DATE, ATTENDEES, DECISIONS, TOPICS] - How action items are assigned: [PERSON AND DUE DATE] </inputs> <task> Specify a Meetings database and an Action Items database. Meetings properties (Property, Notion type, purpose): title, date, type Select, attendees (Person, multiple), and a Relation to Action Items. Action Items properties: task, owner (Person), due Date, Status, and a Relation back to the meeting. Add a Rollup on Meetings counting open action items, a Formula flagging overdue action items, and a Formula for a next-meeting reminder string. Then define a Calendar view of meetings, a filtered "Open action items assigned to me" view, and a Table of meetings grouped by type. Include a meeting page template with Agenda, Notes, Decisions, and Action Items headings. </task> <constraints> - Valid Notion property types and formula syntax; overdue must compare due date to now(). - The action-item relation must be bidirectional and stated clearly. - Template must be concrete, not placeholder-only. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the meeting template contents, then a build order. </format>
Delivers a meetings-hub spec with linked notes and action-items databases, overdue flags, open-item rollups, and a meeting template, ready to use.
Pro tip: Tell Claude to make the action-items view group by owner so each teammate opens one filtered list after every meeting.
Wiki & Knowledge Base
5 promptsCompany Wiki / Handbook
11/30You are a Notion knowledge-architecture expert who builds company wikis. <context> I need a self-contained Notion build spec for a company wiki and handbook that stays organized and searchable as the team grows. It must be recreatable with exact databases, properties, and views. </context> <inputs> - Company size and type: [E.G. 20-PERSON SAAS] - Wiki sections I need: [E.G. POLICIES, TOOLS, PEOPLE, PROCESSES] - Who owns content: [DEPARTMENTS OR ROLES] - Review cadence: [E.G. QUARTERLY] </inputs> <task> Specify a Wiki Pages database with properties (Property, Notion type, purpose): title, category Select, owner (Person), Status (draft/published/needs-review), last-reviewed Date, and tags Multi-select. Add a Formula flagging pages overdue for review (past cadence since last-reviewed), and a Formula for a freshness label. Include a related Departments database with a Relation and a Rollup counting each department's pages. Then define views: a Gallery grouped by category, a "Needs review" filtered view, a Table by owner, and a search-friendly List. Provide a wiki-page template with Summary, Details, Owner, and Related-links sections. </task> <constraints> - Valid Notion property types and formula syntax; review-overdue must use dateBetween or dateAdd. - Category and tags must be structured fields, not free text. - Template must model a real published page. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the page template contents, then a build order. </format>
Builds a company-wiki spec with a categorized pages database, review-overdue and freshness formulas, department rollups, and a page template, ready to use.
Pro tip: Set the review cadence in the input so the overdue formula quietly nudges owners before content goes stale.
Engineering Runbook & Docs
12/30You are a Notion documentation architect who builds engineering knowledge bases. <context> I need a self-contained Notion build spec for an engineering docs and runbook system covering services, incidents, and how-tos. It must be recreatable field-by-field. </context> <inputs> - Stack and services: [E.G. API, WEB, WORKERS, DB] - Doc types: [RUNBOOK, ARCHITECTURE, HOW-TO, POSTMORTEM] - Severity levels for incidents: [SEV1-SEV3] - Owners: [TEAMS OR ENGINEERS] </inputs> <task> Specify a Docs database and an Incidents database. Docs properties (Property, Notion type, purpose): title, doc-type Select, owning service Relation, owner (Person), Status, and last-updated Date. Incidents properties: title, severity Select, affected service Relation, date, and a Relation to the relevant runbook Doc. Add a Rollup on services counting linked docs, a Formula flagging docs not updated in 90 days, and a Formula for incident MTTR from opened/closed timestamps. Then define a Gallery grouped by doc type, a filtered "Runbooks" view, an Incidents Table sorted by severity, and a "Stale docs" view. Include a runbook page template with Symptoms, Diagnosis, Fix, and Rollback sections. </task> <constraints> - Valid Notion formula syntax; MTTR must use dateBetween on real timestamps. - Services must be a shared relation across both databases. - Template must be a usable runbook skeleton. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the runbook template, then a build order. </format>
Generates an engineering runbook-and-docs spec with docs/incidents databases, stale-doc and MTTR formulas, service relations, and a runbook template, ready to use.
Pro tip: Have Claude relate incidents to the exact runbook that resolves them so on-call opens the fix in one click.
SOP Library
13/30You are a Notion operations designer who builds standard-operating-procedure libraries. <context> I need a self-contained Notion build spec for an SOP library that keeps every process documented, owned, and reviewed. It must be recreatable with exact fields and views. </context> <inputs> - Business area: [E.G. OPS, SUPPORT, FINANCE] - Process categories: [E.G. HIRING, BILLING, REFUNDS] - How often SOPs are reviewed: [E.G. EVERY 6 MONTHS] - Who approves SOPs: [ROLE] </inputs> <task> Specify an SOPs database with properties (Property, Notion type, purpose): title, category Select, owner (Person), approver (Person), Status (draft/in-review/approved), version Number, last-reviewed Date, and estimated time Number. Add a Formula for a review-due flag based on the cadence, a Formula for a version label, and a Formula bucketing SOPs by time-to-complete. Add a related Roles database with a Relation and a Rollup counting SOPs per role. Then define a Gallery grouped by category, an "Approved only" filtered view, a "Due for review" view, and a Table by owner. Provide an SOP page template with Purpose, Trigger, Steps, and Checklist sections. </task> <constraints> - Valid Notion property types and formula syntax; review-due uses the input cadence. - Version and status must be structured, not free text. - Template steps must be numbered and concrete. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the SOP template contents, then a build order. </format>
Delivers an SOP-library spec with a categorized process database, review-due and versioning formulas, role rollups, and an SOP template, ready to use.
Pro tip: Ask Claude to add a checkbox-driven percent-complete formula so half-written SOPs are visible at a glance.
New-Hire Onboarding Knowledge Base
14/30You are a Notion people-operations architect who builds onboarding knowledge bases. <context> I need a self-contained Notion build spec for a new-hire knowledge base that guides a new employee through their first 30/60/90 days. It must be recreatable field-by-field. </context> <inputs> - Role types onboarding: [E.G. ENGINEER, SALES, SUPPORT] - Onboarding milestones: [DAY 1, WEEK 1, 30/60/90] - Resources new hires need: [TOOLS, POLICIES, CONTACTS] - Buddy/manager assignment: [YES/NO] </inputs> <task> Specify an Onboarding Tasks database and a Resources database. Tasks properties (Property, Notion type, purpose): task, milestone Select (Day 1/Week 1/30/60/90), owner-role Select, assignee (Person), Status, and a Relation to Resources. Add a Formula for percent-complete per milestone, a Formula flagging overdue onboarding tasks against the hire's start date, and a Formula for a days-since-start counter. Add a Rollup counting completed tasks. Then define a Board grouped by milestone, a "My onboarding" filtered view by current user, and a Resources Gallery grouped by type. Provide a new-hire hub page template linking each milestone section. </task> <constraints> - Valid Notion formula syntax; overdue must reference the start date, not now() alone. - Milestones must be a consistent Select used everywhere. - Template must be a usable hub, not placeholder text. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the hub template contents, then a build order. </format>
Builds a new-hire knowledge-base spec with milestone tasks and resources databases, percent-complete and overdue formulas, and a hub template, ready to use.
Pro tip: Feed Claude a real start date field so every onboarding deadline is computed relative to the hire, not hardcoded.
Personal Second Brain (PARA)
15/30You are a Notion personal-knowledge-management coach who builds PARA-style second brains. <context> I want a self-contained Notion build spec for a personal second brain using the PARA method (Projects, Areas, Resources, Archive) with connected notes. It must be recreatable field-by-field. </context> <inputs> - Main areas of my life/work: [E.G. WORK, HEALTH, FINANCE, LEARNING] - What I capture: [NOTES, ARTICLES, IDEAS, TASKS] - How I want to review: [WEEKLY / MONTHLY] - Devices I capture on: [MOBILE / DESKTOP] </inputs> <task> Specify four related databases: Projects, Areas, Resources, and Notes. Give each a properties table (Property, Notion type, purpose). Notes relate to a Project, an Area, or a Resource; Projects relate to an Area. Add a Rollup on Areas counting active projects, a Formula for a project Status derived from linked task completion, a Formula flagging stale notes untouched in 30 days, and a Formula for a review-priority score. Then define a Board of projects grouped by Area, an "Inbox" filtered view for uncategorized notes, an Archive filtered view, and a weekly-review dashboard List. Provide a quick-capture note template. </task> <constraints> - Valid Notion Relation and Rollup wiring across all four databases, stated explicitly. - Formulas must be valid Notion syntax; stale-note logic uses last-edited time. - Keep capture friction low; the note template must be minimal. </constraints> <format> Return four property tables, the relation map, formulas in code blocks, a views list, the capture template, then a build order. </format>
Generates a PARA second-brain spec with four linked databases, stale-note and review-priority formulas, an inbox view, and a capture template, ready to use.
Pro tip: Ask Claude to add a single "Inbox" filter so anything you capture on mobile without tags surfaces for triage later.
Habit & Goal Tracker
5 promptsDaily Habit Tracker
16/30You are a Notion habit-design specialist who builds streak-based trackers. <context> I need a self-contained Notion build spec for a daily habit tracker that logs each day, computes streaks, and shows completion rates. It must be recreatable with exact fields and formulas. </context> <inputs> - Habits I track: [E.G. WORKOUT, READ, NO SUGAR] - How I log: [ONE ROW PER DAY / ONE ROW PER HABIT-DAY] - Goal frequency: [E.G. DAILY, 5X/WEEK] - Review period: [WEEKLY / MONTHLY] </inputs> <task> Specify a Daily Log database with properties (Property, Notion type, purpose): date, a Checkbox per habit (or a Multi-select of completed habits), a Number for habits completed, and Text for notes. Add a Formula computing the completion percentage for the day, a Formula for a week label from the date, and a Formula rating the day. Add a related Habits database with a Relation and Rollups for each habit's completion count and current-period rate. Then define a Calendar view by date, a Table grouped by week with a completion average, and a "Missed today" filtered view. Include a daily-log database template that prefills today's date. </task> <constraints> - Valid Notion formula syntax; percentages must not divide by zero. - Explain how the streak/rate rollup is aggregated. - Keep daily logging to one quick entry. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the daily template, then a build order. </format>
Delivers a daily habit-tracker spec with a log database, completion-rate and week-label formulas, habit rollups, and a today template, ready to use.
Pro tip: Tell Claude your target frequency per habit so the rollup rate compares against the goal, not a flat 100 percent.
Annual Goals & Quarterly Milestones
17/30You are a Notion goal-systems designer who builds annual planning trackers. <context> I need a self-contained Notion build spec that connects annual goals to quarterly milestones and weekly actions, with rolled-up progress. It must be recreatable field-by-field. </context> <inputs> - Life/work domains: [E.G. CAREER, HEALTH, FINANCE] - Number of annual goals: [HOW MANY] - How I measure progress: [PERCENT / TARGET NUMBER] - Review cadence: [WEEKLY / MONTHLY] </inputs> <task> Specify three related databases: Goals, Milestones, and Actions. Give each a properties table (Property, Notion type, purpose). Milestones relate to a Goal; Actions relate to a Milestone. Add a Rollup on Goals averaging milestone progress, a Formula for percent-to-target on numeric goals, a Formula for an on-track flag comparing progress against the elapsed year, and a Formula for days-remaining in the year. Then define a Board of goals grouped by domain, a Timeline of milestones by quarter, a "This week's actions" filtered view, and a Table of goals sorted by progress. Include a goal page template with Why, Target, Milestones, and Review sections. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - On-track logic must compare progress to time elapsed in the year. - Numeric progress must avoid division by zero. </constraints> <format> Return three property tables, the relation map, formulas in code blocks, a views list, the goal template, then a build order. </format>
Builds an annual-goals spec with goals-milestones-actions databases, percent-to-target and on-track formulas, and a goal template, ready to use.
Pro tip: Have Claude compute the on-track flag from time elapsed so a goal at 40 percent in Q3 correctly shows as behind.
Workout & Fitness Tracker
18/30You are a Notion fitness-tracking designer who builds training logs. <context> I need a self-contained Notion build spec for a workout tracker that logs sessions, exercises, and volume with progress trends. It must be recreatable field-by-field. </context> <inputs> - Training type: [E.G. STRENGTH, RUNNING, HYBRID] - What I log per session: [EXERCISE, SETS, REPS, WEIGHT, DURATION] - Weekly target: [E.G. 4 SESSIONS] - Metrics I care about: [VOLUME, PRs, CONSISTENCY] </inputs> <task> Specify a Workouts database and an Exercises database. Workouts properties (Property, Notion type, purpose): date, type Select, duration Number, notes, and a Relation to Exercise-set entries. Set entries include exercise Relation, sets, reps, and weight (Numbers). Add a Formula for total volume (sets times reps times weight), a Formula for a week label, a Formula flagging a personal record versus prior max, and a Rollup summing weekly session count. Then define a Calendar view by date, a Table grouped by week with a session count, and a per-exercise Gallery showing best set. Include a workout database template prefilling the day's planned exercises. </task> <constraints> - Valid Notion formula syntax; volume must handle blank fields as 0. - Explain how the PR comparison references prior entries. - Only fields a lifter actually logs. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the workout template, then a build order. </format>
Generates a workout-tracker spec with workouts and exercises databases, volume and PR formulas, weekly session rollups, and a session template, ready to use.
Pro tip: Ask Claude to add a rolling weekly-volume rollup so you can spot when you are ramping load too fast.
Reading & Learning Tracker
19/30You are a Notion learning-systems designer who builds reading and study trackers. <context> I need a self-contained Notion build spec for a reading and learning tracker covering books, courses, and notes with progress and yearly goals. It must be recreatable field-by-field. </context> <inputs> - What I track: [BOOKS, COURSES, ARTICLES] - Yearly goal: [E.G. 24 BOOKS] - Fields per item: [AUTHOR, PAGES, STATUS, RATING, TOPIC] - How I take notes: [HIGHLIGHTS / SUMMARY] </inputs> <task> Specify a Library database and a Notes database. Library properties (Property, Notion type, purpose): title, type Select, author, total pages Number, pages-read Number, Status (to-read/reading/done), rating Select, topic Multi-select, finished Date, and a Relation to Notes. Add a Formula for percent-read, a Formula for a completed-this-year flag, a Formula estimating days-to-finish at current pace, and a Rollup counting notes per item. Then define a Gallery grouped by Status, a "Reading now" filtered view, a Table of finished items this year, and a topic-based List. Include a book page template with Summary, Key ideas, and Quotes sections. </task> <constraints> - Valid Notion formula syntax; percent-read must guard against 0 total pages. - Yearly-goal progress should be shown via a view or count, not free text. - Template must be a usable note structure. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the book template, then a build order. </format>
Delivers a reading-and-learning tracker spec with library and notes databases, percent-read and pace formulas, note rollups, and a book template, ready to use.
Pro tip: Give Claude your yearly reading goal so a filtered "finished this year" view doubles as a progress bar toward it.
Personal Budget & Finance Tracker
20/30You are a Notion personal-finance designer who builds budgeting systems. <context> I need a self-contained Notion build spec for a personal budget tracker that logs transactions, groups them by category, and compares spend against monthly budgets. It must be recreatable field-by-field. </context> <inputs> - Income sources: [E.G. SALARY, SIDE INCOME] - Spending categories: [E.G. RENT, FOOD, TRANSPORT, FUN] - Monthly budget per category: [AMOUNTS] - Currency: [E.G. USD] </inputs> <task> Specify a Transactions database and a Categories database. Transactions properties (Property, Notion type, purpose): description, amount Number, type Select (income/expense), date, and a Relation to a Category. Categories properties: name, monthly budget Number, and Rollups summing this month's spend from related transactions. Add a Formula for a month label from the transaction date, a Formula on Categories for budget-remaining and percent-used, and a Formula flagging over-budget categories. Then define a Table grouped by category with spend sums, a Calendar of transactions, a "This month" filtered view, and a Board of categories grouped by over/under budget. Include a quick-add transaction template. </task> <constraints> - Valid Notion formula syntax; percent-used must guard against a 0 budget. - Rollups must filter to the current month; state how. - Only fields a real budget needs. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the transaction template, then a build order. </format>
Builds a personal-budget spec with transactions and categories databases, month-label and budget-remaining formulas, spend rollups, and a quick-add template, ready to use.
Pro tip: Tell Claude your real monthly budgets so the over-budget flag turns categories red the moment you overspend.
Content Calendar
5 promptsSocial Media Content Calendar
21/30You are a Notion content-operations designer who builds social media calendars. <context> I need a self-contained Notion build spec for a social media content calendar covering multiple platforms with a clear approval workflow. It must be recreatable field-by-field. </context> <inputs> - Platforms: [E.G. LINKEDIN, INSTAGRAM, X, TIKTOK] - Content types: [E.G. POST, REEL, CAROUSEL, STORY] - Workflow stages: [IDEA, DRAFT, REVIEW, SCHEDULED, PUBLISHED] - Posting cadence: [E.G. 5X/WEEK] </inputs> <task> Specify a Posts database with properties (Property, Notion type, purpose): title, platform Multi-select, content-type Select, Status, publish Date, owner (Person), Files for assets, and Text for the caption/hook. Add a Formula for a week label, a Formula flagging posts due to publish in the next 3 days that are not yet ready, and a Formula for a days-until-publish countdown. Add a related Campaigns database with a Relation and a Rollup counting posts per campaign. Then define a Calendar view by publish date, a Board grouped by Status, a per-platform filtered view, and a "Publishing this week" Table. Include a post database template prefilling the standard fields per platform. </task> <constraints> - Valid Notion property types and formula syntax; the readiness flag compares Status to the publish date. - Platform must be a shared field usable in filters. - Template must be usable, not placeholder-only. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the post template, then a build order. </format>
Generates a social-media content-calendar spec with a posts database, readiness and countdown formulas, campaign rollups, and a post template, ready to use.
Pro tip: Ask Claude to add a per-platform Board so each channel owner sees only their queue without touching filters.
Editorial / Blog Calendar
22/30You are a Notion editorial-operations designer who builds blog content pipelines. <context> I need a self-contained Notion build spec for an editorial blog calendar that moves articles from idea to published, tracks SEO targets, and connects writers. It must be recreatable field-by-field. </context> <inputs> - Content types: [E.G. HOW-TO, LISTICLE, CASE STUDY] - Workflow stages: [IDEA, OUTLINE, DRAFT, EDIT, PUBLISHED] - SEO fields I track: [TARGET KEYWORD, SEARCH VOLUME, WORD COUNT] - Publishing cadence: [E.G. 2 POSTS/WEEK] </inputs> <task> Specify an Articles database with properties (Property, Notion type, purpose): title, Status, type Select, target keyword, search volume Number, target word count Number, writer (Person), editor (Person), and publish Date. Add a Formula for a days-to-deadline countdown, a Formula flagging drafts overdue for their stage, and a Formula for a content-priority score from volume and effort. Add a related Topics/Clusters database with a Relation and a Rollup counting articles per cluster. Then define a Calendar by publish date, a Board grouped by Status, a Table sorted by priority score, and a per-writer filtered view. Include an article page template with Brief, Outline, Draft, and SEO-checklist sections. </task> <constraints> - Valid Notion formula syntax; priority must guard against 0 effort. - Status and type must be structured selects used across views. - Template must be a usable content brief. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the article template, then a build order. </format>
Delivers an editorial-calendar spec with an articles database, deadline and priority-score formulas, cluster rollups, and a content-brief template, ready to use.
Pro tip: Feed Claude your keyword volumes so the priority score pushes high-opportunity posts to the top of the queue.
YouTube / Video Production Pipeline
23/30You are a Notion video-operations designer who builds production pipelines for creators. <context> I need a self-contained Notion build spec for a YouTube production pipeline covering scripting, filming, editing, and publishing, with per-stage owners. It must be recreatable field-by-field. </context> <inputs> - Channel niche: [WHAT THE CHANNEL COVERS] - Production stages: [IDEA, SCRIPT, FILM, EDIT, THUMBNAIL, PUBLISH] - Team roles: [E.G. SCRIPTWRITER, EDITOR, DESIGNER] - Upload cadence: [E.G. 1 VIDEO/WEEK] </inputs> <task> Specify a Videos database with properties (Property, Notion type, purpose): title, Status through the production stages, format Select, script owner (Person), editor (Person), publish Date, Files for assets, and a Number for target length. Add a Formula for a days-to-publish countdown, a Formula flagging videos behind schedule for their stage, and a Formula for a production-health label. Add a related Ideas backlog database with a Relation and a Rollup counting ideas promoted to production. Then define a Board grouped by production stage, a Calendar by publish date, a per-role filtered view, and a "Behind schedule" Table. Include a video page template with Hook, Script, Shot list, and Description sections. </task> <constraints> - Valid Notion property types and formula syntax; behind-schedule compares stage to publish date. - Stages must be a single Status used everywhere. - Template must be a usable production doc. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the video template, then a build order. </format>
Builds a YouTube production-pipeline spec with a videos database, countdown and behind-schedule formulas, idea rollups, and a video template, ready to use.
Pro tip: Ask Claude to give each stage owner a filtered board so the editor and scriptwriter never wade through each other's queue.
Newsletter Planning Calendar
24/30You are a Notion newsletter-operations designer who builds issue-planning systems. <context> I need a self-contained Notion build spec for a newsletter planning calendar that plans issues, tracks segments and performance, and reuses an issue template. It must be recreatable field-by-field. </context> <inputs> - Newsletter cadence: [E.G. WEEKLY] - Issue sections: [E.G. INTRO, MAIN STORY, LINKS, SPONSOR] - Metrics I track: [OPEN RATE, CLICK RATE, SUBSCRIBERS] - Who writes and reviews: [ROLES] </inputs> <task> Specify an Issues database with properties (Property, Notion type, purpose): title, send Date, Status (planned/drafting/scheduled/sent), theme Select, writer (Person), subject line Text, and Number fields for open rate, click rate, and subscribers. Add a Formula for a days-until-send countdown, a Formula flagging issues not ready 2 days before send, and a Formula comparing open rate to a rolling target. Add a related Story Ideas database with a Relation and a Rollup counting ideas used per issue. Then define a Calendar by send date, a Board grouped by Status, a Table of past issues sorted by open rate, and a "Next issue" filtered view. Include an issue page template with the standard sections. </task> <constraints> - Valid Notion formula syntax; readiness flag compares Status to send date. - Metric fields must be Numbers usable in sorts and formulas. - Template sections must match the input. </constraints> <format> Return the property tables, formulas in code blocks, a views list, the issue template, then a build order. </format>
Generates a newsletter-planning spec with an issues database, countdown and readiness formulas, performance fields, idea rollups, and an issue template, ready to use.
Pro tip: Have Claude add an open-rate-vs-target formula so a quick glance shows which subject-line styles are winning.
Marketing Campaign Calendar
25/30You are a Notion marketing-operations designer who builds multi-channel campaign calendars. <context> I need a self-contained Notion build spec for a marketing campaign calendar that coordinates campaigns, their assets across channels, and budgets. It must be recreatable field-by-field. </context> <inputs> - Channels: [E.G. EMAIL, PAID, SOCIAL, EVENTS] - Campaign types: [E.G. LAUNCH, PROMO, WEBINAR] - What I track: [OWNER, BUDGET, START/END, GOAL] - Reporting metric: [LEADS / REVENUE] </inputs> <task> Specify a Campaigns database and an Assets database. Campaigns properties (Property, Notion type, purpose): name, type Select, Status, owner (Person), budget Number, start Date, end Date, goal Number, and a Relation to Assets. Assets properties: title, channel Select, Status, due Date, and a Relation back to the campaign. Add a Formula for campaign duration in days, a Formula flagging campaigns launching in 7 days with unfinished assets, a Rollup counting completed-of-total assets, and a Formula for budget-per-day. Then define a Timeline by start-to-end, a Board of campaigns grouped by Status, an Assets Calendar by due date, and a "Launching soon" filtered view. Include a campaign page template with Brief, Channels, Assets, and Results sections. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - Readiness flag must combine launch proximity with asset completion. - Only fields a real campaign plan needs. </constraints> <format> Return two property tables, the relation map, formulas in code blocks, a views list, the campaign template, then a build order. </format>
Delivers a marketing campaign-calendar spec with campaigns and assets databases, launch-readiness and budget-per-day formulas, asset rollups, and a campaign template, ready to use.
Pro tip: Ask Claude to roll asset completion up to the campaign so a launch can't quietly go live with half its creative missing.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
OKR & Planning
5 promptsCompany OKR System
26/30You are a Notion strategy-operations architect who builds OKR systems for companies. <context> I need a self-contained Notion build spec for a company OKR system linking objectives to measurable key results with automatic progress rollups. It must be recreatable field-by-field. </context> <inputs> - OKR cadence: [QUARTERLY / ANNUAL] - Team structure: [E.G. COMPANY, DEPARTMENT, INDIVIDUAL] - Key-result measurement: [PERCENT / NUMERIC TARGET] - Grading scheme: [0.0-1.0 / RED-AMBER-GREEN] </inputs> <task> Specify an Objectives database and a Key Results database. Objectives properties (Property, Notion type, purpose): title, owner (Person), level Select (company/team/individual), quarter Select, and a Relation to Key Results. Key Results properties: title, start value Number, current value Number, target value Number, and a Relation to the Objective. Add a Formula on Key Results for percent-to-target, a Formula for a RAG status, a Rollup on Objectives averaging key-result progress, and a Formula on Objectives grading them from that average. Then define a Board of objectives grouped by level, a Table of key results sorted by progress, a per-owner filtered view, and a "At risk" view of red key results. Include an objective page template with Why, Key results, and Check-in sections. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - Percent-to-target must handle start-to-target ranges and guard division by zero. - Grading must derive from the rollup, not manual entry. </constraints> <format> Return two property tables, the relation map, formulas in code blocks, a views list, the objective template, then a build order. </format>
Produces a company OKR spec with linked objectives and key-results databases, percent-to-target and RAG formulas, progress rollups, and an objective template, ready to use.
Pro tip: Give Claude your grading scale so the objective auto-grades from key-result progress instead of subjective color-picking.
Quarterly Planning Hub
27/30You are a Notion planning-operations designer who builds quarterly planning hubs. <context> I need a self-contained Notion build spec for a quarterly planning hub connecting themes, initiatives, and tasks with progress tracking. It must be recreatable field-by-field. </context> <inputs> - Planning horizon: [E.G. Q3 2026] - Strategic themes: [3-5 THEMES] - Who owns initiatives: [TEAMS OR PEOPLE] - Success measure: [PERCENT COMPLETE / OUTCOME METRIC] </inputs> <task> Specify three related databases: Themes, Initiatives, and Tasks. Give each a properties table (Property, Notion type, purpose). Initiatives relate to a Theme; Tasks relate to an Initiative and an owner (Person). Add a Rollup on Initiatives for percent of tasks done, a Rollup on Themes averaging initiative progress, a Formula for an on-track flag against elapsed quarter time, and a Formula for days-remaining in the quarter. Then define a Board of initiatives grouped by Theme, a Timeline by initiative start-to-end, a "My tasks this quarter" filtered view, and a Table of themes sorted by progress. Include an initiative page template with Goal, Tasks, Owner, and Status sections. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - On-track logic must compare progress to time elapsed in the quarter. - Only fields a real quarterly plan uses. </constraints> <format> Return three property tables, the relation map, formulas in code blocks, a views list, the initiative template, then a build order. </format>
Builds a quarterly-planning-hub spec with themes-initiatives-tasks databases, on-track and days-remaining formulas, progress rollups, and an initiative template, ready to use.
Pro tip: Ask Claude to bubble theme-level progress to the top so leadership sees the quarter's health without opening every initiative.
Weekly Review & Priorities
28/30You are a Notion productivity-systems designer who builds weekly-review rituals. <context> I need a self-contained Notion build spec for a weekly review and priorities system that connects each week to its top priorities and pulls in open tasks. It must be recreatable field-by-field. </context> <inputs> - What I review weekly: [WINS, MISSES, PRIORITIES, HABITS] - Number of weekly priorities: [E.G. TOP 3] - Areas of focus: [E.G. WORK, HEALTH, RELATIONSHIPS] - Review day: [E.G. SUNDAY] </inputs> <task> Specify a Weeks database and a Priorities database. Weeks properties (Property, Notion type, purpose): week label, start Date, end Date, reflection Text fields (wins/misses/lessons), and a Relation to Priorities. Priorities properties: title, focus-area Select, Status, and a Relation back to the week. Add a Formula generating the week label and date range, a Rollup on Weeks counting completed-of-total priorities, a Formula for a weekly completion percentage, and a Formula flagging the current week. Then define a List of weeks in reverse-chronological order, a "This week's priorities" filtered view, a Board of priorities grouped by focus area, and a Table showing completion trend. Include a weekly-review page template with Reflect, Rate, and Plan sections. </task> <constraints> - Valid Notion formula syntax; the current-week flag must use date ranges around now(). - Priorities must relate cleanly to a single week. - Template must be a usable review ritual, not placeholders. </constraints> <format> Return two property tables, formulas in code blocks, a views list, the review template, then a build order. </format>
Delivers a weekly-review spec with weeks and priorities databases, week-label and completion formulas, priority rollups, and a review template, ready to use.
Pro tip: Tell Claude your review day so the current-week flag opens straight to this week every time you sit down to plan.
Team Capacity & Resource Planner
29/30You are a Notion resource-planning designer who builds team capacity trackers. <context> I need a self-contained Notion build spec for a team capacity planner that shows who is allocated to what and flags overloaded people. It must be recreatable field-by-field. </context> <inputs> - Team members and weekly capacity: [NAMES AND HOURS] - What consumes capacity: [PROJECTS, TASKS, MEETINGS] - Planning window: [WEEK / SPRINT] - Allocation unit: [HOURS / PERCENT] </inputs> <task> Specify a People database and an Allocations database. People properties (Property, Notion type, purpose): name (Person), role Select, weekly capacity Number, and Rollups summing allocated hours. Allocations properties: title, person Relation, project Relation, allocated hours Number, week Date, and Status. Add a Formula on People for utilization percentage (allocated over capacity), a Formula flagging over-allocation above 100 percent, and a Formula for remaining capacity. Then define a Board of allocations grouped by person, a Table of people sorted by utilization, a per-week filtered view, and an "Overloaded" filtered view. Include an allocation database template for quickly assigning a person to a project for a week. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - Utilization must guard against a 0 capacity. - Only fields a real capacity plan needs. </constraints> <format> Return two property tables, the relation map, formulas in code blocks, a views list, the allocation template, then a build order. </format>
Generates a team-capacity-planner spec with people and allocations databases, utilization and over-allocation formulas, hour rollups, and an allocation template, ready to use.
Pro tip: Feed Claude each person's real weekly hours so the overloaded flag catches burnout before the sprint starts.
Annual Business Operating System
30/30You are a Notion business-operations architect who builds annual planning operating systems for founders. <context> I need a self-contained Notion build spec for an annual business operating system that ties the annual vision to quarterly rocks, weekly scorecards, and a meeting cadence. It must be recreatable field-by-field. </context> <inputs> - Business type and stage: [WHAT WE DO, SIZE] - Annual goals: [3-5 GOALS] - Scorecard metrics: [E.G. MRR, LEADS, CHURN] - Meeting cadence: [WEEKLY / MONTHLY / QUARTERLY] </inputs> <task> Specify four related databases: Annual Goals, Quarterly Rocks, Scorecard Metrics, and Meetings. Give each a properties table (Property, Notion type, purpose). Rocks relate to an Annual Goal and an owner (Person); Scorecard Metrics have weekly target and actual Numbers; Meetings relate to Rocks discussed. Add a Rollup on Annual Goals averaging rock progress, a Formula for on-track flags on goals and rocks against elapsed time, a Formula on metrics for target-vs-actual variance with a RAG color, and a Formula for days-remaining in the quarter. Then define a Board of rocks grouped by goal, a Table of scorecard metrics with variance, a Timeline of rocks by quarter, and a meeting Calendar. Include a quarterly-planning page template with Review, Rocks, Metrics, and Next-steps sections. </task> <constraints> - Valid Notion Relation, Rollup, and formula configuration, stated explicitly. - Variance and on-track logic must be computed, not manually colored. - Guard all divisions against zero. </constraints> <format> Return four property tables, the relation map, formulas in code blocks, a views list, the planning template, then a build order. </format>
Builds an annual business-OS spec with four linked databases, on-track and metric-variance formulas, progress rollups, and a quarterly-planning template, ready to use.
Pro tip: Give Claude your real scorecard metrics so the weekly target-vs-actual variance turns red automatically when you miss.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.